Difference between revisions of "Package the Weave Server"
(→Project Details) |
(→Project Plan) |
||
| Line 39: | Line 39: | ||
Goals for each release and plans for reaching those goals: | Goals for each release and plans for reaching those goals: | ||
<!-- 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 | + | * 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 draft RPMs including spec/srpm files for build and testing |
| − | * 0.2 - | + | * 0.2 - Packages to be tested with Koji to ensure support for the necessary architectures. Package review process should already be underway at this point. |
| − | * 0.3 - | + | * 0.3 - Packages should pass the Fedora package review process and be entered into the release management system. Documentation should be complete in addition. |
== Communication == | == Communication == | ||
Revision as of 10:47, 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
Weave consists of two APIs:
Sync is used for synchronizing data with the Weave server, while Reg-Server is used for setting up and managing user accounts.
The objective of the project is to have the Weave server packaged and available on the main Fedora respositories (yum install weave). This package should include a clean install/uninstall while streamlining Apache administration/configuration for Weave.
Project Plan
Tracking mechanism (bugzilla, trac, github, ...):
- Bugzilla
- GIT
Key contact: 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 draft RPMs including spec/srpm files for build and testing
- 0.2 - Packages to be tested with Koji to ensure support for the necessary architectures. Package review process should already be underway at this point.
- 0.3 - Packages should pass the Fedora package review process and be entered into the release management system. Documentation should be complete in addition.
Communication
Mailing Lists
Weave Server List (Google Groups)
Upsteam Wiki and Web
Links/Bugs/Tracking
Sync-Server 1.1 Setup/Config (Source)
Reg-Server 1.0 Setup/Config (Source)
Source Code Control
Blogs
Seneca Particpants
Non-Seneca Participants
Planets
Project News
- Initial project page draft. Built with information obtained from Mike Hoye and the project wikis.
