From Fedora Project Wiki

(updated Resources section)
 
(46 intermediate revisions by 11 users not shown)
Line 25: Line 25:
 
* Consolidating all key Fedora websites onto one uniform scheme
 
* Consolidating all key Fedora websites onto one uniform scheme
 
* Maintaining content that doesn't fall under any particular sub-project
 
* Maintaining content that doesn't fall under any particular sub-project
* Generally, making the sites as fun and exciting as the project they represent
+
* Generally, making the sites as fun and exciting as the projects 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 [http://fedoraproject.org/ Fedora site].
+
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 [https://getfedora.org/ Get 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 [[Infrastructure|  Fedora Infrastructure Team]] , [[DocsProject|  Fedora Documentation Project]]  and the [[Marketing|  Fedora Marketing Project]] .
 
Work on specific sections of the sites will be coordinated by the appropriate projects.  A great deal of coordination will be necessary with the [[Infrastructure|  Fedora Infrastructure Team]] , [[DocsProject|  Fedora Documentation Project]]  and the [[Marketing|  Fedora Marketing Project]] .
  
For a list of community websites, see the [[CommunityWebsites]] page.
+
For a list of community websites, see the [http://fedoracommunity.org Community Websites] 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 of old meetings (actually no meetings are scheduled).
 +
<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://pagure.io/fedora-websites/new_issue new ticket] and we'll be notified.
 +
 
 +
Alternatively, email '''webmaster AT fedoraproject DOT org''' which is sent to the {{fplist|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 {{fplist|websites}} list.
  
Alternatively, email '''webmaster AT fedoraproject DOT org''' which is handled by [https://admin.fedoraproject.org/mailman/listinfo/websites websites list] .
 
  
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] .
+
'''Tracking a bug?'''
  
A list of active page building requests from other projects within Fedora are located [[Websites/PageRequests| here]] .
+
Bug tracking for the Fedora websites is handled through our [https://pagure.io/fedora-websites/issues Fedora Websites Trac instance].
  
 +
Bugs that are related to the [[DocsProject|  Fedora Documentation Project]] or https://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://pagure.io/fedora-websites/issues 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 to 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.
 +
 +
{{Anchor|spins}}
 +
 +
== Spins ==
 +
 +
If you are the owner of a new and approved Spin that needs to be included on the websites there are just a few websites specific tasks (you will have to make others) to accomplish:
 +
* Open a ticket in the websites track and refer to your wiki page, provide support informations, mailing list and IRC channel.
 +
* Provide a features list, they are different if your spin is a [https://spins.fedoraproject.org Desktop Spin] or a [https://labs.fedoraproject.org Functional Spin].
 +
* Open a ticket in the design trac to request design.
 +
* Provide an actual screenshot with a full HD resolution (1920x1080): only for Desktop Spins!
  
 
{{Anchor|communicate}}
 
{{Anchor|communicate}}
Line 69: Line 94:
 
== 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 ===
 +
 
 +
Update this [http://fedoraproject.org/wiki Wiki's] theme.
 +
 
 +
Team: [[User:Sijis|Sijis Aviles]], [[User:Ianweller|Ian Weller]] (leads)
 +
 
 +
Status: Not started
 +
 
 +
=== All Fedora Websites Update ===
 +
 
 +
Update all Fedora websites similar to getfedora.org's bootstrap design. All websites should be responsive and easy to navigate.
  
Articulate and document the consensus-based decision making process of the websites team.
+
Team: [[User:Robyduck|Robert Mayr]] (lead)
  
Team: [[User:Sijis|Sijis Aviles]] (lead)
+
Status: In progress
  
Next steps:
+
Deadline: Summer 2016
#  Ricky to send a draft here's-how-to-present-your-patch-to-the-list checklist to the mailing list
 
  
 
=== Translations ===
 
=== Translations ===
  
Make sure all webpages are translated for the F13 release.
+
Make sure all websites, primarily fedoraproject.org subdomains and getfedora.org are translated for Fedora releases. All source files now are on [https://fedora.zanata.org/project/view/fedora-web fedora.zanata.org]. This project needs to work close to the L10n teams.
  
Team: '''Nobody yet! Please help!'''
+
Team: [[User:Robyduck|Robert Mayr]], [[User:Shaiton|Kévin Raymond]] (leads)
  
(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.)
+
Status: Migration completed, make sure all websites have I18n.
  
=== User gallery ===
+
=== Decision making process ===
  
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.
+
Articulate and document the consensus-based decision making process of the websites team.
  
Team: [[User:hiemanshu|Hiemanshu Sharma]] (lead)
+
Team: [[User:Sijis|Sijis Aviles]], [[User:Robyduck|Robert Mayr]] (leads)
  
== Communicating ==
+
=== Hubs ===
  
=== Mailing List ===
+
Create a new web-interface for contributors and for gathering new contributors, where people can have an easy overview of what's going on in the single team. Will need a framework and working close together with Design and Infrastructure is a must!
  
The mailing list behind this effort is the [https://lists.fedoraproject.org/mailman/listinfo/websites websites] mailing list.  All contributors to this effort and interested third-party site maintainers should join this list.
+
Team: [[User:Robyduck|Robert Mayr]], [[User:Duffy|Máirín Duffy]] (leads)
  
=== IRC ===
+
Status: Prototype created, QA in progress
  
The #fedora-websites channel on [http://freenode.net/ freenode]  is the best place to go for chat.
+
Deadline: F24
  
=== Meetings ===
+
=== Fedora Developer Portal ===
 +
developer.fedoraproject.org - a new go-to place for app developers running Fedora
  
Details about the regular meetings for the Fedora Websites team can be found on the [[/Meetings| Meetings]] page.
+
Wiki page: [[Websites/Developer|Websites/Developer]]
 +
 
 +
Team: [[User:Phracek|Petr Hracek]], [[User:Jstribny|Josef Stribny]], [[User:Asamalik|Adam Samalik]] (leader)
 +
 
 +
Status: '''Completed''', [https://developer.fedoraproject.org/ now live]
 +
 
 +
Deadline: End of the summer 2015
  
 
== Resources ==
 
== Resources ==
  
 
===CSS and Images===
 
===CSS and Images===
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.
+
All CSS files and images used in Fedora sites can be found in our [https://pagure.io/fedora-websites/tree/master fedora-websites.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):
 
We encourage using the stylesheets in a cascading method when working on official Fedora Project domains (sites on this list):
 
[[Websites/DomainsList]]
 
[[Websites/DomainsList]]
 +
 +
All websites based on bootstrap use the same basic CSS file. Any specific stylesheet needs to be written in the website's app.css file. Don't modify the main bootstrap CSS.
  
 
=====Fedora CSS in your application=====
 
=====Fedora CSS in your application=====
  
 
Load the Fedora CSS file
 
Load the Fedora CSS file
[http://fedoraproject.org/static/css/fedora.css fedora.css]
+
[http://getfedora.org/static/css/bootstrap.css bootstrap.css]
 +
Load a Specific app CSS file
 +
[http://getfedora.org/static/css/app.css app.css]
  
And then load your custom css file and override elements as needed. As an example, something like
+
And then load your custom css file and override elements as needed.
[http://fedoraproject.org/w/skins/fedora/main.css main.css] (as used for fedoraproject.org/wiki).
 
  
 
===Boilerplate responses to common mailing list inquires===
 
===Boilerplate responses to common mailing list inquires===
Line 129: Line 173:
 
== Completed Projects ==
 
== Completed Projects ==
  
* [[Websites/Spins| Fedora Spins]]
+
* [https://getfedora.org Get Fedora]
* fedoraproject.org Redesign
+
* [https://start.fedoraproject.org Start Fedora]
* join.fedoraproject.org (as part of fedoraproject.org redesign)
+
* [https://spins.fedoraproject.org Fedora Spins]
 
+
* [https://labs.fedoraproject.org Fedora Labs]
 
 
== Agenda ==
 
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]]

Latest revision as of 18:40, 31 January 2017

Artwork DesignService fedorawebsitesbanner 3.png


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 projects 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 Get 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 Community Websites 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 of old meetings (actually no meetings are scheduled).
WikiElements meetingL.png

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 https://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 to the ticket and add yourself as owner.

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

Spins

If you are the owner of a new and approved Spin that needs to be included on the websites there are just a few websites specific tasks (you will have to make others) to accomplish:

  • Open a ticket in the websites track and refer to your wiki page, provide support informations, mailing list and IRC channel.
  • Provide a features list, they are different if your spin is a Desktop Spin or a Functional Spin.
  • Open a ticket in the design trac to request design.
  • Provide an actual screenshot with a full HD resolution (1920x1080): only for Desktop Spins!

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.

Team: Sijis Aviles, Ian Weller (leads)

Status: Not started

All Fedora Websites Update

Update all Fedora websites similar to getfedora.org's bootstrap design. All websites should be responsive and easy to navigate.

Team: Robert Mayr (lead)

Status: In progress

Deadline: Summer 2016

Translations

Make sure all websites, primarily fedoraproject.org subdomains and getfedora.org are translated for Fedora releases. All source files now are on fedora.zanata.org. This project needs to work close to the L10n teams.

Team: Robert Mayr, Kévin Raymond (leads)

Status: Migration completed, make sure all websites have I18n.

Decision making process

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

Team: Sijis Aviles, Robert Mayr (leads)

Hubs

Create a new web-interface for contributors and for gathering new contributors, where people can have an easy overview of what's going on in the single team. Will need a framework and working close together with Design and Infrastructure is a must!

Team: Robert Mayr, Máirín Duffy (leads)

Status: Prototype created, QA in progress

Deadline: F24

Fedora Developer Portal

developer.fedoraproject.org - a new go-to place for app developers running Fedora

Wiki page: Websites/Developer

Team: Petr Hracek, Josef Stribny, Adam Samalik (leader)

Status: Completed, now live

Deadline: End of the summer 2015

Resources

CSS and Images

All CSS files and images used in Fedora sites can be found in our fedora-websites.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

All websites based on bootstrap use the same basic CSS file. Any specific stylesheet needs to be written in the website's app.css file. Don't modify the main bootstrap CSS.

Fedora CSS in your application

Load the Fedora CSS file bootstrap.css Load a Specific app CSS file app.css

And then load your custom css file and override elements as needed.

Boilerplate responses to common mailing list inquires

Boilerplate Responses

Completed Projects