[Radiance-dev] radiance-online changes in June 2006

[Georg Mischler]

I guess it's time to crawl out from under my rock once again...

It may make sense to split the job into the following parts:

1) CVS
2) Source and binary downloads
3) Mailing lists
4) Mailing list archives
5) General introduction and links
6) Workshop data
7) Knowledge base (future)

The first three can easily be solved on Sourceforge. I already
run a project there, and would have no problem to set up another
one. Unfortunately, their mailing list archive functionality
is suboptimal, so we better keep item 4) on a seperate site.

I can host another domain on my account at www.pair.com for 1 USD
per Month. It should not be too much work (I hope) to maintain
the mailing list archives and the general information pages there.
The easiest way to distribute the workload would be to turn the
complete site (minus the archives) into a wiki. Most of the
currently static pages could be made dynamic, so that the members
of the community can help to keep them up to date. The wiki
technology then allows to grow that into a more complete
knowledgebase collaboratively over time.

The only problem are the presentations from the Workshops,
because of their sheer volume. If we want to keep those CDs
online both as ISO images and for direct access, then we need a
place to store up to 1.5 GB of data per year. Since this data
never changes once it has been posted, maybe Radsite at LBNL
would be a good place to host it. That way they could help us the
most with the least maintenance effort at their end.

I'm still waiting for Peter do divulge a few real life figures
about work effort, disk usage, and bandwidth requirements. The
latter shouldn't be a problem as I have 200GB/month to burn, but
knowing more about the first two would make it easier to decide
about the best way to proceed.

over the last year or so, I have neglected the Radiance community
(and others) much more than I would have liked. I'm not sure if
I'll have much more time available for active development in the
future, but I'd be happy to offer some support for the community
infrastructure. Keeping an eye on a few mostly automated
procedures should be well within my capacities.  I am already
familiar with both Mailman (for the archives) and MoinMoin (for
the wiki), so it's just a matter of configuring another instance
of each for this domain.


-schorsch

-- 
Georg Mischler  --  simulations developer  --  schorsch at schorsch com
+schorsch.com+  --  lighting design tools  --  http://www.schorsch.com/