www-infrastructure-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: Whimsy: permissions needed to view committer/committee info
Date Thu, 12 Mar 2015 14:26:02 GMT
There's not much else in the same SVN tree, so technically it should
be easy to allow the public to read the contents.
Note: there is an example file
(normalize-committee-info.example.diff.txt) which includes some
historic information containing possibly private mail addresses etc.
This could be redacted to show a generic change.

However, this made me realise that exposing that part of SVN to the
public would allow access to all the previous history, which might
well contain additional private information.
Also the rest of the contents is not really of interest to the public.

So I think it would be safest to expose only the *content* of the CI
file to the public, assuming this can be agreed.
Once there is agreement that the CI file contents (as a whole, or just
certain sections) are public then tools can be written to extract that
information and publish it elsewhere.
For example, the people.a.o app could add the info.

So how do we go about getting agreement that the info can (should!) be

On 12 March 2015 at 11:19, Sam Ruby <rubys@intertwingly.net> wrote:
> I also don't see why committee-info is private.  If possible, I'd like
> either get that fixed or understand why it should be private before
> changing the ACLs on whimsy.
> - Sam Ruby
> On Wed, Mar 11, 2015 at 11:00 PM, sebb <sebbaz@gmail.com> wrote:
>> At present, Whimsy requires a login for access to the PMC membership
>> information.
>> That seems unnecessary, given that very similar information is
>> available from the people.a.o website.
>> Would it be possible to move this information to the public area?
>> Is there anything in committee-info.txt section 3 that is not public?
>> Actually, although there is a note at the start of the file to say
>> that some of the info in it is private, I'm having difficulty finding
>> anything that should not be public.

View raw message