On Mon, Jul 14, 2008 at 10:24 AM, Eben Eliason [EMAIL PROTECTED] wrote:
2008/7/14 Kim Quirk [EMAIL PROTECTED]:
I've been thinking about this problem for the last year -- when it first
became obvious (to me) that:
1 - we were definitely NOT going to be able to lock down APIs for at least a
Hi All,
Responding to all in one pass.
From Scott -
The general solution to this problem is trac #4951, the activity
updater, which I've landed recently. Trac #7495 says that the first
boot after an upgrade should open the activity updater, so that a
version of the activity compatible with
On Mon, Jul 14, 2008 at 15:14, Greg Smith [EMAIL PROTECTED] wrote:
GS - Does anyone have the contact info for the developers of all the
currently available activities? Can we document the changes they need to
make in 8.2.0 and contact them? Let's also ask them what they think
about us
On Mon, 2008-07-14 at 09:14 -0400, Greg Smith wrote:
- Leaving aside how its done technically, I believe that Linux
distributions are fully backward compatible. That is, you can go to the
latest supported Distribution and leave your Firefox (or any
application) on its older release and it
I've been thinking about this problem for the last year -- when it first
became obvious (to me) that:
1 - we were definitely NOT going to be able to lock down APIs for at least a
year or two
2 - we have no control over the activity developers and the maintainability
of any given activity (unless
2008/7/14 Kim Quirk [EMAIL PROTECTED]:
I've been thinking about this problem for the last year -- when it first
became obvious (to me) that:
1 - we were definitely NOT going to be able to lock down APIs for at least a
year or two
2 - we have no control over the activity developers and the
On Mon, Jul 14, 2008 at 10:35 AM, Tomeu Vizoso [EMAIL PROTECTED] wrote:
On Mon, Jul 14, 2008 at 4:24 PM, Eben Eliason [EMAIL PROTECTED] wrote:
2008/7/14 Kim Quirk [EMAIL PROTECTED]:
3 - Encourage schools to completely reflash (cleaninstall) their laptops
each year. At the end of the school
Hmmm... I'm not sure that we have to lose all the information just becuase
we did a clean install. If the backup of user data can be recovered
(especially on a file by file basis). Don't we keep the meta data, so if the
user choose to bring those items back into their laptop don't they still
have
On Mon, Jul 14, 2008 at 11:02 AM, Kim Quirk [EMAIL PROTECTED] wrote:
Hmmm... I'm not sure that we have to lose all the information just becuase
we did a clean install. If the backup of user data can be recovered
(especially on a file by file basis). Don't we keep the meta data, so if the
user
2008/7/14 Kim Quirk [EMAIL PROTECTED]:
3 - Encourage schools to completely reflash (cleaninstall) their laptops
each year. At the end of the school year, you save away kids data (hopefully
that is done automatically) and you do a cleaninstall of the next year's
image; retest all the latest
On Mon, Jul 14, 2008 at 11:22 AM, C. Scott Ananian [EMAIL PROTECTED] wrote:
The other points sound reasonable. I think we need to include a
'contact email' field in the activity.info for each activity (i'm
kinda shocked we haven't done so yet) so that we can get in touch with
This is
On Mon, Jul 14, 2008 at 11:32 AM, Eben Eliason [EMAIL PROTECTED] wrote:
when that button is pressed. The problem with this design, of course,
is that it exposes the email in a place where spammers can easily find
Yes, that is life in the 200x's. Every major package management
system has this
On Mon, Jul 14, 2008 at 6:32 PM, C. Scott Ananian [EMAIL PROTECTED] wrote:
Also, there's nothing saying that this has to be a particular person's
email address. It could be a list, or a mailinator account, or pass
through an anonymizer or something else.
I suppose some activity authors might
On Mon, Jul 14, 2008 at 6:37 PM, Marco Pesenti Gritti
[EMAIL PROTECTED] wrote:
On Mon, Jul 14, 2008 at 6:32 PM, C. Scott Ananian [EMAIL PROTECTED] wrote:
Also, there's nothing saying that this has to be a particular person's
email address. It could be a list, or a mailinator account, or pass
On Mon, Jul 14, 2008 at 12:37 PM, Marco Pesenti Gritti
[EMAIL PROTECTED] wrote:
On Mon, Jul 14, 2008 at 6:32 PM, C. Scott Ananian [EMAIL PROTECTED] wrote:
Also, there's nothing saying that this has to be a particular person's
email address. It could be a list, or a mailinator account, or pass
On Mon, Jul 14, 2008 at 3:14 PM, Greg Smith [EMAIL PROTECTED] wrote:
RE: Marco's comments.
GS - Thanks! Can you start adding the names of all activities that we
know should/will work to the Release notes too?
I can add the Fructose ones, where are the release notes? :)
How does someone know
On Mon, Jul 14, 2008 at 10:49 PM, C. Scott Ananian [EMAIL PROTECTED] wrote:
And I'd strongly prefer that they *not* do so. First off, it's
pointless to do so, since the web page is a lot easier to spam-spider
than the activity bundle. But fundamentally, I want to be able to use
On Mon, Jul 14, 2008 at 5:24 PM, Marco Pesenti Gritti [EMAIL PROTECTED]
wrote:
On Mon, Jul 14, 2008 at 10:49 PM, C. Scott Ananian [EMAIL PROTECTED]
wrote: The activities database at http://wiki.laptop.org/go/Activities
already has a 'source url' field for the web page. What is needed is
a
On Mon, Jul 14, 2008 at 11:30 PM, Eben Eliason [EMAIL PROTECTED] wrote:
What an email does do is allow, for instance, the Log activity to actually
be useful in practice, since the send log button can send the log to the
people who might actually look at it and make any necessary changes to
On Mon, Jul 14, 2008 at 11:35 PM, Marco Pesenti Gritti
[EMAIL PROTECTED] wrote:
On Mon, Jul 14, 2008 at 11:30 PM, Eben Eliason [EMAIL PROTECTED] wrote:
What an email does do is allow, for instance, the Log activity to actually
be useful in practice, since the send log button can send the log to
On Mon, Jul 14, 2008 at 5:39 PM, Marco Pesenti Gritti
[EMAIL PROTECTED] wrote:
They could be made available on a web site instead, or we could aim at
integrating log with trac.
GNOME, for example, has bug-buddy which reports crashes to bugzilla.
The goal from the beginning has been to
On Mon, Jul 14, 2008 at 11:36 PM, C. Scott Ananian [EMAIL PROTECTED] wrote:
On Mon, Jul 14, 2008 at 5:35 PM, Marco Pesenti Gritti
[EMAIL PROTECTED] wrote:
On Mon, Jul 14, 2008 at 11:30 PM, Eben Eliason [EMAIL PROTECTED] wrote:
What an email does do is allow, for instance, the Log activity to
On Mon, Jul 14, 2008 at 11:42 PM, C. Scott Ananian [EMAIL PROTECTED] wrote:
The goal from the beginning has been to minimize cost-of-entry to
develop applications for our platform. Requiring that people set up
bugzilla in order to receive bug reports is a high bar! Requiring
that they have
On Mon, Jul 14, 2008 at 10:05:46AM -0400, Daniel Drake wrote:
On Mon, 2008-07-14 at 09:14 -0400, Greg Smith wrote:
- Leaving aside how its done technically, I believe that Linux
distributions are fully backward compatible. That is, you can go to the
latest supported Distribution and leave
On Sat, Jul 12, 2008 at 12:56 AM, Greg Smith [EMAIL PROTECTED] wrote:
I understand that we do not have backward compatibility in 8.2.0 as it
currently stands.
For Glucose we are supposed to be backward compatible with Update.1.
ABI breaks should be reported as bugs.
Can we bound the test
On Fri, Jul 11, 2008 at 06:56:35PM -0400, Greg Smith wrote:
We should definitely have backward compatibility for activities!
Your desire to maintain backwards compatibility for activities is a
worthy goal but you need to be aware that there remain several areas in
which we will likely break
The general solution to this problem is trac #4951, the activity
updater, which I've landed recently. Trac #7495 says that the first
boot after an upgrade should open the activity updater, so that a
version of the activity compatible with the new OS can be installed if
necessary. The activity
On Sat, Jul 12, 2008 at 00:56, Greg Smith [EMAIL PROTECTED] wrote:
Hi Guys,
We should definitely have backward compatibility for activities!
In my opinion, there should be compatibility from one release to the
next. APIs should not break from release to release unless critically
necessary. If
On 7/12/08, Morgan Collett [EMAIL PROTECTED] wrote:
On Sat, Jul 12, 2008 at 00:56, Greg Smith [EMAIL PROTECTED] wrote:
Hi Guys,
We should definitely have backward compatibility for activities!
In my opinion, there should be compatibility from one release to the
next. APIs should not
Hi Guys,
We should definitely have backward compatibility for activities!
That is, activities that used to work (maybe starting at 656) must
continue to work. If a new release requires that all activity authors
have to recode some of their work, that will be a major deterrent to
working with us.
On Wed, Jul 09, 2008 at 02:29:17PM -0400, Kim Quirk wrote:
With almost 400,000 deployed in the world, we need to have some good
discussions on the backward compatibilty and upgradability of Activities.
Some of the bugs Charlie is writing up from the QA first look at joyride may
be answered
On Wed, 2008-07-09 at 21:06 +0200, Morgan Collett wrote:
2008/7/9 Kim Quirk [EMAIL PROTECTED]:
1 - Is there anyway to ensure backward compatibility of activities (the
8.1.1 activities will work with 8.2)? -- seems like a long shot to me.
My 2c worth here... There haven't been API breaks
On Thu, Jul 10, 2008 at 10:53:20AM -0400, Michael Stone wrote:
We already ship one on the laptop (yum)! Perhaps we could be using it
to handle our activity updates? If the problem is that yum is slow and
awful, then maybe we need to start thinking about using apt.
Here are several
On Thu, Jul 10, 2008 at 2:15 AM, Erik Garrison [EMAIL PROTECTED] wrote:
Commonly utilized solution (at least in the Linux world):
Use a package manager to manage such details for the user. For each
packaged version of an activity, record which versions of other system
libraries and
On Thu, Jul 10, 2008 at 02:35:23PM -0400, Erik Garrison wrote:
On Thu, Jul 10, 2008 at 10:53:20AM -0400, Michael Stone wrote:
Here are several problems you might think about:
1) We'd like people to be able to package activities on a wide variety
of systems including on Windows. To the
I've been running a smoketest on the recent joyride-2128 build, and have just
posted the results of what i've done so far at
http://wiki.laptop.org/go/Test_Group_Release_Notes#Joyride_Builds .
Here's a short summary of some of the more glaring issues:
- The two XOs tested could not see each
With almost 400,000 deployed in the world, we need to have some good
discussions on the backward compatibilty and upgradability of Activities.
Some of the bugs Charlie is writing up from the QA first look at joyride may
be answered by upgrading an activity to a newer one.
So here are the
On Wed, 2008-07-09 at 21:06 +0200, Morgan Collett wrote:
My 2c worth here... There haven't been API breaks for activities. I've
had to do nothing to my activities to keep them working from 8.1.0 to
joyride current.
Some external things have bitten us though. gtksourceview API change
prevents
Hi,
On Wed, 2008-07-09 at 21:06 +0200, Morgan Collett wrote:
My 2c worth here... There haven't been API breaks for
activities. I've had to do nothing to my activities to keep them
working from 8.1.0 to joyride current.
Some external things have bitten us though. gtksourceview
39 matches
Mail list logo
