On Apr 15, 2016 12:05, "Mark Terranova" <doctorfoss@xxxxxxxxx> wrote:
>
> Glad to see more TOSW applied. /me still has concern we are aiming for stasis, rather than growth. What about new contribs? They are joining and it seems to me that they will concern local folks- there is only so much money to go around. New contribs = less money for people's existing events. We are using old flawed budget process to make our new process.... the same numbers? Methinks that's folly. Acting like there were no flaws makes the new process dubious (unless growth is included.)
>
> As a Fedoran I'm starting to worry that CentOS is Daddy Shadowman's *new toy* (as some FOSSers have predicted) and we are being placated.
>
> https://www.redhat.com/en/about/press-releases/red-hat-reports-third-quarter-results-fiscal-year-2016 I see plenty of growth for RH, we make a good product/test bed. I can see how Cent can help, tho have concerns it's WHERE the new growth is planned.
>
> WHERE is Fedora's growth? When has that been planned?
>
> I salute the efforts here, but can see the Voice thing to help encourage more funding might be needed or its
>
> "Meet the new process (money), same as the old money,"
>
> -MD
The "same-as" numbers were already in our stars for this year, because we are actually seeing the results of the "same-as" process that we've always had. The new process officially started Q1FY17. If we wanted to make the case for growth in this cycle, that is something that needed to happen by the end of Q3FY16.
Shaking the magic-budget-8ball (my experience from this past year suggests), if we don't have proper reports from FY16 (last year,) the 2 full quarters of FY17 that we're going to (in theory) properly report by Q3FY17 in August will *not* be enough data on their own from which to reasonably make the case for growing the Fedora budget for FY18. We need at least a full cycle of data (which we can deliver with FY16 data included.)
I cannot promise that if we report all the spending, and all the events until Q3FY17 thoroughly and on time that that will guarantee we get an increase in FY18, but it does ensure that the budget process itself cannot be faulted as a reason for not growing.
And remember, even if we do it right, and establish these new good habits, it could still take more than one cycle to grow the budget. Budget cycles are slow-moving, annual cycles, in stark contrast to our fast-paced world of 6ish month (sometimes 2week or continuous) release cycles.
No one here, in the council, or OSAS, or Red Hat is mustache-twisting and plotting ways we can exploit, and/or burn out the community faster. Everyone here wants to grow--the budget, our Rel-eng capabilities, and our user and contributor bases. Promise.
I know what is going to take, and it's not simply saying "by virtue of having more money, you can afford to give us a larger piece of it."
There is a difference between advocating for a region (talk) and delivering the data from that region that can actually change our situation (action.) Everyone in the project can contribute in ways that justify growth--this is THE way that Ambassadors can help us grow the budget.
Numbers and metrics aren't just an "on paper" requirement, just some arbitrary hoop to jump through because of some asinine corporate ritual. They actually and substantially help us make more effective decisions, and increase (or at the very least approximate or measure) our impact per dollar spent.
That is how we make predictions, and show results.
That is how we test theories, and fail faster.
That is how we adjust strategy, and show how and why we grow.
Please, help me deliver these numbers.
Please, help me help Fedora.
--RemyD
> On Fri, Apr 15, 2016 at 6:15 AM, Remy DeCausemaker <decause@xxxxxxxxxx> wrote:
>>
>>
>> On Apr 14, 2016 20:12, "Josh Boyer" <jwboyer@xxxxxxxxxxxxxxxxx> wrote:
>> >
>> > On Thu, Apr 14, 2016 at 7:43 PM, Remy DeCausemaker <decause@xxxxxxxxxx> wrote:
>> > > Councils,
>> > >
>> > > Attached is a text file (and spreadsheet) with the scenarios we discussed
>> > > during our meeting.
>> >
>> > I'm going to guess D&I in the text file is Diversity and Inclusion?
>> > It isn't spelled out anywhere so I'd just like to clarify.
>>
>> Yes, that is correct. Diversity and inclusion.
>>
>> >
>> > > tl;dr - "Best Case Scenario" (lowest amount of Council/Events Budget) it's a
>> > > roughly 23% cut in budget for each region (except for APAC, but more on that
>> > > later)
>> > >
>> > > If you'd like to edit/adjust/append any info to these documents, they can be
>> > > found in the fedora-budget repo in FY17/adjustedannualbudget/council:
>> > >
>> > > https://pagure.io/fedora-budget
>> > >
>> > > Thanks mattdm for helping to hunt down this info, and I'll add more
>> > > historical information as it comes from Ambassadors.
>> >
>> > I would really really like to see actual numbers from FY16 from all
>> > the regions before we really commit to any percentages based on
>> > historical context. If we cannot get accurate reporting, we cannot do
>> > accurate planning.
>>
>> Gee whiz, me too! I've only been asking for the tallied reports for a month now via IRC, mailing list, telegram, ticket, and word of mouth--pretty much everything but carrier pigeon. The only fully reported region is EMEA, and even then I still need them to select their storyteller delegate. We have some reports from the other regions, but they are incomplete, and supposedly in the process being updated. I'll update the budget site, and repo, and council, as I get more information.
>>
>> Looking Forward,
>> --RemyD.
>>
>>
>> _______________________________________________
>> council-discuss mailing list
>> council-discuss@xxxxxxxxxxxxxxxxxxxxxxx
>> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>> http://lists.fedoraproject.org/admin/lists/council-discuss@xxxxxxxxxxxxxxxxxxxxxxx
>>
>> The Fedora Project's mission is to lead the advancement of free and
>> open source software and content as a collaborative community.
>
>
>
> _______________________________________________
> council-discuss mailing list
> council-discuss@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> http://lists.fedoraproject.org/admin/lists/council-discuss@xxxxxxxxxxxxxxxxxxxxxxx
>
> The Fedora Project's mission is to lead the advancement of free and
> open source software and content as a collaborative community.
_______________________________________________ council-discuss mailing list council-discuss@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct http://lists.fedoraproject.org/admin/lists/council-discuss@xxxxxxxxxxxxxxxxxxxxxxx The Fedora Project's mission is to lead the advancement of free and open source software and content as a collaborative community.
