From Fedora Project Wiki
 
(3 intermediate revisions by 2 users not shown)
Line 7: Line 7:
 
{{admon/important|Personal Information|Fedora is a very visible and transparent project, which means that its mailing lists are archived and mirrored in many places on the internet outside of our control. Please use caution when sharing personal information with Fedora on a mailing list, because it is not possible for us to remove any postings from the wider Internet universe after they are sent. For more details, please refer to [https://fedoraproject.org/wiki/Legal/PrivacyPolicy Fedora's Privacy Policy].}}
 
{{admon/important|Personal Information|Fedora is a very visible and transparent project, which means that its mailing lists are archived and mirrored in many places on the internet outside of our control. Please use caution when sharing personal information with Fedora on a mailing list, because it is not possible for us to remove any postings from the wider Internet universe after they are sent. For more details, please refer to [https://fedoraproject.org/wiki/Legal/PrivacyPolicy Fedora's Privacy Policy].}}
  
# Join the [https://admin.fedoraproject.org/mailman/listinfo/websites websites] mailing list.
+
# Join the [https://lists.fedoraproject.org/admin/lists/websites.lists.fedoraproject.org/ websites] mailing list.
 
# Establish an account and sign the Fedora Project Contributor Agreement through the [[Infrastructure/AccountSystem|  Fedora Account System]].
 
# Establish an account and sign the Fedora Project Contributor Agreement through the [[Infrastructure/AccountSystem|  Fedora Account System]].
 
# Review the [[WikiEditing | wiki editing]] page to understand the wiki guidelines.
 
# Review the [[WikiEditing | wiki editing]] page to understand the wiki guidelines.
 
# Start with the [[How to fix bugs on the Fedora Project website | How to fix bugs on the Fedora Project website]] to familiarize with the right procedure and prepare your system as described. (You can do so also if you are not part of the websites group)
 
# Start with the [[How to fix bugs on the Fedora Project website | How to fix bugs on the Fedora Project website]] to familiarize with the right procedure and prepare your system as described. (You can do so also if you are not part of the websites group)
 
# Send a self-introduction email with some notes about your experience and skill level to the [mailto:websites@lists.fedoraproject.org websites list]. ('''Don't forget this!''')
 
# Send a self-introduction email with some notes about your experience and skill level to the [mailto:websites@lists.fedoraproject.org websites list]. ('''Don't forget this!''')
# Start contributing with the [http://fedoraproject.org/easyfix/#fedora-websites easyfix items], which have been evaluated as easy entrance point and send your patches to the ML.
+
# Start contributing with the [http://fedoraproject.org/easyfix/#fedora-websites easyfix items], which have been evaluated as easy entrance point and file pull requests.
# A summary of all the open tickets is available in the [https://fedorahosted.org/fedora-websites/report/1 trac page].
+
# A summary of all the open tickets is available in the [https://pagure.io/fedora-websites/issues pagure issues page].
 
# Once you have gotten familiar with the team and have contributed some, request sponsorship by applying to the 'web' group in the [[Infrastructure/AccountSystem|Fedora Account System]].
 
# Once you have gotten familiar with the team and have contributed some, request sponsorship by applying to the 'web' group in the [[Infrastructure/AccountSystem|Fedora Account System]].
# At some point, you will be requested to apply for sponsorship to the 'gitfedora-web' group, which will allow you to commit to the [http://git.fedorahosted.org/git/?p=fedora-web.git fedora-web repository] (where the website source code is at)
+
# At some point, you will be requested to apply for sponsorship to the 'gitfedora-web' group, which will allow you to commit to the [https://pagure.io/fedora-websites fedora-websites repository] (where the website source code is at)
 
# After getting write access to our repository you should read and get familiar with our [[Websites/workflow|workflow]].
 
# After getting write access to our repository you should read and get familiar with our [[Websites/workflow|workflow]].
  

Latest revision as of 20:46, 1 January 2017

Artwork DesignService fedorawebsitesbanner 3.png

Joining the Fedora Websites Project

If you're interested in helping with this effort, please complete the following steps:

Important.png
Personal Information
Fedora is a very visible and transparent project, which means that its mailing lists are archived and mirrored in many places on the internet outside of our control. Please use caution when sharing personal information with Fedora on a mailing list, because it is not possible for us to remove any postings from the wider Internet universe after they are sent. For more details, please refer to Fedora's Privacy Policy.
  1. Join the websites mailing list.
  2. Establish an account and sign the Fedora Project Contributor Agreement through the Fedora Account System.
  3. Review the wiki editing page to understand the wiki guidelines.
  4. Start with the How to fix bugs on the Fedora Project website to familiarize with the right procedure and prepare your system as described. (You can do so also if you are not part of the websites group)
  5. Send a self-introduction email with some notes about your experience and skill level to the websites list. (Don't forget this!)
  6. Start contributing with the easyfix items, which have been evaluated as easy entrance point and file pull requests.
  7. A summary of all the open tickets is available in the pagure issues page.
  8. Once you have gotten familiar with the team and have contributed some, request sponsorship by applying to the 'web' group in the Fedora Account System.
  9. At some point, you will be requested to apply for sponsorship to the 'gitfedora-web' group, which will allow you to commit to the fedora-websites repository (where the website source code is at)
  10. After getting write access to our repository you should read and get familiar with our workflow.
Idea.png
You do not need to request sponsorship in the 'web' group until after you have introduced yourself and begun contributing.

Interested in translating pages of this wiki? See the Languages page!