[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Debconf-team] two more, rather restricted, repos to limit exposure of historic private data (was Re: Why the secrecy (was: Request to Join Project DebConf private repository)



Hi,

(taking this from the dc15 list to here...)

On Montag, 7. April 2014, Philipp Kaluza wrote:
> including a link to a git repository. However,
> Am 07.04.2014 22:17, schrieb noreply@alioth.debian.org:
> > Your request to join the DebConf private repository project was denied by
> > an administrator.

the "secrecy" is not about the constitution of the to be founded german 
debconf association, but about other contents in that repository, which makes 
me ask here what I have been wondering the last days already: 

now that we have a zillion^w30 new git repositories, we still only have 3 
alioth repos (-private, -data and -video), so everybody who gets access to the 
debconf-private project on alioth has access to all past debconf private 
repos, correct?

Thats rather unfortunate.

My idea would be to create two more alioth projects: debconf-historic-data and 
debconf-previous-data (or similar names), the first should collect all 
previous DebConf repositories and should only be accessable by long term core 
debconf-team members (committee??), while the previous-data project should 
currently probable be open to dc13+14+15 team members.

How does that sound? Other, better ideas?


cheers,
	Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: