Ansible Contributor Summit. Tuesday, April 12, 2022.

[Andersson007]

Ansible Contributor Summit

We are happy to announce that the registration for the Ansible Contributor Summit is open!

Why

• This is a great opportunity for interested people to meet, discuss related topics, share their stories and opinions, get the latest important updates and just to hang out together.

• There will be different announcements & presentations by Community, Core, Cloud, Network, and other teams.

• Current contributors will be happy to share their stories and experience with newcomers.

• There will be links to interactive self-passed instruqt scenarios shared during the event that help newcomers learn different aspects of development.

Where/when

Online on Matrix and Youtube. Tuesday, April 12, 2022, 12:00 - 20:00 UTC.

How to join

• Add the event to your calendar. Use the ical URL (for example, in Google Calendar "Add other calendars" > "Import from URL") instead of importing the .ics file so that any updates to the event will be reflected in your calendar.

• Check out the Summit page:

  • Add you name to attendees.
  • Suggest summit topics that would be interesting to you to hear about.
  • Vote on and propose changes to topics suggested by others.
  • If you want to be a presenter, please contact the Ansible Community team via [email protected].

We are looking forward to seeing you!:)

[MarkusTeufelberger]

I don't like this way of (ab-)using the "Issues" feature on Github as a mailing list by the way. :-/

[Andersson007]

@MarkusTeufelberger thanks for the feedback, much appreciated!
Why we do this is because people subscribed to collection repos can be interested in what's going on in the repos and probably in such events as potential contributors and not only.
Among other things, there will be instruqt courses shared with participants (feedback on them after last Summit was very positive), recently created guidelines (including for newcomers), etc. which really help to get started.
A lack of contributors and maintainers is not the case for community.crypto but it's an issue for many collections.
The Summit takes place 2-3 times a year, so can not interested people, who get a notification about every comment in a repo, survive if they get Summit-related emails once in 4-6 months? Feels pretty rarer but relevant, doesn't it?
If you have any other options, we'd be grateful if you share them with us.
Thank you!

[MarkusTeufelberger]

https://github.com/ansible-collections/news-for-maintainers exists as well as a newsletter ("The Bullhorn") and various other communication channels for these kinds of announcements.

Enduring spam is not necessarily a matter of survivability or life and death, but toil. No big thing in the grand scheme of things, just something that might be worth considering if you don't want to push maintainers(!) to unsubscribe from issues. Personally I view Issue reporters also as vital contributors in this ecosystem and want to show them the necessary respect by taking the time to respond to their problems. If I first have to filter out announcements (your last one was not even 2 months ago by the way: #386) this makes it juuuust a little bit more annoying. Anyways, too many words for little gain and I think the feedback was received.

[felixfontein]

I did think a bit about this this morning, and didn't came to an conclusion yet. Since you already started discussing this here are my thoughts :)

I'd like to distinguish between #386 and (non collection specfic) event announcements like this one. IMO #386 is something important that should be known to all maintainers and contributors, and deserves spamming ;) Also it is a meta-announcement because it tells you exactly what you have to do to get more announcements, namely subscribe to that repository.

For events on the other hand, especially ones not specific to this collection (I'm not sure what to do about ones specific to this collection, if that should ever happen :) ), I think it's better to either use the existing pinboard (#24) - at least for infrequent announcements -, or - especially if such announcements come more frequently - have only one meta announcement to some way to receive these announcements.

@MarkusTeufelberger do you think the pinboard is ok for such announcements as this one (which happens only every few months)? Or do you think that's already too much?

[MarkusTeufelberger]

Some people seem to equate "number of open Github issues" with "number of open bugs", so I'd rather keep the number of non-issue issues at least in the single digits by whatever means ("pinboard" issues, "announcement" issues, using the "Discussions" feature instead...).

Personally I get the newsletter anyways and I am also reading a few other places where this announcement is posted, which is why I'm not too happy about blasting redundant information wherever someone might read it. There are diminishing returns on how many people can be reached with such a strategy and to me it feels rather off-putting if it is preferred to have people "survive" notifications in multiple repositories every few months rather than focusing on a select few low noise/high signal communication channels. Especially if this is not even perceived as a relevant issue for this repository in the first place(!).

To the question in case: As long as this issue is being closed by @Andersson007 on April 13th, I'm fine either way (I'll get pinged either way with no way of initially ignoring these types of notifications as I'd need to stay subscribed to new issues and a general pinboard thread). I still think that writing close to 100 Github Issues is not the place to advertise generic community-wide events. Personally I can't attend anyways, since I have a day job. Have fun at the summit, I guess - maybe you can also discuss this type of communication there.

[Andersson007]

i'll close the issue now, thanks for the feedback and discussion