> Here, we reach the end of my tale. You see, my friend and I agreed that our > desired next step would be to send our change to sugar-devel@ along with, > well, this story.
> -1: Unfortunately, there's no obvious way to do this with Sugar and > Pippy today. I don't want to spoil the party, but what are you going to do if that works and kids from around the world start bombarding sugar-devel with their changes? I've heard the term "success disaster" used for problems like this. The idea is that you can ignore a potential problem for now because if something like that really does become a serious problem, that's because the project as a whole was successful and (somehow) it will have picked up adequate resources to fix the problem. Still, I'd be happier if we avoided scaling problems as much as possible. -- These are my opinions, not necessarily my employer's. I hate spam. _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel