[Linuxcoe-devel] HP LinuxCOE versus Open Source LinuxCOE

[Shank, J. R. <js...@hp...>]

One of the first threads I'd like to discuss is how we want to partition
HP LinuxCOE (the old LinuxCOE project) versus the LinuxCOE open source
project. There are a range of possibilities, two of which define
opposite ends of the spectrum.

1) We will continue doing all development internally using our present
processes and tools. When we are ready to release, we sanitize it for
external usage and dump it to CVS on SourceForge. When external people
contribute, we merge their contributions into the internal project and
continue the internal development process.

2) We move all development to the Open Source LinuxCOE Project (OSLP) on
SourceForge. Development that is still HP proprietary (such as certain
bundles) becomes a new internal project that functions as a
customization/integration project for the OSLP. The old LinuxCOE project
is migrated then sunset from HP.

I'll post my own opinion as a reply to this thread. I would really
appreciate hearing back from everyone on this list as soon as possible.
Hammering this issue out is the first and most vital step on the OSLP
road.