Difference between revisions of "Package the Weave Server"
(→Project Plan) |
(→Project Plan) |
||
| Line 35: | Line 35: | ||
<!-- Note: each contributor is expected to have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. --> | <!-- Note: each contributor is expected to have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. --> | ||
* 0.1 - Will begin with setting up a build-from-source Weave server for necessary understanding/testing. To be followed by research into Apache/MySQL configuration and streamlining. End result for 0.1 should be a draft RPM including spec/srpm files for build and testing | * 0.1 - Will begin with setting up a build-from-source Weave server for necessary understanding/testing. To be followed by research into Apache/MySQL configuration and streamlining. End result for 0.1 should be a draft RPM including spec/srpm files for build and testing | ||
| − | * 0.2 - Package | + | * 0.2 - Package is to be tested with Koji to ensure support for the necessary architectures. Package review process should already be underway at this point. |
* 0.3 - Package has passed the Fedora package review process and entered the release management system. | * 0.3 - Package has passed the Fedora package review process and entered the release management system. | ||
Revision as of 00:43, 3 February 2011
Contents
Package the Weave Server
Project Description
Weave is the server used by Mozilla Sync for synchronizing personal data (bookmarks, passwords, form values, and cookies) across multiple machines and architectures (Windows/Linux, Android, etc). This project involves packaging Weave for Fedora and getting it through the package review process. This is being done so individuals, groups, and companies can run their own private weave server.
Project Leader(s)
Project Contributor(s)
Project Details
Objective of the project is to have the weave server RPM available on the main Fedora respositories. In addition, to streamline a clean install/uninstall of Weave including Apache administration.
Project Plan
Tracking mechanism (bugzilla, trac, github, ...): Bugzilla
Key contacts: Mike Hoye (mhoye)
Goals for each release and plans for reaching those goals:
- 0.1 - Will begin with setting up a build-from-source Weave server for necessary understanding/testing. To be followed by research into Apache/MySQL configuration and streamlining. End result for 0.1 should be a draft RPM including spec/srpm files for build and testing
- 0.2 - Package is to be tested with Koji to ensure support for the necessary architectures. Package review process should already be underway at this point.
- 0.3 - Package has passed the Fedora package review process and entered the release management system.
Communication
Mailing Lists
Weave Server List (Google Groups)
Upsteam Wiki and Web
Links/Bugs/Tracking
Weave Server 1.1 Setup/Config (Source)
