From Fedora Project Wiki

Revision as of 13:39, 20 April 2010 by Pfrields (talk | contribs) (moved Fixing a bug on the Fedora Project website to How to fix bugs on the Fedora Project website: Just created, so it's OK to move this still)

This page describes how to fix a bug or submit other changes to the Fedora Project website. Anyone can perform these steps, and you do not need special permission to send a patch to the websites list for consideration.

Procedure

  1. Ensure you have the Package-x-generic-16.pnggit package and the Apache web server installed:
    su -c 'yum shell'
    > install git
    > groupinstall 'Web Server'
    > run
  2. Set up at least your name and email address in your global git configuration, as shown on Git_quick_reference#Configure_your_global_git_settings this section of the git quick reference.
  3. Make sure you are in a directory to which you have write access, such as your home directory or a subdirectory, and clone the websites repository:
    cd $HOME
    git clone git://git.fedorahosted.org/git/fedora-web.git
  4. Change directory to the website you want to change. The repository carries several sites, including fedoraproject.org, spins.fedoraproject.org, and others.
    cd fedora-web/fedoraproject.org
  5. Make a new branch for your changes ("mychanges" is a name you can choose):
    git checkout -b mychanges
  6. Make your changes. It's best to make a set of related changes together, but don't make many unrelated changes at once. For instance, it's OK to make several spelling fixes together, but don't combine those with an additional navigation menu option.
  7. Stage the files you changed:
    git add data/content/file1.html data/content/file2.html
  8. Commit the staged changes:
    git commit -m 'Fix spelling errors'
  9. When you're done, create patch files for your changes:
    git format-patch origin/master
  10. Now you can send the patches you've created, which will have names such as 0001-my-change.patch, to the websites list.

Additional information

The git quick reference might be useful for you, beyond just setting up your global configuration.

The Git Community Book is an excellent reference if you find git useful and want to learn more about it.

You don't have to be a member of the Websites team to help fix things on the site, but if you find yourself doing it more than once, you might want to join us!