Meeting minutes

[David Farning]

<morgs> We'll wait a bit for dfarning

My apologies for missing our initial meeting.  I had a number of organizations tell me to 'go to hell' when I asked if they
were interested in working with Sugar Labs.  I needed to take a break and reassess my commitment to SL.

<morgs> * Who we are and what we are interested in

I am David Farning.  I am a community contributor who would like to see the interesting technologies and visions that have
been developed by OLPC distributed to a wider audience of potential users and developers.

<morgs> OK, a run down on what resources we have:

I fully agree on this point.  We are working hard on creating a dependable release cycle for Sugar. 
http://sugarlabs.org/go/ReleaseTeam/Roadmap/0.84 is our upcoming release roadmap.

<janimo> morgs: do we also want most of the activities as well or just core?

Once the core activities are correctly packaged, the activities should be pretty trivial.  There will be a few .lib
breaks.

<janimo> morgs: I think we can request upload exceptions to universe especially since these packages do not break anyhting else
<janimo> it would be easier if we just synced form debian but I do not know their status

Debian has some well maintained packages.  The problem from Ubuntu's point of view is that the maintainer is using his Sugar
packages to do some testing of potential CDBS updates.  Thus the .diffs are several thousands of lines longs:)  Jonas will
work on incorporating the CDBS changes upstream but, it will be a several month process.

<janimo> at least evince is arguably an upsteram olpc task but it is not doen for lack of time I guess

As a result of spinning off Sugar from OLPC, there are many lingering questions about who is responsible for what;(  As a
downstream to sugar, we will need to make our needs known on the development mailinglists.  

<janimo> morgs: do you think it is very useful to track development sugar release?

This is a question of what our short and long term goals are.  I think that these goals align closely with Ubuntu's goals
for gnome:
1:  Stable core+ in the current release.  This will help make Sugar available to as many users as possible.  Most of
these users will not be interested in actively participating in Sugar development.
2:  Track core development tarballs in backports/testing.  This will help make the semi-stable APIs available to potential
activity developers.  Theses users tend to be more active in reporting and following up on bug reports.  
3:  Jhbuild: will be used by core developers to keep up to date with the latest sugar development tree.

<jmunro> i would like to continue my work with the development packaging, but i fear that my packages lack the quality required for inclusion in intrepid, as mentioned we should probably look to the debian packages for this

The ubuntu release process is very good at helping new packages improve the quality of their packages.  Once you start
pushing packages through the review process, all of the deficiencies in your packages will be caught;)

<morgs> How can we get more Ubuntu people involved?

We might want to wait until we have working packages in a current release before making any public announcements.  The 
interest in having Sugar packages available in Ubuntu is huge.  But no one seems to know how to get started.  If we can
form a core team a packages and some working processes we will have specific places for interested individuals to get involved.
       
<morgs> hmm, I think there are some people in janimo's LP sugar team that we can get involved...
<janimo> not ure if they're still active

Sorry for dropping the ball on that one! Before starting sugarteam I did a search for user+teams = sugar and got some
many false positives I stopped looking:(  I will ask about merging the two teams.

<morgs> OK
<morgs> Anything else?

For those intrested in tracking debian progress the debian olpc list is at
debian-olpc-devel at lists.alioth.debian.org

thanks
dfarning