Difference between revisions of "Package the Weave Server"
(→Project Leader(s)) |
(→Project Details) |
||
| Line 16: | Line 16: | ||
== Project Details == | == Project Details == | ||
| + | <!-- Provides more depth than the Project Description. This is the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into multiple pages and linking to them. --> | ||
Weave consists of two APIs: [http://hg.mozilla.org/services/sync-server Weave Server (sync-server)] and [http://hg.mozilla.org/services/reg-server/summary Weave Registration Server (reg-server)]. Sync is used for synchronizing data with the Weave server, while Reg-Server is used for setting up and managing user accounts. | Weave consists of two APIs: [http://hg.mozilla.org/services/sync-server Weave Server (sync-server)] and [http://hg.mozilla.org/services/reg-server/summary Weave Registration Server (reg-server)]. 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. | 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 == | == Project Plan == | ||
Revision as of 11:31, 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: Weave Server (sync-server) and Weave Registration Server (reg-server). 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
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 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. Documentation should be complete as well.
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.
