FYI: I've requested the CoApp project be renamed to CoApp-Engine, and we're creating a CoApp project group which all our new projects can be created under.
I anticipate creating projects like "coapp-trace" and "coapp-mkProject" etc... very soon. As for creating the CoApp shallow forks, we could do one of two things: Create projects like 'CoPackage-zlib' (or some other coapp-like prefix (just 'co-' ? ) and keep link them to the CoApp project group. Or Create another project group called 'CoApp-packages' and add them under that. (still with a prefix "Co-" , "CoPackage-", etc... ) G [Description: fearthecowboy]<http://fearthecowboy.com/> Garrett Serack | Microsoft's Open Source Software Developer | Microsoft Corporation Office:(425)706-7939 email/messenger: garre...@microsoft.com<mailto:garre...@microsoft.com> blog: http://fearthecowboy.com<http://fearthecowboy.com/> twitter: @fearthecowboy<http://twitter.com/fearthecowboy> I don't make the software you use; I make the software you use better on Windows.
<<inline: image001.gif>>
_______________________________________________ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
