[council] #40: Enforcing the code of conduct
by fedora-badges
#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
6 years, 10 months
[council] #38: Dopr
by fedora-badges
#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
7 years, 6 months
[council] #27: Proposed Schedule for PRD Refresh
by fedora-badges
#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
7 years, 9 months
[council] #41: Budget Request: Outreachy Intern(s) for 2015 Winter Cycle
by fedora-badges
#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
7 years, 10 months
[council] #22: Objective Proposal: University Involvement
by fedora-badges
#22: Objective Proposal: University Involvement
----------------------+-------------------
Reporter: sgallagh | Owner:
Status: new | Priority: normal
Component: General | Keywords:
----------------------+-------------------
I alluded to this during the Council meeting on Monday, so I'm going to
attempt to turn this into a formal proposal.
== Objective: University Involvement ==
=== Overview ===
Increase Fedora's exposure in university environments, particularly
engineering universities.
=== Expected Impact ===
Increased user base with a specific focus on future contributors.
=== Timeframe ===
For maximum effect, if we elect to work towards this Objective, we should
kick it into gear at the beginning of the summer with the intent of having
events planned during the 2015-2016 school year.
=== Aspects ===
* Coordinate marketing, ambassador and outreach groups to focus on
university needs
* Work with universities to provide install-fests during student
orientation periods
* Work with universities to regularly run Fedora-focused hackfests
* Work with university IT departments to co-maintain one or more Fedora
computer labs (and help them upgrade them during breaks)
* Establish work-study, co-op and for-credit programs at universities
=== Metrics ===
* Increased contributions from university programs
* Increased bug reports and feature requests
* Increased mind-share among potential contributors (not easily measured)
=== Additional Notes ===
Some prototypes of this have been performed at Brno universities over the
last few years, with very positive results. We should coordinate with the
contributors involved in those efforts and learn from their successes and
failures.
There is also a University Outreach program run by Red Hat's "Open Source
and Standards" department which was involved in the RIT partnership from
which we eventually acquired Remy DeCausemaker. I assume he will have
plenty to add to this discussion as well as contacts in the university
world.
--
Ticket URL: <https://fedorahosted.org/council/ticket/22>
council <https://fedorahosted.org/council>
Fedora Council Public Tickets
7 years, 11 months
for discussion: Fedora OpenShift as an objective
by Matthew Miller
Red Hat's OpenShift Platform as a Service (PaaS, for those following
the buzzwords) offering is starting to get industry momentum.¹ ² What's
more, there are only two major open source PaaS offerings³, and we
currently have neither of them in Fedora.
We used to have OpenShift v1, but when v2 came along, it was just too
difficult to keep all of the Ruby requirements in sync. (I remember
some kernel-related pain, too, but I'm kind of hazy — that was several
years ago.)
But now, there's a shiny new OpenShift v3, rewritten in Go. I'd like to
talk about (and eventually if enough people think this is a good idea,
officially propose) a 12-month (e.g, Fedora 24 and 25 cycle) initative
to better our relationship with OpenShift, in order to put Fedora in a
position of leadership in this important area of computing — and,
thinking bigger, to advance the state of open source in this area by
doing that.
Specifically (outcomes!⁴), I'd like to:
- Have OpenShift Origin v3 packaged in Fedora, so users Fedora users
can deploy it locally and we can use it in Fedora Infrastructure.
- Establish good communication channels between Fedora userbase and
upstream developers, so that PaaS innovators⁵ and maybe early
adopters⁶ choose Fedora for their leading-edge deployments
- Increase PaaS knowledge and skills in the Fedora contributor
community. Possibly have an OpenShift Origin instance running in
Fedora infrastructure for contributor community use.
I think this is something on the order of an Objective rather than just
a change/feature proposal because it's actually a rather tall order. On
the technical side, currently OpenShift can't be easily packaged
because it includes some 200+ Go libraries, and we don't even have
approved Go packaging guidelines. This probably means we'd be asking
for a very large bundling exception (note 'Active upstream Security
Team' as part of the justification). On the less technical but still
important side, I'd like to see related marketing and documentation,
and coordination with Fedora Atomic and the Fedora Cloud WG, and
possibly with Fedora Server as well (I know OpenShift node as server
role is already under some consideration).
Thoughts, comments, thrown vegetables?
Notes:
1. http://www.redhat.com/en/about/blog/red-hat-cited-%E2%80%9Cvisionary%E2%8...
2. http://www.infoworld.com/article/2608445/cloud-computing/review--openshif...
3. The other is CloudFoundry, which I'm sure is fine, but which is kind
of.... out of ecosystem. (I don't think it even officially runs on
CentOS.)
4. http://fedoramagazine.org/lets-talk-about-fedora-project-objectives/
5. https://en.wikipedia.org/wiki/Technology_adoption_lifecycle
6. ibid.
Disclaimer with my red hat on: this isn't an official message from Red
Hat, and while other Red Hatters, including people involved in
OpenShift, are _interested_, there isn't a specific request from Red
Hat to do this.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
7 years, 11 months