#40: Enforcing the code of conduct
-------------------+---------------------------------
Reporter: duffy | Owner:
Status: new | Priority: normal
Component: Legal | Keywords: coc, code of conduct
-------------------+---------------------------------
See this post from the outreach-list regarding the actual enforcement of
the code of conduct as currently written:
https://lists.fedoraproject.org/pipermail/outreach/2015-July/000067.html
Langdon asked that this be made a ticket for council discussion, with the
concern that an unenforceable / consequence without an SOP is a threat and
isn't the right way to go:
https://lists.fedoraproject.org/pipermail/outreach/2015-August/000073.html
For reference, the actual text is:
"FUDCon brings together contributors and users from all over the world and
this diversity is one of our greatest strengths. This diversity however
can also lead to communication issues and unhappiness. Attendees are
required to be considerate and respectful of each other. This includes,
but is not limited to:
- "Refraining from rude behaviour
- "Refraining from any sort of harassment or discrimination (based on
ethnic background, religion, gender, sexuality, body shape, disability,
geographic location, sports team, preferred operating system or anything
else)
- "Obeying local laws
"Attendees who are in violation of this policy may be subject to removal
and banning from FUDCon (and future Fedora events). Whether an attendee is
in violation is at the sole discretion of the conference organizers.
Anyone with a possible concern relating to the code of conduct is
encouraged to either email Rupali Talwatkar or talk directly to one of the
designated FUDCon volunteers. Designated FUDCon volunteers will have a
dark blue coloured VOLUNTEER badge."
The line of particular concern here is:
"Attendees who are in violation of this policy may be subject to removal
and
banning from FUDCon (and future Fedora events)."
--
Ticket URL: <https://fedorahosted.org/council/ticket/40>
council <https://fedorahosted.org/council>
Fedora Council Public Tickets
#43: Create the Fedora Public Budget Page
-------------------------+-------------------------------------------------
Reporter: decause | Owner: decause
Status: new | Priority: normal
Component: General | Keywords: budget, websites, FCL, transparency,
| community
-------------------------+-------------------------------------------------
As per the results of our council discussion here
(https://lists.fedoraproject.org/pipermail/council-
discuss/2015-October/013742.html) we are heretofore establishing a new
page (wiki or otherwise) that will track the timeline and particulars of
the Fedora Public Budget. It shall include:
Budgetary Components, Projected and Adjusted for each fiscal year:
- Regional Budget Allocations (APAC/EMEA/LATAM/NA)
- Fedora Premier Event Budgets (FLOCK, FUDCon)
- Central Discretionary Fund (approved by Council)
- FAD specific Budgets
Budgetary Milestones and Timelines:
- August: In person meeting at FLOCK
- September: Proposed budget components and metrics from each region
- October: Ratification of Proposed Budget by Council
- March: Confirmation of Received budget w/ Adjustment Meeting
- Quarterly Check-ins with Regional Treasurers
- Halfly approvals of Regional Funds, pending metrics and outcomes
reporting
If there are other details or resources that should be included on this
page, feel free to leave them in the comments below. I would propose that
this page eventually be made available at http://budget.fedoraproject.org
--
Ticket URL: <https://fedorahosted.org/council/ticket/43>
council <https://fedorahosted.org/council>
Fedora Council Public Tickets
#16: Periodic contributor survey
---------------------+-------------------
Reporter: mattdm | Owner:
Status: new | Priority: normal
Component: General | Keywords:
---------------------+-------------------
This is a tracking ticket for establishing a process by which we get
regular feedback from the Fedora contributor base.
This is a companion to https://fedorahosted.org/council/ticket/1. The
desired goals, methodology, and basically everything else are really
different between users and contributors it will be better to track them
separately.
--
Ticket URL: <https://fedorahosted.org/council/ticket/16>
council <https://fedorahosted.org/council>
Fedora Project Board Public Tickets
#42: Schedule a FLOCK Budget Planning Session w/Council
-------------------------+-------------------------------------------------
Reporter: decause | Owner: decause
Status: new | Priority: minor
Component: Board Meta | Keywords: FLOCK, session, budget, council,
| fiscal,
-------------------------+-------------------------------------------------
As per our discussion about Budget Planning here,
(https://lists.fedoraproject.org/pipermail/council-
discuss/2015-October/013742.html) one conclusion we came to was that
Budget Planning for the next fiscal year would begin during August at
FLOCK with a high-bandwidth in person meeting, that continued on maillists
and IRC through September, and was delivered to the FCL in October, to be
presented to Red Hat via OSAS.
This ticket is a reminder that we need to schedule a session at FLOCK for
the high-bandwidth in person session.
--
Ticket URL: <https://fedorahosted.org/council/ticket/42>
council <https://fedorahosted.org/council>
Fedora Council Public Tickets
#38: Dopr
------------------------+-------------------
Reporter: msuchy | Owner:
Status: new | Priority: normal
Component: Trademarks | Keywords:
------------------------+-------------------
Hi,
we (as Copr team) would like to introduce new service "DOPR".
It is very easy. It combine user Dockerfile and user's Copr and create new
docker image on DockerHub.
You can see staging instance at:
http://dopr-dev.cloud.fedoraproject.org/
We would like to start production instance. However some members of
fedora-infra would like to see this go through Council first.
There is some sense on this as this is kind of new way of distribution of
Fedora (beside Spins, Remixs...).
It creates all docker images directly on DockerHub so technically speaking
they are not created in Fedora infrastructure, but they are created under
Fedora account.
And we would like to market it as "Fedorea + Copr" or similar.
So my question: Does Fedora Council approve granting trademark usage on
resulting docker images?
--
Ticket URL: <https://fedorahosted.org/council/ticket/38>
council <https://fedorahosted.org/council>
Fedora Council Public Tickets
#45: Sponsorship/Funding for FAD EMEA BUDAPEST 2015
---------------------+--------------------
Reporter: rgeri77 | Owner: decause
Status: new | Priority: normal
Component: General | Keywords:
---------------------+--------------------
In this year we would like to organise, and run for FAD EMEA BUD 2015. We
have made our calculations, and we have the venue places, but we require
full funding/cover for food and hotel costs. NOT REIMBURSEMENT. More about
the details can be found at here:
Wiki: https://fedoraproject.org/wiki/FAD_Budapest_2015_bid. The event is
planned to be held at 2015. nov. 27-29.
Budget sheet :
https://docs.google.com/spreadsheets/d/1wl5YcHQOlcM6BeRludN9eq1iTKkbfp2HICg…
We have less and less time to have confirmation for the venues, and the
current date that we can hold the offers are 2015 oct. 25. After this date
the hotel cancel the reservation, and give other price (I guess
expensive), so as the conference room owner.
--
Ticket URL: <https://fedorahosted.org/council/ticket/45>
council <https://fedorahosted.org/council>
Fedora Council Public Tickets
#44: Tracking Elections in Council's ticketing system
---------------------+--------------------
Reporter: jkurik | Owner:
Status: new | Priority: normal
Component: General | Keywords: meeting
---------------------+--------------------
Hi Council,
as discussed on FESCo meeting and in the
[https://fedorahosted.org/fesco/ticket/1486 FESCo ticket], I would like to
track progress of Elections in a ticket. As Elections are a part of the
way how we assure governance and Council is the top-level governance body,
it makes sense for me to track it under a "Council's namespace".
Anyone has an objection to use [https://fedorahosted.org/council/report
Council's ticketing system] for this purpose ?
Regards,
Jan
--
Ticket URL: <https://fedorahosted.org/council/ticket/44>
council <https://fedorahosted.org/council>
Fedora Council Public Tickets
#27: Proposed Schedule for PRD Refresh
----------------------+-------------------
Reporter: sgallagh | Owner:
Status: new | Priority: normal
Component: General | Keywords:
----------------------+-------------------
As discussed in the Hangout meeting today, we need to do a periodic
refresh of the PRDs to make sure they are kept up-to-date. I propose that
each of the Edition, Base and Env/Stacks groups should provide an update
by 23:59 UTC on June 12, 2015 for review. This gives a little over a week
for them to be reviewed prior to the Change Submission Freeze as currently
scheduled.
--
Ticket URL: <https://fedorahosted.org/council/ticket/27>
council <https://fedorahosted.org/council>
Fedora Council Public Tickets
#41: Budget Request: Outreachy Intern(s) for 2015 Winter Cycle
-------------------------+-------------------------------------------------
Reporter: decause | Owner: decause
Status: new | Priority: major
Component: General | Keywords: outreachy, EDU Objective,
| internship, interns, co-ops, D&I
-------------------------+-------------------------------------------------
Outreachy (formerly GNOME Outreach Program for Women) is administering
their winter cycle, and there are members of the Fedora project willing to
mentor on a handful of projects.
You can view this year's proposed program on the Fedora Wiki (Work in
Progress): https://fedoraproject.org/wiki/Outreachy/2015
General information about the Outreachy program can be found here:
https://wiki.gnome.org/Outreachy
Information Specific to this upcoming round can be found here:
https://wiki.gnome.org/Outreachy/2015/DecemberMarch
The cost of sponsoring an intern is $6,500 USD. They are paid
incrementally 3 times over the course of their internship by the Outreachy
program, who handles the administrative burden via the Software Freedom
Conservancy. A $500 travel stipend is included in that cost, which could
be used to help subsidize the intern's travel to FOSS conferences, Events,
or workshops (ideally Fedora Events, FADs, or hackfests.)
I would propose that we *provisionally* allocate funding for at least 1
slot ($6,500), but ideally 2 slots ($13,000) pending suitable applicants
to fill the slot(s).
Outreachy program representatives will be available during our Monday
meeting on 9/28 to answer our questions.
--
Ticket URL: <https://fedorahosted.org/council/ticket/41>
council <https://fedorahosted.org/council>
Fedora Council Public Tickets