-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hiya, So this is a follow up from the meeting we had. I've summarise some of it in a blog post that should hopefully show up on the planet[1].  During the meeting, we discussed how we need to ensure that the work that CommOps is doing towards improving the different teams' onboarding processes seems to overlap with the general goal of the Join SIG. So, to make sure we don't have two teams doing the same thing, we should come up with a set of specific goals and some example tasks that we can undertake to achieve these goals. I'm starting with the goals here, and once we have them listed and agreed to, we will begin working on ideas on how to achieve them. Good so far, I hope? OK. So, our aim is summarised on the wiki page here[2]. As it says, we want to establish a set of communication channels that enable newbies to speak to contributors and become part of the community socially even before they join a team and begin contributing.  The point being that the common philosophy we all believe in, and the relationships we make because we share this view should bind us together, not only the work we do together, which should be a *result* of our commitment to our philosophy. Does that make sense? :D I'll explain this a little more - usually, someone turns up, after some surfing picks a team to join up, introduces themselves to the team members, gets to know them, works, makes friends, maybe even finds a mentor in the team, maybe begins to help another team later and then makes friends there, and repeat.  What we think would be better is - someone turns up, finds us cool contributors hanging around here, speaks to us, makes friends, gets to know how the community works, our philosophy (and finds it awesome) and what teams we have, finds a mentor (community mentor as opposed to team specific mentor), picks one or more teams to work in, becomes a part of the community, not just a specific team in the community. The major differences in the two are the order in which things happen. We, or at least I think, that it is more beneficial for people to first become a social part of the community in general, build relationships, and then jump into work. The advantages of this order of onboarding are but not limited to: - - newbies are not limited to team specific relationships - - newbies that join together can work together, even if they work in different teams (we're all always closer to our classmates than to seniors/juniors) - - they get a much better overall idea of how the community functions and are exposed to the workflows of different teams through us (including tooling, admin, process, goals, tasks, ninjas) - - they go on to develop into contributors that also have a good idea of how the multiple arms of the community work to keep Fedora going So, what do people think about this, does this reasoning appear sound? So, our goals would be on the lines of: - - advertise our channels (ML, IRC, something else) as the first stop for prospective contributors - - act as a net to gather prospective contributors, help them socialise with the community and among themselves - - further, via our conversations with them, help them pick teams where they can contribute to - - further, keep a constant ongoing discussion about free software so that our first foundation is regularly reinforced Please do share your thoughts. If we can do this in the next few days, we can then summarise it during next Monday's meeting and begin working on ideas for tasks. :) [1] http://ankursinha.in/blog/2016/09/27/fedora-join-meeting-26-september-2016-summary.html [2] https://fedoraproject.org/wiki/Fedora_Join_SIG#Aim - -- Thanks, Regards, Ankur Sinha "FranciscoD" http://fedoraproject.org/wiki/User:Ankursinha