[Sugar-devel] Pippy not ready for Sucrose
brian at laptop.org
Mon Feb 23 17:39:43 EST 2009
Yup, I will have it completed this week. Apologies for my recent
absence, and thanks for the reminder:
---------- Forwarded message ----------
From: Brian Jordan <bcjordan at gmail.com>
Date: Mon, Feb 23, 2009 at 3:10 PM
Subject: Re: Migrating activities from OLPC to SL
To: David Farning <dfarning at sugarlabs.org>
Cc: Wade Brainerd <wadetb at gmail.com>
Hey David and Wade,
On Mon, Feb 23, 2009 at 2:42 PM, David Farning <dfarning at sugarlabs.org> wrote:
> We are handing off development and distribution of Sugar activities
> from OLPC to the SL community.
> Would you please insure that your activities:
> 1. Have been migrated to http://git.sugarlabs.org for a source code repository.
> 2. Are being tracked via pootle for internationalization.
> 3. Are registered in the the Sugar Labs bug tracker at
> http://dev.sugarlabs.org .
> 4. Have been uploaded to http://addons.sugarlabs.org for distribution.
> We have you listed as working on or maintaining:
Will do, I'll have that done this week. Thanks for the heads up, and
sorry for my radio silence the past couple weeks. I've been taking
some time off to complete my college transfer applications.
> I have cced Wade the Sugar Labs activity Team Leader in case you have
> any questions.
On Mon, Feb 23, 2009 at 4:41 PM, Simon Schampijer <simon at schampijer.de> wrote:
> Brian Jordan wrote:
>> On Fri, Jan 23, 2009 at 2:21 PM, Simon Schampijer <simon at schampijer.de> wrote:
>>> Simon Schampijer wrote:
>>>> the Sucrose package of Pippy is version 25 - when I last released it
>>>> back in August. Since then there has been some development going into
>>>> Pippy (now version 30)
>>>> But none of the maintainers did follow the Sucrose release cycle, even
>>>> though I sent a reminder
>>>> Any, specific reason for that? Pippy has not been moved to
>>>> git.sugarlabs.org, as well.
>>>> please indicate clearly:
>>>> * if you still want to be part of Sucrose (including following the
>>>> release cycle)
>>>> * any new maintainer that is willing to do this task if you does not want to
>>>> * any issues/reasons you have to do so
>>> To follow up on this, I mainly want to find a maintainer for Pippy for
>>> Sucrose. If there is no one willing to do that we drop it, which is ok -
>>> one can still download the xo etc, I just want a clearer situation.
>> I will maintain Pippy for Sucrose, though I may need a bit of hand holding.
>> Please let me know if what I did seems correct (esp. step 2):
>> 1. l got the most recent version of Pippy from git
>> git-clone git://dev.laptop.org/projects/pippy-activity
>> cd pippy-activity
>> 2. ./setup.py gave a bunch of "invalid entry in MANIFEST" errors about
>> different locales, so I ran:
>> ./setup.py fix_manifest
>> 3. ./setup.py dist_source
>> 4. I asked a crank sysadmin to add me to the Sugar group,
>> And I moved Pippy-30.tar.bz2 to:
>> http://dev.laptop.org/pub/sugar/sources/Pippy/Pippy-30.tar.bz2 (805K)
>> I will move pippy over to git.sugarlabs.org as well.
> Hi Brian,
> where are we with that? Pippy is the only activity of fructose that has
> not been moved to sugarlabs services (trac and git). Are you still
> planning to?
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
More information about the Devel