Final Request for Information: Budget Numbers and Delegates
by Remy DeCausemaker
Ambassadors,
As some of you may have noticed by now, the new Budget site for Fedora
has been pushed to Production!
Production: http://budget.fedoraproject.org
Source: http://pagure.io/fedora-websites
This site is part of the new Budget.next process you may recall from
emails previously on this list:
http://fedoraproject.org/wiki/Budget.next
In keeping with the process there, I'm gathering all the information
needed to comply with our revised policies. This email is a *final*
request for three (3) items of information we need from each region:
FY16 Budget Report
FY17 Budget Proposed
FY17 Regional Delegates
Here is what we have had reported thusfar:
APAC
--------
- FY16 Budget Report:
https://fedoraproject.org/wiki/Ambassadors/APAC/Budget:2016
- FY17 Budget Proposed: _____
- FY17 Regional Delegates: ______
LATAM
---------
- FY16 Budget Report:
https://fedoraproject.org/wiki/Ambassadors/LATAM/Budget:2016
- FY17 Budget Proposed:
https://fedoraproject.org/wiki/Ambassadors/LATAM/Budget:2017
- FY17 Regional Delegates: _____
NA
----
- FY16 Budget Report: _______
- FY17 Budget Proposed: _______
- FY17 Regional Delegate Selections: https://budget.fedoraproject.org/#delegates
EMEA
---------
- FY16 Budget Report:
https://docs.google.com/spreadsheets/d/11nWHrooCwoiWqGx4iEUnITQAWwQrQ6_2i...
- FY17 Budget Proposed:
https://docs.google.com/spreadsheets/d/1IAt2udlv-gwTjUYfhqvNOnwL_1FH_NC4A...
- FY17 Regional Delegates: _________
Please be sure that the links above reflect the latest information for
your region, as we will be using it to determine the
soon-to-be-released Fedora Budget for FY17.
Without having a FY17 Proposed Budget (let alone a completed FY16
Budget Report from last year) it will be difficult to decide how much
budget to allocate to your region in FY17. Regions without proposed
and reported budgets run the risk of having their budgets allocated
centrally by the council until in compliance with the process. This is
*not* the preferred or ideal method of budgeting, and would be an
unnecessary burden on both the council and the regions.
It is possible that I have either misplaced your responses, or have
not looked in the correct places where this information is
historically tracked, so if your region's information is missing,
please accept my apologies and respond here on the ambassador list
with updated links and/or information.
In the future, we will be utilizing a repository on Pagure to track
budget and delegate information. We have discussed the possibility of
using this repository to automatically update the Budget site in
production, but for now, consider it a static repository of documents
and data.
https://pagure.io/budget
Thank you all for your patience as we transition into this new era of
budget transparency. It is my hope that we can stay on top of the
process this year, streamline the reporting requirements, and thereby
streamline the reimbursement process, while improving information
access to everyone in Fedora :)
Looking Forward,
--RemyD.
--
Remy DeCausemaker
Fedora Community Lead & Council
<decause(a)redhat.com>
https://whatcanidoforfedora.org
7 years, 8 months
Announcing Fedora's Diversity Adviser and Newest Council Member: María “tatica” Leandro!
by Remy DeCausemaker
Fedorans,
As some of you may recall, Fedora added a new seat to the Fedora
Council for a Diversity Adviser.
It is with great pleasure that we do hereby announce, that this seat
has been filled by long-time Fedora contributor María “tatica”
Leandro!
https://fedoraproject.org/wiki/User:Tatica
The Fedora Diversity Adviser acts as a source of support and
information for all contributors and users, especially those from
underrepresented populations, so that issues of inclusion and equity
can be discussed and addressed with planning and strategy.
The Fedora Diversity Adviser 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 Adviser will also be the point of contact for Fedora’s
participation in third-party outreach programs and events.
Full description here: https://fedoraproject.org/wiki/Diversity_Adviser
To help communicate the responsibilities of the position, we asked
María a few questions about being the Diversity Adviser and any goals
she had as she begins her new position on the Fedora Community Blog.
Here is an excerpt:
---Snip---
Q: How would you describe your position as Diversity Adviser in
relation to the current situation in Fedora?
A: “Since this is the first time Fedora set a position like this, I
see my role more as an informative one. Fedora is a quite diverse
community despite what most people think. We have contributors all
around the world who gather every day to create fantastic software and
spread knowledge; breaking gender, language and distance barriers on a
daily basis.
I also want to serve as a mediator, and let our contributors know that
Fedora has ears for everyone. It’s no secret that being different is
great, but sometimes that puts you on a vulnerable position (as a
Latin American, Spanish Speaker and Female contributor, I can relate
to some), and we want to make sure everyone feels comfortable with the
Fedora family.”
Q: What are some of your goals or vision as Fedora’s Diversity Adviser?
A: “I will start kicking a small survey to know how diverse our
community is, as it’s important to me to understand the reach of our
contributors, their experiences, needs and culture prior to start any
project. It is no secret that to know our future actions we need to
know our numbers, and because we are such a worldwide community,
sometimes we have a huge lack of information about those who
constantly help us be what we are. These actions will allow us to have
a yearly report that will show us more in detail how our progress on
diversity have worked out. This is not a life-time position, so my
main goal is to leave all the needed information ready and available
for those who will follow. Everything in Fedora is a team work, and
the Diversity Adviser position is no different from others.
As we start to learn more from our contributors we will also be able
to create programs to help each minority group. I would like this to
be the second stage of the diversity action plan for 2016. Either
gather once a week to practice English for about half an hour with
some volunteers, to make monthly meetings where one of our
contributors enlighten us with something about their culture; the idea
is to spread knowledge beyond just technology.
Also having a monthly short meeting to discuss those topics that might
need help (revisions on our politics, codes of conduct, an
anti-harassment paper, etc.) or just someone that wants to tell their
experiences. I’m interested into people knowing that Fedora has an
insane cultural background and maybe in a near future, this will open
the eyes of those who think that everything in Fedora is plain blue.”
---Snip---
This interview originally appeared as part of a larger article on the
Fedora Community Blog, titled "Women in Computing and Fedora". You're
encouraged to give it a read and share it with others in and out of
the community!
https://communityblog.fedoraproject.org/women-in-computing-and-fedora/
María is available weekly on Tuesdays at 12:30pm UTC in
#fedora-diversity on Freenode, where you are invited to stop by and
join the conversation.
Congratulations Tatica, and please all join me in giving her a warm
welcome to the Council :)
--RemyD.
--
Remy DeCausemaker
Fedora Community Lead & Council
<decause(a)redhat.com>
https://whatcanidoforfedora.org
7 years, 8 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, 8 months
Fedora Council IRC meeting Today in #fedora-meeting (18:00 UTC)
by Matthew Miller
Sorry, I forgot to send out an agenda last week.
This is a "Tickets & Ongoing" meeting — while our goal is to do regular
work without needing meetings to advance topics, reviewing monthly
makes sure we don't drop things.
Things I see:
1. Need topics/guests for upcoming subproject report sessions
2. Security Fad <https://fedorahosted.org/council/ticket/52>
- This actually already happened, so presumably the dollar amount is
known, if any. I'm not sure if budget is still requested.
3. Budget status? Almost April... do we know, yet?
4. Diversity advisor - user survey?
5. Update on refreshed university involvement objective
6. Update on proposed Python marketing objective?
7. Privacy policy proposal:
https://fedorahosted.org/council/ticket/53
7. Anything else?
I'm not sure we'll get through this in an hour, so let's move as
quickly as we can, and what we can't resolve in the meeting, handle in
tickets.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
7 years, 8 months
Suggestion about Fedora activity day acronym FAD
by pravin.d.s@gmail.com
Hi All,
FAD - an interest followed with exaggerated zeal; "he always follows the
latest fads"; "it was all the rage that season" [syn: {craze}, {furor},
{furore}, {cult}, {rage}]
During last G11N FAD, i got comment on Facebook post as follows:
*Ray Doc <https://www.facebook.com/raymond.doctor?fref=ufi>** I don't like
the acronym FAD. It basically means:an intense and widely shared enthusiasm
for something, especially one that is short-lived; a craze. Something
different by way of an Acronym would be better. This means that the action
is short-lived.*
And just saw one more. "Slightly unfortunate naming there – “Python 3
fad”" [1]
I think we should make sure to name it as "Fedora ---- activity day" i.e
Fedora python activity day. FPAD or "Fedora Globalization activity day"
FGAD.
Regards,
Pravin
1.
https://fedoramagazine.org/help-port-python-packages-python-3/#comment-45...
7 years, 8 months
Fedora Design Team FAD Proposal for July 2016
by Máirín Duffy
Hi Council!
As we alluded to during our council presentation last fall [1], the Fedora Design team would like to propose a Fedora Activity Day for July of this year. For our planned date, it'd be over a year and a half past the last FAD we had. Our last FAD was quite successful:
- We cleaned up our ticket queue (it remains clean after years of being a pit of despair!)
- We established a regular process for keeping on top of tickets (we still use it a year+ later, and it's working!)
- We reinstated regular team meetings - still going strong.
We are hoping to build on the same success and tackle one of our biggest weaknesses - recruitment - while also working on a project strategic to Fedora: Fedora Hubs.
We've put together a proposal with a rough budget. We're proposing to hold the event in the same location, so we have a solid idea of the lodging and food pricing, and the facility will be free of charge.
***
https://fedoraproject.org/wiki/FAD_DesignTeam_2016
***
I wanted to open our plans up for discussion here, make any needed revisions, and then I can file a ticket on the council trac to make it a formal agenda item. What do you think?
~m
[1] https://communityblog.fedoraproject.org/the-state-of-fedoras-design-team/
7 years, 8 months
proposed meeting schedule for upcoming months
by Matthew Miller
I'm assuming Monday at the same timeslot.
Feb 22 -- Tickets and Ongoing
Feb 29 -- Open Floor (and Leap Day!)
Mar 7 -- Subproject Report (TBD)
Mar 14 -- Review of Council Objectives (University, Modularization)
Mar 21 -- Tickets and Ongoing
Mar 28 -- Open Floor
Apr 4 -- Subproject Report (TBD)
Apr 11 -- Open Floor
Apr 18 -- Tickets and Ongoing
Apr 25 -- Open Floor
May 2 -- Subproject Report (TBD)
(and probably on in an similar manner from there)
Note that March 14 is right after the US switch to Daylight Saving
Time. Should we move our meeting with it? But, since the composition of
the council changes, it may be that the answer is different every time.
And the topic I've penciled in for that day isn't necessarily something
to solve in a meeting, but I wanted to get it on the table -- let's
talk about before then. The University Involvement initiative was
slated for having results in the 2015-2016 academic year. And, you
know, best laid plans and all that. And, the modularization initiative
was specifically supposed to be in phases, and so that needs to be
refreshed too. AND, there might be other things we might want to add.
(Fedora Hubs, maybe?)
For the subproject reports, what would people like to see? I'd be kind
of interested in seeing a demo of the state o xdg-app in Workstation,
as I know there's talk of having a prototype ostree-based workstation
with xdg-app as a F25 feature. Possibly we could have a report from
FAMSCo/FOSCo as that does (or doesn't?) get back up off the ground.
What else?
Also note that we should have a budget session, some point after the
budget actually drops. Probably will take over one of the Open Floors
for that.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
7 years, 8 months