|
Boost : |
Subject: Re: [boost] [Boost-users] Maintenace Guidelines wiki page
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2008-11-23 08:37:07
----- Original Message -----
From: "Henrik Sundberg" <storangen_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Sunday, November 23, 2008 2:07 PM
Subject: Re: [boost] [Boost-users] Maintenace Guidelines wiki page
>
> On Sun, Nov 23, 2008 at 1:01 PM, vicente.botet <vicente.botet_at_[hidden]> wrote:
>> ----- Original Message -----
>> From: "Henrik Sundberg" <storangen_at_[hidden]>
>> To: <boost_at_[hidden]>
>> Sent: Sunday, November 23, 2008 12:18 PM
>> Subject: Re: [boost] [Boost-users] Maintenace Guidelines wiki page
>>
>>
>>>
>>> On Sun, Nov 23, 2008 at 11:29 AM, vicente.botet
>>> <vicente.botet_at_[hidden]> wrote:
>>>> The Daniel proposal implies some changes in the writing rights of the authors. I prefer to let this point out of these guidelines. Of course I think that this is a good idea.
>>>
>>> I think this is absolutely wrong. The authors are the experts and they
>>> do all work. You should never try to make them inferior. Do not handle
>>> quality in Boost as in old fashioned handling of "Quality" (which
>>> *not* is the same as product/code quality) in big companies. There is
>>> a release management in Boost. The release manager can choose not to
>>> accept something in the release if something is considered to be too
>>> bad.
>>
>> I have never said the contrary.
>
> I'm sorry.
> I thought a restriction was meant with "changes in the writing rights
> of the authors". And I thought "Of course I think that this is a good
> idea" referred to that restriction.
No problem. I was not enough explicit.
> I agree with you to place such rules outside of the maintenance
> guidelines. But I think that all author restrictions will make fewer
> people interested in contributing to Boost. Subversion makes it fairly
> simple to revert changes. Fix problems when they have occurred
> instead.
Do you know if the author can change himself the permision on his own SVN files?
> Back to what I misunderstood; what does "that" refer to in "Of course
> I think that this is a good idea"?
I think that is a good idea that the author do not change the released test files.
If he thisnk that this is good, changing the write permission to these files will
avoid to change them by error. I don't think that it is a good idea to make this a rule and improse this guideline to authors, but I would like they adopt this guideline because I really think that it helps them.
I hope that it is clear that I don't want to impose any rule to the authors, release manager or users. Guidelines that are used could incite other to use them. If some of the guidelines seems no useful at all, I have no problem to remove them from this Maintenance Guidelines.
Please let me know if there are some guidelines that seems rules. I'll try to rephrase them.
Best regards,
Vicente
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk