Bienvenido
La iniciativa de sitios web de Fedora tiene como objetivo mejorar la imagen de Fedora y crear la mejor interfaz posible para los usuarios y colaboradores en Internet.
Roles que contribuyen en el proyecto de sitios web
Estas son sólo sugerencias, cualquiera puede contribuir, la imaginación pone los límites.
Sobre los sitios web de Fedora
Los principales objetivos son:
- Consolidar todos los sitios web claves de Fedora bajo un esquema uniforme.
- El mantenimiento de los contenidos que no esté comprendido en otros sub-proyectos.
- Por lo general, hacer que los sitios sean más entretenidos, que representen 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 al sitio de Fedora.
Trabajos en secciones específicas coordinando con cada proyecto. Una gran parte de la coordinación será necesaria con el Equipo de infraestructura de Fedora, Proyecto de documentación de Fedora y el Proyecto de marketing de Fedora.
Para obtener la lista de sitios web comunitarios, consulte: Sitios web comunitarios.
Unirse al equipo de sitios web
Por favor consulte la página Unirse para saber cómo comenzar el proceso.
Comunicarse con nosotros
| Cómo contactar con el equipo sitios web | |
|---|---|
| Lista de correo: websites Visite este enlace para inscribirse en la lista de correo electrónico para el equipo sitios web. |
Chat: #fedora-websites[?] Aquí es donde se realiza el chat en tiempo real con los miembros del equipo sitios web. |
- Lista de correo: Todos los colaboradores interesados deben unirse a la lista de correo websites.
- IRC: El canal #fedora-websites[?] es el mejor lugar para chat, errores, problemas, parches y discusiones generales.
- Reuniones: Nuestra página de reuniones tiene detalles sobre cuando se llevan a cabo.
Errores
Si usted encuentra un error en una página web y crees que puedes solucionarlo, prueba! Aquí hay una página 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 https://fedorahosted.org/fedora-websites/
Alternativamente, la dirección de correo webmaster AT fedoraproyect DOT org que es manejado por websites list.
Los errores que se relacionen con el Proyecto Documentación Fedora pueden reportarse usando esta plantilla.
Una lista de páginas en construcción que están en petición por otros proyectos se encuentra aquí.
Tareas abiertas
Si usted esta interesado en trabajar en alguna de nuestras tareas abiertas. Revise alguno de los tickets.
- tickets Website (nuevos tickets)
- tickets de Infraestructura (antiguos tickets)
Estas tareas pueden variar, pasar de html/css hasta un script en python.
Proyectos
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:
- Ricky to send a draft here's-how-to-present-your-patch-to-the-list checklist to the mailing list
fedoraproject.org
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: http://poelstra.fedorapeople.org/schedules/f-14/f-14-web-tasks.html
Contact: Sijis Aviles
join.fedoraproject.org
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):
- Create a project (wiki) page for this.
- 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:
- creating "how good is this join process?" heuristics - probably with a lot of help and advice from the design team
Translations
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)
blogs.fedoraproject.org
Please refer to the Fedoraproject Blogs page to get started on your blog.
Team
Team: Nick Bebout (lead), hiemanshu, onekopaka
Next steps (suggestions by mchua)
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).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
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.
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 websites mailing list. All contributors to this effort and interested third-party site maintainers should join this list.
IRC
The #fedora-websites channel on 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 page.
Resources
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 fedoraproject.org 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="http://fedoraproject.org/static/images/banners/paulfrieldstv2.png">
results in a webpage:
Boilerplate responses to common mailing list inquires
Completed Projects
Agenda
The current agenda for the Fedora Websites initiative is tracked on the Tasks page.