[openbeos] Re: File format support in Haiku
- From: Simon Taylor <simontaylor1@xxxxxxxxxxxx>
- To: <openbeos@xxxxxxxxxxxxx>
- Date: Fri, 6 Apr 2007 8:50:55 +0000
>
> From: Ar18@xxxxxxxxxxx
> Date: 2007/04/05 Thu PM 11:37:45 GMT
> To: openbeos@xxxxxxxxxxxxx
> Subject: [openbeos] Re: File format support in Haiku
>
> > I don't think you should get that impression...
> >
> > This mailing list was chartered for current development goals. The future
> > of the OS is discussed on the Glass Elevator Mailing List. This is to keep
> > people here focused on a R1 milestone. If you want to rally up new ideas
> > that would possibly define an R2 milestone... go right ahead... but do it in
> > the appropriate list. ;)
> I tried out the list. The email never got in and it appears that the list
> just turned into a spam trap. I got spam at my email for the first time in a
> long time.
> Also, as I understand it, the list is not really active with any current
> developers and is not really actually focusing on any work right now. I was
> hoping to actually start getting some things done. Was I at the wrong place
> or what is going on?
The Haiku site has a page about GE, with a link to the mailing list:
http://haiku-os.org/glass_elevator
Glancing at the archives shows it is not a spam trap, but that there is also
not a huge amount of active discussion. As Urias said, it's because people are
busy working on producing R1.
GE has been used as a general place to throw ideas around. However there is
still no concrete plan for R2 and beyond - I hope that when R1 has been
released the core devs will take some time out to plan exactly what is being
targeted for R2 and what the APIs should look like. Then we can have another
period of development as focussed as the current one has been for the R1
release.
And I have to say that your attempts to "start getting things done" on this
list have not been too successful. Your first suggestions about the translation
kit showed a lack of knowledge about the current system and your proposal was
simply broken - I spent an hour replying to your email to explain how an
uber-standard-that-supports-everything would not work and had no reply from you
to my points. You then shifted topic completely and suggested abandoning the
very widely used and mature GCC in favour of writing a new compiler (which as
people have pointed out is not a wise use of resources now).
Please don't take that paragraph the wrong way. I'm not trying to discourage
discussion or anything - my point is simply that you cannot expect the gods of
the project to respond to every post you make. As for the process of finalising
APIs and things for future Haiku, I agree that it is a very important process -
but as I mentioned earlier it is not yet time for it to happen. It is certainly
a process that the core devs need to be a driving force in, and the time when
they will be able to focus on that is after the R1 release.
> Thanks,
> Kevin
Simon
>
-----------------------------------------
Email sent from www.virginmedia.com/email
Virus-checked using McAfee(R) Software and scanned for spam
Other related posts:
