8:29 a.m.
Hi everyone,
Thank you for making time to attend the meeting. We had quite a
constructive meeting.
In short, we discussed what the best way to go forward from here is.
What can be done is broadly divided into - tooling and non-tooling
tasks.
By tooling, we mean things like "whatcanidoforfedora", join.fp.o and so
on. At some point, we'd like to unify the join process followed by
different teams since they all do have quite a few common steps to
begin with - creation of an FAS account system, for example. Now, we're
all aware that we're going to have a new fedora hubs system in place
soon. We spoke to robyduck from the websites team and he clarified
quite a few things for us:
- hubs is like an intranet for contributors
- so, you need to have an fas account to access the hubs
- there will be pages for joining new teams but the details on how this
will be implemented still need to be fleshed out
- the wiki has too much stuff on it and will continue to exist
So, basically, we decided to leave the tooling part for the moment,
quite simply because we want to wait until the hubs are up and then
decide on what we need to modify/improve.
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 and
set up a "team join day".
- we'll keep a set of simple tasks ready for this day - easyfix and so
on
- we'll try and get contributors from the selected team to hang around
to speak to the newbies and help them out
- we'll spread the word about this - magazine, personal blogs, twitter
and so on (try and make heavy use of the marketing resources at
Fedora's disposal)
- newbies come, we speak to them, we walk them through the join
process, we get them to do a simple task and therefore contribute to
the functioning of the team
- they get to do some work, they get to join Fedora, they get to know
some of the team's contributors
- the teams get new contributors and also get some of their simple
tasks done
- if we can focus on universities and student groups (commops is
speaking about a university outreach program for example), that'd be
awesome too
So, we need to work on:
- which team to begin with? Ideas? (Keeping in mind that F23 is release
soon - something coinciding with the release would be nice)
- when do we do the join day
- rewards - newbies get a badge for joining the community anyway.
Should we have a badge for community members that help out?
- metrics to collect - community members involved, newbies involved,
work done, *what else*?
- after the join day - get newbies and contributors to write about
their experiences (feedback?)
- what else?
The logs are below:
Meeting started by FranciscoD_ at 20:02:35 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-join/2015-10-16/fedora-join.201
5-10-16-20.02.log.html
.
Meeting summary
---------------
* rollcall (FranciscoD_, 20:02:51)
* flock summary (FranciscoD_, 20:05:39)
* IDEA: merge join processes of different Fedora teams (FranciscoD_,
20:16:04)
* IDEA: join.fp.o redo (FranciscoD_, 20:16:36)
* IDEA: integrate "join days" with release tasks (FranciscoD_,
20:35:35)
* LINK: http://developer.fedorainfracloud.org/ (FranciscoD_,
20:59:07)
Meeting ended at 21:20:32 UTC.
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
https://meetbot.fedoraproject.org/fedora-join/2015-10-16/fedora
-join.2015-10-16-20.02.html
--
You received this message due to your preference settings at
https://apps.fedoraproject.org/notifications/fmnmeetingminutes.id.fedor
aproject.org/email/29368
_______________________________________________
meetingminutes mailing list
meetingminutes(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/meetingminutes
2:20 p.m.
So, we need to work on:
- which team to begin with? Ideas? (Keeping in mind that F23 is release
soon - something coinciding with the release would be nice)
- when do we do the join day
- rewards - newbies get a badge for joining the community anyway.
Should we have a badge for community members that help out?
- metrics to collect - community members involved, newbies involved,
work done, *what else*?
- after the join day - get newbies and contributors to write about
their experiences (feedback?)
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.
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 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.
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?).
Having badges for community members that help out is a good idea too.
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.
Anyways, this is just some of my take on this, curious as to what the
rest of you think.
Cheers,
------------
Justin W. Flory
jflory7(a)gmail.com
3:36 a.m.
Il giorno lun, 19/10/2015 alle 14.29 +0100, Ankur Sinha ha scritto:
Hi everyone,
Hi
[cut]
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
and
set up a "team join day".
That's ok.
- we'll keep a set of simple tasks ready for this day - easyfix
and
so
on
Do we take this easyfix from https://fedoraproject.org/easyfix/ or do
we create a join-SIG easyfix page?
- we'll try and get contributors from the selected team to hang
around
to speak to the newbies and help them out
ok
- we'll spread the word about this - magazine, personal blogs,
twitter
and so on (try and make heavy use of the marketing resources at
Fedora's disposal)
About G+ we should get in touch with Matthew Williams (FAS
https://fedoraproject.org/wiki/User:Lorddrachenblut), I'm not aware
about people behind Facebook and others; I'm sure Ankur can help in
this.
[cut]
So, we need to work on:
- which team to begin with? Ideas? (Keeping in mind that F23 is
release
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.
Gabri
[cut]
4:11 a.m.
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
11:03 a.m.
In my FLUG we are going to cut a 15inch Cake, served with coffee. If you don't want
cake, there will be other cold refreshments.
About 35cm diameter. Regards
Leslie
Mr. Leslie Satenstein
Montréal Québec, Canada
From: Ankur Sinha <sanjay.ankur(a)gmail.com>
To: Fedora Join Mailing list <fedora-join(a)lists.fedoraproject.org>
Sent: Monday, October 19, 2015 9:29 AM
Subject: [Fedora-join] Meeting logs and summary - and work to be done
Hi everyone,
Thank you for making time to attend the meeting. We had quite a
constructive meeting.
In short, we discussed what the best way to go forward from here is.
What can be done is broadly divided into - tooling and non-tooling
tasks.
By tooling, we mean things like "whatcanidoforfedora", join.fp.o and so
on. At some point, we'd like to unify the join process followed by
different teams since they all do have quite a few common steps to
begin with - creation of an FAS account system, for example. Now, we're
all aware that we're going to have a new fedora hubs system in place
soon. We spoke to robyduck from the websites team and he clarified
quite a few things for us:
- hubs is like an intranet for contributors
- so, you need to have an fas account to access the hubs
- there will be pages for joining new teams but the details on how this
will be implemented still need to be fleshed out
- the wiki has too much stuff on it and will continue to exist
So, basically, we decided to leave the tooling part for the moment,
quite simply because we want to wait until the hubs are up and then
decide on what we need to modify/improve.
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 and
set up a "team join day".
- we'll keep a set of simple tasks ready for this day - easyfix and so
on
- we'll try and get contributors from the selected team to hang around
to speak to the newbies and help them out
- we'll spread the word about this - magazine, personal blogs, twitter
and so on (try and make heavy use of the marketing resources at
Fedora's disposal)
- newbies come, we speak to them, we walk them through the join
process, we get them to do a simple task and therefore contribute to
the functioning of the team
- they get to do some work, they get to join Fedora, they get to know
some of the team's contributors
- the teams get new contributors and also get some of their simple
tasks done
- if we can focus on universities and student groups (commops is
speaking about a university outreach program for example), that'd be
awesome too
So, we need to work on:
- which team to begin with? Ideas? (Keeping in mind that F23 is release
soon - something coinciding with the release would be nice)
- when do we do the join day
- rewards - newbies get a badge for joining the community anyway.
Should we have a badge for community members that help out?
- metrics to collect - community members involved, newbies involved,
work done, *what else*?
- after the join day - get newbies and contributors to write about
their experiences (feedback?)
- what else?
The logs are below:
Meeting started by FranciscoD_ at 20:02:35 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-join/2015-10-16/fedora-join.201
5-10-16-20.02.log.html
.
Meeting summary
---------------
* rollcall (FranciscoD_, 20:02:51)
* flock summary (FranciscoD_, 20:05:39)
* IDEA: merge join processes of different Fedora teams (FranciscoD_,
20:16:04)
* IDEA: join.fp.o redo (FranciscoD_, 20:16:36)
* IDEA: integrate "join days" with release tasks (FranciscoD_,
20:35:35)
* LINK: http://developer.fedorainfracloud.org/ (FranciscoD_,
20:59:07)
Meeting ended at 21:20:32 UTC.
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
https://meetbot.fedoraproject.org/fedora-join/2015-10-16/fedora
-join.2015-10-16-20.02.html
--
You received this message due to your preference settings at
https://apps.fedoraproject.org/notifications/fmnmeetingminutes.id.fedor
aproject.org/email/29368
_______________________________________________
meetingminutes mailing list
meetingminutes(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/meetingminutes
_______________________________________________
fedora-join mailing list
fedora-join(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/fedora-join
7:02 p.m.
On 10/21/2015 05:11 AM, Gabriele Trombini wrote:
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)
I take it you meant badges instead of t-shirts? In either case, I think
the "Fedora User" idea partially exists already in signing the FPCA.
However, I *really* like the idea of a badge like Fedorian/Fedoran - do
you think that decause's ticket here
(https://fedorahosted.org/fedora-badges/ticket/409) is similar to this goal?
As for the Contributor idea, I'm a big fan of that idea too - I actually
have a ticket for a similar badge that I submitted a couple weeks ago
(https://fedorahosted.org/fedora-badges/ticket/407).
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.
I had a hunch about being close to the release cycle seeing as how close
it is, so that's no problem.
Like mentioned in your reply to Ankur, I think the non-technical groups
would be the best places to begin, and we can try to craft the best way
of going about it with these groups and apply what works and what
doesn't to the groups that aren't as represented in this SIG as of now.
For the Magazine, we have our weekly meeting on Thursdays, 17:00 to
18:00 in US EST time zone. Not sure if you're awake then, but I
regularly attend that meeting and I can bring it up tomorrow if that's
something we want to go ahead and start discussing.
> 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?
True - only thing I would imagine is if they proactively shared their
blog post with us afterwards. But in retrospect, I don't think it's
something to focus on anyways.
I think this is an exciting idea, I know I definitely want to help out
with the Marketing join-day - seems like it would be fun anyways. :)
--
Cheers,
------------
Justin W. Flory
jflory7(a)gmail.com
12:25 p.m.
On Mon, Oct 19, 2015 at 02:29:30PM +0100, Ankur Sinha wrote:
Thank you for making time to attend the meeting. We had quite a
constructive meeting.
Hey everyone. This is really exciting. Let me know what I can do to
help support your work!
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
3102
days inactive
3106
days old
fedora-join@lists.fedoraproject.org
6 comments
5 participants
participants (5)
-
Ankur Sinha -
Gabriele Trombini -
Justin W. Flory -
Leslie S Satenstein -
Matthew Miller