Fedora is full of FPL responsibilities documented in scattered
locations all over the project wiki waiting to surprise me. Not that
there's any problem with responsibilities, just that I don't want to
let anything drop on the floor because I overlooked it. Sirko from the
Ambassadors noted that one of the things where lack of FPL action can
block the community is the FUDCon bid process — see
<https://fedoraproject.org/wiki/FUDCon_bid_process>. I see that this
also refers to some outdated things like the "CommArch manager", which
is confusing because CommArch isn't even a thing anymore.
This is a great example of one of the reasons we created the Council in
the first place, and I'd like to suggest that we update this page to
replace FPL with the Council, and specifically make this a
responsibility of the Community Action and Impact Coordinator.
I don't know the exact the right mix between putting this entirely on
that person (shoving Remy under the bus?) and making it a
collective/shared Council responsibility; thoughts on that? The part in
the end about "decision process" is also somewhat unclear — I'm pretty
sure I know what it means to say, but it's left as assumed that we know
who that means... maybe we can clear that up, especially with the basic
plan of having the Council have more responsibility for the budget.
(Overall, the basic process looks solid, and the 2010 goals still seem
Fedora Project Leader
i just had a very strange experience today where i thought the council
was separate from the board and that the board still existed. i needed
to refer someone to the board for a trademark issue. none of the board
links on the wiki for contacting the board worked (board trac links,
board ml links) - they all 404ed.
so i finally figured out (yes there is a yellow box at the top of the
page, no i dont typically pay attention to those :) ) that the council
replaced the board, but unlike the board's wiki page the council has no
information on how to contact the council, so now i'm not sure where to
point this fellow to in order to get a trademark request approved (does
the council do this? unclear from wiki page.)
just some feedback in the interest of being helpful.
#23: No contact info on Council wiki page
Reporter: sgallagh | Owner:
Status: new | Priority: normal
Component: General | Keywords:
http://fedoraproject.org/wiki/Council contains a list of council members
but no contact information for them. We should probably either add email
addresses there or else clearly state that the expectation is for people
to reach out through the public discussion list. (Or add links to a
private list for sensitive matters)
Ticket URL: <https://fedorahosted.org/council/ticket/23>
Fedora Council Public Tickets
I've added a new section to the Objectives page at
<https://fedoraproject.org/wiki/Objectives>, and noted that the
existing text is still valid but, 1990s internet style, under
construction. I *would* like to work on updating that, but I also don't
want to get tooooo bogged down in navel-gazing. As I said in
I think the existing objectives are basically good, just not everything
we need (and not necessarily aligned with what we're actually doing).
Fedora Project Leader
Hi everyone! We are planning to have a Fedora Council meeting this
coming Monday, May 9th, at 17:00 UTC (which is 1pm US/Eastern — note
the daylight saving time change). This will be an IRC meeting in the
old Fedora Board meeting slot.
Topics will include:
- Outreach Steering Committee — status, and what we need to do.
— Objectives Updates — we only have one; developing more?
- Diversity advisor search committee (mailing list post from me coming
in a couple days, btw)
— Discussion around Fedora Workstation's plan for third-party repos and
possible future for containerized apps. (I know the workstation WG
hasn't yet come up with a formal new proposal, but we should engage
constructively rather than sit back and wait.)
Fedora Project Leader
Hi everyone! One of the open positions on the Fedora Council is the
Diversity Advisor, which we've defined like this:
Fedora's Diversity Advisor works on initiatives to assess and promote
equality and inclusion within the Fedora contributor and user
communities, and helps develop project strategy on diversity issues.
Additionally, the Diversity Advisor administers and is the point of
contact for Fedora's participation in third-party outreach programs
This position is appointed by the Fedora Project Leader, with the
approval of the Council.
The selection process is left undefined. My plan is to form a search
committee to help find the best person for the job.
In earlier discussion (online and at Flock), we've talked about the
various benefits of asking someone within the project vs. someone more
from the outside, with experience in open source and communities but
not necessarily deeply with Fedora. I think there clearly _are_
benefits and disadvantages either way, and I'm open to either one. I'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 process back the choice (and, indeed,
were part of making it); and if we choose someone from within the
project, that we also have the benefit of outside perspective in doing
I spoke with Jamie Williams, who works on diversity within Red Hat, and
she shared a simple application they used to help form an internal
diversity group; I've adapted that for this search committee.
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
2) What specific minority group(s) or issues can you offer insight
about or speak on behalf of? 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 3 people who can speak to your passion,
interest, or experience with diversity and inclusion.
My plan is to ask people to send these to me directly, and I will share
them confidentially with the current members of the Council, and we'll
form the committee from there. I'll publicize this within Fedora, and
also ask people with connections outside the project to help spread the
word and to directly invite people who they think would be good. Actual
details of how the search will work, we will leave up to the searchers.
Does this plan sound good to everyone? Anything you'd do differently?
(Note that the Diversity Advisor currently an unpaid, volunteer
position. I personally hope we can change that in the future.)
Also, it may end up that someone with interest in being on the search
team will also be the best candidate; I don'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 I
also don't want to raise barriers by making that an initial obligation.
Fedora Project Leader