Hi Stuart.

> > dcoutts has described the current practice we use in the Haskell
> > team, but that doesn't necessarily mean that it's the only practice
> > that would work for us. I can imagine that if we can come up with
> > reasonable policies for o.g.o, we can switch to a slightly different
> > (i.e., more public) scheme ...
> 
> I want to thank both you and Duncan for your explaination of how the
> Haskell overlay works.  I would love to get your overlay onto
> overlays.g.o, without disrupting the working practices that you've
> found successful.
> 
> Which means we need to take another look at the vision of all overlays
> being publically readable, because having a non-public overlay seems
> to be a key part of what you're already doing.

Not really. I discussed this with Duncan and we're perfectly ok with
a publically readable repo. In fact, our overlay is currently publically
readable. It's just not very well-known or advertised.

If we change the situation, we'll have to write up a few guidelines specific
to our repository.

Here's a list of things that I think are essential or highly helpful to
our working process:

* We should be allowed to continue using darcs for our version management.
  If that's not possible on Gentoo infra, we should be allowed to host on
  another machine and just have a pointer or ChangeLog on o.g.o.

* It should be possible for us to assign commit permissions to any people
  we think are qualified without any formalities and delay.

> If the overlay's changelog is included on o.g.o's front-page, and the
> wiki / GuideXML site is publically readable, but we just disallow
> anonymous access to the overlay itself (only if requested, this
> wouldn't be the default setup) ... how would that work for you?

It would work, of course, and it would help prevent certain complaints,
but it's not absolutely necessary. If "on request" is chosen, it's also
important that read access can be given by us without any delay, i.e.,
without going through any formal process.

Cheers,
  Andres

Attachment: pgp1gbtnP4HWd.pgp
Description: PGP signature

Reply via email to