[Design Team] #58: T-Shirt region Design
by fedora-badges
#58: T-Shirt region Design
----------------------------------------+-----------------------------------
Reporter: wonderer(a)fedoraproject.org | Type: task
Status: new | Priority: minor
Milestone: | Version:
Keywords: |
----------------------------------------+-----------------------------------
at the last EMEA Ambassadors Meeting 20090722 we had the idea we want a
new T-Shirt Design for EMEA Users. This should be not Event specific and
more for allday usage. This idea could also be for "transformed" to NA,
LATAM, etc. later if wanted.
--
Ticket URL: <https://fedorahosted.org/design-team/ticket/58>
Design Team <http://fedoraproject.org/wiki/Design>
Fedora Design Team
11 years, 10 months
[Design Team] #65: Mockups for a desktop bugzilla client
by fedora-badges
#65: Mockups for a desktop bugzilla client
--------------------------------+-------------------------------------------
Reporter: sundaram | Owner: duffy
Type: mockup request | Status: new
Priority: major | Component: Interaction Design / Usability
Severity: Moderately Involved | Keywords:
--------------------------------+-------------------------------------------
https://fedoraproject.org/wiki/Bugzilla_Desktop_Client
We are looking to write a client from scratch or modify the bug buddy
client to suit our needs. The target audience is primarily end users who
want to interactively report a bug (Excluding crashes etc detected by bug
buddy or abrt) on a system that is facing the problem.
Most of the bugs are against a top few components (kernel, firefox, yum
etc) and it is not reasonable to expect users to necessarily understand
the exact component (only source packages are listed in bugzilla). We can
collect the logs, hardware details etc and be more intelligent because it
is a desktop client. The challenge is to make the process very simple
while leaving enough room for other more expert users to report a bug as
well. We want the ability to report the bug against a specific component
if the user understands the details but the application itself is oriented
towards non technical users.
--
Ticket URL: <https://fedorahosted.org/design-team/ticket/65>
Design Team <http://fedoraproject.org/wiki/Design>
Fedora Design Team
11 years, 10 months
[Design Team] #129: Fedora Summer Coding 2010 design help
by fedora-badges
#129: Fedora Summer Coding 2010 design help
--------------------------------+-------------------------------------------
Reporter: quaid | Owner: nobody
Type: task | Status: new
Priority: major | Component: Other Artwork
Severity: Moderately Involved | Keywords:
--------------------------------+-------------------------------------------
So you might have heard about ...
https://fedoraproject.org/wiki/Summer_Coding_2010
Being a whole new program for us, I thought it deserved a new, non-GSoC-
specific ticket. :)
Ideas that have come up so far:
* summercoding.fedoraproject.org -- static go-to site, using current fp.o
design and templates and framework.
* Posters to put up around schools.
* A logo?
I'll go the list to see if there is actual interest in this, but thought
I'd file a ticket first to refer to.
If there is interest, we'll make this the master ticket (as a task), and
I'll file separate tickets for the logos, website help, etc. That sound
right?
--
Ticket URL: <https://fedorahosted.org/design-team/ticket/129>
Design Team <http://fedoraproject.org/wiki/Design>
Fedora Design Team
12 years, 6 months
[Design Team] #82: Need a logo for the Docs team
by fedora-badges
#82: Need a logo for the Docs team
-------------------------+--------------------------------------------------
Reporter: rlandmann | Owner: duffy
Type: task | Status: new
Priority: minor | Component: Artwork
Severity: Quick & Easy | Keywords:
-------------------------+--------------------------------------------------
Publican (the XML publishing tool used by the docs team) includes a small
logo and hyperlink at the top right corner of the pages it builds in HTML.
The hyperlink points to the documentation team responsible for the doc (in
the case of Fedora docs, the Fedora Documentation Project), plus that
team's logo.
No logo for the Fedora docs team actually exists, so on all our Publican
docs, we just get a "Made with Publican" logo instead. You can see an
example here:
http://docs.fedoraproject.org/release-notes/f11/en-US/
Something actually relevant to Fedora, documentation, or Fedora
documentation would be much better :)
--
Ticket URL: <https://fedorahosted.org/design-team/ticket/82>
Design Team <http://fedoraproject.org/wiki/Design>
Fedora Design Team
12 years, 6 months
[Design Team] #84: need to get fpo.org banner rotation js working in insight
by fedora-badges
#84: need to get fpo.org banner rotation js working in insight
--------------------------------+-------------------------------------------
Reporter: mchua | Owner: duffy
Type: task | Status: new
Priority: major | Component: HTML/CSS Work
Severity: Moderately Involved | Keywords: insight
--------------------------------+-------------------------------------------
From mizmo: i tried to get the js for the banner rotation on www.fpo
working in zikula. it just spit out the js plain text rather than working.
for now i've statically linked out to the F11 release banner but one of
two things is going to need to happen before insight goes live:
* js needs to be working OR
* we need to statically link to a non F11 banner
(formerly in the Marketing team trac at https://fedorahosted.org
/marketing-team/ticket/53)
--
Ticket URL: <https://fedorahosted.org/design-team/ticket/84>
Design Team <http://fedoraproject.org/wiki/Design>
Fedora Design Team
12 years, 6 months
[Design Team] #108: CHASM logo
by fedora-badges
#108: CHASM logo
--------------------------------+-------------------------------------------
Reporter: mathstuf | Owner: duffy
Type: logo design request | Status: new
Priority: minor | Component: Artwork
Severity: Quick & Easy | Keywords:
--------------------------------+-------------------------------------------
Requesting a design for the CHASM logo. Discussed at FUDCon with Mo.
--
Ticket URL: <https://fedorahosted.org/design-team/ticket/108>
Design Team <http://fedoraproject.org/wiki/Design>
Fedora Design Team
12 years, 8 months
[Design Team] #50: ABRT GUI rework
by fedora-badges
#50: ABRT GUI rework
---------------------------------+------------------------------------------
Reporter: zprikryl | Owner:
Type: usability assessment | Status: new
Priority: major | Milestone:
Version: | Keywords:
---------------------------------+------------------------------------------
Hi,
since we are "command line" users, we aren't sure about how GUI is
designed. Can anybody tak a look at it? Basically, there are two windows.
First window includes a list of bugs with basic information like
application name, package name, ... An user has two options. Either report
a crash or delete a crash. If the user wants to report a crash, he chooses
some crash by clicking and then click on the icon in the icon panel, after
a while a second windows is displayed. If he wants to delete a crash, then
he click on another icon.
Second window includes a list of detailed information. Some information
the user can not change (like linux kernel version), some information he
can change (like backtrace). When data have binary form (possibly large
amount of data) the user can decide if he wants to include then in a
report (by clicking on a checkbutton on left side). The same situation is
when data have text form and text is large.
--
Ticket URL: <https://fedorahosted.org/design-team/ticket/50>
Design Team <http://fedoraproject.org/wiki/Design>
Fedora Design Team
12 years, 9 months