Re: [Savannah-dev] Re: [DotGNU]SourceForge drifting

[Christian BAYLE]

Hi all

I use this mail as a starting point, but could choose an other one

I red with attention Loic document, but maybe should read one again :-)

I always wonder if it is planned to have some kind of centralized 
data for "users" and "group"

I like the idea of a distributed sourceforge.

I also like the original sourceforge for it's trove map.

One of the goal, I understand is to be able to migrate a project from
place to 
place, with readable and writeable copy

This can't difficultly be done without some kind of centralised DB for
users and groups, 
because conflict in group names, user names will rapidly occurs, 
you will have to deal with changing uid/gid username/groupname for all
files.

I was just wondering, if using LDAP services to store users and groups
wouldn't be a good solution
LDAP has some embedded replication services, that can make it not so
centralized
LDAP can be used for the unix authentication.
 
Do you also plan to keep the attribution of one subdomain per project ?
In this case unity of group name could be think in unicity of domain
name.
The distributed nature of DNS can also be interesting to use

What is the approach planed by savannah?

Is a reflexion in this direction pertinent? 

As a co-developper of the sourceforge debian package, 
I find that using a LDAP db for authentication is nice, 
interaction with exim for mailing lists alias management is well done  
LDAP seems also have been one of the solution adopted by VA for it's
distribution

Christian  


Loic Dachary wrote:
> 
> David Sugar writes:
>  > I think Savannah, and what is now happening there, is the codebase for
>  > the future, not Sourceforge or whatever happens to the pre-fork
>  > codebase.  Being able to setup a Savannah anywhere will be very useful.
>  >  It is a mistake in my view to have "one" monster site.  There are
>  > plenty of projects organized around a small community or a campus, and
>  > having a Savannah one can role out to manage them locally would be very
>  > nice.
>  >
>  > At most, what would be nice is a meta-aggregation site, such as thru a
>  > search/directory engine for "published" projects on Savannah-like sites.
>  >  Not all projects need to be published widely; sometimes someone might
>  > create a small site and set of projects for personal work, for example.
>  >  Another example might be a company or organization which has some
>  > custom projects and some public projects.  Being able to move projects
>  > between such sites easily could be nice also.
> 
>         I'd even say that it's mandatory to prevent centralization to
> happen.
> 
>  > I think being able to deploy Savannah in a distributed manner, and
>  > having a global directory/search engine site that can sit on top of it
>  > would meet everyone's needs very well.  I also think much of the work
>  > that has gone into Savannah will eventually make this become reality.
> 
>         Hopefully ;-)
> 
>         I completly agree with your views.
> 
>         Cheers,
> 
> --
> Loic   Dachary         http://www.dachary.org/  address@hidden
> 24 av Secretan         http://www.senga.org/      address@hidden
> 75019    Paris         T: 33 1 42 45 09 16          address@hidden
>         GPG Public Key: http://www.dachary.org/loic/gpg.txt
> 
> _______________________________________________
> Savannah-dev mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/savannah-dev