Re: [Linuxcoe-devel] HP LinuxCOE versus Open Source LinuxCOE

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

On Tue, 2005-07-26 at 16:54 -0400, Lee Mayes wrote:
> I think we have to do this.  Then we just maintain our 'addons', we can
> still call it LinuxCOE internally, changing names would just confuse our
> internal audience IMO.  But *WE* know it's really HPCOE, OSM, etc....

D'oh! Replied directly to Lee instead of the list. Here is what I sent
directly to Lee:

"Agreed. Perhaps keep the LinuxCOE prefix and classify it mentally as
the LinuxCOE [Integration] Project. :)"

On the other hand, I want to make sure that we communicate with users
that LinuxCOE is being moved to SourceForge. Bug reports, enhancement
requests, and even e-mail about the non-proprietary parts of LinuxCOE
should be handled through our SourceForge tools. It might actually
result in more confusion to retain the LinuxCOE project name because HP
people will not be sure where to go for help or to contribute.
Sunsetting the LinuxCOE project and providing clear communication about
the new OSLP might be the best way to avoid confusion.