[haiku-development] Re: R1alpha 2 : time to get the ball rolling ?

On Fri, Feb 26, 2010 at 07:50, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> On 2010-02-24 at 09:01:35 [+0100], PulkoMandy <pulkomandy@xxxxxxxxx> wrote:
...
>> R1 alpha 2 :
>>   * Already a good set of improvements since the alpha1. Some things that
>> could still be missing :
>>   * Finish localization of every app in Haiku (lots of work, but it will
>> allow people to contribute catalogs)
>
> That would definitely help for a more polished impression. On the other hand
> that would also need to include third party applications we distribute in
> the release. This in turn raises the question where we stand with respect to
> making the locale kit public API. IMHO ATM it's nowhere near being in a
> shape for that. Furthermore that would effectively require the layout
> functionality to be made public, too, which needs a bit of work as well.

+1 while localization would be great to have, i'd rather it not be a
blocker for any pre-R1 releases.

>>   * Unencrypted Wifi support (mostly done already, mmadia submitted some
>> patches that should be commited to load firmwares and enable drivers by
>> default
>
> How useful is unencrypted Wifi support? Sure you can access public WLANs,
> but since you wouldn't set up your home WLAN without encryption, this is how
> far it goes. Maybe Colin can add some insight how things look on the
> encryption front and whether we should include that, too.

When Colin and I last spoke, he mentioned userland integration as
being more valuable than encryption -- being able to detect available
networks and such.

Wifi, even unencrypted, would be a nice bullet point to catch people's eyes.
And for some users, unecrypted wifi may be enough to lower the barrier
of using Haiku.

>> R1 alpha 3 :
>>   * Package manager
>>   * Encrypted Wifi
>>   * IRQ routing
>
> Save for Wifi no one is actively working on these yet or has expressed to do
> that in the foreseeable future. This makes them rather hard to schedule.
>
As a reminder, Haiku Inc., is indeed interested in receiving contract
proposals from developers with commit access :
http://www.haiku-os.org/news/2010-02-21_haiku_inc_hiring_funds_needed

To note, info@xxxxxxxxxxxx is a private address, accessible to the BOD.
(i'm also pushing for an address that is more descriptive)

If anyone's curious, by early next week, Haiku Inc will put together a
small summary and thank you to the supporters.

> As for additions, I'd throw the Debugger in here, too.
+1
are there any reasons why its not in the default images or part of the
Development optional packages?


On Fri, Feb 26, 2010 at 12:05, scott mc <scottmc2@xxxxxxxxx> wrote:
> I want to make use of the next release to step through the included
> optional packages and make sure HaikuPorts has the .bep and
> .OptionalPackageDescription files updated for all of them.

I'd love for the .OptionalPackageDescription files to be updated to
use "SourceURL:" as per http://www.haiku-os.org/node/2525
IIRC HaikuPorter even supports archiving the sources, which will help
to satisfy licensing, distribution, & providing sources.

> Should we start a wiki page and a list of requirements and a list of
> optional packages that should be part of Alpha2?  We could copy paste
> the Alpha1 and update it from there.

I'll start stubbing out the R1/Alpha2 wiki pages today.

--mmadia

Other related posts: