[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
meeting today (17:00 UTC, #fedora-meeting)
by Matthew Miller
This is a tickets-and-ongoing-stuff meeting, or "closing loops".
The time-sensitive agenda item I see is the APAC planning FAD budget
request -- see https://fedorahosted.org/council/ticket/46 and
https://fedoraproject.org/wiki/FAD_Singapore_2015.
There are other open tickets at https://fedorahosted.org/council/report/1
... are there any particular items that we think will benefit from
real-time discussion? I'm going to take some time before the meeting to
comment on those that are left hanging, and I encourage everyone else
on the council to find some time sooner or later to do the same. :)
upcoming meeting schedule:
Nov 16: Open Floor
Nov 23: Skip for Thanksgiving week
Nov 30/Dec 7: Subproject report from __________ (Tickets/Ongoing other
week)
Dec 14: Open Floor
Dec 21: Skip for Holidays
Dec 28: Skip for Holidays
Jan 4: Open Floor
Jan 11: Tickets/Ongoing
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
7 years, 10 months
design team council presentation tomorrow, over IRC (note NOON US Eastern time)
by Matthew Miller
There will be slides, but the actual presentation and discussion in IRC
in #fedora-meeting.
The council meeting is specified as 17:00UTC. The United States has
just switched off DST, so that means an hour earlier than we've been
used to. If we want to change that, we should discuss. :)
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
7 years, 10 months
Followups from Council phone call monday — Budget discussion for this year and beyond
by Matthew Miller
Here's the rough notes from the call:
- Inside Red Hat, budget is due _way_ early now. We'll need to
adjust our planning around that. (Specifically, we need it in by
October.)
- This year's budget request is set as same as last year's; we
won't know for sure until possibly as late as March what we
actually get.
- In the future, we need to do our request planning in the Flock
timeframe. (Discussion before Flock, high-bandwidth in-person
session at Flock, followup and ratification after.)
- Council (and specifically Remy as community action/impact lead)
will work to thoroughly understand budget request, and then act
as contact for the finance people. Remy will also help maintain
an overall "state of the budget" document as we go through the
year.
- Given the long period between request and actual budget, makes
sense to also have a second round of planning at the start of the
fiscal year (which is March, and years are named after the one in
which they end, so we're in FY16 right now, and the upcoming
budget is FY17.)
- Right now, all money is allocated to ambassadors through regions,
including Flock and FUDCons, and except for FADs. We want to do
that differently for FY18 — probably split out at least Flock,
and have non-regional budget for marketing and other centralized
community activities.
- If we want to do more with our money, and request more as needed,
we need to make sure we're spending what we have already — the
Council should do a quarterly budget review with ambassadors (and
in future any other groups). In the future, "no budget" should
mean "no spending".
- NA ambassadors in particular need to get a budget organized. APAC
and LATAM need to get better at spending the money that's
budgeted.
- We want to ask for more money to grow Fedora. In order to do
that, we need to demostrate that the money we do have is being
spent well. Need ambassadors to connect spending to results in a
a way that _we_ can take to the budget people.
Not mentioned at the meeting, but a thing I'm concerned with and have
mentioned before: having a Fedora presence at conferences is good, but
is it the best use of Fedora money? Do we grow new users at Linux fests
in the 21st century? What things could we do instead?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
7 years, 10 months
Re: council/design meeting -- wait, can we do it at 18:00UTC instead? US Eastern time)
by Rex Dieter
On 11/02/2015 07:15 AM, Matthew Miller wrote:
> On Sun, Nov 01, 2015 at 07:20:29PM -0500, Matthew Miller wrote:
>> The council meeting is specified as 17:00UTC. The United States has
>> just switched off DST, so that means an hour earlier than we've been
>> used to. If we want to change that, we should discuss. :)
>
> Looks like I have a conflicting meeting from 11-1 EST (No lunch for
> me?!) -- will switching this to an hour later work for people?
ok with me
-- Rex
7 years, 10 months