From Fedora Project Wiki
Line 49: Line 49:
Alternativamente, la dirección de correo '''webmaster AT fedoraproyect DOT org''' que es manejado por [ websites list] .
Alternativamente, la dirección de correo '''webmaster AT fedoraproyect DOT org''' que es manejado por [ websites list] .
Bugs that are related to the [[DocsProject|  Fedora Documentation Project]] can be reported using [ this template] .
Los errores que se relaciones con el [[DocsProject|  Proyecto Documentación Fedora]] pueden reportarse usando [ this template] .
A list of active page building requests from other projects within Fedora are located [[Websites/PageRequests| here]] .
A list of active page building requests from other projects within Fedora are located [[Websites/PageRequests| here]] .

Revision as of 17:09, 13 December 2011

Artwork DesignService fedorawebsitesbanner 3.png


La iniciativa Fedora Website tiene como objetivo mejorar la imagen de Fedora y crear la mejor interfaz para que los usuarios puedan contribuir por internet.

Roles que contribuyen al proyecto Fedora Website

Roles que contribuyen
Estas son sólo sugerencias cualquiera puede contribuir, la imaginación pone los límites.

Join OSDeveloper.png

Join WebDeveloper.png
Desarrollador Web o Administrador

Sobre Fedora Websites

Los principales objetivos son:

  • Consolidar todos los sitios web's claves de Fedora bajo un esquema uniforme.
  • El mantenimiento de los contenidos que no este comprendido en otros sub-proyectos.
  • Por lo general, hacer que los sitios sean más entretenidos, que represente una mejor experiencia.

Con el fin de alcanzar mejor nuestros objetivos, así como los beneficios para la comunidad, el trabajo de este proyecto consistirá en ser los mantenedores de todos los sitios donde fuere posible. El trabajo directo de este proyecto se limita a sitio Fedora.

Trabajos en secciones especificas coordinando con cada proyecto. Una gran parte de la coordinación será necesaria con el Equipo de Infraestructura Fedora , Proyecto de Documentación Fedora y el Proyecto Marketing Fedora .

Para obtener la lista de sitios web comunitarios, consulte: Sitios Web Comunitarios .

Únete al Proyecto Fedora Website

Para enterarse como unirse al Proyecto Fedora WebSite, por favor revise la página unirse .

Si tiene alguna sugerencia rápida, puede mostrarla , mirar y leerla how to fix bugs on the Fedora Project website .


¡Usted puede ayudarnos!
Si usted encuentra un error en una pagina web y crees que puedes solucionarlo, prueba! Aquí hay una pagina en la wiki que te ayuda a solucionar errores en el Proyecto Fedora Website.

El Bug tracking para los website de Fedora se maneja a través del Trac Website Fedora en

Alternativamente, la dirección de correo webmaster AT fedoraproyect DOT org que es manejado por websites list .

Los errores que se relaciones con el Proyecto Documentación Fedora pueden reportarse usando this template .

A list of active page building requests from other projects within Fedora are located here .

Open Tasks

If you are interested in working on some of our open tasks. Take a look at our tickets

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


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 2009-06-19 meeting, But remember, you decide priority by voting with your feet and doing things to move these projects forward.

Decision making process

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

Team: Sijis Aviles (lead)

Next steps:

  1. Ricky to send a draft here's-how-to-present-your-patch-to-the-list checklist to the mailing list

This is going to be redesigned and its targeted for F14. We anticipate using 960 fluid framework to facilitate implementation/design. Current schedule is based on the release schedule:

Contact: Sijis Aviles

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.

Team: Mel Chua (lead)

Currently stalled.

Next steps (for the week of June 28, 2009):

  1. Create a project (wiki) page for this.
  2. 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.
  3. 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.
  4. 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).
  5. interviewing people to find how they got involved with Fedora, and writing up those stories
    1. Ricky: experiences with packaging/infrastructure/web
    2. Hiemanshu: web/sysadmin/sysadmin-test
    3. nb: sysadmin/sysadmin-devel/sysadmin-test/web
    4. Mel: web, packaging
    5. Mel: find at least one feedback-writer from each Fedora team

Further down, here are some things we are considering:

  1. creating "how good is this join process?" heuristics - probably with a lot of help and advice from the design team


Make sure all webpages are translated for the F13 release.

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

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)

Please refer to the Fedoraproject Blogs page to get started on your blog.


Team: Nick Bebout (lead), hiemanshu, onekopaka

Next steps (suggestions by mchua)

  1. 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 instead of Fix has been included in puppet (sijis).
  2. left sidebar: “create a blog” may be better link text than ’sign up’
  3. 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 except manually typing in the url (


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.

Fedora Insight

Assisting with the launch of Fedora Insight, in particular the 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. Hiemanshu and Tatica are working on the initial release CSS and are good contact points.


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.


Mailing List

The mailing list behind this effort is the websites mailing list. All contributors to this effort and interested third-party site maintainers should join this list.


The #fedora-websites channel on freenode is the best place to go for chat.


Details about the regular meetings for the Fedora Websites team can be found on the Meetings page.


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.

This is especially true when working on official domains ( things on this list ):


Fedora CSS in your application

Load the main Fedora CSS file


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


Fedora Images in your application

Images simply need to be loaded via their 'href' attributes' url:

<a href="">

results in a webpage:


Boilerplate responses to common mailing list inquires

Boilerplate Responses

Completed Projects


The current agenda for the Fedora Websites initiative is tracked on the Tasks page.