Beast Tutorial Volunteers

[Tim Janik]

hi All.

the idea/need for a comprehensive manual or tutorial for beast
has been brought up a few of times recently:
   http://mail.gnome.org/archives/beast/2007-May/msg00000.html
   http://mail.gnome.org/archives/beast/2007-May/msg00003.html

unfortunately i am fairly busy with other projects (rapicorn,
glib/gtk+ which also have resource shortages), so i probably
won't have the time to write a full manual any time soon.

thus, i'd like to suggest to start this as a community effort,
e.g. people from the beast mailing list could speak up if they
have interest/resources to help with tutorial creation.

first, we'd need someone to coordinate the effort and continuously
bug people about outstanding actions on accomplishing the tutorial.
any single person or also small team of people could do this, we
just need someone to speak up, who is determined enough to actually
persue this subproject over some time ;)

the core developers (Stefan, me) will of course provide all the
help that is required, i.e. just flood us with questions where
needed and we'll do our best to answer. given we get the personal
resources sorted out, i think a suitable process probably could
look like this:

a) come up with an section index and discuss that here on the beast
    list, the "current" version of that index is probably kept easiest
    as a beast.gtk.org wiki page. people don't even need to sign
    up there for editing.

b) do coarse fill-ins of the sections outlined in the index, this
    can be done by multiple persons, core devels are required to
    review and help with the fill-ins here. sending us weekly
    reminders about the sections still waiting for review would
    probably help in the progress, e.g. similar to the weekly
    bug report lists on gtk-devel-list:
      http://mail.gnome.org/archives/gtk-devel-list/2007-May/msg00267.html

c) after coarse material is available, the sections will need some
    editing/rewriting/complementing to be more coherent and fit
    an overall style, this probably needs little to no core devel
    attention (so it has little chance to block on us ;)

so folks, please stand up if there is any constructive input
you can provide on this subproject. because without any voluntary
efforts coming from the user base, beast is highly unlikely to
get a manual or extensive tutorial.

---
ciaoTJ
_______________________________________________
beast mailing list
beast@...
http://mail.gnome.org/mailman/listinfo/beast

[Stefan Westerfeld]

   Hi!

On Mon, May 28, 2007 at 02:59:30PM +0200, Tim Janik wrote:

> the idea/need for a comprehensive manual or tutorial for beast
> has been brought up a few of times recently:
>    http://mail.gnome.org/archives/beast/2007-May/msg00000.html
>    http://mail.gnome.org/archives/beast/2007-May/msg00003.html
>
> unfortunately i am fairly busy with other projects (rapicorn,
> glib/gtk+ which also have resource shortages), so i probably
> won't have the time to write a full manual any time soon.
>
> thus, i'd like to suggest to start this as a community effort,
> e.g. people from the beast mailing list could speak up if they
> have interest/resources to help with tutorial creation.
>
> a..c) [...]

d) I'd like to add that there is also the "Glossary" in the Wiki
already:

   http://beast.gtk.org/wiki:BeastGlossary

It right now only explains two terms, as derived from IRC questions:

   http://beast.gtk.org/wiki:InstrumentOutput
   http://beast.gtk.org/wiki:PostProcessor

However, it may be a good idea for those that are working on the manual
to try to capture more of the BEAST terminology there. By choosing
suitable Wiki words for each term relevant in thinking about BEAST, we
could create a useful resource. Of course, where it is not clear what is
to say about something, core developers like me can provide info or edit
as needed.

There is of course a technical problem with terms that don't become wiki
words easily, like Track, Part, Song and so on, but I think it is worth
the extra markup required to make glossary entries for them, too. See

   http://beast.gtk.org/wiki:ExtendedWikiMarkup

(i.e. they should be written as [Track] in the wiki).

   Cu... Stefan
--
Stefan Westerfeld, Hamburg/Germany, http://space.twc.de/~stefan
_______________________________________________
beast mailing list
beast@...
http://mail.gnome.org/mailman/listinfo/beast