From Fedora Project Wiki

Purpose

The Fedora Cloud SIG works to make Fedora successful on all major cloud platforms, public and private.

Looking for Fedora EC2 information?

A list of currently supported AMIs is maintained here

We also have Instructions for rolling your own AMIs with boxgrinder.

Joining and participating in the Cloud SIG

We don't have a formalized join process. Signing up on the mailing list, coming to Cloud SIG meetings, and joining our IRC channel are good ways to get involved. If you're interested in helping out with packaging, see the Current Projects section on this wiki page.

Mailing List

IRC

Fedora Cloud folks hang out on irc.freenode.net at #fedora-cloud.

Haven't used IRC for communication before? More information on how to use IRC is available here.

Meetings

Meetings are held weekly on Fridays, 1900 UTC (3pm Eastern, Noon Pacific, CEST 2100) on #fedora-meeting.

See the Cloud SIG meetings page for more information and archived meeting logs.

Fedora 17 Plans

Cloud Features in Fedora 17

Planned cloud-related features for Fedora 17 will be listed here.

Test Days

  • The date of the Fedora 17 Cloud SIG test day is currently TBD.
  • Results of the Fedora 16 test day can be seen here.
  • Results of the Fedora 15 test day can be seen here.

Current Projects and Features

What we're working on

There are a number of folks from various projects participating in the Cloud SIG. The projects are listed below:

F16 Features

Packaging

Interested in helping out with packaging? Feel free to grab a package from any of the projects you see here. If you're not sure what to work on, feel free to drop a note to our mailing list. If you're not a packager yet, or still need help, we can help out with that on the mailing list as well, or you can read the package maintainers page for more information.

Cloud SIG Packaging request list

Documentation

In addition to the excellent Cloud Guide created by the Fedora Documentation team with help from Cloud SIG contributors, we have a few wiki pages with documentation: