FAMSCo moves forward. Recent progress report.
by Cesar Pinto
Hello All.
In light of recent discussions from what this group is meant to be or
address. I am happy to report that we held a meeting recently (with
declause as chair) and we had a good dialogue.
Full logs available here:
http://meetbot.fedoraproject.org/fedora-meeting/2015-03-24/fedora-meeting...
As the discussions continue on this list on topics related to FAMSCo´s
remit, membership and scope of activities, we have agreement that the first
initiative we should tackle is one of measurement and goal setting.
As such, FOSCo´s Executive Dashboard initiative has been initiated on the
marketing list. (But with a remit to be cross-functional in nature)
With enthusiastic support from FranciscoD and Mailga we are off to a good
start to begin designing and implementing, more details to follow.
The task at hand is to define the metrics. The team has made some
assumptions below, but we could really use your input here.
What are the top level metrics we should be measuring to track success?
Get involved: http://etherpad.osuosl.org/FOSCO_EXECUTIVE_DASHBOARD
Finally, here is a summary of the areas where it seems to be consensus on
the following wiki page
https://fedoraproject.org/wiki/FOSCo
Feel free to edit the page with your suggestions or ideas as you see fit.
>From the discussions so far, I think it is fair to say that FOSCo is in a
state of flux so it will be what those involved make of it, so a great time
to get active and help us build.
Look forward to your comments.
Cheers
Cesar
--
Cesar Pinto
+47 481 20 772
9 years
FOSCo moves forward. Recent progress report.
by Cesar Pinto
Hello All.
In light of recent discussions from what this group is meant to be or
address. I am happy to report that we held a meeting recently (with
declause as chair) and we had a good dialogue.
Full logs available here:
http://meetbot.fedoraproject.org/fedora-meeting/2015-03-24/fedora-meeting...
As the discussions continue on this list on topics related to FAMSCo´s
remit, membership and scope of activities, we have agreement that the first
initiative we should tackle is one of measurement and goal setting.
As such, FOSCo´s Executive Dashboard initiative has been initiated on the
marketing list. (But with a remit to be cross-functional in nature)
With enthusiastic support from FranciscoD and Mailga we are off to a good
start to begin designing and implementing, more details to follow.
The task at hand is to define the metrics. The team has made some
assumptions below, but we could really use your input here.
What are the top level metrics we should be measuring to track success?
Get involved: http://etherpad.osuosl.org/FOSCO_EXECUTIVE_DASHBOARD
Finally, here is a summary of the areas where it seems to be consensus on
the following wiki page
https://fedoraproject.org/wiki/FOSCo
Feel free to edit the page with your suggestions or ideas as you see fit.
>From the discussions so far, I think it is fair to say that FOSCo is in a
state of flux so it will be what those involved make of it, so a great time
to get active and help us build.
Look forward to your comments.
Cheers
9 years
Logs from fedora-outreach meeting from 24 March 2015.
by Ankur Sinha
-------- Forwarded Message --------
From: notifications(a)fedoraproject.org
To: meetingminutes(a)lists.fedoraproject.org
Subject: decause's meeting ended in #fedora-meeting
Date: Tue, 24 Mar 2015 22:14:10 +0000 (UTC)
=======================
#fedora-meeting Meeting
=======================
Meeting started by decause at 21:07:36 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2015-03-24/fedora-meeting...
.
Meeting summary
---------------
* rollcall (decause, 21:07:46)
* agenda (decause, 21:09:51)
* LINK: http://etherpad.osuosl.org/fosco-032415 (Pintomatic,
21:10:25)
* LINK: http://etherpad.osuosl.org/fosco-032415 (decause, 21:11:28)
* What is Outreach? (decause, 21:11:47)
* LINK:
http://blog.linuxgrrl.com/2015/03/24/enabling-new-contributors-brainstorm...
(decause, 21:22:10)
* LINK: http://fedoraproject.org/wiki/FOSCo exists but is blank :)
(FranciscoD, 21:33:22)
* ACTION: Pintomatic introduce yourself and fosco resources to
fedora-mktg maillist (decause, 21:52:14)
* Next Meeting (decause, 21:52:36)
Meeting ended at 22:11:55 UTC.
Action Items
------------
* Pintomatic introduce yourself and fosco resources to fedora-mktg
maillist
Action Items, by person
-----------------------
* Pintomatic
* Pintomatic introduce yourself and fosco resources to fedora-mktg
maillist
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* Pintomatic (100)
* decause (99)
* randomuser (50)
* FranciscoD (43)
* sesivany (16)
* zodbot (11)
* mitzie (1)
* giannisk (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
https://meetbot.fedoraproject.org/fedora-meeting/2015-03-24/fedora-meetin...
--
You received this message due to your preference settings at
https://apps.fedoraproject.org/notifications//fmnmeetingminutes.id.fedora...
_______________________________________________
meetingminutes mailing list
meetingminutes(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/meetingminutes
9 years
Enabling New Contributors Brainstorm Session Tomorrow
by Remy DeCausemaker
Outreaches,
Wednesday March 25 (tomorrow!) from 14:00-16:00 GMT (10-12 AM US Eastern) There will be a brainstorming session led by Mizmo (cc'd here) about strategies for new contributor engagement. You can read more about the Fedora Hubs concept here: http://blog.linuxgrrl.com/2015/03/24/enabling-new-contributors-brainstorm...
This is an exciting and concrete project that has support from both the design and infrastructure teams, and has already had a year's worth of input. I look forward to hearing about the end results, as many of you likely are as well, hence the post here.
Looking Forward,
--RemyD.
--
Remy DeCausemaker
<decause(a)redhat.com>
Fedora Community Lead & Council Member
http://whatcanidoforfedora.org
9 years
[fosco] #8: Create FOSCo Metrics
by Fedora Release Engineering
#8: Create FOSCo Metrics
---------------------+---------------------
Reporter: decause | Owner: decause
Type: defect | Status: new
Priority: major | Milestone:
Component: other | Version:
Keywords: |
---------------------+---------------------
How will we know if FOSCo is being effective, and what kinds of things
should we be measuring?
--
Ticket URL: <https://fedorahosted.org/fosco/ticket/8>
fosco <https://fedorahosted.org/fosco>
My example project
9 years, 1 month
[fosco] #6: Create FOSCo Mission Statement
by Fedora Release Engineering
#6: Create FOSCo Mission Statement
---------------------+---------------------
Reporter: decause | Owner: decause
Type: defect | Status: new
Priority: major | Milestone:
Component: other | Version:
Keywords: mission |
---------------------+---------------------
This will require us to gather input, and rework language, but should help
provide a clear direction for FOSCo.
--
Ticket URL: <https://fedorahosted.org/fosco/ticket/6>
fosco <https://fedorahosted.org/fosco>
My example project
9 years, 1 month
Summary of previous discussions around FOSCo
by Christoph Wickert
Hi,
the idea of FOSCo, the Fedora Outreach Steering Committee has been
brought up before, but as there were different assumptions and ideas,
the council asked to summarize the previous discussion.
The general idea behind FOSCo is to strengthen our outreach by
bundling the efforts of the ambassadors, marketing, and the design
team.
You can break down the previous discussion into two groups:
1. Discussion within FAmSCo, see https://fedorahosted.org/famsco/ticket/373
FAmSCo agreed we want FOSCo and we want it to replace FAmSCo, and
extend its scope to other outreach teams such as the design and
marketing teams. I suggest we do not fall back behind this consensus.
2. Discussion started by Matthew, who sent out a message to various
mailing lists, see
https://lists.fedoraproject.org/pipermail/ambassadors/2014-October/022896...
There was no feedback whatsoever on the ambassadors and design team
lists. On the marketing list, the question of eligible voters was
raised. FAmSCo elections were opened to CLA+1 two years ago and as the
new body represents different FAS groups, we certainly want to keep it
this way. The question however is if we elections at all. Having a
more meritocratic approach was one of the ideas behind recent Fedora
governance changes, so just like in the council, we could also have
appointed seats.
This brings us to the question of FOSCo's composition. At this point,
we need to keep two things in mind:
1. The ambassadors are the by far biggest group. This not only means
we need to represent a lot of people but also that they have a big
impact on elections.
2. Unlike the other groups, the ambassadors project is set up in a
very regional manner. The different regions (NA, LATAM, EMEA, APAC)
take care of their own business in terms of event organization, budget
etc. FAmSco only acts as an umbrella.
I think preserving the regional approach is a must. Each region should
appoint one representative. Marketing and design also need to have
representatives to make sure communication and collaboration with the
other teams works. This will give us 6 appointed (or indirectly
elected) seats.
The question is if we also want / need to have some elected seats and
if, how many of them. The council has two, but I think having an
uneven number is always a good idea. Personally I think three is best
but also the maximum because everything > 9 people in total will be
hard to manage.
I take all appointed candidates are eligible to make decisions and
each have one vote. What about the elected ones? Do we need something
like auxiliary seats as we have in the council?
There are still a lot of open questions here, e.g. the objectives,
scope, and policies of the new body. We can borrow a lot from the
council, e.g. the lazy consensus for decision making.
For everything else, I suggest we discuss the questions as they arise,
so unless people disagree, let's first discuss the composition.
Comments, feedback?
Best regards,
Christoph
9 years, 1 month
[fosco] #5: Create Social Media Accounts and Infrastructure
by Fedora Release Engineering
#5: Create Social Media Accounts and Infrastructure
--------------------------+-----------------------
Reporter: decause | Owner: decause
Type: task | Status: new
Priority: major | Milestone: Fedora 22
Component: marketing | Version:
Keywords: social media |
--------------------------+-----------------------
FOSCo is going to need to create accounts in a variety of social media
channels and places. We should also create a mechanism for Fedora
Community members to queue up articles to be posted and scheduled.
There are some subtasks that need to be arranged from under here, but this
is a good place to start.
--
Ticket URL: <https://fedorahosted.org/fosco/ticket/5>
fosco <https://fedorahosted.org/fosco>
My example project
9 years, 1 month
Help Fedora find a Diversity Advisor
by Remy DeCausemaker
Message sent on Behalf of the FPL.
--RemyD.
<http://fedoramagazine.org/help-fedora-find-a-diversity-advisor/>
Increased diversity is crucial to the future of open source. A range of
contributors from varying backgrounds brings broader experience to the
table, which makes for healthier projects — and ultimately better
software. To make Fedora a more diverse community, the Fedora Council
(our new governance and leadership body) has an open position for a
Diversity Advisor, and we need your help to find the perfect person for
this role.
What does a Diversity Advisor do?
---------------------------------
The Fedora Diversity Advisor will lead initiatives to assess and
promote equality and inclusion within the Fedora contributor and user
communities, and will develop project strategy on diversity issues. The
Diversity Advisor will also be the point of contact for Fedora’s
participation in third-party outreach programs and events.
What’s happening now?
---------------------
We’re forming a search committee to find the most awesome and
incredible human being for the job — and this message is the invitation
to join that committee.
In earlier conversations, we’ve talked about the various benefits of
asking someone within the project to fill the role vs. inviting someone
from the outside, with experience in open source and communities but
not necessarily deeply with Fedora. There clearly are benefits and
disadvantages either way, and we’re open to either one. We’d like the
search committee to include both perspectives (as well as of course
different backgrounds and expertise with minority groups). That way, if
we choose someone external, we can feel confident that people with a
longer history within the project back the choice (and, indeed, were
part of making it); and if we choose someone from within Fedora, that
we also have the benefit of outside perspective in doing so.
How can I help?
---------------
If you’re interested in helping with the search, please email me at
<mattdm(a)fedoraproject.org> with answers to the following questions
(and/or anything else you’d like to say). I’ll share responses
confidentially with other members of the Fedora Council, and we’ll form
the committee from there.
1. Why do you believe diversity and inclusion are important for Fedora,
and why do you want to join the search team for Fedora’s Diversity
Advisor?
2. What specific minority group(s) or issues can you offer insight
about? What perspectives, experiences, or knowledge about diversity
and inclusion could you share as a member of the search team?
3. To give us further insight, feel free to provide names and contact
information for up to three people who can speak to your passion,
interest, or experience with diversity and inclusion.
Please send responses by March 31st, 2015, so we can get the search
underway. We will leave actual details of how the search will work up
to the searchers. It may end up that someone with interest in being on
the search team will also be the best candidate; the Council doesn’t
see that as a problem. And, it may be that the committee will want to
continue to exist after the search, in an advisory role or as part of
an action team, but we also don’t want to raise barriers by making that
an initial obligation.
Note that the Diversity Advisor currently an unpaid, volunteer
position. I personally hope we can change that in the future, but we
also wanted to take the steps we can *now* to make progress. This is
not a token role; it carries full participation in Council consensus
for any and all project issues relevant to diversity.
Please share!
-------------
Please share this invitation with anyone you think might be interested,
both within Fedora and outside of Fedora in relevant communities. Thank
you!
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
--
announce mailing list
announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/announce
9 years, 1 month
