design-team-tickets October 2016

design-team-tickets@lists.fedoraproject.org

1 participants
20 discussions

[Design Team] #401: Review: Updated cheat cube to use DNF instead of yum
by fedora-badges 13 Feb '17

13 Feb '17

#401: Review: Updated cheat cube to use DNF instead of yum ------------------------------+--------------------------- Reporter: ankursinha | Owner: Type: Print/Swag Design | Status: new Priority: low | Severity: Quick & Easy Keywords: | Blocked By: Blocking: | ------------------------------+--------------------------- Hiya, I updated the cheatcube to use dnf instead of yum. Could someone please take a look and put it up on the wiki here:(or give me a "go ahead" to put it up) https://fedoraproject.org/wiki/Marketing_collateral#Fedora_Cheat_Cubes -- Ticket URL: <https://fedorahosted.org/design-team/ticket/401> Design Team <http://fedoraproject.org/wiki/Design> Fedora Design Team

2 11

[Design Team] #477: Stand-up banner design for developer conferences
by fedora-badges 21 Nov '16

21 Nov '16

#477: Stand-up banner design for developer conferences ------------------------------+---------------------------------- Reporter: eischmann | Owner: Type: Print/Swag Design | Status: new Priority: medium | Severity: Moderately Involved Keywords: | Blocked By: Blocking: | ------------------------------+---------------------------------- I'd like to produce a stand-up banner for developer conferences. My idea is simple: Vertical Fedora logo and "The System for Developers" below it. Once we have drafts I can find a vendor a specify concrete dimensions. It should be roughly 200x80-100cm. -- Ticket URL: <https://fedorahosted.org/design-team/ticket/477> Design Team <http://fedoraproject.org/wiki/Design> Fedora Design Team

1 11

[Design Team] #487: Deco Banner FUDCon Phnom Penh
by fedora-badges 31 Oct '16

31 Oct '16

#487: Deco Banner FUDCon Phnom Penh ------------------------------+--------------------------- Reporter: gnokii | Owner: Type: Print/Swag Design | Status: new Priority: medium | Severity: Quick & Easy Keywords: | Blocked By: Blocking: | ------------------------------+--------------------------- == Deadline == * latest 2nd November * 4th November We need 4 banner for FUDCON Phnom Penh Size 1.63 meter x 2.45 meter, please use Fedora logo in small size as background pattern, its for the later reuse -- Ticket URL: <https://fedorahosted.org/design-team/ticket/487> Design Team <http://fedoraproject.org/wiki/Design> Fedora Design Team

1 6

[Design Team] #485: Poster design for Fedora 25 Release Parties
by fedora-badges 29 Oct '16

29 Oct '16

#485: Poster design for Fedora 25 Release Parties ------------------------------+--------------------------- Reporter: zsun | Owner: Type: Print/Swag Design | Status: new Priority: medium | Severity: Quick & Easy Keywords: | Blocked By: Blocking: | ------------------------------+--------------------------- This is a tracking ticket for Fedora 25 Posters == Deadline == * Deadline for design to be sent to printer 2016-11-07 as of design team schedule * Deadline for items to be shipped and ready to hand out ETA 2016-11-14 as of 1 day before Release Parties time slot. * If you can, please provide us with example photos of items that are similar to the result you're looking for General poster for release events like https://fedoraproject.org/wiki/F24_Artwork#Posters * Printer contact information if available N/A * Is this for an event? Yes * Location, date, and website/wiki page for the event Fedora 25 release parties worldwide * Is this in a language other than English? No * Print or embroidery Print -- Ticket URL: <https://fedorahosted.org/design-team/ticket/485> Design Team <http://fedoraproject.org/wiki/Design> Fedora Design Team

1 2

[Design Team] #471: Tshirt motiv FUDCon Phnom Penh 2016
by fedora-badges 25 Oct '16

25 Oct '16

