Difference between revisions of "Package the Weave Server"

From CDOT Wiki
Jump to: navigation, search
(Package the Weave Server)
(Milestone 0.3)
 
(55 intermediate revisions by the same user not shown)
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 ==
 
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 [http://fedoraproject.org/wiki/Package_Review_Process package review process]. This is being done so individuals, groups, and companies can run their own private weave server.
 
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 [http://fedoraproject.org/wiki/Package_Review_Process package review process]. This is being done so individuals, groups, and companies can run their own private weave server.
<!-- Description should be no longer than a paragraph.  Include links to any relevant on-line resources.  For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->
 
  
 
== Project Leader(s) ==
 
== Project Leader(s) ==
 +
[http://zenit.senecac.on.ca/wiki/index.php/User:Jpmorgan Justin Morgan]
 +
 +
== 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. -->
  
<!-- Name(s) of primary people working on the project.  If you want to join a project as leader, discuss with other leaders first. Include links to personal pages within wiki and to blog sites. -->
+
Weave Server consists of two APIs:
 +
* [http://hg.mozilla.org/services/sync-server Sync (sync-server)]
 +
* [http://hg.mozilla.org/services/reg-server Registration (reg-server)]
  
 +
Sync-server is used to synchronizing data with Sync clients. Reg-server is used for creating and managing user accounts.
  
== Project Contributor(s) ==
+
The objective of the project is to have the Weave server packaged and available on the main Fedora respositories (yum install weave). The package should allow a user to install a working Weave server with minimal configuration.
  
<!-- Name(s) of people casually working on the project, or who have contributed significant help.  Include links to personal pages within wiki. Adding the names of your contributors here is a nice way to thank them.
+
== Project Plan ==
  
NOTE: only Project Leader(s) should add names here. You should not add your own name to the Contributor list. -->
+
Tracking Mechanism:
 +
* [http://bugzilla.redhat.com Bugzilla]
  
== Project Details ==
+
Key Contacts:
 +
* [http://zenit.senecac.on.ca/wiki/index.php/User:Mhoye Mike Hoye]
 +
* [http://zenit.senecac.on.ca/wiki/index.php/User:Chris_Tyler Chris Tyler]
  
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.
+
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 submitted for package review process.
 +
* 0.3 - Package completes review process and is ready for inclusion in the official Fedora repos.
  
The 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 Milestones/Releases ==
  
<!-- 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. -->
+
=== Milestone 0.1 ===
 +
[http://justinpaulmorgan.blogspot.com/2011/03/installing-weave-server-fedora.html Installing Weave Server Documentation]
  
== Project Plan ==
+
=== Milestone 0.2 ===
 +
[https://bugzilla.redhat.com/show_bug.cgi?id=690360 Bugzilla ID: 690360 - Package Review]
  
Tracking mechanism (bugzilla, trac, github, ...): [https://bugzilla.mozilla.org/ Bugzilla]
+
=== Milestone 0.3 (Not Final)===
 +
Latest Package Release (20110314-1):
 +
* [http://matrix.senecac.on.ca/~jpmorgan/SPECS/weave.spec SPEC]
 +
* [http://matrix.senecac.on.ca/~jpmorgan/SRPMS/weave-20110314-1.fc14.src.rpm SRPM]
 +
* [http://matrix.senecac.on.ca/~jpmorgan/RPMS/weave-20110314-1.fc14.noarch.rpm RPM]
  
Key contacts:
+
[http://zenit.senecac.on.ca/wiki/index.php/Winter_2011_Handout_-_Package_the_Weave_Server Winter 2011 Handout - Package the Weave Server]
[http://zenit.senecac.on.ca/wiki/index.php/User:Mhoye Mike Hoye (mhoye)]
 
<!-- Add links to any mentors or key participants in the community. -->
 
  
 +
== Communication ==
  
Goals for each release and plans for reaching those goals:
+
=== IRC ===
<!-- 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.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 ==
+
[irc://irc.mozilla.org:6667/sync #Sync on Moznet]
  
 
=== Mailing Lists ===
 
=== Mailing Lists ===
Line 50: Line 62:
 
[https://wiki.mozilla.org/Services/Sync Weave Mozilla Wiki]
 
[https://wiki.mozilla.org/Services/Sync Weave Mozilla Wiki]
  
=== Links/Bugs/Tracking ===
+
=== Source Code (Mozilla) ===
<!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) -->
+
<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories -->
 +
[http://hg.mozilla.org/services/sync-server/ Sync-server Source/Changelog]
 +
 
 +
[http://hg.mozilla.org/services/reg-server/ Reg-server Source/Changelog]
 +
 
 +
=== Blogs ===
 +
<!-- Links to the blogs of people involved, both inside and outside Seneca -->
 +
* [http://justinpaulmorgan.blogspot.com/ My Blog]
  
[https://wiki.mozilla.org/Labs/Weave/Sync/1.1/Setup Sync-Server 1.1 Setup/Config (Source)]
+
* [http://annasob.wordpress.com Anna Sobiepanek]
  
[https://wiki.mozilla.org/Labs/Weave/User/1.0/Setup  Reg-Server 1.0 Setup/Config (Source)]
+
* [http://tobyelliott.wordpress.com/ Toby Elliot (Building Weave)]
  
=== Source Code Control ===
+
== Project News ==
<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories -->
+
===4/12/2011===
[http://hg.mozilla.org/services/sync-server/ Sync-Server Source/Changelog]
+
Weave package now uses upstream sources, version reflect Mercurial tag date.
[http://hg.mozilla.org/services/reg-server/ Reg-Server Source/Changelog]
 
  
=== Blogs ===
+
===4/10/2011===
<!-- Links to the blogs of people involved, both inside and outside Seneca -->
+
Updated Milestone 0.2 with latest package release with Bugzilla Review Process fixes.
[http://tobyelliott.wordpress.com/ Building Weave (Toby Elliot)]
 
  
==== Seneca Particpants ====
+
===3/30/2011===
[http://zenit.senecac.on.ca/wiki/index.php/User:Jpmorgan Justin Morgan]
+
Updated Milestone 0.2 to release 3 as per changes from review process.
  
==== Non-Seneca Participants ====
+
===3/27/2011===
<!-- Links to the blogs of any non-Seneca participants in this project -->
 
  
==== Planets ====
+
Both 0.1 and 0.2 milestones have been completed. Install documentation added to wiki and initial bugzilla request has been submitted for Package review. Links added to package files.
<!-- Links to any planets related to this project -->
 
  
== Project News ==
+
===2/2/2011===
  
 +
Initial wiki page created. Met with Mike Hoye to discuss initial package design. It was decided that the /etc/httpd/conf.d/ folder would be used to automatically pick up the weave apache conf file to help automate the install process.
 
<!-- 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. -->

Latest revision as of 20:53, 12 April 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 Details

Weave Server consists of two APIs:

Sync-server is used to synchronizing data with Sync clients. Reg-server is used for creating 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). The package should allow a user to install a working Weave server with minimal configuration.

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 submitted for package review process.
  • 0.3 - Package completes review process and is ready for inclusion in the official Fedora repos.

Project Milestones/Releases

Milestone 0.1

Installing Weave Server Documentation

Milestone 0.2

Bugzilla ID: 690360 - Package Review

Milestone 0.3 (Not Final)

Latest Package Release (20110314-1):

Winter 2011 Handout - Package the Weave Server

Communication

IRC

#Sync on Moznet

Mailing Lists

Weave Server List (Google Groups)

Upsteam Wiki and Web

Weave Mozilla Wiki

Source Code (Mozilla)

Sync-server Source/Changelog

Reg-server Source/Changelog

Blogs

Project News

4/12/2011

Weave package now uses upstream sources, version reflect Mercurial tag date.

4/10/2011

Updated Milestone 0.2 with latest package release with Bugzilla Review Process fixes.

3/30/2011

Updated Milestone 0.2 to release 3 as per changes from review process.

3/27/2011

Both 0.1 and 0.2 milestones have been completed. Install documentation added to wiki and initial bugzilla request has been submitted for Package review. Links added to package files.

2/2/2011

Initial wiki page created. Met with Mike Hoye to discuss initial package design. It was decided that the /etc/httpd/conf.d/ folder would be used to automatically pick up the weave apache conf file to help automate the install process.