You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by Tomaz Muraus <to...@cloudkick.com> on 2011/01/25 01:11:06 UTC
[libcloud] Driver maintainers
Today I have proposed an idea on IRC about having one maintainer for each
driver.
The driver's maintainer primary responsibility would be to keep up to date
with the driver and API which he is maintaining and make a necessary changes
if a new image or functionality gets added / existing one changes / API
changes / etc.
This does't mean that other people are not allowed to contribute to this
drivers (outside contributions are encouraged and more then welcome), but it
means that we have at least one person on which we can rely that will fix /
update the driver in a timely manner if the API changes / whatever.
Paul has expressed multi concerns about it:.
- https://issues.apache.org/jira/browse/JSPWIKI-589.
- "you end up with code no one touches for years because there is a
maintainer label on it":
<pquerna> you end up with code no one touches for years because there is a
> maintainer label on it
> <Kami_> I don't mean that other people shouldn't touch the code is someone
> else is a maintainer
> <Kami_> but the maintainer should be up-to date what's going on with the
> apis he is maintaining and if something changes he will probably be the
> first one to notice and fix it
> <pquerna> yes, but having a maintainer line thats what 'seems' to happened
> <pquerna> at least it did with modules inside httpd
I agree that we shouldn't name this person an "author", but a "maintainer"
sounds fine imo.
Opinions?
Thanks,
Tomaz
Re: [libcloud] Driver maintainers
Posted by Upayavira <uv...@odoko.co.uk>.
Apache projects don't work that way, the idea of a "maintainer" doesn't
really fit.
What might work is a wiki page where people can sign themselves up as
knowledgeable about a particular driver.
Some drivers will have no-one, some one person, some many. That seems
more in keeping with an Apache approach. It allows the project to keep
on top of driver coverage - are there people who are able to fix a
driver? If not, can we find someone, or else drop the driver?
Upayavira
On Tue, 25 Jan 2011 01:11 +0100, "Tomaz Muraus" <to...@cloudkick.com>
wrote:
> Today I have proposed an idea on IRC about having one maintainer for each
> driver.
>
> The driver's maintainer primary responsibility would be to keep up to
> date
> with the driver and API which he is maintaining and make a necessary
> changes
> if a new image or functionality gets added / existing one changes / API
> changes / etc.
>
> This does't mean that other people are not allowed to contribute to this
> drivers (outside contributions are encouraged and more then welcome), but
> it
> means that we have at least one person on which we can rely that will fix
> /
> update the driver in a timely manner if the API changes / whatever.
>
> Paul has expressed multi concerns about it:.
>
> - https://issues.apache.org/jira/browse/JSPWIKI-589.
> - "you end up with code no one touches for years because there is a
> maintainer label on it":
>
> <pquerna> you end up with code no one touches for years because there is
> a
> > maintainer label on it
> > <Kami_> I don't mean that other people shouldn't touch the code is someone
> > else is a maintainer
> > <Kami_> but the maintainer should be up-to date what's going on with the
> > apis he is maintaining and if something changes he will probably be the
> > first one to notice and fix it
> > <pquerna> yes, but having a maintainer line thats what 'seems' to happened
> > <pquerna> at least it did with modules inside httpd
>
>
> I agree that we shouldn't name this person an "author", but a
> "maintainer"
> sounds fine imo.
>
> Opinions?
>
> Thanks,
> Tomaz
>
Re: [libcloud] Driver maintainers
Posted by Jerry Chen <je...@apache.org>.
On Jan 24, 2011, at 6:11 PM, Tomaz Muraus wrote:
> I agree that we shouldn't name this person an "author", but a "maintainer"
> sounds fine imo.
>
> Opinions?
I have no problem with "maintainer," although I do quite like the term "champion."
Whatever is decided upon, we should keep the list of driver contacts/maintainers on the wiki and outside of the code.
It really comes down to expectations.
Do we expect maintainers to constantly test the drivers and keep the code working? What about simple tasks like making sure the prices are updated? More on the specifics, where do patches go? If the maintainer is not a committer, do external patches have to be written off by the maintainer before committing the code?
IMHO, I don't think our community is at such a scale in which we require rigid processes and hold such expectations.
If we view driver maintainers as volunteers, rather than elected officials, I think we will continue to grow.
Cheers,
Jerry