Re: [boost] Transfer of Maintenance Rights

Subject: Re: [boost] Transfer of Maintenance Rights
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-03-26 06:50:58

David Abrahams wrote:
> Stewart, Robert wrote:
> >
> > Dave asked for a policy proposal for how Boost library maintenance
> > rights may be transferred.  Edward Diener declined, so I'll offer
> > one and go a little further while I'm at it.  Consider the following
> > as a replacement for the text at
> > <http://www.boost.org/community/reviews.html#Maintainer>.

Note: I have included an updated version of my initial proposal below.

> Can you describe the difference from the existing policy and why you
> think yours is an improvement?

My version splits the original section into two -- one for library authors and one for maintainers -- because they aren't necessarily the same person or people.

My original version only required a Boost-compatible license upon acceptance.  There was concern that perhaps that should be upon submission.  Indeed, Phil Endecott said he wouldn't look at a candidate library otherwise.  I wasn't sure I could or should specify that.  I look forward to hearing from others on that point.  In the meantime, I've reworded that part to indicate the need for that upon submission.

My version stresses the maintainer role and indicates that the author can select a cadre of maintainers if desired.

My version describes the maintainer's activities and stresses the importance of responding within a reasonable time and to not let bug reports or bug fixes languish.  This is to address the state of some current libraries that have many outstanding bugs that have existed for years and of others that have changes in the trunk that have not been released.

My version includes the suggested (and controversial) idea of allowing others to commit patches to a library after proposing the patch and giving others an opportunity to reject it.

My version spells out more clearly what should happen when maintainers wish to abandon that role and what the Boost community can do if a maintainer simply vanishes.

Here's an updated version of the proposal based upon feedback received thus far:

_____________________________

Library Author's Responsibilities

By submitting a library to Boost, you agree to apply the Boost License to the library and its documentation, solely or alongside other licenses you may wish to apply, if it is accepted.

If your library is accepted, you are free to change it any way you wish.  Indeed, we encourage you to make improvements, at least until the library reaches a proven level of maturity.  At that point, changes may be less helpful to the user community and might be better put into a new library that would coexist with the original, if accepted.  Note that because peer review is an important part of the Boost process, you should consider getting Boost community feedback before making substantial changes to the interface of your library.

Furthermore, if your library is accepted, you agree to be the library maintainer or to find a qualified volunteer to serve in your stead.  You may, of course, assemble a qualified group to act as maintainers of your library, regardless of whether you continue to be a maintainer.

Library Maintainer's Rights and Responsibilities

As a library maintainer, you agree to provide timely support to users of the library, to note and fix regression test failures, to fix bugs and release those fixes in a timely fashion, and not allow any active bugs to languish for longer than a year.  You also agree to consider making library enhancements and improvements.  Note that others may offer and even commit patches to a library you maintain, provided the patch is posted to the Boost Developer's mailing list for verification for at least two weeks and is not rejected by anyone.  That gives the maintainer and interested users a reasonable chance to notice and reject the patch.

If you find that you can no longer fulfill your responsibilities as maintainer of a library, you are responsible to advertise this to the Boost community.  If you are the sole maintainer, you are responsible to find a replacement.  If for some reason you fail to fulfill your responsibilities as maintainer of a library, as judged by the Boost community, whether through willful neglect or otherwise, you agree to allow the Boost community to provide a suitable replacement.

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer, Core Software      using std::disclaimer;
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.