#471: Tshirt motiv FUDCon Phnom Penh 2016 ------------------------------+---------------------------------- Reporter: gnokii | Owner: Type: Print/Swag Design | Status: new Priority: medium | Severity: Moderately Involved Keywords: | Blocked By: Blocking: | ------------------------------+---------------------------------- == Deadline == * Deadline for design to be sent to printer mid October * Deadline for items to be shipped and ready to hand out first week November * If you can, please provide us with example photos of items that are similar to the result you're looking for * Printer contact information if available not yet '''If you need printer recommendations, please include that in the ticket Include any text or content needed *No, we will not write your brochure for you''' * Is this for an event? Yes FUDCon Phnom Penh * Location, date, and website/wiki page for the event Norton University Phnom Penh, https://fedoraproject.org/wiki/FUDCon:Bid_for_PhnomPenh_2016 * Is this in a language other than English? '''Size requirements, can be standard paper size or width and height''' * For apparel or products * Apparel or product type TShirt, preferred Royal Blue * Number of colors to use 3 in max 4 * Background color of the object Royal Blue * Print or embroidery Print * Print area size (printer can provide this) A4 * Templates (if provided by printer) For the logo see #453 -- Ticket URL: <https://fedorahosted.org/design-team/ticket/471> Design Team <http://fedoraproject.org/wiki/Design> Fedora Design Team

1 3

[Design Team] #475: [Marketing] Pagure-friendly icon
by fedora-badges 24 Oct '16

24 Oct '16

#475: [Marketing] Pagure-friendly icon ----------------------------+---------------------------------- Reporter: jflory7 | Owner: Type: Digital Artwork | Status: new Priority: medium | Severity: Moderately Involved Keywords: | Blocked By: Blocking: | ----------------------------+---------------------------------- * '''Deadline''': 2016 September 30 (?) * '''Size requirements in pixels if applicable''': Square (downscaled automatically, whatever a good/preferred resolution is) * '''Logo or icon?''': Icon * '''What application is this for?''': [https://pagure.io Pagure] repository icons * '''Brief description of what the application does''': Source control management (SCM) * '''Developer contact information''': pingou (I think he's fairly easy to locate) * '''Desktop icons or web application icons?''': Web application The targeted place for this image right now is here (and wherever repo icons are used in the future). [[Image(https://i.imgur.com/BIp0HQL.png)]] -- Ticket URL: <https://fedorahosted.org/design-team/ticket/475> Design Team <http://fedoraproject.org/wiki/Design> Fedora Design Team

1 7

[Design Team] #483: Help design a new release validation testing system
by fedora-badges 23 Oct '16

23 Oct '16

#483: Help design a new release validation testing system -----------------------+---------------------------------------- Reporter: adamwill | Owner: Type: Web Design | Status: new Priority: medium | Severity: Long-Term / Complex Issue Keywords: | Blocked By: Blocking: | -----------------------+---------------------------------------- * What's your deadline (could be date, could be Fedora release milestone) No strict deadline. * Who's the developer writing the code (IRC nick + email + wiki profile page URL) For now, me (adamw / adamwill / adamwill(a)fp.o) * If you can, please provide us with example URLs of web designs that are similar to the result you're looking for Well, the thing I wanna replace is: https://fedoraproject.org/wiki/Test_Results:Current_Summary There's nothing precisely similar to what I want instead (which is kinda why we're thinking of making a new thing), but in the same vein, there's Ubuntu's QAtracker: http://iso.qa.ubuntu.com/ and Moztrap, which we were looking at using for a while: https://moztrap.mozilla.org/ * What type of web project is this? A system for reporting and viewing Fedora release validation testing results. * Wireframes or mockups for a website / web application Will attach my SUPER AWESOME literally-on-the-back-of-an-envelope sketch. * Is this for a new or existing site? (if existing, provide URL) Do you need CSS/HTML for the design? This would be an entirely new webapp. * Provide a link to the application project page or github page Don't have one yet. * Provide a link to the theming documentation if available * Provide a link to the deployment to be themed, if available Ditto. * Set up a test server and provide connection/login information App doesn't exist yet. :) So for a long time we (Fedora QA) have been using the wiki for storing validation test results. There is a hilariously complex mess of stuff - clever wiki templates, python-wikitcms, and the relval fedmsg consumer - all conspiring to produce all the wiki validation pages for new Fedora composes when appropriate, then we ask the squishy humans who actually do (some of) the testing to either edit the wiki pages directly or use the `relval report-results` command (basically a crappy TUI which knows how to edit the wiki) to report their results. We don't like this for one really important reason and a few less important ones. The really important reason is, it's a terrible interface for humans to report test results; needlessly hard to understand and easy to get wrong (wiki syntax is awful). The less important reasons are, it needs an awful lot of complicated (and just plain dumb) code to keep it all working, and it's a really stupid way to store results, which makes pretty much any kind of analysis of said results more work than it ought to be. So we'd quite like to come up with a completely new way to do release validation testing. We've gone through several versions of this plan in the past and none has quite worked out. The current idea is to write a new webapp from scratch which would be tuned to the release validation workflow and would store the results in ResultsDB (which will make it easy to consolidate them with results from automated test systems in future). My current very rough idea for approximately how this could look is in the image I'm gonna attach, if you can read it. It's basically somewhat similar to how the wiki pages look, but smarter. The basic flow would be that you'd pick a deliverable and report results for that deliverable. The 'pick a deliverable' stuff would happen at the top of the page: my first thought is to have two lists (drop-downs?) side- by-side, one for 'arch' and one a list of deliverables; picking an arch would cause the deliverable list to only show deliverables for that arch. In the arch list, release-blocking arches would have clear prominence over non-blocking arches, and similarly in the deliverable list, release- blocking deliverables would have clear prominence over non-blocking. Once you'd picked a deliverable we'd show a download button with the image size, and show a table of the test cases that can be run with that deliverable. The default sort for the test cases would prioritize important tests that had not yet been run: there's kinda a few different properties of tests that could be used for sorting, I'm not sure yet exactly how to combine them and whether to offer any sorting options to the user. But there's the test's 'milestone' - in the current implementation these are Alpha, Beta, Final and Optional, that's basically the effective order of importance - whether the test has been run by anyone else, and the test's 'type' (Installation, Base, Server etc - we aren't tied to these test types for the new system, but they are actually not a bad concept and could probably stand to stick around). One more concept we'd need to keep in mind is that running every relevant test for every image is likely impossible, so we need to be smart about saying 'as long as this test has been run for any live image, we're OK' or things along those lines. In the wiki system we mess around with the result columns to achieve this - if you look at the titles of the columns where results go they flip around constantly, sometimes we use arch, sometimes 'product', there's all kinds. In the new system I want the *user* to only have to worry about what ISO they're testing, but for the *admins* and people involved in the release process, we'll need it to be possible to specify 'groups' of images for each test case. So say for a single test case we'd set up four groups of images and say 'as long as the test has been run with at least one image from each group, we're covered'. The way this would be significant to the user is that it'd be less important for them to run a given test on their chosen ISO if its 'group' was already covered, so we'd ideally indicate that somehow. I figured it would be good to get some help with the design before we run off and start coding stuff, which is why I'm opening this ticket; I'm basically hoping you folks can help us think intelligently about what we're going to build before we start, and come up with some nice blueprints for us to work off (nicer than my envelope...) Thanks! -- Ticket URL: <https://fedorahosted.org/design-team/ticket/483> Design Team <http://fedoraproject.org/wiki/Design> Fedora Design Team

1 5

[Design Team] #438: Redesign Anaconda install banners
by fedora-badges 23 Oct '16

23 Oct '16

#438: Redesign Anaconda install banners ----------------------------+---------------------------------- Reporter: pidgornyy | Owner: Type: Release Artwork | Status: new Priority: medium | Severity: Moderately Involved Keywords: | Blocked By: Blocking: | ----------------------------+---------------------------------- * Deadline / Release milestone: none * Description: The Anaconda banners are almost the first thing a new user sees when he decides to try Fedora. Currently the banners don't look very welcoming, but rather ugly compared to the rest of Fedora's beautiful artwork (and compared to banners from other distributions). No offence against their creator(s), but the following things should really be improved: - No overuse of the Fedora logo font, Comfortaa. Comfortaa may look good for headings, but it's used for *all* the text on the banners, which looks unprofessional and simply ugly. - No sudden colour change in the middle of the text, like on the make- fedora-better banner. Either add outline or shadows to the text, or don't allow text to overlap with pictures. - No inconsistent distances between lines of text (present on all banners). - No inconsistent placing of images (compare the LibreOffice logo and the Rhythmbox loudspeaker). - No URLs starting with a capital letter. - Replace Beefy with something (the current release's logo?). - (Maybe generate the banners programmatically depending on locale? Currently the text is embedded into the images, which makes it a bit difficult to edit it for inexperienced contributors). Ever since these banners appeared in Anaconda in Fedora 19, I was hoping they'd be changed soon, but see no progress yet. Other distributions make good use of the banners in their installation, informing the user about new features in the release, what software is being installed onto the new system, how to navigate the desktop environment (the banners appear at the very end of the installation process, when we already know what desktop environment was selected for installation), where to get help (this we have already) and other little tips regarding the distribution. I will be attaching installer banners from Ubuntu and Xubuntu. We should agree on a design pattern that is used in all banners. It includes a fixed font, font size, line distance and margins. I will attach my proposal, but keep in mind that I am not a designer. Please suggest something, too. Another consideration would be to make the banners larger. There is a lot of wasted space on the installation progress screen. Larger banners (similar to *buntu) would allow us to put more information into them, for example screenshots of some popular software that is bundled with the Fedora image that is currently being installed. Steps to Reproduce: 1. Start the Fedora installation process 2. Complete all required steps and hit "Begin installation" 3. The banners start to appear at the bottom of the screen Benefit for Fedora: Improve aesthetics of Fedora, pleasing the eyes of all users. Newcomers are more likely to like Fedora when they are greeted with beautiful banners in the first few minutes they spend with Fedora. -- Ticket URL: <https://fedorahosted.org/design-team/ticket/438> Design Team <http://fedoraproject.org/wiki/Design> Fedora Design Team

1 17

[Design Team] #486: Request of mockups for targeted Marketing message related to the Fedora upgrade.
by fedora-badges 21 Oct '16

21 Oct '16

#486: Request of mockups for targeted Marketing message related to the Fedora upgrade. ----------------------------+--------------------------- Reporter: mailga | Owner: Type: Release Artwork | Status: new Priority: high | Severity: Quick & Easy Keywords: | Blocked By: Blocking: | ----------------------------+--------------------------- * Deadline: F25 release * Description: In the Marketing ML, Mattdm threw on the table the idea to illustrate the achieved rapidity of the upgrading process in Fedora. [https://lists.fedoraproject.org/archives/list/marketing@lists.fedoraproject… Here] the link to the discussion. Our early thoughts ran towards to a promotional campaign done by cartoon, but we're open to any artistic idea from the team. Thanks. Gabri -- Ticket URL: <https://fedorahosted.org/design-team/ticket/486> Design Team <http://fedoraproject.org/wiki/Design> Fedora Design Team

1 3

[Design Team] #448: advertising Magazine and CommBlog on AskFedora
by fedora-badges 18 Oct '16

18 Oct '16

#448: advertising Magazine and CommBlog on AskFedora ---------------------------------------+--------------------------- Reporter: viorel | Owner: Type: Design and Tools Education | Status: new Priority: medium | Severity: Quick & Easy Keywords: | Blocked By: Blocking: | ---------------------------------------+--------------------------- = phenomenon = We would like to use AskFedora as another place to advertise articles published in Magazine and CommBlog. = reason = AskFedora is a busy site and we're thinking that 1) articles will get more visibility and 2) advertising allows us to "republish" articles, that is draw attention on important topics published previously = recommendation = We need the Design team's help to advise on whether this is feasible and where the said ads can be added. Thanks! -- Ticket URL: <https://fedorahosted.org/design-team/ticket/448> Design Team <http://fedoraproject.org/wiki/Design> Fedora Design Team

1 10

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

design-team-tickets October 2016