https://fedoraproject.org/wiki/Meeting:Board_strategic_working_group_2010-03-01 == Roll Call == * Attendees: John Poelstra, Paul Frields, Chris Tyler, Mike McGrath, Colin Walters, Matt Domsch * Notes from last meeting: https://fedoraproject.org/wiki/Meeting:Board_strategic_working_group_2010-02-22 == Spins Work == * Background: ** Matt and Colin have been collecting feedback to questions asked ** https://fedoraproject.org/wiki/User:Walters/SpinsSigsRemixes_TargetAudience ** https://fedoraproject.org/wiki/User:Walters/SpinsSigsRemixes_ChangeDistribution ** http://lists.fedoraproject.org/pipermail/spins/2010-February/000996.html ** https://fedoraproject.org/wiki/User:Mdomsch/SWG_Spins * Each spin producing group does believe they can and should define a target audience * John: would it help clarify our message to refer to the live gnome desktop as the ''default offering'' rather than referring to it as a spin? ** Paul: Spins were initially conceived as a range of things the community can produce that are alternatives to what we feel must be created, or add-ons that narrowly focus on special use cases * Matt: Rel-eng sits in the middle of the spin creation process right now -- a couple communication breakdowns have happened over time, sometimes spin producers didn't know their spin was being built ** Matt: semi-OT -- at some point need to reconsider the question of who builds the spins. Does it always have to be Release Engineering? ** Paul: more narrowly aimed spins (FEL, Games, ...) seem to nail their use cases quite well * Top of mind problem seems to be some dependency chains (system-config-keyboard), whether or not that is the most serious problem or not isn't clear * '''PAIN POINT IDENTIFIED''': Dependency chain requirements cause alternate desktop spins to still pull in a large portion of the GNOME stack. ** '''NEXT STEPS''': Mike will file ticket with FESCo requesting they look at dependency chain requirements. This could be a Fedora Engineering Services task. ** Colin willing to look at helping with dependency chain issues ** ''TICKET''': https://fedorahosted.org/fesco/ticket/345 * '''NON PAIN POINT''': Spins SIG does feel that resolution processes have been working well when they're needed. * Resources: ** Infrastructure now has the ability to host additional content, including spins. This has been a long time incoming, and needs to be implemented and announced, but the capacity is there now. ** Ambassadors who want to pass out specific spins can make requests for monetary resources to CommArch, to be evaluated in the scope of media requests and budget. *** The Board is not taking a stance on what medias should be produced for any particular event. * Not sure what to do with feedback from survey work that showed that some people don't want the board to help or ask questions about how they can help === Next Steps & Positive Outcomes === # dependency chain requirements #* https://fedorahosted.org/fesco/ticket/345 # hosting space for Spins #* Each spin should file a request for space with infrastructure # (tentative) being able to offer AutoQA #* individual Spins should get involved with QA Team to ensure their needs are addressed as well as those of the rest of the Project. # banners on get.fp.o #* https://fedorahosted.org/fedora-websites/ticket/16 # Update wiki pages for information collected == Default Offering == * https://fedoraproject.org/wiki/User:Pfrields/Current_default_offering * https://fedoraproject.org/wiki/User:Pfrields/Different_default_offering * Give feedback to Paul by tomorrow, 2010-03-02 * Paul will send to Board for approval on 2010-03-02 == Topics and plan for next meeting == * John/Chris will take up topic of "What is a target audience?" * Meet next week, 2010-03-08 at 20:00 UTC (3:00pm EST/12:00pm PST) _______________________________________________ advisory-board mailing list advisory-board@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/advisory-board
