22 messages in ru.sysoev.nginxRe: Access key module
FromSent OnAttachments
Evan MillerDec 29, 2007 7:19 pm 
Cliff WellsDec 30, 2007 12:53 am 
Manlio PerilloDec 30, 2007 7:41 am 
Cliff WellsDec 30, 2007 3:47 pm 
Grzegorz NosekDec 31, 2007 12:32 am 
Manlio PerilloDec 31, 2007 3:43 am 
Manlio PerilloDec 31, 2007 3:55 am 
Grzegorz NosekDec 31, 2007 5:31 am 
Manlio PerilloDec 31, 2007 6:46 am 
Evan MillerDec 31, 2007 8:00 am 
Grzegorz NosekDec 31, 2007 8:07 am 
Manlio PerilloDec 31, 2007 8:32 am 
Manlio PerilloDec 31, 2007 8:49 am 
Grzegorz NosekDec 31, 2007 9:06 am 
Adrian PerezDec 31, 2007 9:52 am 
Evan MillerDec 31, 2007 12:12 pm 
Evan MillerDec 31, 2007 12:41 pm 
Grzegorz NosekDec 31, 2007 1:06 pm 
Cliff WellsDec 31, 2007 3:34 pm 
Manlio PerilloJan 1, 2008 9:03 am 
Manlio PerilloJan 1, 2008 9:07 am 
Adrian PerezJan 4, 2008 8:13 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Access key moduleActions...
From:Manlio Perillo (manl@public.gmane.org)
Date:Dec 31, 2007 3:43:19 am
List:ru.sysoev.nginx

Cliff Wells ha scritto:

[...] This would be better, but seems more complicated than need be (at least initially). All we really need for the moment is a place where not just any anonymous user who creates a wiki account can change where source code is available from.

Ah, ok. What about a Trac instance with a strict access policy?

[...]

This actually brings up another thought: perhaps we should start an RCS tree for Nginx. We don't actually need Igor to use it (I'm sure he has his own tools and methods and I don't want to interrupt that): diffs can be generated automatically from the tarball Igor provides.

Latest versions of Subversion include the svnsync tool, so Igor can just use it to create a public copy of his repository, keeping it in sync.

Then from this public SVN repository, each developer can create a copy using his favorite RCS.

Later we may discuss about using a shared repository.