Project Hosting - ITv
Alfonso de la Guarda
alfonsodg at gmail.com
Thu Oct 25 12:32:24 EDT 2007
1. Project name : ITv
2. Existing website, if any : http://www.cos-la.org/ITv
<http://www.cosperu.com/EduKT>
3. One-line description : Interactive Television with realtime
audio/video, graphics and text
4. Longer description : ITv has 2 parts, a daemon which is
resident on the school server (for local streams) or
a regular high bandwidth internet
server, which can share realtime and bi-directional contents
between their users. The client is gtk
based and uses gstreamer for XO and vlc for windows/linux/osx.
The main goal is provide an all-one
window which has draggable components. The daemon takes a regular
stream through icecast, shoutcast and
steamcast and syncronises with the contents, but also the
children with their XOs can stream using
their cameras.
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 at gmail.com
#2 cecilia.contreras Cecilia Contreras Vassallo
cecilia.contreras at gmail.com
#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 goal is provide an auxiliar tool for tele-education, allowing sharing
realtime contents.
--
--------------------------------
Alfonso de la Guarda
ICTEC SAC
www.cos-la.org
www.delaguarda.info
Telef. 97550914
4726906
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20071025/525fbd97/attachment.html>
More information about the Devel
mailing list