Project Hosting Application
Noah Kantrowitz
kantrn at rpi.edu
Wed Sep 26 05:44:55 EDT 2007
Danny, don't bother making a git tree for them. I was going to set them
up with a Subversion account on olpc.coderanger.net. Their team is
largely windows based so git will just be a headache (no that that isn't
normal ;-).
--Noah
Jason J. Kong wrote:
> 1. Project name : OnLine Processing of Content
> 2. Existing website, if any :
> 3. One-line description : A online content processing and
> management system for OLPC.
> 4. Longer description : OnLine Processing of Content (codename:
> sara) is
> a content management system that accepts and catalogs media and makes it
> accessible to users of the OLPC Project laptops in an organized
> manner. The
> system will be simple and easy to use, store relationship information
> between
> content, and be language-portable. Content submitters can log in using
> OpenID
> to submit a wide variety of media such as images, videos, audio clips,
> articles,
> or translated versions of existing content, which will then be made
> available
> to users. All content is tagged to make it easy for users to browse
> related
> items, or find the same item in an alternate language.
>
> 5. URLs of similar projects :
>
> 6. Committer list
> Please list the maintainer (lead developer) as the first entry. Only
> list
> developers who need to be given accounts so that they can commit to
> your
> project's code repository, or push their own. There is no need to list
> non-committer developers.
>
> Username Full name SSH2 key URL
> E-mail
> -------- --------- ------------
> ------
> #1 debsj John Debs debsj-publickey
> debsj at rpi.edu
> #2 hurlop Paul Hurlock-Dick hurlop-publickey
> hurlop at rpi.edu
> #3 kongj Jason Kong kongj-publickey
> kongj at rpi.edu
> #4 zandem Michael Zander zandem-publickey
> zandem at rpi.edu
>
>
> If any developers don't have their SSH2 keys on the web, please
> attach them
> to the application e-mail.
>
> 7. Preferred development model
>
> [X] Central tree. Every developer can push his changes directly to the
> project's git tree. This is the standard model that will be
> familiar to
> CVS and Subversion users, and that tends to work well for most
> projects.
>
> [ ] Maintainer-owned tree. Every developer creates his own git tree, or
> multiple git trees. He periodically asks the maintainer to look
> at one
> or more of these trees, and merge changes into the
> maintainer-owned,
> "main" tree. This is the model used by the Linux kernel, and is
> well-suited to projects wishing to maintain a tighter control on
> code
> entering the main tree.
>
> If you choose the maintainer-owned tree model, but wish to set up some
> shared trees where all of your project's committers can commit
> directly,
> as might be the case with a "discussion" tree, or a tree for an
> individual
> feature, you may send us such a request by e-mail, and we will set
> up the
> tree for you.
>
> 8. Set up a project mailing list:
>
> [X] Yes, named after our project name
> [ ] Yes, named ______________________
> [ ] No
>
> When your project is just getting off the ground, we suggest you eschew
> a separate mailing list and instead keep discussion about your project
> on the main OLPC development list. This will give you more input and
> potentially attract more developers to your project; when the volume of
> messages related to your project reaches some critical mass, we can
> trivially create a separate mailing list for you.
>
> If you need multiple lists, let us know. We discourage having many
> mailing lists for smaller projects, as this tends to
> stunt the growth of your project community. You can always add more
> lists
> later.
>
> 9. Commit notifications
>
> [ ] Notification of commits to the main tree should be e-mailed to
> the list
> we chose to create above
> [ ] A separate mailing list, <projectname>-git, should be created
> for commit
> notifications
> [X] No commit notifications, please
>
> 10. Shell accounts
>
> As a general rule, we don't provide shell accounts to developers unless
> there's a demonstrated need. If you have one, please explain here, and
> list the usernames of the committers above needing shell access.
>
> 11. Notes/comments:
> The project is been working on with the help of Noah Kantrowitz.
> ------------------------------------------------------------------------
>
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
URL: <http://lists.laptop.org/pipermail/devel/attachments/20070926/ead82355/attachment.sig>
More information about the Devel
mailing list