council January 2015

council-discuss@lists.fedoraproject.org

2 participants
6 discussions

[council] #16: Periodic contributor survey
by fedora-badges 07 Nov '16

07 Nov '16

#16: Periodic contributor survey ---------------------+------------------- Reporter: mattdm | Owner: Status: new | Priority: normal Component: General | Keywords: ---------------------+------------------- This is a tracking ticket for establishing a process by which we get regular feedback from the Fedora contributor base. This is a companion to https://fedorahosted.org/council/ticket/1. The desired goals, methodology, and basically everything else are really different between users and contributors it will be better to track them separately. -- Ticket URL: <https://fedorahosted.org/council/ticket/16> council <https://fedorahosted.org/council> Fedora Project Board Public Tickets

1 3

[council] #17: Objective proposal: Fedora Flavors Phase 2
by fedora-badges 29 May '15

29 May '15

#17: Objective proposal: Fedora Flavors Phase 2 ------------------------+------------------- Reporter: mattdm | Owner: Status: new | Priority: normal Component: Objectives | Keywords: ------------------------+------------------- I posted this on [https://lists.fedoraproject.org/pipermail/council- discuss/2014-December/013066.html council-discuss] a few weeks ago and there was a little discussion. Because this is really a continuation of something we've previously agreed to, I think this is straightforward. Since objectives are non-trivial, we should go for the "full +3 with no -1s" consensus, but also, since this has technical components which impact F22 planning -- which is starting now! -- I'd like to have the final decision as soon as possible. = Objective: Fedora Flavors, Second Phase. = Overview: * Take the initial Server/Workstation/Cloud split from Fedora 21 from an experiment into solid production. Increase autonomy from FESCo and improve targetted outreach. Expected Impact: * Increased user base and user satisfaction in targetted areas. Increased contributor community around the targets. Increased ability to adapt to future or expanded targets as needed. Timeframe: * Although we expect the "Fedora flavors" concept to be ongoing, this "second phase" is targetted for the F22 and F23 releases, making it an approximately 12-month objective. That way, this council objective lead slot will be open shortly after Flock 2015. Aspects: - Coordinate Working Groups' development of updated PRDs and changes and features for each release. - Work with FESCo and Fedora Program Manager to develop process whereby flavor-specific Changes are handled primarily at the WG level. - Work with Outreach (marketing, ambassadors, etc.) to identify and plan representation at new conferences specific to the various target audiences. - Plan, coordinate, and schedule release engineering and infrastructure changes in advance of the F22 and F23 alpha releases. - Lay groundwork for possible different release cycles and lifespans. - Tooling and infrastructure for spins and remixes to increase differentiation. # _Note: perhaps this is big enough to be an independent objective of its own, along with better promotion for spins._ - Work with Council and community to develop concrete process for expansion (or possible contraction) of Fedora flavors as identified needs change, working from the product definition previously approved by the Board Metrics: - PRDs updated. Changes filed, changes accepted, changes completed. - Conference reports; user data from those conferences. - User and contributor surveys, and other user and contributor measures - Usability is increased as measured by user testing specific to each target group ---- (My only regret here is that we are not up to Phase Four, for full-on Fedora alliteration.) ---- Additionally, I would like to nominate Stephen Gallagher for the role of Objective Lead. Stephen brought the "three products" idea to Fedora.next, was instrumental in its realization in the F21 release, and, also, tells me that he will have significant time to dedicate to this over the next year. (Please vote on this nomination as a separate +1/-1 along with any +1 votes to the proposal overall.) -- Ticket URL: <https://fedorahosted.org/council/ticket/17> council <https://fedorahosted.org/council> Fedora Council Public Tickets

1 27

[council] #18: decision on reverting start.fpo change
by fedora-badges 27 Apr '15

27 Apr '15

