Il giorno mar, 20/10/2015 alle 15.20 -0400, Justin W. Flory ha scritto:
[cut]
I've been thinking about this for the past couple of days, and I
think
the badges are a powerful "motivator" to engage potential or would-be
contributors to become more involved, especially with university
students. Not sure what you guys would think about this, but what
about
doing team "Badge-athons", where maybe teams can select a few of the
easyfix tasks and combine those with the objectives that are already
set
up (mostly) by badges. Then, I think it will be easier for current
contributors to have definite objectives, e.g. "here's goal one, goal
two, goal three, try doing task x and task y to earn these badges"
sort
of thing.
I'm thinking also about a unviable idea:
T-shirt attesting several levels of the process e.g.:
- Fedora User (joining FAS)
- Fedorian (end of join process)
- Contributor (joining group)
In terms of what team to begin with, perhaps since the release is so
close and if we'd want to organize something close to F23, I think
the
marketing team may be a good first candidate? The Magazine is a
possible
starting place, or perhaps some of the tasks surrounding the wiki or
other areas.
As Mktg member I'm available for a join-day but too near to the release
day is impossible. Marketing works basically on the tasks and people
really involved are not so many. Its work is distributed along the
whole release cycle but often we are ok for readiness only the day
before the meeting....
After the F23 release we can plan the join-day when you want.
In the mktg case (and I'm sure also Ankur will agreed), I think that
someone of the people already member of the group needs to follow the
join-day.
About magazine, I can ask to Ryan, Chris and Paul which day is better
to meet.
As for when, it's obviously going to depend on the schedule of each
individual team that has their own Join Day, but I would perhaps
think
spacing them apart by a few weeks would provide us with enough time
to
plan and execute the event. The planning time may fluctuate between
teams too, but I'm not well-versed enough to have a definite idea for
that.
Ok, I agree.
For rewards, I think in the big picture, badges are the "quick"
reward
for participants to get, but I think trying to incorporate the
foundations of Fedora, particularly with community, would be the
thing
that turns the one-time contributor into a regular. Having multiple
people around for the team would probably help contribute to this, so
it
should definitely be a prerogative for the team (which leads me to
another question I'm still confused on, is this something the Join
SIG
works on or is it delegated to each individual team with assistance
from
the Join SIG?).
IMO join-SIG is formed by the only people working on this project; it
would be better if at least one effective member of each group join our
SIG.
Contributors will join their targeted group.
[cut]
As for post-join day activities, I think encouraging blogging to
Fedora
Planet is a good idea to help the participants become more involved -
I
know it would probably be a super cool thing for someone who does
this
and writes about it to have a bunch of the people that helped them
get
started like / share / comment on their blog entry.
Of course, but how we can check it happens?
Anyways, this is just some of my take on this, curious as to what the
rest of you think.
Thank you so much Justin.
Gabri