Difference between revisions of "Package the Weave Server"

From CDOT Wiki
Jump to: navigation, search
(Project Plan)
Line 1: Line 1:
 
= Package the Weave Server =
 
= Package the Weave Server =
<!-- Replace "Project Name" with the actual name of the project in the line above. -->
 
  
 
== Project Description ==
 
== Project Description ==
Line 28: Line 27:
 
== Project Plan ==
 
== Project Plan ==
  
Tracking mechanism (bugzilla, trac, github, ...):
+
Tracking Mechanism:
* [https://bugzilla.mozilla.org/ Bugzilla]
+
* [https://bugzilla.redhat.com/show_bug.cgi?id=690360 Bugzilla ID: 690360]
* GIT
 
  
Key contact:
+
Key Contacts:
[http://zenit.senecac.on.ca/wiki/index.php/User:Mhoye Mike Hoye (mhoye)]
+
* [http://zenit.senecac.on.ca/wiki/index.php/User:Mhoye Mike Hoye]
<!-- Add links to any mentors or key participants in the community. -->
+
* [http://zenit.senecac.on.ca/wiki/index.php/User:ctyler Chris Tyler]
  
  
 
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. -->
+
* 0.1 - Documentation for the manual installation of Weave server.
* 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 - Initial package release tested with mock and koji. Bugzilla request made to begin Fedora package review process.  
* 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 - Package passes the review process and is submitted to koji for inclusion in Fedora repo.
* 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 ==
 +
 +
=== IRC ===
 +
 +
[irc://irc.mozilla.org:6667/sync #Sync on Moznet]
  
 
=== Mailing Lists ===
 
=== Mailing Lists ===
Line 68: Line 69:
 
=== Blogs ===
 
=== Blogs ===
 
<!-- Links to the blogs of people involved, both inside and outside Seneca -->
 
<!-- Links to the blogs of people involved, both inside and outside Seneca -->
[http://tobyelliott.wordpress.com/ Building Weave (Toby Elliot)]
+
* [http://justinpaulmorgan.blogspot.com/ My Blog]
 
 
[http://justinpaulmorgan.blogspot.com/ Justin's Blog]
 
 
 
==== Seneca Particpants ====
 
[http://zenit.senecac.on.ca/wiki/index.php/User:Jpmorgan Justin Morgan]
 
 
 
==== Non-Seneca Participants ====
 
<!-- Links to the blogs of any non-Seneca participants in this project -->
 
  
==== Planets ====
+
* [http://tobyelliott.wordpress.com/ Building Weave (Toby Elliot)]
<!-- Links to any planets related to this project -->
 
  
 
== Project News ==
 
== Project News ==
 
- Initial project page draft. Built with information obtained from Mike Hoye and the project wikis.
 
- Initial project page draft. Built with information obtained from Mike Hoye and the project wikis.
 
<!-- This is where a permanent record of your releases and updates will go.  In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc. -->
 
<!-- This is where a permanent record of your releases and updates will go.  In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc. -->

Revision as of 10:54, 27 March 2011

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)

Justin Morgan

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:

Key Contacts:


Goals for each release and plans for reaching those goals:

  • 0.1 - Documentation for the manual installation of Weave server.
  • 0.2 - Initial package release tested with mock and koji. Bugzilla request made to begin Fedora package review process.
  • 0.3 - Package passes the review process and is submitted to koji for inclusion in Fedora repo.

Communication

IRC

#Sync on Moznet

Mailing Lists

Weave Server List (Google Groups)

Upsteam Wiki and Web

Weave Mozilla Wiki

Links/Bugs/Tracking

Sync-Server 1.1 Setup/Config (Source)

Reg-Server 1.0 Setup/Config (Source)

Source Code Control

Sync-Server Source/Changelog

Reg-Server Source/Changelog

Blogs

Project News

- Initial project page draft. Built with information obtained from Mike Hoye and the project wikis.