Il giorno lun, 19/10/2015 alle 14.29 +0100, Ankur Sinha ha scritto:
This brings us to the non tooling tasks - ideas for people, as
randomuser put it - how can we engage better with newbies ourselves
instead of making them interact the wiki or the join tool and so on.
For this, we came up with the idea of "join days". Think of them as
test-days, but for different teams:
- on a fixed frequency, say monthly, we'll speak to one Fedora team
set up a "team join day".
- we'll keep a set of simple tasks ready for this day - easyfix
Do we take this easyfix from https://fedoraproject.org/easyfix/
we create a join-SIG easyfix page?
- we'll try and get contributors from the selected team to hang
to speak to the newbies and help them out
- we'll spread the word about this - magazine, personal blogs,
and so on (try and make heavy use of the marketing resources at
About G+ we should get in touch with Matthew Williams (FAS
), I'm not aware
about people behind Facebook and others; I'm sure Ankur can help in
So, we need to work on:
- which team to begin with? Ideas? (Keeping in mind that F23 is
soon - something coinciding with the release would be nice)
For a correct begin I think we should start with some less technical
groups (Ambassadors, Mktg, Docs that are also easier for us, because we
are involved in) and when things are clear, we might start with others.
But the release period isn't the best choice for me.
- when do we do the join day
Good question; maybe we should have a planning task (something like
release tasks, not related to the release itself). For sure we have to
fix days between join-day announce, on socials, fedmag an so on, and
the day it happen. Two weeks?
- rewards - newbies get a badge for joining the community anyway.
Should we have a badge for community members that help out?
We have badge for applying FPCA in FAS, the faster way to get
information is checking user activity in fedmesg.
- metrics to collect - community members involved, newbies involved,
work done, *what else*?
This is another good question, I'm really interested in; Decause should
be aware of the metrics stuff.
- after the join day - get newbies and contributors to write about
their experiences (feedback?)
Of course, this is important; the problem in where... Following their
blogs is impossible, a wiki page for each one of them is impossible as
well; maybe we can edit join-days page (such like "join-day feedback
2015-10-20 - marketing") with columns as name - feedback.
About this, the first join-day should be about wiki (docs?) writing.