Hello All, For my opinion - Project Lead should answer on questions: 1. When new release planed for publishing 2. What components should be fixed/updated for new release 3. Road map - where we go
If we have release scheduler with road map - Project Lead should be tracking scheduler and ask some additional leads. We can split big project to some small groups. For example: 1. Text components - we can split by groups 2. X11 components - we can split by groups We can identify list of components for desktop and server sides. And we can identify some persons who will track/leads components. It is my proposal - my vision. If it is possible Alasdair can continue manage OI and we can help him by additional helps. I can help with text components through DilOS userland. At this moment I have checked dilos-userland components by IPS installation to OI with upgrades - all works well for me on ipkg zone. But I have no experience with consolidations updates - I have made clean consolidations for resolve conflicts. I have dilos-userland build system for builds both - IPS and DEB packages. I have updates from userland-gate(Oracle) and builds by gcc44 (with patches for illumos-gate). --- Best regards, Igor Kozhukhov IRC# igork On 9/3/12 3:21 AM, "Sašo Kiselkov" <[email protected]> wrote: >On 09/03/2012 01:14 AM, Nick Zivkovic wrote: >> Do we have any idea who the new project lead is? Or is it too soon to >>tell? > >While having a lead is important, I don't think it's as important in the >day-to-day operation of the project. A project lead should really be >only necessary when high-level either/or decisions are to be made. The >rest of the time, I believe rough community consensus should work out >just fine to steer the project. > >So a much more pressing question that needs to be answered, IMO, is to >establish some sort of direction in the individual components of OI and >delegate responsibility. I think finding people for these smaller >components will be much easier. > >Anyway, just my quick thoughts on the matter... > >Cheers, >-- >Saso > >_______________________________________________ >oi-dev mailing list >[email protected] >http://openindiana.org/mailman/listinfo/oi-dev _______________________________________________ oi-dev mailing list [email protected] http://openindiana.org/mailman/listinfo/oi-dev
