[openbeos] Re: the new website

Hi Stephan,

On 2006-08-27 at 18:04:30 [+0200], Stephan Assmus <superstippi@xxxxxx> wrote:
> 
[ ... ] 
> You guys keep discussing the idealistic way... what you seem to completely
> forget is that the new website was designed to fix a specific problem. And
> if your view on the new site would be fully implemented, we would have that
> same problem again/still! Which is that "official news letters" will be
> released once every three quarters of a year.

Yes, official newsletters will be released only once in a while, as we 
haven't got enough resources to sustain a higher output rate. But, unless I 
miss something important, nothing is every going to change that, no matter 
the structure of the website. There simply have been too few volunteers 
writing articles, I guess. While we might try to improve that by implementing 
some kind of schedule, that would only work if there are enough volunteers 
(and good topics to write about).
However, I thought the idea was to replace that void with the developer 
articles, for which it should be possible to keep a much higher output rate 
(as they are allowed to be short snippets and needn't go throught the 
PR-machinery). I still find this could surely improve the situation. Several 
developers actually did external blogs, which contain valuable information 
that should be given higher exposure by being transferred right onto haiku's 
official site. I thought that was agreed upon, wasn't it?

> There is your visions on the one side, but the real Haiku project (the
> people behind it with their limited resources) on the other side. Where is
> the content going to come from that goes into official news letters? 

As always, the content is going to come from volunteers (most of the time 
project members, I suppose). Hey, even I could find it necessary to volunteer 
one day if you bully me enough >;o).

> Will
> you have three or four articles all at once every month? Our website is
> going to look _again_ like their is no progress.

Yes, I agree, that situation should really be avoided by writing lots of 
developer articles (in "educated blog-style", so to speak).

Stephan, I am a bit confused, what is the alternative you have in mind?

cheers,
        Oliver

Other related posts: