Project Hosting Application: ImageToSound
1. Project name : ImageToSound
2. Existing website, if any : http://wiki.laptop.org/go/ImageToSound
3. One-line description : ImageToSound is an Activity to sonify images.
4. Longer description : ImageToSound is an Activity to sonify images.
Currently, images should
be created with another Activity (e.g. Paint or Record) and then opened from
the Journal with ImageToSound.
Requires csound >= 5.08.
:
:
:
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 URLE-mail
- --
#1 cesare Cesare Marilungo
#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, -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. Translation
[X] Set up the laptop.org Pootle server to allow translation commits to be
made
[ ] Translation arrangements have already been made at ___
12. Notes/comments:
ssh-rsa
B3NzaC1yc2EBIwAAAQEAp8AcZjjwVI7UbldocoB6NPp4pBmRpHUtPvLEx4K+zQwpqfbSXERxXaQuXij17q8rAdTVYO1cB8KyEsxcMnvPCIyd7YPBfRF5BYdWGabc5sPM/IE5e8KUPbLAFMdjtwjhYW9SAwGU2G00zVid6mWK3mRfZkQSVICqMatz4nCx1iuGpGk5U4gXaiChoBg5JrfK90VkDnz5cmS6HcSAJr9Lfy713SxeOiKdFdnVNZ+9dMALk58VQCsKsMHqoyjnv4gmX/h5bg0zd4QdjunR4GX0N/Y0PDzK88W2xFhKfdsaw9pC8YhWVTxGLKQHZ1NUZcJYxHdKdQP3M9K0qY4CK+YJ4Q==
[EMAIL PROTECTED]
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: OLPC promotes terrorism
Bernardo Innocenti wrote: > http://erratasec.blogspot.com/2008/01/why-olpc-promotes-terrorism.html > > Didn't you know that Python was a communist language? > > If any chip maker was paying for this bullshit, they'd be > really wasting their money! > > Depressing. - c. -- www.cesaremarilungo.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Hershey Felder, Zulu Musical Instruments, Essential To Develop Musical Traditions In Africa
You're answering to a spambot message. Regards, -c. M. Edward (Ed) Borasky wrote: > william romsay wrote: > >> Hershey Felder, Zulu Musical Instruments, Essential To Develop Musical >> Traditions In Africa >> >> >> African music is the music of Africans who live in a large region of 50 >> nations, each with a special culture, history and language, South of >> Sahara. Zulu musical instruments are part of this multilingual culture. >> African music has some distinct characteristics: the use of repetition >> is one of them. Another important characteristic is the polyphony; this >> is the combination of different musical parts played simultaneously. >> >> >> >> >> ___ >> Devel mailing list >> Devel@lists.laptop.org >> http://lists.laptop.org/listinfo/devel >> > > 1. Interesting ... can you post some links? > > 2. I think it's time the OLPC project had a list specific to audio on > the XO and the "world music" aspects of it. Does someone on the project > want to create such a list in the main MailMan area, or should I go > ahead and start a Google group on the subject? > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > > > -- www.cesaremarilungo.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: pyglet
Ah! I didn't notice that it is based mostly on OpenGL. Sorry for the noise. -c. NoiseEHC wrote: > The XO does not have hardware OpenGL support and has a very slow > processor so OpenGL is disabled in X. It means that 70% of pyglet will > not be too useful. > > Cesare Marilungo wrote: >> http://www.pyglet.org/ >> >> Just installed and tested (not on the XO yet). It seems a good >> alternative to pygame. >> >> -c. >> >> > > -- www.cesaremarilungo.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
pyglet
http://www.pyglet.org/ Just installed and tested (not on the XO yet). It seems a good alternative to pygame. -c. -- www.cesaremarilungo.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Sugar on Slackware 12.0
Eduardo Silva wrote: >> Should I add this infos on the wiki? >> > > > That would be good, maybe you can follow this entry as a guide > http://wiki.laptop.org/go/Ubuntu > > cheers. > > Ed. > > > I've already made a page on the wiki. But I plan to rebuild sugar on a clean Slackware installation (mine wasn't exactly fresh, I already had lots dependencies) to document this more in detail. -c. -- www.cesaremarilungo.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Sugar on Slackware 12.0
I just wanted to report that I've sucessfully got sugar built and running on Slackware 12. Of course there are a lot of dependencies to install (gstreamer and friends, some gnome libs) and some library to update if you start from a fresh Slackware installation. But sugar is not so hard to build in distros other than Fedora and Ubuntu, really. I did: sugar-jhbuild update sugar-jhbuild built and then I compiled and installed the missing libraries and the python modules. The most tricky part was Xephyr, which was missing. Since I didn't want to mess with my xorg installation I just took xorg-server-1.3.0.0 source (which is the version that ships with Slackware 12) and compiled it with: ./configure --prefix=/usr/local/xserver-xephyr --exec-prefix=/usr/local/xserver-xephyr --enable-kdrive --enable-xephyr && make && make install Then I made a symbolic link to xephyr in /usr/local/bin. Should I add this infos on the wiki? Cheers, -c. -- www.cesaremarilungo.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Updating a B4 machine for the first time
Jake B wrote: > Could you please post instructions? I think others would benefit > (myself included). > Thanks. > > Jake I don't know if these instructions will work for others. Anyway: I've followed the infos on the wiki to prepare a usb key with latest firmware and build image. Then, from the open firmware prompt (ok is the prompt, it is not part of the command): ok flash u:\boot\q2d07.rom This updated the firmware. Then I did: ok copy-nand u:\boot\os653.img to update the image. Cheers, -c. > > On Dec 21, 2007 2:47 PM, Cesare Marilungo < [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Ivo Emanuel Gonçalves wrote: > > On 12/21/07, Cesare Marilungo < [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > >> The developer console says: > >> OLPC Build: None. > >> Firmware: None. > >> > > > > That IS strange. > > > > The process of updating is easy, though. > > > > 1) Get a USB key with 500mb of free space. > > 2) Get the olpc-auto.zip (it's linked on the wiki) and extract > it to the USB key > > 3) You'll have a "boot" directory there now. Download the > stable or > > unstable image (also linked in the wiki). If you want the stable > > right now it's version 653. You'll find a os653.img and os653.crc, > > get both files inside the "boot" directory > > 4) Plug the energy cord, turn off the laptop, insert USB key, > turn on laptop > > 5) It's all automatic, but watch for warnings and that's it > > > > -Ivo > > > > P.S: I reckon the olpc-auto.zip has an older firmware image. > That is > > not a problem, but if you'll want to use the more recent one, > you have > > to throw it inside the "boot" folder AND delete the older .rom file > > there. > > > > > > > Thank you for your help, Ivo. > > I already solved everything. Mitch Bradley kindly guided me > through the > whole process on irc. > > -c. > > -- > www.cesaremarilungo.com <http://www.cesaremarilungo.com> > > ___ > Devel mailing list > Devel@lists.laptop.org <mailto:Devel@lists.laptop.org> > http://lists.laptop.org/listinfo/devel > > -- www.cesaremarilungo.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Updating a B4 machine for the first time
Ivo Emanuel Gonçalves wrote: > On 12/21/07, Cesare Marilungo <[EMAIL PROTECTED]> wrote: > >> The developer console says: >> OLPC Build: None. >> Firmware: None. >> > > That IS strange. > > The process of updating is easy, though. > > 1) Get a USB key with 500mb of free space. > 2) Get the olpc-auto.zip (it's linked on the wiki) and extract it to the USB > key > 3) You'll have a "boot" directory there now. Download the stable or > unstable image (also linked in the wiki). If you want the stable > right now it's version 653. You'll find a os653.img and os653.crc, > get both files inside the "boot" directory > 4) Plug the energy cord, turn off the laptop, insert USB key, turn on laptop > 5) It's all automatic, but watch for warnings and that's it > > -Ivo > > P.S: I reckon the olpc-auto.zip has an older firmware image. That is > not a problem, but if you'll want to use the more recent one, you have > to throw it inside the "boot" folder AND delete the older .rom file > there. > > > Thank you for your help, Ivo. I already solved everything. Mitch Bradley kindly guided me through the whole process on irc. -c. -- www.cesaremarilungo.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Updating a B4 machine for the first time
Hi, I just received a B4 machine and I am a bit puzzled by the info in the wiki about updating to the latest build. The developer console says: OLPC Build: None. Firmware: None. and there isn't any 'olpc-update' script. There's no /security directory also. I have a wireless network (WPA encrypted) which is not seen at the moment. So I need to use a Usb key. I just need to test an activity I'm developing so I guess I can use the stable build. How should I update the machine without risking to brick it? Thanks in advance. Cesare -- www.cesaremarilungo.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
