Re: [Ambassadors] the "premier" label [was Re: Fedora Budget.next - https://fedoraproject.org/wiki/Budget.next]
by Truong Anh Tuan
----- On Nov 6, 2015, at 11:15 PM, Josh Boyer jwboyer(a)fedoraproject.org wrote:
> On Fri, Nov 6, 2015 at 10:51 AM, Matthew Miller
> <mattdm(a)fedoraproject.org> wrote:
>> On Fri, Nov 06, 2015 at 09:11:45AM -0600, inode0 wrote:
>>> > - I would almost prefer to see premier events not be split out
>>> > separately, and instead force the Council to transparently allocate
>>> It isn't quite clear to me if the Fedora Premier Events are still
>>> intended to be the responsibility of OSAS or of the Council. I think
>>> moving them to the Council, whether lumped with Discretionary Council
>>> Budget or not would be good for transparency and Council flexibility.
>>
>> From the wiki, the word "premier" label means:
>>
>> * organized by the Fedora community
>> * all about Fedora
>>
>> I find this a little odd, because the word literally means "most
>> important or best", and I don't think that's actually what we mean.
>>
>> My preference would be to not use this label for FADs. If we want to
>> keep using the word, let's call Flock _the_ premier global Fedora
>> event, and FUDCons premier regional events. I don't think we even need
>> a special term for FADs.
>
> Agreed.
+1 too. FAD is smaller than Flock or FUDCon. Some FADs are less than 10
attendees.
The process to organize a FAD is also different from FUDCon/Flock's one
and budget allocation process should be different too.
>> And, I think *some* FADs make sense from the central community budget
>> (whether we call that the Council budget or something else), while
>> others — like the ambassadors' planning FADs — make sense to me to be
>> part of the regional budgets directly.
>
> Also agreed. E.g. a rel-eng FAD would likely come from the central budget.
+1 too. This could make regional community more active.
>> This implies regionalizing some things which have not been
>> traditionally in the ambassadors scope — for example, a translation
>> activity day focused a language or languages of a region might be best
>> planned and organized within that region.
>
> Yes. Though it might require us to examine the regional budget
> allocation a bit more closely after the first year to make sure
> regions are getting enough budget to cover such things.
+1. Actually, we are doing something similar this.
Rgds,
Tuan
8 years, 4 months
Fedora Budget.next -, https://fedoraproject.org/wiki/Budget.next
by Ben Williams
OK Remy
Afew questions
1) on your .next page it has quarterly reports are those reported by the regions or by Redhat or both
2) it lists Quarterly Budgets, so if we are under budget on one quarter do we keep that money or (use it or lose it) is it lost?
Date: Wed, 4 Nov 2015 23:35:35 -0500
From: Remy DeCausemaker<decause(a)redhat.com>
To:ambassadors@lists.fedoraproject.org,
famsco(a)lists.fedoraproject.org, Discussions with the Fedora Council
and community <council-discuss(a)lists.fedoraproject.org>
Subject: [Ambassadors] Fedora Budget.next -
https://fedoraproject.org/wiki/Budget.next
Message-ID:
<CALiMsejHV-JvD+h+chLBsXfmxquy-J5Gt8Mn3X9JCWie4FKLMw(a)mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Ambassadors,
As some of you may be aware, there have been some changes to how Budget is
proposed and allocated for the coming fiscal year. This conversation has
been happening on the Council-discuss list, and through meetings with
members of the OSAS team:
https://lists.fedoraproject.org/pipermail/council-discuss/2015-October/01...
With input from the council, OSAS, and other Ambassador Leads, I've taken
the results of these budget meetings up until this point, and the
discussions around FOSCo/FAMSCo, and created a wiki page to help explain
our best understanding of how things should work going forward. The policy
seen here is a blend of the results from public discussions and meetings
over the past year on mailing lists, in IRC, and at FLOCK:
https://fedoraproject.org/wiki/Budget.next
*tl;dr* - We're proposing 3 delegated roles in each ambassadorial region
for treasurer, logistics, and storytelling. We're keeping our reimbursement
and other policies as close to the same as possible. There is a now
quarterly budget timeline with scheduled FADs and planning. There will be a
webpage available in the near-ish future athttp://budget.fedoraproject.org
where folks can find the budget and policies related to it.
This is not a permanent, set-in-stone policy, but we need to start
somewhere, beginning with the new budget year (FY17) and the next Fedora
Release (F24.) We can always come back and tinker and change what is on
that wiki page, but for now, this is what we'd like to propose to close the
loop on budget.
Please read the wiki page, as the daemon is always in the details, and we
can use as much informed input and feedback as we can get. I'm hoping to
spend about a week gathering feedback, and then move forward implementing
these new budget processes together with all of you
Thank you Ambassador Leads and fellow council members for your early input
and efforts on this. Your feedback helped to round off some of the rough
corners, and provided a consistent reminder to adhere to the Fedora-way of
defaulting to open.
This formalized regional approach to budget is the first step in working
out a larger community-wide strategy around integrating subprojects and
other Fedora constituencies with eachother--but that will be a whole nother
conversation after this one.
Looking Forward,
--RemyD.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:<http://lists.fedoraproject.org/pipermail/ambassadors/attachments/20151104...>
8 years, 4 months
Re: [Ambassadors] the "premier" label [was Re: Fedora Budget.next - https://fedoraproject.org/wiki/Budget.next]
by Matthew Miller
On Fri, Nov 06, 2015 at 11:15:49AM -0500, Josh Boyer wrote:
> > My preference would be to not use this label for FADs. If we want to
> > keep using the word, let's call Flock _the_ premier global Fedora
> > event, and FUDCons premier regional events. I don't think we even need
> > a special term for FADs.
> Agreed.
Cool. Unless someone has an objection, I'll update the wiki to reflect
this in a little bit.
> Yes. Though it might require us to examine the regional budget
> allocation a bit more closely after the first year to make sure
> regions are getting enough budget to cover such things.
Yeah — this isn't a plan to squeeze people or anything.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
8 years, 4 months
Fwd: Fedora Ambassador
by Remy DeCausemaker
Welcome Back LordDrachenblut!
We're thrilled that you would like to represent Fedora at SCALE!
Below you will find a number of links to places where you can find the
specific information you requested, but first, you should absolutely join
#fedora-ambassadors on Freenode and hang out there (My nick is decause if
ever you want to ping me directly :) ), and subscribe to the ambassadors'
mailing list if you haven't already.
General Ambassador Information:
https://fedoraproject.org/wiki/Ambassadors
Specific Ambassador Information:
https://fedoraproject.org/wiki/Ambassadors_FAQ
Each Region has their own rules/policies for the most part, but for North
America, all the places you want to request resources that require private
information like shipping addresses (which includes things like Swag) can
be routed through the FAMNA request tracker here:
https://fedorahosted.org/famnarequests/
You'll need to go through the process of officially becoming a North
American Ambassador (instructions here:
https://fedoraproject.org/wiki/Ambassadors_Join_start?rd=Ambassadors/Join )
but after that you can request swag for the event via the FAMNA request
tracker above.
As far as travel reimbursement, the Wiki page for that can be found here:
https://fedoraproject.org/wiki/Reimbursements
If you have other questions, stop by IRC and ask. My advice to you would be
that since Ambassadors are almost entirely volunteer driven, that you give
yourself *ample* time to apply and coordinate, and get your requests
submitted asap.
Good Luck, Happy Hacking, and see you in channel :)
--RemyD.
P.S. - You can also join #fedora-commops and #fedora-join on Freenode if
you're looking for other new-contributor-focused groups within the project.
---------- Forwarded message ----------
From: "Brian Proffitt" <bproffit(a)redhat.com>
Date: Nov 3, 2015 2:28 PM
Subject: Fedora Ambassador
To: "Remy DeCausemaker" <rdecause(a)redhat.com>
Cc:
Remy:
Matt Williams (Lord Drachenblut) has put in some Fedora talks at SCALE this
January and wanted to know the process to apply for travel assistance as a
Fedora rep.
Also, he wanted to know how he could get some swag (stickers, etc) to pass
out at local meetups?
Peace,
Brian
--
Brian Proffitt
Principal Community Analyst
Open Source and Standards
@TheTechScribe
8 years, 4 months
Fedora Budget.next - https://fedoraproject.org/wiki/Budget.next
by Remy DeCausemaker
Ambassadors,
As some of you may be aware, there have been some changes to how Budget is
proposed and allocated for the coming fiscal year. This conversation has
been happening on the Council-discuss list, and through meetings with
members of the OSAS team:
https://lists.fedoraproject.org/pipermail/council-discuss/2015-October/01...
With input from the council, OSAS, and other Ambassador Leads, I've taken
the results of these budget meetings up until this point, and the
discussions around FOSCo/FAMSCo, and created a wiki page to help explain
our best understanding of how things should work going forward. The policy
seen here is a blend of the results from public discussions and meetings
over the past year on mailing lists, in IRC, and at FLOCK:
https://fedoraproject.org/wiki/Budget.next
*tl;dr* - We're proposing 3 delegated roles in each ambassadorial region
for treasurer, logistics, and storytelling. We're keeping our reimbursement
and other policies as close to the same as possible. There is a now
quarterly budget timeline with scheduled FADs and planning. There will be a
webpage available in the near-ish future at http://budget.fedoraproject.org
where folks can find the budget and policies related to it.
This is not a permanent, set-in-stone policy, but we need to start
somewhere, beginning with the new budget year (FY17) and the next Fedora
Release (F24.) We can always come back and tinker and change what is on
that wiki page, but for now, this is what we'd like to propose to close the
loop on budget.
Please read the wiki page, as the daemon is always in the details, and we
can use as much informed input and feedback as we can get. I'm hoping to
spend about a week gathering feedback, and then move forward implementing
these new budget processes together with all of you :)
Thank you Ambassador Leads and fellow council members for your early input
and efforts on this. Your feedback helped to round off some of the rough
corners, and provided a consistent reminder to adhere to the Fedora-way of
defaulting to open.
This formalized regional approach to budget is the first step in working
out a larger community-wide strategy around integrating subprojects and
other Fedora constituencies with eachother--but that will be a whole nother
conversation after this one.
Looking Forward,
--RemyD.
8 years, 4 months