[IAEP] Project hosting

[David Farning]

On Tue, 2008-05-27 at 15:32 -0400, Ivan Krstić wrote:
> Why the seemingly purposeless duplication of infrastructure which  
> outsiders are almost sure to find confusing? While OLPC's development  
> lists (in particular sugar@) serve their purpose, no new lists are  
> needed. While OLPC is providing adequate code hosting infrastructure,  
> no new hosting infrastructure is needed, and so on. Let's please start  
> offering sugarlabs.org code hosting when OLPC rejects a project and  
> not before that. Until then, mirroring will suffice.
> 
Without clear purposes and responsibilities, _both_ projects suffer. 
>From reading the archives of this mailing list and the wiki, I had come
to the conclusion that the purpose of Sugar Labs was to develop a
software stack that could be passed on to others for customization and
distribution.

On the other hand, OLPC is going to receive the Sugar stack from Sugar
Labs and customize it for their machines.  OPLC will be able focus on
developing new laptops and deploying them.

This does not require duplication of infrastructure. Rather, it requires
a clear allocation of infrastructure between the two organization.

The splitting off of SLs from OPLC allows two different cultures to
develop.  OLPC can remain a bit more closed.  Hardware development and
negotiating contracts and inherently more closed.

Sugar Labs can be more open, in the nature of KDE or Gnome.

>From a philosophical perspective, it does not matter who hosts what as
long as it is clear to everyone who is responsible for what.

>From a practical perspective, I don't know enough about the relationship
between OLPC and Sugar Labs to have a valid opinion on the
infrastructure should be set up.   

Dfarning