From Fedora Project Wiki
(80 intermediate revisions by 22 users not shown)
Line 1: Line 1:
{{autolang|base=yes}}
{{header|websites}}
{{header|websites}}


Line 6: Line 7:


== Contributing roles in the Websites Project ==
== Contributing roles in the Websites Project ==
{{admon/tip|Contributing roles|This is only suggestions for contributing roles. Only your imagination sets the limts. }}
{{admon/tip|Contributing roles|These are only suggestions for contributing roles. Only your imagination sets the limits. }}


{|class="nobordersplz"
{|class="nobordersplz"
Line 22: Line 23:
The key goals of this effort include:
The key goals of this effort include:


* Trying to consolidate all the key Fedora websites onto one uniform scheme
* Consolidating all key Fedora websites onto one uniform scheme
* Maintaining the 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 be as fun and exciting as the project they represent
* 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:
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].


:: [http://fedoraproject.org/ fedoraproject.org]
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 with 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 [http://fedoracommunity.org Community Websites] page.


For a list of community websites, see the [[CommunityWebsites]] page.
== Join the Websites Team ==


== Join the Fedora Websites Project ==
Please refer to the [[Websites/Join| Join]] page on how to get the process started.


To learn how to join Fedora Websites Project, please refer to the [[Websites/Join| Join]] page. If you just have a quick fix or suggestion, give [[Websites/ShowUs| Show Us]] a look.
== Communicating with Us==
<!--== Artwork ==-->
{{Team contact|Websites|websites|#fedora-websites}}
<!--Artwork for use on Fedora websites and with other Fedora resources can be obtained from the [[Artwork|  Fedora Artwork Project]] .-->
* '''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}}
== Bugs ==
== Bugs ==


Bug tracking for the Fedora websites is handled through the Fedora Infrastructure Trac instance at https://fedorahosted.org/fedora-infrastructure/ (file a ticket under the [https://fedorahosted.org/fedora-infrastructure/newticket?component=Webmaster Webmaster component] )
{{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]].}}


Alternatively, email '''webmaster AT fedoraproject DOT org''' which is handled by [https://www.redhat.com/mailman/listinfo/fedora-websites-list fedora-websites-list] .
'''Found a bug?'''


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] .
Create a [https://fedorahosted.org/fedora-websites/newticket new ticket] and we'll be notified.


A list of active page building requests from other projects within Fedora are located here [[Websites/PageRequests|  Current Page Requests]]
Alternatively, email '''webmaster AT fedoraproject DOT org''' which is sent to the {{fplist|websites}} list.


{{Anchor|communicate}}


== Projects ==
'''Fixing a bug or sending patches?'''


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 stuff'' to move these projects forward.
Here is [[how to fix bugs on the Fedora Project website]].  


=== get.fedoraproject.org ===
Patches can be sent to our {{fplist|websites}} list.


See [[Website redesign 2009]].


Get people who want the non-default dl option - whether they know it or not - to find and download the right thing with minimal cognitive effort and mouse-clicks.
'''Tracking a bug?'''


=== Decisionmaking process ===
Bug tracking for the Fedora websites is handled through our [https://fedorahosted.org/fedora-websites/report/1 Fedora Websites Trac instance].


Articulate and document the consensus-based decision making process of the websites team.
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] .


Team: [[User:Ricky|Ricky Zhou]] (lead)
{{Anchor|Open Tasks}}


Next steps:
== Open Tasks ==
#  Ricky to send a draft here's-how-to-present-your-patch-to-the-list checklist to the mailing list
Want to see a list of our open tasks?
* [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]


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


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


=== docs.fedoraproject.org ===
{{Anchor|spins}}


Needs a description!
== Spins ==


Team: [[User:Ricky|Ricky Zhou]] (lead)
If you are the owner of a new 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).


Action items:
{{Anchor|communicate}}
# Ricky will bring his critiques to the docs team and report back via email to the list.


=== join.fedoraproject.org ===
== Projects ==


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.
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.


Team: [[User:Mchua|Mel Chua]] (lead)
=== Wiki Theme Update ===


Currently stalled.
Update this [http://fedoraproject.org/wiki Wiki's] theme.


Next steps (for the week of June 28, 2009):
Team: [[User:Sijis|Sijis Aviles]], [[User:Ianweller|Ian Weller]] (leads)


# Create a project (wiki) page for this.
Status: Not started
# 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:
=== All Fedora Websites Update ===


# creating "how good is this join process?" heuristics - probably with a lot of help and advice from the design team
Update all Fedora websites similar to getfedora.org's bootstrap design. All websites should be responsive and easy to navigate.


=== Translations ===
Team: [[User:Robyduck|Robert Mayr]] (lead)


Make sure all webpages are translated for the F12 release.
Status: In progress


Team: '''Nobody yet! Please help!'''
Deadline: Summer 2016


(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.)
=== Translations ===


=== User gallery ===
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.


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: [[User:Robyduck|Robert Mayr]], [[User:Shaiton|Kévin Raymond]] (leads)


Team: [[User:hiemanshu|Hiemanshu Sharma]] (lead)
Status: Migration completed, make sure all websites have I18n.


=== blogs.fedoraproject.org ===
=== Decision making process ===


''Needs a description of the goal.''
Articulate and document the consensus-based decision making process of the websites team.
 
Team: [[User:nb|Nick Bebout]] (lead), hiemanshu, onekopaka


Next steps (suggestions by mchua)
Team: [[User:Sijis|Sijis Aviles]], [[User:Robyduck|Robert Mayr]] (leads)
# <strike>From the signup screen, when you click the “create blog” button, it takes you to a screen that shows you incorrect urls for your blog (it shows https://blogs.fedoraproject.org/wp/ instead of https://blogs.fedoraproject.org/wp/name-of-your-blog).</strike> Fix has been included in puppet (sijis).
# left sidebar: “create a blog” may be better link text than ’sign up’
# once I create a blog there’s no obvious way to get to the dashboard. If I log out and log back in,I’m taken to the dashboard; it’s just that there’s no way to get there from logged-in state on https://blogs.fedoraproject.org except manually typing in the url (https://blogs.fedoraproject.org/wp/name-of-your-blog/wp-admin/))


=== Heuristics ===
=== Hubs ===


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]]. [[User:Mchua|Mel Chua]] is working on this.
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!


== Brainstorms ==
Team: [[User:Robyduck|Robert Mayr]], [[User:Duffy|Máirín Duffy]] (leads)


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.
Status: Brainstorming started


== Communicating ==
Deadline: F23 or F24


=== Mailing List ===
=== Fedora Developer Portal ===
developer.fedoraproject.org - a new go-to place for app developers running Fedora


The mailing list behind this effort is the [https://www.redhat.com/mailman/listinfo/fedora-websites-list fedora-websites-list] mailing list.  All contributors to this effort and interested third-party site maintainers should join this list.
Wiki page: [[Websites/Developer|Websites/Developer]]


=== IRC ===
Team: [[User:Phracek|Petr Hracek]], [[User:Jstribny|Josef Stribny]], [[User:Asamalik|Adam Samalik]] (leader)


The #fedora-websites channel on [http://freenode.net/ freenode]  is the best place to go for chat.
Status: Project definition


=== Meetings ===
Deadline: End of the summer 2015
 
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]]
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 main Fedora CSS file
Load the Fedora CSS file
 
[http://getfedora.org/static/css/boostrap.css bootstrap.css]
[http://fedoraproject.org/static/css/fedora.css fedora.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. Something like:
 
[http://fedoraproject.org/w/skins/fedora/main.css main]
or
[http://fedoraproject.org/css/fedora_planet.css fedora_planet.css]
 
=====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 een webpage:
And then load your custom css file and override elements as needed.
 
http://fedoraproject.org/static/images/banners/paulfrieldstv2.png


===Boilerplate responses to common mailing list inquires===
===Boilerplate responses to common mailing list inquires===
[[Websites/Boilerplate|  Boilerplate Responses]]
[[Websites/Boilerplate|  Boilerplate Responses]]


== Projects ==
== Completed Projects ==
 
* [[Websites/Spins| Fedora Spins]]
* [http://www.eluneart.com| Web Design Company]
 
== 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] .
-->


* [https://getfedora.org Get Fedora]
* [https://start.fedoraproject.org Start Fedora]


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

Revision as of 15:15, 14 August 2015


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 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 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 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 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).

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: Brainstorming started

Deadline: F23 or 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: Project definition

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-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

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

Retrieved from "https://fedoraproject.org/w/index.php?title=Websites&oldid=420052"