[prev in list] [next in list] [prev in thread] [next in thread]
List: olpc-devel
Subject: EduKT Project
From: "Alfonso de la Guarda" <alfonsodg () gmail ! com>
Date: 2007-05-29 19:11:06
Message-ID: ed60564a0705291211i22d7ef0eo6a53025ac42b2c78 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
1. Project name : EduKT
2. Existing website, if any : http://www.cosperu.com/EduKT
3. One-line description : Content Multimedia Builder
4. Longer description : Application that allow create books,
presentations or any type of multimedia
: contents with a few clicks easly. It
works on any platform with gtk+python
:
:
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 alfonsodg Alfonso de la Guarda Reyes
alfonsodg@gmail.com
#2
#3
...
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:
[ ] Yes, named after our project name
[ ] Yes, named ______________________
[X] 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. Vhost setup
[x] Yes, set up a vhost for the domain cosperu.com pointing to our
project website.
[ ] No, we don't have a project domain, or don't want to use one. We'll
use the laptop.org website address.
11. 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.
12. Notes/comments:
The idea is that the contents will be made on any OS and then played on the
OLPC and -obviously- shared by the mesh
--
--------------------------------
Alfonso de la Guarda
INVESTIGACION Y CONSULTORIA TECNOLOGICA SAC
Telef. 97550914
4726906
[Attachment #5 (text/html)]
<pre>1. Project name : EduKT<br>2. Existing website, if any : \
<a href="http://www.cosperu.com/EduKT">http://www.cosperu.com/EduKT</a><br>3. \
One-line description : Content Multimedia Builder<br><br>4. Longer \
description : Application that allow create books, presentations or any \
type of multimedia <br> : contents with a few clicks \
easly. It works on any platform with gtk+python<br> \
:<br> :<br><br>5. URLs of similar \
projects :<br><br>6. Committer list <br> Please list the maintainer (lead \
developer) as the first entry. Only list <br> developers who need to be given \
accounts so that they can commit to your<br> project's code repository, or push \
their own. There is no need to list <br> non-committer developers.<br><br> \
Username Full name SSH2 key URL E-mail<br> \
-------- --------- ------------ ------<br> #1 \
alfonsodg Alfonso de la Guarda Reyes <a \
href="mailto:alfonsodg@gmail.com">alfonsodg@gmail.com</a><br> #2<br> #3<br> \
...<br><br> If any developers don't have their SSH2 keys on the web, please \
attach them <br> to the application e-mail.<br><br> 7. Preferred development \
model<br><br> [X] Central tree. Every developer can push his changes directly to \
the <br> project's git tree. This is the standard model that will be \
familiar to <br> CVS and Subversion users, and that tends to work well for most \
projects. <br><br> [ ] Maintainer-owned tree. Every developer creates his own git \
tree, or<br> multiple git trees. He periodically asks the maintainer to look at \
one<br> or more of these trees, and merge changes into the maintainer-owned, \
<br> "main" tree. This is the model used by the Linux kernel, and is \
<br> well-suited to projects wishing to maintain a tighter control on code<br> \
entering the main tree.<br><br> If you choose the maintainer-owned tree model, but \
wish to set up some <br> shared trees where all of your project's committers \
can commit directly, <br> as might be the case with a "discussion" tree, \
or a tree for an individual <br> feature, you may send us such a request by e-mail, \
and we will set up the <br> tree for you.<br><br>8. Set up a project mailing \
list:<br><br> [ ] Yes, named after our project name<br> [ ] Yes, named \
______________________<br> [X] No<br><br> When your project is just getting off \
the ground, we suggest you eschew <br> a separate mailing list and instead keep \
discussion about your project<br> on the main OLPC development list. This will give \
you more input and <br> potentially attract more developers to your project; when \
the volume of <br> messages related to your project reaches some critical mass, we \
can <br> trivially create a separate mailing list for you.<br><br> If you need \
multiple lists, let us know. We discourage having many <br> mailing lists for \
smaller projects, as this tends to <br> stunt the growth of your project community. \
You can always add more lists<br> later.<br><br>9. Commit notifications<br><br> [ \
] Notification of commits to the main tree should be e-mailed to the list<br> \
we chose to create above <br> [ ] A separate mailing list, <projectname>-git, \
should be created for commit<br> notifications<br> [X] No commit \
notifications, please<br><br>10. Vhost setup<br><br> [x] Yes, set up a vhost for \
the domain <a href="http://cosperu.com">cosperu.com</a> pointing to our <br> \
project website.<br><br> [ ] No, we don't have a project domain, or don't \
want to use one. We'll<br> use the <a href="http://laptop.org"> \
laptop.org</a> website address.<br><br>11. Shell accounts<br><br> As a general \
rule, we don't provide shell accounts to developers unless <br> there's a \
demonstrated need. If you have one, please explain here, and <br> list the \
usernames of the committers above needing shell access.<br><br>12. \
Notes/comments:</pre>The idea is that the contents will be made on any OS and then \
played on the OLPC and -obviously- shared by the mesh<br clear="all"> <br>-- \
<br><br>--------------------------------<br>Alfonso de la Guarda<br>INVESTIGACION Y \
CONSULTORIA TECNOLOGICA SAC<br>Telef. \
97550914<br> 4726906
_______________________________________________
Devel mailing list
Devel@laptop.org
http://mailman.laptop.org/mailman/listinfo/devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic