<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV>Why don't you write about the topmost position - project coordinator? What should he do?</DIV><DIV>And also one missing thing is the one who can actually help resolve such internal conflicts (which really doesn't add to reactos popularity).</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Also what you wrote is a bit wrong - a concept of "maintainers" sounds better to me. Otherwise you end up with LOTS of coordinators :-) - device driver, network, user interface, kernel, win32k coordinator, other subsystems coordinator, well, usb coordinator maybe? :-)))</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Coordinators should really coordinate (manage) things which they can manage. They can't dictate developers or artists or other people involved in project what to do, but their aim is to help devs do the work they like to do. To help devs have fun at last.</DIV><DIV>And not end up loosing developers on questions which doesn't cost anything to the project.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>WBR,</DIV><DIV>Aleksey Bragin.</DIV><BR><DIV><DIV>On Oct 15, 2005, at 11:29 PM, Rick Langschultz wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">There has been a great deal of talk lately about coordinators. In my opinion there should be:</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">kernel coordinator - controls the development of the kernel.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">device driver coordinator - makes sure device drivers are written and code managed.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">network coordinator - makes sure networking is complete before 0.3.0 or other release.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">User interface coordinator - enables the UI is stable and allows users to get a great ReactOS experience.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">testing coordinator - this team will test reactos on various hardware bits. They will keep a log of what hardware bits work and those that need support - for instance on Virtual PC (latest Mac OS X) enabling USB support makes ReactOS crash. A list of that hardware needs to be supported -- eventually.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">release coordinator - Once a release is scheduled this team makes sure releases are released on time.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">web coordinator - this team managers the web aspects of ReactOS. This team is pretty much complete.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">and IRC coordinator - this coordinator will keep logs of what has been discussed on the IRC channels. A daily list of main topics will be available on the wiki. This will keep developers up to speed on what is happening on IRC if they are away, or if someone has a quick message for other teams.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">These are suggested teams. Each team should have a coordinator and keep a log of information for each team. The coordinators should be able to communicate with other coordinators of other teams. Once weekly they should have a personal chat on IRC or email discussing the next release or feature addition. This is the way my company operates and it is very efficient.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Rick Langschultz</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="mailto:rlangschultz@cox.net">rlangschultz@cox.net</A> (Home)</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="mailto:rlangschultz@ellemaespa.com">rlangschultz@ellemaespa.com</A> (Work)</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="mailto:rlangschultz@email.uophx.edu">rlangschultz@email.uophx.edu</A> (School)</DIV></BLOCKQUOTE></DIV><FONT class="Apple-style-span" color="#0000DD"><BR class="khtml-block-placeholder"></FONT></BODY></HTML>