#18: decision on reverting start.fpo change ---------------------+------------------- Reporter: mattdm | Owner: Status: new | Priority: normal Component: General | Keywords: ---------------------+------------------- See https://lists.fedoraproject.org/pipermail/council- discuss/2014-November/013049.html We don't have complete project consensus, which is why the Firefox maintainer asked for a council decision. I think, though, that we _do_ have council consensus, at least based on everyone I've heard from. So, the proposal is: > Please revert the Firefox start page to http://start.fedoraproject.org/. Future improvements for usability or other enhancements can be made for the F22 timeframe or beyond, taking both user experience design and other Fedora stakeholders like marketing and outreach into account. Since F21 has already shipped, the urgency has decreased, but assuming this passes, let's get it reset for the next update for for F22 by default in absence of another plan. I'm proposing this as a lazy approval decision (see [http://fedoraproject.org/wiki/Council#Making_Decisions Making Decisions], and since the holidays are upon us, let's make the timeframe for votes be the rest of December. -- Ticket URL: <https://fedorahosted.org/council/ticket/18> council <https://fedorahosted.org/council> Fedora Council Public Tickets

1 13

[council] #19: new terminology for cloud/server/workstation
by fedora-badges 27 Apr '15

27 Apr '15

#19: new terminology for cloud/server/workstation -------------------------+------------------- Reporter: mattdm | Owner: Status: new | Priority: normal Component: Fedora.next | Keywords: -------------------------+------------------- We've been using the term "product" to refer to the different Fedora variants produced and marketed as part of the new (or by now, not so new) Fedora.next plan. This has a number of problems -- we're not actually selling anything, and we don't want to give that impression. And some spins users have expressed that it doesn't carry the meaning that we did intend very well. So, we're looking for something new. I had suggested "flavors", but that has its own problems: it's idiomatic, doesn't translate well, and apparently I'm the only one that likes it. :) So let's find something else. -- Ticket URL: <https://fedorahosted.org/council/ticket/19> council <https://fedorahosted.org/council> Fedora Council Public Tickets

1 37

[council] #20: Request to extend the mandate of current members of FAmSCo
by fedora-badges 16 Mar '15

16 Mar '15

#20: Request to extend the mandate of current members of FAmSCo -----------------------+------------------ Reporter: eischmann | Owner: Status: new | Priority: major Component: Other | Keywords: -----------------------+------------------ Hi, we're currently figuring out how to reorganize the outreach part of the Project to meet today's needs better. FAmSCo most likely will be dissolved and replaced by FOSCo. In FAmSCo [1], we agree that it doesn't make much sense to organize elections to a body that is going to cease to exist in a couple of months. Instead we'd like to ask the Council as a higher authority to extend our mandate till the F22 release to figure out a new governance model and make a transition from FAmSCo to FOSCo. The new elections should already be to the new body after F22. [1] http://meetbot.fedoraproject.org/fedora- meeting-2/2014-11-25/famsco_2014-11-25.2014-11-25-16.00.html -- Ticket URL: <https://fedorahosted.org/council/ticket/20> council <https://fedorahosted.org/council> Fedora Council Public Tickets

1 5

getting things rolling again
by Matthew Miller 28 Jan '15

28 Jan '15

Okay, so, kind of quiet in here. This has been largely on me, with a slow start to the new year -- vacation, sick kid, sick *me*, blizzard, and now travel, travel, travel. So so many excuses. But, ah well, moving on. :) I think most or all of the current council will be at DevConf.cz in Brno in a week or two, so we should definitely meet in person and talk at that point. But we're accumulating a number of other things to talk about too, and we also don't want to hold the action to in-person meetings. So, things to talk about, in no particular order: 1. Fedora project objectives, including the next-phase-of-products one we're 95% of the way towards officially endorsing (I know I owe y'all an update on that proposal -- I'll put it in the wiki), but also we have slots for several more. What should go in those? I'm to see a proposal around containerization. But what else? 2. Diversity advisor -- I'm planning to put together a search committee for this, and will ask for volunteers for that soon. 3. The Outreach steering committee -- progress, status, etc. 4. Community Working Group.... does not seem very active, but we've got a number of contentious personal issues which could be worked on. What to do? And others? -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

MOVED to https://discussion.fedoraproject.org/tag/council January 2015