Open main menu

CDOT Wiki β

Changes

Package the Weave Server

1,984 bytes added, 11:11, 25 January 2011
no edit summary
=Package the Weave Server = <!-- Replace "Project Name == Package " with the actual name of the project in the Weave Serverline above. -->
== Project Description ==
 
Weave is a server used by Mozilla Sync for synchronizing personal data (bookmarks, passwords, form values, and cookies) across multiple machines (Windows/Linux, Android, etc). This project involves packaging Weave for Fedora and getting it through the review process. This is so individuals/groups can run a private weave server for their own security or testing purposes.
<!-- 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) ==
<!-- 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 == Project Member(s) == --and to blog sites. -->
== Project Contributor(s) ==
<!-- 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.
NOTE: only Project Leader(s) should add names here. You '''can’t''' should not add your own name to the Contributor list.-->
== 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. --------->
== Project Plan ==
Tracking mechanism (bugzilla, trac, github, ...): Key contacts:<!-- Add links to any mentors or key participants in the community. -->Mike Hoye (mhoye) - mhoye@feralspace.com Goals for each releaseand 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* 0.2* 0.3
== Communication ==
=== Mailing Lists ===
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org -->
== Project News =Upsteam Wiki and Web ===<!-- Links to upstream wiki/web pages -->
This is where your regular updates will go. In these you should discuss the status or === Links/Bugs/Tracking ===<!-- Add a link to any page(s) related to your work, your interactions with other members of including the community bug numbers (e.g., Seneca and Mozillaon bugzilla or trac), problems you have encountered, etc.-->
Put detailed technical information into the Project Details page (i.e.=== Source Code Control ===<!-- Add a link to source code URLs, update it as you go), and save this section for news about participation in the project.including git/mercurial/svn/cvs repositories -->
== Learning subjects =Blogs ===<!-- Links to the blogs of people involved, both inside and outside Seneca -->
==== Seneca Particpants ====
Justin Morgan (Tentative)
==== Non-Seneca Participants ====
<!-- Links to the blogs of any non-Seneca participants in this project -->
== Resources == Planets ====<!--Links to any planets related to this project -->
== Meeting(s) Project News ==
<!--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. --->
1
edit