Alpha 1 Proposals

On the the 7th of August, Axel Dörfler started a discussion on the things to do in the thread ​Haiku R1/alpha decisions. Here's a summary of that discussion. Axel called for:

The aim of this thread should be to compile a complete list of things
we want to have in the first alpha release, be it feature or software.

• This page lists concrete proposals that came out of that discussion.
• Every item should have an adopter. This person is responsible for the implementation (which of course does not mean he/she has to do it themselves).
• This page is open for editing for all users that are in the developers group. Feel free to register as adopter, tweak your adopted proposals or add new ones.
• This page will be marked read-only on Sunday at 13:00 GMT.

General Proposals

The proposals are general when they apply to procedures, requirements that cannot be quantified or qualified, or tendencies that are not covered by sections deeper down.

Prop # 1: All known bugs that cause data corruption need to be resolved before the release

Adopted by: no one

• ​BGA:

  Speaking in general terms, the important thing, even for an alpha, is 
  that we have no know bug that can cause data corruption. As long as 
  we reach a point where we are reasonably certain that this is the case, 
  everything else can be attributed to it being an alpha. :)
  

Prop # 2: Name the release 'Developer Release 1'

Adopted by: no one

Prop # 3: Create a welcome package

Adopted by: no one

• Have links on the desktop that refer first time experimenters to things that they can do next.
• Have a short 'what to do next'-guide

Prop # 4: Release as the GCC 2/4 hybrid

Adopted by: no one

The release should be done in such a way that applications compiled with GCC 2 and 4 can run out of the box.

Prop # 5: Make sure that a live Haiku install can be updated

Adopted by: no one

Prop # 6: Recruit a Release Coordinator that investigates the needed steps

Adopted by: nielx

• The release coordinator will be a community volunteer that investigates the required work to prepare for a release, and report this info back to the developers and Haiku Inc.
• Areas of investigation should be marketing, bandwith and mirrors, procedures to streamline the release.
• The volunteer does not have to be a developer. Community members are encouraged to join in the process.
• The volunteer is selected per developer vote.

Software proposals

Prop # 10: Include the Development toools

Adopted by: no one

The development tools currently in the 'Development' package should be included. Currently that means: (​Rene Gollent)

• gcc 2.95.3
• autoconf-2.61
• automake-1.10.1
• bison-2.3
• flex-2.5.35
• jam
• libtool-1.5.26
• texinfo-4.11
• Perl 5.10

Prop # 11: Include Firefox

Adopted by: no one

Include the latest version of Firefox.

Prop # 12: Include OSS

Adopted by: no one

Include the OSS drivers developed by mmu_man.

Prop # 13: Include BePDF

Adopted by: no one

Prop # 14: Include a copy of the original BeBook

Adopted by: no one

We can include the ​BeBook as released by Access.

Prop # 15: Include a special Haiku-only unlocked version of Wonderbrush

Adopted by: no one

Offered by Stephan Assmus

Prop # 16: Include a Webkit-based browser

Adopted by: no one

Prop # 17: Include Vision

Adopted by: no one

Prop # 18: Include CVS

Adopted by: no one

Prop # 19: Include Subversion

Adopted by: no one

Prop # 20: Include Git

Adopted by: no one

Prop # 21: Include Python

Adopted by: no one

Prop # 22: Include 'box'

Adopted by: no one

Prop # 23: Include a Makefile engine to build existing projects

Adopted by: no one

Distribution

All proposals that apply to the physical distribution of the operating system.

Prop # 30: Distribute as ISO that functions as LiveCD

Adopted by: no one

This one should be able to install by itself.

Prop # 31: Distribute as Live USB stick

Adopted by: no one

Prop # 32: Distribute as image for emulators

Adopted by: no one

For QEMU and VMWare.