On 1/17/08, Allen Winter <[EMAIL PROTECTED]> wrote: > Here's a quick list to start with: > + help determine release schedules > +communicate release schedules with the module developers > + provide feedback from developers to the Release Team > + review new applications for inclusion in the module > + review old, unmaintained applications for removal from the modules > + review external dependencies for the module > + help set and review goals for major and feature releases > + a module coordinator is NOT: > - the module police > - the final authority > - the maker of rules > - management > > Comments? Suggestions? Should I have lose my coordinatorship? :)
I like your list! I'd add, that they're the primary point of contact for the release team concerning issues with the module. Cheers Rich. _______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
