Re: [Boost-maint] Community Maintenance Team and neglected libraries

Subject: Re: [Boost-maint] Community Maintenance Team and neglected libraries
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2014-04-23 05:01:00

> -----Original Message-----
> From: Boost-maint [mailto:boost-maint-bounces_at_[hidden]] On Behalf Of
> Andrey Semashev
> Sent: 22 April 2014 19:10
> To: boost-maint_at_[hidden]
> Subject: Re: [Boost-maint] Community Maintenance Team and neglected libraries
> 
> On Wednesday 23 April 2014 00:29:17 Ben Pope wrote:
> > In case you haven't heard of the CMT:
> > https://svn.boost.org/trac/boost/wiki/CommunityMaintenance
> >
> > I'm also interested in getting the test results less yellow and more
> > green, I don't have a lot of time, I'm sure I'm not alone.
> >
> > There are quite a few places where the library code is probably fine,
> > but the failure is in the test itself, the fix is often simple and
> > uncontroversial.
> >
> > These easy fixes should just happen; make a pull request, ticket with
> > patch, whatever; commit goes in; reminder when tests have cycled;
> > merged to master; profit.
> 
> This is a recurring topic and unfortunately the problem still stands. CMT was
a step
> forward, but to my mind this is not enough. With SVN we had commit rights
> everywhere, and such simple fixes went in much easier. After modularization
some
> libraries were left effectively unmaintained and inaccessible. CMT does have
rights
> to push to some libraries but not all and therefore does not fix the problem
> completely.
> 
> To my mind CMT should have access to all libraries, maintained or not. If a
given
> library is actively maintained then CMT doesn't need to intervene.
> However, if the maintainer goes silent for considerable time, CMT has the
ability to
> apply such fixes.

+1

I'd go so far as to suggest that we go back to the previous SVN arrangements
where all library authors had write access to everything.  I don't remember it
causing trouble - rather that it was felt so ill-mannered  to change someone
else's library that changes were not made when it would have much better if they
had!

Where I feel a finer grained control is useful is to allow write access just to
experimental branches from develop.

Paul

---
Paul A. Bristow
Prizet Farmhouse
Kendal UK LA8 8AB
[phone]