From Fedora Project Wiki

(30 intermediate revisions by 6 users not shown)
Line 33: Line 33:
For a list of community websites, see the [[CommunityWebsites]] page.
For a list of community websites, see the [[CommunityWebsites]] page.


== Join the Fedora Websites Project ==
== Join the Websites Team ==


To learn how to join Fedora Websites Project, please refer to the [[Websites/Join| Join]] page.
Please refer to the [[Websites/Join| Join]] page on how to get the process started.
 
If you just have a quick fix or suggestion, give [[Websites/ShowUs| Show Us]] a look and read [[how to fix bugs on the Fedora Project website]].
<!--== Artwork ==-->
<!--Artwork for use on Fedora websites and with other Fedora resources can be obtained from the [[Artwork|  Fedora Artwork Project]] .-->


== Communicating with Us==
{{Team contact|Websites|websites|#fedora-websites}}
* '''Mailing List''': All interested contributors should join the {{fplist|websites}} mailing list.
* '''IRC''': The {{fpchat|#fedora-websites}} channel is the best place to go for chat, bugs, issues, patches and general discussions.
* '''Meetings''': Our [[Websites/Meetings| meetings]] page has details on when they are held.
<div style="float: right;">[[Image:WikiElements_meetingL.png]]</div>
{{Anchor|bugs}}
{{Anchor|bugs}}


Line 47: Line 49:
{{admon/note | You can help! | If you find a bug on the website you think you can help fix, try it!  Here's a page on the wiki that tells you [[how to fix bugs on the Fedora Project website]].}}
{{admon/note | You can help! | If you find a bug on the website you think you can help fix, try it!  Here's a page on the wiki that tells you [[how to fix bugs on the Fedora Project website]].}}


Bug tracking for the Fedora websites is handled through the Fedora Websites Trac instance at https://fedorahosted.org/fedora-websites/
'''Found a bug?'''
 
Create a [https://fedorahosted.org/fedora-websites/newticket new ticket] and we'll be notified.
 
Alternatively, email '''webmaster AT fedoraproject DOT org''' which is sent to the {{fplist|websites}} list.
 


Alternatively, email '''webmaster AT fedoraproject DOT org''' which is handled by [https://admin.fedoraproject.org/mailman/listinfo/websites websites list] .
'''Fixing a bug or sending patches?'''


Bugs that are related to the [[DocsProject|  Fedora Documentation Project]]  can be reported using [https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Documentation&op_sys=Linux&target_milestone=---&bug_status=NEW&version=devel&component=fedora-websites&rep_platform=All&priority=normal&bug_severity=normal&assigned_to=web-members%40fedoraproject.org&cc=&bug_file_loc=http%3A%2F%2F&short_desc=&comment=Description%20of%20problem%3A%0D%0A%0D%0A%0D%0AVersion-Release%20number%20of%20selected%20component%20%28if%20applicable%29%3A%0D%0A%0D%0A%0D%0AHow%20reproducible%3A%0D%0A%0D%0A%0D%0ASteps%20to%20Reproduce%3A%0D%0A1.%0D%0A2.%0D%0A3.%0D%0A%20%20%0D%0AActual%20results%3A%0D%0A%0D%0A%0D%0AExpected%20results%3A%0D%0A%0D%0A%0D%0AAdditional%20info%3A&commentprivacy=0&status_whiteboard=&ext_bz_id=0&ext_bz_bug_id=&data=&description=&contenttypemethod=list&contenttypeselection=text%2Fplain&contenttypeentry=&maketemplate=Remember%20values%20as%20bookmarkable%20template&form_name=enter_bug this template] .
Here is [[how to fix bugs on the Fedora Project website]].  


A list of active page building requests from other projects within Fedora are located [[Websites/PageRequests| here]] .
Patches can be sent to our {{fplist|websites}} list.


'''Tracking a bug?'''
Bug tracking for the Fedora websites is handled through our [https://fedorahosted.org/fedora-websites/report/1 Fedora Websites Trac instance].
Bugs that are related to the [[DocsProject|  Fedora Documentation Project]] or http://docs.fedoraproject.org can be reported using [https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Documentation&op_sys=Linux&target_milestone=---&bug_status=NEW&version=devel&component=fedora-websites&rep_platform=All&priority=normal&bug_severity=normal&assigned_to=web-members%40fedoraproject.org&cc=&bug_file_loc=http%3A%2F%2F&short_desc=&comment=Description%20of%20problem%3A%0D%0A%0D%0A%0D%0AVersion-Release%20number%20of%20selected%20component%20%28if%20applicable%29%3A%0D%0A%0D%0A%0D%0AHow%20reproducible%3A%0D%0A%0D%0A%0D%0ASteps%20to%20Reproduce%3A%0D%0A1.%0D%0A2.%0D%0A3.%0D%0A%20%20%0D%0AActual%20results%3A%0D%0A%0D%0A%0D%0AExpected%20results%3A%0D%0A%0D%0A%0D%0AAdditional%20info%3A&commentprivacy=0&status_whiteboard=&ext_bz_id=0&ext_bz_bug_id=&data=&description=&contenttypemethod=list&contenttypeselection=text%2Fplain&contenttypeentry=&maketemplate=Remember%20values%20as%20bookmarkable%20template&form_name=enter_bug this template] .


{{Anchor|Open Tasks}}
{{Anchor|Open Tasks}}


== Open Tasks ==
== Open Tasks ==
If you are interested in working on some of our open tasks. Take a look at our tickets
Want to see a list of our open tasks?
* [https://fedorahosted.org/fedora-websites/report/1 Website tickets] (newer tickets)
* [https://fedorahosted.org/fedora-websites/report/1 Website tickets]
* [https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assigned&status=reopened&owner=~web&order=priority Infrastructure tickets] (older tickets)
* [https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assigned&status=reopened&owner=~web&order=priority Infrastructure tickets]
 
If you find something you'd like to take on, add a comment the ticket and add yourself as owner.


These tasks can vary from html/css changes to python scripting.
These tasks can vary from html/css changes to python scripting.
Line 69: Line 85:
== Projects ==
== Projects ==


These are projects with specific goals actively being worked on for the F12 release cycle. They're in rough order of the priority discussed at the [[/Meetings/2009-06-19|2009-06-19 meeting]], But remember, ''you'' decide priority by ''voting with your feet'' and ''doing things'' to move these projects forward.
These are projects with specific goals being worked on. They're in rough order of the priority, but remember, ''you'' decide priority by ''voting with your feet'' and ''doing things'' to move these projects forward.


=== Decision making process ===
=== Wiki Theme Update ===


Articulate and document the consensus-based decision making process of the websites team.
Update this [http://fedoraproject.org/wiki Wiki's] theme to match fedoraproject.org's 960.gs design.


Team: [[User:Sijis|Sijis Aviles]] (lead)
Team: [[User:Sijis|Sijis Aviles]], [[User:Ianweller|Ian Weller]]


Next steps:
Status: Not started
#  Ricky to send a draft here's-how-to-present-your-patch-to-the-list checklist to the mailing list


=== fedoraproject.org ===
Deadline: Spring 2012


This is going to be redesigned and its targeted for F14. We anticipate using 960 fluid framework to facilitate implementation/design.
=== All Fedora Websites Theme Update ===
Current schedule is based on the release schedule: http://poelstra.fedorapeople.org/schedules/f-14/f-14-web-tasks.html


Contact: [[User:Sijis|Sijis Aviles]]
Update all Fedora websites simialar to fedoraproject.org's 960.gs design. The list to tackle are the ones in the [http://git.fedorahosted.org/git/?p=fedora-web.git website git repository].


=== join.fedoraproject.org ===
Team: [[User:Sijis|Sijis Aviles]] (lead)


Increase the number of first-time Fedora contributors working on F12 by putting a support system behind this page and tweaking it to reflect that.
Status: Not started


Team: [[User:Mchua|Mel Chua]] (lead)
Deadline: Summer 2012


Currently stalled.
=== Translations ===


Next steps (for the week of June 28, 2009):
Make sure all websites, primarily fedoraproject.org is translated for Fedora releases.


# Create a project (wiki) page for this.
Team: [[User:Shaiton|Kévin Raymond]]
# Make a map of "entry routes" to Fedora participation, using websites as a framework - join.fp.o goes to what other pages, which go to what other pages, and so on... and what actions do people take at each page? What sequence of webpages is a new contributor likely to see? Post this to the wiki, send to list for comment.
# List the communication channels used by Fedora contributors (IRC, wiki, lists, etc) and resources that already exist to explain their usage. Post to wiki, send to list.
# List the location, for each team, where newcomers can go and pick up their first encapsulated task (clear objectives, clear deliverable, clear person-to-deliver-it-to).
# interviewing people to find how they got involved with Fedora, and writing up those stories
## Ricky: experiences with packaging/infrastructure/web
## Hiemanshu: web/sysadmin/sysadmin-test
## nb: sysadmin/sysadmin-devel/sysadmin-test/web
## Mel: web, packaging
## Mel: find at least one feedback-writer from each Fedora team


Further down, here are some things we are considering:
Deadline: Ongoing


# creating "how good is this join process?" heuristics - probably with a lot of help and advice from the design team
=== Decision making process ===


=== Translations ===
Articulate and document the consensus-based decision making process of the websites team.


Make sure all webpages are translated for the F13 release.
Team: [[User:Sijis|Sijis Aviles]] (lead)
 
Team: '''Nobody yet! Please help!'''
 
(We aren't actually worrying about this until the end of July, but if you are interested in picking this up and keeping us from panicking then, that would be ''awesome.'' Please email the list if you are keen on this, and someone will respond to you.)


=== User gallery ===
=== User gallery ===
Line 126: Line 127:
Team: [[User:hiemanshu|Hiemanshu Sharma]] (lead)
Team: [[User:hiemanshu|Hiemanshu Sharma]] (lead)


=== Heuristics ===
Status: Stalled


Coming up with a list of suggested guidelines and tests against which new and modified websites can be evaluated - things like checking that it works on various browsers, screen resolutions, etc. See [[/Heuristics]]. Nobody is working on this.
Deadline: N/A
 
=== Fedora Insight ===
 
Assisting with the launch of [[Fedora Insight]], in particular the [[Fedora Insight#Design|CSS-related work]] that needs to be done before initial launch; after launch, the back-end infrastructure maintenance will transition to the Websites team, with content and workflow remaining the responsibility of [[Marketing]] and [[FWN]]. [[User:Hiemanshu|Hiemanshu]] and [[User:Tatica|Tatica]] are working on the initial release CSS and are good contact points.
 
== Brainstorms ==
 
For things we're thinking about, images we're kicking around, and posting thoughts that might not yet be well formed, see [[/Brainstorms]] - a lot of this discussion also happens on the mailing list.
 
== Communicating ==
 
=== Mailing List ===
 
The mailing list behind this effort is the [https://admin.fedoraproject.org/mailman/listinfo/websites websites] mailing list.  All contributors to this effort and interested third-party site maintainers should join this list.
 
=== IRC ===
 
The #fedora-websites channel on [http://freenode.net/ freenode]  is the best place to go for chat.
 
=== Meetings ===
 
Details about the regular meetings for the Fedora Websites team can be found on the [[/Meetings|  Meetings]]  page.


== Resources ==
== Resources ==


===CSS and Images===
===CSS and Images===
One can find all CSS files and images used in the Fedora sites on the web and we encourage the community to use them directly from our urls in a cascading implementation.
All CSS files and images used in Fedora sites can be found in our [http://git.fedorahosted.org/git/?p=fedora-web.git;a=tree;f=fedoraproject.org/static;h=6b13643a1bdbd95a66dc6f2bb7319bb8a1110690;hb=HEAD fedora-web.git repository]. The community may use the css directly from our urls in a cascading implementation.
 
This is especially true when working on official fedoraproject.org domains ( things on this list ):


We encourage using the stylesheets in a cascading method when working on official Fedora Project domains (sites on this list):
[[Websites/DomainsList]]
[[Websites/DomainsList]]


=====Fedora CSS in your application=====
=====Fedora CSS in your application=====


Load the main Fedora CSS file
Load the Fedora CSS file
 
[http://fedoraproject.org/static/css/fedora.css fedora.css]
[http://fedoraproject.org/static/css/fedora.css fedora.css]


And then load your custom css file and override elements as needed. Something like:
And then load your custom css file and override elements as needed. As an example, something like
 
[http://fedoraproject.org/w/skins/fedora/main.css main.css] (as used for fedoraproject.org/wiki).
[http://fedoraproject.org/w/skins/fedora/main.css main]
 
=====Fedora Images in your application=====
 
Images simply need to be loaded via their 'href' attributes' url:
 
<code><nowiki><a href="http://fedoraproject.org/static/images/banners/paulfrieldstv2.png"></nowiki></code>
 
results in a webpage:
 
http://fedoraproject.org/static/images/banners/paulfrieldstv2.png


===Boilerplate responses to common mailing list inquires===
===Boilerplate responses to common mailing list inquires===
Line 187: Line 153:


* [[Websites/Spins| Fedora Spins]]
* [[Websites/Spins| Fedora Spins]]
 
* fedoraproject.org Redesign
== Agenda ==
* join.fedoraproject.org (as part of fedoraproject.org redesign)
The current agenda for the Fedora Websites initiative is tracked on the [[Websites/Tasks|  Tasks]]  page.
 
<!--Also, see [[Websites/PageRequests|  Current Page Requests]]  and ##[https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assigned&status=reopened&group=milestone&component=Webmaster&order=priority ##Fedora Websites tickets] .
-->




[[Category:Websites]]
[[Category:Websites]]
[[Category:Fedora sub-projects]]
[[Category:Fedora sub-projects]]

Revision as of 05:49, 28 January 2013


Welcome

The Fedora Websites initiative aims to improve Fedora's image and to create the best possible interface for users and contributors on the Internet.

Contributing roles in the Websites Project

Idea.png
Contributing roles
These are only suggestions for contributing roles. Only your imagination sets the limits.

Join OSDeveloper.png
OS Developer

Join WebDeveloper.png
Web Developer or Administrator

About Fedora Websites

The key goals of this effort include:

  • Consolidating all key Fedora websites onto one uniform scheme
  • Maintaining content that doesn't fall under any particular sub-project
  • Generally, making the sites as fun and exciting as the project they represent

In order to better achieve these goals, as well as to benefit the community, the work of this project will involve third-party site maintainers where possible. The direct work of this project is limited to the formal Fedora site.

Work on specific sections of the sites will be coordinated by the appropriate projects. A great deal of coordination will be necessary with the Fedora Infrastructure Team , Fedora Documentation Project and the Fedora Marketing Project .

For a list of community websites, see the CommunityWebsites page.

Join the Websites Team

Please refer to the Join page on how to get the process started.

Communicating with Us

How to contact the Websites team
Mailing list: websites
Visit this link to sign up for the email list for the Websites team.
Chat: #fedora-websites[?]
This is where real-time chat with Websites team members happens.
  • Mailing List: All interested contributors should join the websites mailing list.
  • IRC: The #fedora-websites[?] channel is the best place to go for chat, bugs, issues, patches and general discussions.
  • Meetings: Our meetings page has details on when they are held.

Bugs

Note.png
You can help!
If you find a bug on the website you think you can help fix, try it! Here's a page on the wiki that tells you how to fix bugs on the Fedora Project website.

Found a bug?

Create a new ticket and we'll be notified.

Alternatively, email webmaster AT fedoraproject DOT org which is sent to the websites list.


Fixing a bug or sending patches?

Here is how to fix bugs on the Fedora Project website.

Patches can be sent to our websites list.


Tracking a bug?

Bug tracking for the Fedora websites is handled through our Fedora Websites Trac instance.


Bugs that are related to the Fedora Documentation Project or http://docs.fedoraproject.org can be reported using this template .

Open Tasks

Want to see a list of our open tasks?

If you find something you'd like to take on, add a comment the ticket and add yourself as owner.

These tasks can vary from html/css changes to python scripting.

Projects

These are projects with specific goals being worked on. They're in rough order of the priority, but remember, you decide priority by voting with your feet and doing things to move these projects forward.

Wiki Theme Update

Update this Wiki's theme to match fedoraproject.org's 960.gs design.

Team: Sijis Aviles, Ian Weller

Status: Not started

Deadline: Spring 2012

All Fedora Websites Theme Update

Update all Fedora websites simialar to fedoraproject.org's 960.gs design. The list to tackle are the ones in the website git repository.

Team: Sijis Aviles (lead)

Status: Not started

Deadline: Summer 2012

Translations

Make sure all websites, primarily fedoraproject.org is translated for Fedora releases.

Team: Kévin Raymond

Deadline: Ongoing

Decision making process

Articulate and document the consensus-based decision making process of the websites team.

Team: Sijis Aviles (lead)

User gallery

Create a gallery for mini-interview-style user profiles and stories. This may end up being in conjunction with existing projects/frameworks/pages such as Community.

Team: Hiemanshu Sharma (lead)

Status: Stalled

Deadline: N/A

Resources

CSS and Images

All CSS files and images used in Fedora sites can be found in our fedora-web.git repository. The community may use the css directly from our urls in a cascading implementation.

We encourage using the stylesheets in a cascading method when working on official Fedora Project domains (sites on this list): Websites/DomainsList

Fedora CSS in your application

Load the Fedora CSS file fedora.css

And then load your custom css file and override elements as needed. As an example, something like main.css (as used for fedoraproject.org/wiki).

Boilerplate responses to common mailing list inquires

Boilerplate Responses

Completed Projects

  • Fedora Spins
  • fedoraproject.org Redesign
  • join.fedoraproject.org (as part of fedoraproject.org redesign)