17 Jun
2009
17 Jun
'09
12:25 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Marc-Olivier Barre wrote:
There's a git repository and gitweb available on git.linuxaudio.org,
even though it's not been used for much yet.
Furthermore the wiki allows for personal pages. eg.
http://wiki.linuxaudio.org/wiki/user/ppalmers
There's a GTD (getting things done) plugin for dokuwiki to schedule
tasks and organize collaborations. Surely it'll need some customizing
and a certainly a moderator who manages the project(s).
We're using < 20% of our bandwidth and download.linuxaudio.org currently
has ~100GB available. OTOH. archive.org would just as well be usable to
host the audio and project files.
On Tue, 16 Jun 2009 23:37:26 +0800, Ray Rashif
<schivmeister(a)gmail.com>
wrote:
Why that? Ok, it is minimalistic, but a full-screen video monitor
synchronized to the soundtrack is quite sufficient. I've done a few film
soundtracks like that.
Having had done film audio for a few months, I
have to say it's a really
difficult task for free software to handle as of the current state
(Ardour
> +
> Xjadeo is not a solution). Well, Blender has it's own audio track... we could
also try that out
Robin: btw, how's your ardour patch going ?
Frozen in ice :-/ I'm too busy with work and don't have another film
project until the end of the year that would make scratch this itch.
Anyway, why
not get together and provide THEM w/ content? The Blender
team
wants to test their capabilities, and in order
for LA to do the same, I
suggest taking the initiative first and offer something to someone
instead
of waiting for an offer.
Indeed, taking the fight to them is probably better suited. But in this
case it would not be a matter of working on durian, but taking the former
projects and making our own audio ?
I'm thinking sound design collaboration:
* Create a team (open to all LA subscribers and anyone interested in
Linux
+
Audio)
* Finalise registrants/team members (if you don't do this and decide to
make
the whole thing informal there'll be trouble later on)
* Set up a Wiki with the tasks; each member puts their name down if they
want to undertake a task (eg. sound design for character so
and so, include a README of sort documenting the software used - can be a
logbook if you want)
* Set up a VCS repo so each member can commit his work, and it can be
reviewed and edited by others if required (perhaps a core committee;
decided
upon during the registration finalising stage) eg.:
That could work. Now, where do we host ? ICO : HELLLLOOOOOO ???
(I'm trying hard to send a signal here :D)
Yeah, Mr. linuxaudio.org, what do you think?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAko4/NwACgkQeVUk8U+VK0K+cQCeLKgWuMHN/GwHUNu3XIEMfcGV
OskAnjaxsnRJs1K9zW+FWsHPjNtKQfUg
=JYTN
-----END PGP SIGNATURE-----