[openbeos] BU clears up some misconceptions
- From: "Michael Phipps" <mphipps1@xxxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Tue, 15 Jan 2002 21:19:25 -0500
This is from a conversation thread that Deej and I had
going in the Phoenix mailing list. I know that many people
had misconceptions about what BU had/has in mind. This clarifies
it and should set people's mind at ease. I think, with this, this
topic should be considered closed. :-) FYI - my comments are the >> comments.
>> I posted a lot more in another thread.
>
>Read - and am absorbing the inputs fully. :)
>
>> It is warmly welcomed by me. As long as y'all do
>> something with them. I would *love* to have Postmaster
>> updates.
>
>That's why I'm shooting for source. So that the apps can continue to
>improve on OBOS, but still be "owned" by their original owners. As
>such, Postmaster would still be "given" to all registered Postmaster
>owners, as in Kenny's original deal. Too bad I have yet to hear back
>from Kenny. Anyone with another email other than kennyc.com?
>
>> I think you really have the gist of what I am thinking, here.
>
>Yep, we've touched on this topic many a time... :)
>
>> And OBOS is controlled, too. Maybe not by the same people.
>> Think about Linux. Linus controls it, to this day. There
>> are not gazillions of forked linux kernels flying around.
>> Most people run the 'standard' kernel. Why? Because that
>[...]
>> I guess I am not sure that I understand what that panel/
>> forum would hope to achieve. For technical decisions, I
>> would doubt it. Any more than Walnut Creek runs the
>> committee for BSD. Or RedHat tells Linus what patches
>> to accept.
>
>Mmmm. I think I'm getting where the confusion is... 3rd Party
>Developers is what I'm talking about.
>
>Committee - Not about the OS itself - but how _non_OS apps should look,
>feel and act. That's what I'm talking about. So that Menu systems and
>buttons and touchy feely stuff on different applications all behave
>similar enough to feel like they belong on the same platform. So all
>preferences are saved in the same manner (and same locations - not all
>over the hard disks). Basically, getting standards that 3rd party devs
>should follow (and possibly get certified for) so all apps they write
>feel like they belong on the platform.
>
>And to belong on the platform, they must act like the platform's build
>in interfaces and apps - which is where I keep saying involving OBOS
>devs. To do this right, OBOS devs need to be greatly involved in the
>process.
>
>Clearer?! :D
>
>> It isn't that it is BU vs ??? Inc. I *think*, and I
>> could be wrong - I am guessing what people who are not
>> me are thinking, that it is an issue of "we have done
>> all this work, these people are now coming in and telling
>> us what to do". That is my *GUESS*. And there is a point.
>
>What's happening, and likely because of the above miscommunication, is
>it's a BU vs OSS thing to many OBOS devs. Whether BeUnited is actually
>doing the distro or not... I'd like to see the *name* BeUnited behind
>any standards for UIs and the like for _3rd_ party development. Little
>BeUnited people logo thingy on compliant apps. ;) And I don't want to
>tell the OBOS devs "what to do", but find out what they are doing, and
>if BU has different ideas, tell them what "we think should be done"...
>and then finalize it between the two, so everyone, not just OBOS and
>BeUnited, but *everyone* can be on the same page.
>
>Deej
>
>
>
Other related posts:
- » [openbeos] BU clears up some misconceptions
