design-team June 2009

design-team@lists.fedoraproject.org

56 participants
42 discussions

Release artwork process
by Martin Sourada 14 Jul '09

14 Jul '09

Hi all, based on a discussion in another thread, I've put together a skeleton DRAFT of our new release artwork process [1] so that we have something to work with. I was pretty brief with the wording, so it will probably need an expansion. Feel free to add your comments/edits/... :-) The ultimate goal is to get it finished and officially accepted sometime around FUDCon so that we can start on next release using this new process. I think it would also be useful to also keep release specific sub-pages with exact dates and perhaps a task list (can be a reference to a milestone in our ticket system) included. Martin References: [1] https://fedoraproject.org/wiki/Design/DRAFTS/Release_Artwork_Process

3 6

Design Team meetings on IRC?
by John Poelstra 09 Jul '09

09 Jul '09

Reading the other recent posts it seems there are a few unresolved issues that we need to get rolling on for Fedora 12. Does the Design Team have regular weekly meetings? If not would it consider having them to discuss the schedule for Fedora 12 and resolve which approach will be used to design the artwork for Fedora 12? I'd be willing to help organize and lead the meetings for the first month to help get things off the ground. Thanks, John

2 5

Constantine
by Nicu Buculei 07 Jul '09

07 Jul '09

I am sure you are all already aware, the announcement is official since yesterday when Paul delivered in in front of the FUDCon audience, the release name for Fedora 12 was voted Constantine. When I think about it, I had in my mind Byzantine culture (Roman emperor Constantine the Great) and I think a graphic in the style of a Byzantine mosaic can be an effective approach. The major trick is to leave out any religious implications and stay only with cultural references. Think of something like http://www.flickr.com/photos/gauiscaecilius/2139332420/ but with some modernist imagery and some blue. It also can work like this http://www.flickr.com/photos/gauiscaecilius/2140942774/ with the symbols for our 4 foundations. Get a better idea from those photos: http://www.flickr.com/photos/gauiscaecilius/tags/mosaic/ I talked about this yesterday evening (night) with Mo and Paul and today with Samuele (FUDCon is awesome for such things) and it seems the idea hs some potential.

18 36

CMS (Zikula) kick-off
by John Poelstra 02 Jul '09

02 Jul '09

Hi, I've volunteered to help kick off and facilitate the Fedora cross-team CMS (Zicula) planning and implementation meetings. I think things will work best if each team puts forth a representative. We will hold our meetings on IRC or over Fedora Talk and they will be open to anyone, but it will make it easier to schedule and coordinate the meetings if I know who the key people from each team are. I believe the key teams we need representatives from are: Documentation, Design, and Marketing. Are there any others? Once I know who the key people are I'll reach out to those people to find a meeting time and day that works best. I'd like to get a response by Thursday, June 25, 2009, so we can kick things off. Thanks, John

5 7

Re: [Design-team] Constantine
by brian hurren 01 Jul '09

01 Jul '09

here is a thought. Constantine is also a city, what about having an abstract of a city scape. here is a link to a photo of the city of Constantine http://img61.imageshack.us/img61/6965/con5nd2.jpg or we could do the aerial view of a city, looking down on it so that it fulls the screen. then it could represent connectivity and sharing, networking, what linux and Fedora a good at. It would be an easy concept to abstract. --- On Wed, 1/7/09, María Leandro <tatica(a)fedoraproject.org> wrote: From: María Leandro <tatica(a)fedoraproject.org> Subject: Re: [Design-team] Constantine To: "Fedora Design Team" <design-team(a)lists.fedoraproject.org> Received: Wednesday, 1 July, 2009, 6:10 PM I don't have words..... only graphic ideas on my head :S . I'll work on some stuff, now that I'm back in Venezuela ... btw, awesome brainstorm. 2009/6/30 Luya Tshimbalanga <luya_tfz(a)thefinalzone.net>: > Lets not forget about bay leaves crow seem on most Roman emperors. Those > bay leaves could be subtle in background. As for mosaic, I think the > concept should not be too complex unless someone know to effectively > render them as wallpaper. > _______________________________________________ > design-team mailing list > design-team(a)lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/design-team > -- tatica Maria Gracia Leandro http://www.tatica.org http://www.iseit.net http://www.latinux.org http://www.latinux.com http://www.fedora-ve.org http://fedoraproject.org/wiki/MariaLeandro LinuxUser= 440285 GPG Public Key: E1CDCC56 "Be yourself... Don't be anyone else" _______________________________________________ design-team mailing list design-team(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/design-team

6 6

Sorry for the NOise. Forwards?
by Frank Murphy 30 Jun '09

30 Jun '09

Sorry about any Noise Occasionnally, the other lists get Q? re . Fedora provided Image apps\formats. Would it be ok, for me to forward those. Without throwing the teams work-flow. eg: https://www.redhat.com/archives/fedora-ambassadors-list/2009-June/msg00328.… Frank -- jabber | msn | skype: frankly3d http://www.frankly3d.com http://fedoraproject.org/wiki/SIGs/Development

3 4

Re: [Design-team] Constantine
by Storari Samuele 29 Jun '09

29 Jun '09

Hi all, I talked with Nicu about the Mosaic Theme at Fudcon just yesterday, and I think will be a good idea to work on. Maybe not as a mosaic effect, but a mosaic "subject". We can also think to an "Innovation Theme" cos Constantine the Emperor was the first to allow the Christian Religion all around the Roman Emp. so we can work on the innovation aspect and not on the religious side of the approach, maybe it will work. So another idea we can work on is a "spiritual Focused theme", 'cause Constantine decide to allow the religion only before dyin'; and for SPIRITUAL I don't mean RELIGIOUS focused but something about the "Soul" and the Soul is common to every people in the world. Maybe I can work on some other idea in those days so we can try to work on some little mockup. Samuele ----- Original Message ----- From: "Luya Tshimbalanga" <luya(a)fedoraproject.org> To: "Fedora Design Team" <design-team(a)lists.fedoraproject.org> Sent: Monday, 29 June, 2009 10:32:59 GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna Subject: Re: [Design-team] Constantine Lets not forget about bay leaves crow seem on most Roman emperors. Those bay leaves could be subtle in background. As for mosaic, I think the concept should not be too complex unless someone know to effectively render them as wallpaper. _______________________________________________ design-team mailing list design-team(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/design-team -- Samuele Storari Art Director Byte-Code srl mobile: +39 347 50 798 32 office: +39 02 9840047 http://www.byte-code.com

3 3

Fedora 11 Retrospective Recap
by John Poelstra 23 Jun '09

23 Jun '09

Fedora 11 Retrospective Recap 2009-06-16 Wiki version: https://fedoraproject.org/wiki/Fedora_11_Retrospective_Notes Invitees: Cross section of people and leads from each group: https://fedoraproject.org/wiki/Fedora_11_Retrospective_Invitees Attendees: James Laska, Bruno Wolff, Jóhann B. Guðmundsson, John McDonough, Jon Stanley, Jarod Wilson, Todd Zullinger, Ricky Zhou, Steven Moix, Mike McGrath,Jack Aboutboul, Paul Frields, Eric Christensen, John Poelstra, Edward Kirk, Adam Williamson, Máirín Duffy, and Jesse Keating Unrepresented Teams: Ambassadors, Translation Location: Global teleconferencing system & Fedora Gobby When: 2009-06-16 @ 14:00 UTC == Meeting Guidelines & Agenda == 1) Each person gets five minutes to say whatever they want. Suggested questions to answer: a) What went well? b) What could have gone better? c) If time and resources were not an issue, what three things would make Fedora 12 our best release ever? 2) While the speaker has the floor nobody can interrupt or correct what they are saying --there are no "wrong" ideas --other participants can seek clarification from speaker after they are done 3) Other attendees will help capture points raised in gobby 4) Open discussion and go forward plans after each person has had an opportunity to speak == Meeting Outcomes == o Individual feedback (see below) o John Poelstra will create a wiki version of these notes and post link to in email recap to fedora-advisory-board --https://fedoraproject.org/wiki/Fedora_11_Retrospective_Notes o Jesse suggested checking back in a month to see how we are doing on the things we said we said we wanted to change --email is fine; telephone not required o Jesse strongly urged people on the call to take the proposals from the recent FAD back to their teams --feedback needed ASAP --will affect many parts of Fedora --https://fedoraproject.org/wiki/Fedora_Activity_Day_Fedora_Development_Cycle_2009#Resulting_Output o John Poelstra encourage attendees to blog about this meeting to give a wider audience an understanding of what the meeting was like and what they thought about it o The Fedora CMS (Zicula) will affect a lot of groups in Fedora --We need a point person to coordinate these efforts for our greatest chance at success --No one has been identified o ADDED AFTER THE FACT by John Poelstra --Anyone is free to tag onto the end of the wiki document to add their own feedback --https://fedoraproject.org/wiki/Fedora_11_Retrospective_Notes#Additional_Feedback_Outside_of_the_Meeting == Legend == (+) Went well (-) Could have gone better (w) Wish-list--no limits--everyone CAN have a pony == Jon Stanley (jds2001) - fesco == (+) Feature process went well --good contingency plans (-) X item fell through the cracks (-) Meeting minutes creation failed (+) Started using a minute meeting bot (w) Massive QA testing (w) Earlier freezing/branching for critical packages == Eric Christensen (Sparks) - docs == (-) Release notes churn at the last minute --some is legitimately unforeseen, other notes just not timely enough (-) docs.fedoraproject.org page doesn't flow well --languages hard to find (+) Turned out more guides and docs than past releases (+) use of Red Hat guides that were relicensed (w) Zikula CMS --will replace the existing docs.fp.o (w) standardize and focus on release notes and meet more users point == Jarod Wilson (j-rod) - FESCo == (+) Feature process went smoothly--deadlines understood and less confusion (+) No major disagreements within FESCo (-) No major disagreements within FESCo (-) Meeting minutes (-) Collection of public feedback not optimal (need more _constructive_ feedback) (-) Secondary architecture team updates (w) Focused Fedora kernel QA effort--build up community == John J. McDonough (jjmcd) - docs == (+) people were great (+) use of publican went surprisingly well (+) install guide is the best we've ever had (-) integrating milestones better into schedule (-) pushing to docs.fedoraproject.org is an ugly process --Too many formats (-) Need more packagers on the docs team (w) More engagement with developers/determining who to talk to (w) PackageKit get fixed --problems finding application to click on (w) Problems with wireless on NetworkManager == Edward Kirk (tk009) - BugZappers == (+) Communication really good about what was going on between all the teams and across the project (+) More people are joining the project and contributing (-) Blocker bugs were not handled very well (-) Problems at the end with Anaconda --identifying blocker bugs before the last minute (w) A more solid, stable release that is technically better than anything else out there == James Laska (jlaska) - QA == (+) 20 test days--way more than F10 (+) Documentation around test days and how to create live images, etc. (+) Test results reporting (+) Common F11 Bugs --multiple teams were invested in success (+) Community testing (-) No specific test days for Sound (-) No concept of capacity (-) Clarify hand off procedures between Release Engineering & QA for RC --"who has the ball?" (-) Transparency around release readiness decision and whether to slip --public discussion & publish minutes (-) Automation of testing (-) No metrics around health of QA community (w) Micro-communities around each of the features --specific dashboard --blocker bug tracking (w) Community test case management system == Adam Williamson (adamw) - QA/BugZappers == (-) reading several reviews that Fedora 11 is un-installable (-) unclear how to get in late release notes additions in a cooperative way (+) Test Days were fantastic (+) BugZappers and QA wiki spaces were substantially revised (w) A massive testing lab (w) Improving kernel triage for future releases == Bruno Wolff - Games Spin == (+) Help from Jeremy Katz to enhance livecd-tools for larger games iso size (+) Rawhide updates come quickly from the mirrors and Koji (+) test days were helpful and gave focus to people (+) New Spin process documentation got developed --specific test instructions are now available (-) Broken installer and video got in the way of testing --painful when rawhide was broken (-) We don't have a process for maintaining recurring spins (w) Less broken stuff (w) Spins process document finished (w) Lots of test days (w) More with live USB with persistent storage == Jack Aboutboul & Steven Moix - Marketing == (+) Lots of progress restructuring the marketing team (+) Release schedule helped cross team coordination (-) Need to identify task inter dependencies and add them to the schedule (-) Better capture things that get accomplished (+) Inter group communication with Art, Translation, etc. (w) Host mini-meetings with different teams throughout the release cycle (+) Continuous content production --building up and telling stories (w) Fedora Magazine (+) Tracking press reports in different languages (w) Finding a better way to do metrics to identify how far our reach is and understand audience (w) More marketing to younger audiences and greater public awareness == Ricky Zhou - Websites== (+) two or three people helping consistently with Web team tasks (-) Late changes from marketing and docs team which had minor impact (w) Add a review period so that issues can be identified and corrected before release == Mairin Duffy - Design == (-) Need to see feedback to the Design list as opposed to sprung on blogs (w) Six more designers on the team! (w) pink pony!!!!11!! == Jesse Keating - Release Engineering == (+) Better involvement with QA and Triage --improved confidence in QA beating on the trees (+) Did a better job of managing the blocker lists (+) Good help from others verifying blocker bugs (+) Test Days ... more feature owners are requesting targeted testing (+) No last minute compose-related surprises (-) Better communication around what testing needs to be done --improve capture of testing outside of the matrix (mailing lists) (-) Clearer guidelines around code changes (+) FAD Proposals - https://fedoraproject.org/wiki/Fedora_Activity_Day_Fedora_Development_Cycle… (w) earlier review blocker bugs --maybe weekly after we branch (w) automated QA which provides automatic feedback == Jóhann B. Guðmundsson - QA Team== (w) Taking test days to the next level --improved advertisement --re-use live images for additional testing (w) coordinate with upstream testing (w) litmus testing system added to Fedora --litmus is coded to be quite mozilla-specific (according to jlaska) (w) Use of Fedora QA Trac system to track request from maintainers (w) Host test day without requiring maintainer present (-) lack consensus amongst maintainers if a reporter is supposed to report to our bugzilla or upstream one (w) Daily scheduled testing on components. == Todd Zullinger -- Websites Team == (+) more complete translations than we've had before (+) Infrastructure team syncing release content earlier than past releases (w) relocate everyone to a tropical island where we can all work together in person == Mike McGrath - Infrastructure == (+) team is growing (-) multiple release slips hindered work in infrastructure due to freezes --one big slip would be nicer (w) Feature freezes in earlier (w) Contingency plans for core distro functionality (w) Look for key ways that Infrastructure can enable success of QA Team == Paul Frields == (+) Well coordinated for the releases including slip announcements (+) Ambassadors did a great job behind the scenes --media production --release parties (-) Feedback mechanisms are unclear and point to too many different places --documentation and marketing materials --could anaconda bug reporting mechanism be helped by design team? (w) Marketing, Docs, Website, Design team work on coordinated approach to the Zicula (CMS) --organized and well coordinated fashion (w) More forceful in not allowing late/invasive changes to rawhide and putting them off to next release

9 36

Building Brand Together
by Ujjwol Lamichhane 22 Jun '09

22 Jun '09

As a Fedora KDE user i am forwarding this link to Fedora Artwork Team and KDE Fedora....

11 15

ok, now what?
by angella inzinga 19 Jun '09

19 Jun '09

OK, so I signed up for my first project of the queue. Now that I've got a few starter ideas, very rough- mostly just testing image direction of the people who need it. What now? Do we have a place to post images and direct clients where to go? Or usually just attach to email to client and so on.... Thanks!! Angie

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

design-team June 2009