[openbeos] Re: Who wants obedn.com?
- From: "Erik Jakowatz" <erik@xxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Thu, 13 Sep 2001 19:19:58 -0700
While the interface kit team isn't anywhere near ready to start coughing
up design docs for a newsletter, I think this is a great idea as well.
Just as long as we don't use that god-awful blue background. ;)
e
>Hype is a great motivator - it inspires people to wait for great things
>ahead, and it pushes the developers to reach the objectives promised.
A
>newsletter every fortnight should do the trick, posted on the front
page
>(and archieved) for all the world to see the latest news and status
reports.
>Since we're slowly finalising our research and moulding designs, we
should
>start coding in a few weeks time, which is when the newsletters should
>start. I suggest the first articles to be a defense of the designs,
that
>is, the first newsletter documents should be our design documents.
>
>I've emailed you privately with a list of people working on the
networking
>kit.
>
>> -----Original Message-----
>> From: Michael Phipps [SMTP:mphipps1@xxxxxxxxxxxxxxxx]
>> Sent: Friday, September 14, 2001 12:33 AM
>> To: openbeos@xxxxxxxxxxxxx
>> Subject: [openbeos] Re: Who wants obedn.com?
>>
>>
>> What do we want out of a web page?
>>
>> I would like a list of who is working on what. What groups exists,
who is
>> on them.
>> The only way that I could see to do that within source forge was to
make
>> seperate
>> source forge projects for each kit. That kind of seems like a lot
more
>> work that I
>> want to go through. Plus all of the integration pains we would have
to go
>> through.
>>
>> People need info about the project. What it is, what we are doing,
etc.
>> Status is nice,
>> too. I was kind of thinking maybe something like what Wine does - a
web
>> news letter.
>> Maybe like Be did originally? Once a week, we make a newsletter with
>> interesting bits
>> from 1 or 2 of the developers? Maybe I could top it off with an
>> interesting piece? I don't know.
>> Just a thought. :-)
Data is not information, and information is not knowledge: knowledge is
not understanding, and understanding is not wisdom.
- Philip Adams
Other related posts:
