On Mon, 2009-11-02 at 07:10 +1100, Patrick Shirkey wrote: > On 11/02/2009 03:11 AM, David Robillard wrote: > > On Sun, 2009-11-01 at 12:09 +1100, Patrick Shirkey wrote: > > > >> I'm not sure what the limitations of the existing system are but in > >> general having a central location where all extensions are collated with > >> explicit details about their usage and examples for how to write code > >> for them them would go a long way to making the system more developer > >> friendly. > >> > >> Providing a weekly/monthly mailout which lists the new extensions and a > >> brief description with links to code examples and usage cases would also > >> be helpful for developers who want to keep up to date with the latest > >> offerings. > >> > >> Essentially spending some time on automating the notifications system > >> now will be useful for everyone and could go a long way to increase the > >> pickup and development rate for LV2 which is good for everyone. > >> > >> > > The volume isn't really big enough for this, to be honest. We can set > > up an RSS feed or something, or an announce list, but I really don't see > > this as being an effective thing to worry about at this point in time. > > > > > I see it as being highly effective. Having a regular community wide > update of useful LV2 news is a good thing (tm). For example it would be > useful to have a monthly update for the wider community that is sent to > the LAA list. the reason I suggest an automated letter is so that you or > someone else doesn't have to manually compile the news. If LV2 really > starts to take off (and it should) then we can expect to see literally > thousands of plugins and extensions being produced over the coming > years. Automating the process now gives us a head start.
Isn't this basically what LAA is for anyway? At the end of the day the author of <whatever> needs to send the announcement to /somewhere/, you can't automate news generation, it has to come from people somehow. The fully automated thing is feasible for extensions published at http://lv2plug.in/ but not much else. This is an argument for using a CMS over a wiki though. It's easy to make an RSS feed of a 'news' page and tag posts to go there. With a wiki, not so much. The only real options are wordpress and drupal since they are trivial to install on Dreamhost. > > So maybe the best housekeepingey thing to do right now is get all the > > content over to the wiki, and tidy up the wiki, then we can make it the > > main page for http://lv2plug.in ? > > > > This won't be a problem. I can start on this process on Wed. Feel free > to contact me off list about the specific items you would like to get > some attention. Don't start until we're sure this is the best plan. It's not really feasible to do the above stuff via mediawiki. -dr _______________________________________________ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev