This sounds good. On 11 May 2015 at 21:18, Greg DeKoenigsberg <[email protected]> wrote:
> This leaves some open questions that we'll need to sort out: > > * How will we know who the module owner is? One option: we ask owners > to put their names and github IDs into the module itself. Another > option: we keep an external database linking owners to their modules. > Depends I guess on the options on how to parse things and to trigger github. Having some ID in the module itself would have the advantage to easily delegate that, when necessary, core maintainers can also easily change it. > * How will module owners be notified of PRs/issues against their > modules? Matt Martz has a tool that will allow people to subscribe to > notifications to their modules; we can use that or something similar. > ! Keep in mind that the "maintainer" might be a Github organisation and not a lone developer, > * How do module owners hand off their modules to someone else, or > "orphan" a module entirely? In the short term, an email to the > ansible-devel mailing list is probably sufficient. > If the ID is maintained within the module, the original owner can easily change it. > * What happens if a module owner fails to maintain their modules in a > timely manner? Ultimately, we may reserve the right to deprecate a > module that is persistently broken and who has an unresponsive > maintainer. > If the ID is maintained within the module, a core maintainer can easily change it. Serge -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAEhzMJA366_n8Jd%2BJYXL9P7PGRF3Fr1%2BZuSheFbSoGemOMDVCw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
