#2064 BLOC Retriag: All Activities should live in /home/olpc/Activities
Zarro Boogs per Child
bugtracker at laptop.org
Wed May 7 20:47:13 EDT 2008
#2064: All Activities should live in /home/olpc/Activities
----------------------+-----------------------------------------------------
Reporter: cscott | Owner: dgilmore
Type: defect | Status: reopened
Priority: blocker | Milestone: Retriage, Please!
Component: distro | Version:
Resolution: | Keywords:
Verified: 0 | Blocking:
Blockedby: |
----------------------+-----------------------------------------------------
Comment(by sj):
Replying to [comment:11 bert]:
> Nope. The [http://pilgrim.laptop.org/~pilgrim/olpc/streams/olpc3/ olpc3]
build is a regression. It has activities in the base build again. Also,
joyride still includes activities.
>
> It is fixed for update.1 though, so I'll request retriaging. Is anybody
doing this these days?
I agree with Scott's original idea of having fallback activities in
/usr/share.. This suggests that 'core' activities can be defined as those
which we consider worth using space in all builds for. We can support
"removing" them by adding a stub activity with the same name in
/home/olpc/Activities that is functionless and invisible, and "updating"
them by installing a new version into /home/olpc/Activities, at a space
hit of at most twice the disk footprint of the original.
These 'core' activities should be ones which
- comply well with our criteria for great activities (see #6598 and the
wiki page)
- specifically demonstrate collaboration and what makes Sugar special
- help bootstrap the transparency and hackability of the system (so if
'view source' or 'publish' or 'journal' are implemented as Activities
[which I'm not sure they should be, simply for clarity of jargon], they
rank highly here)
- are small enough for the advantages to outweigh the extra disk used
(extra weight on this criterion; at most double the normal weight :)
Bert and marco, would you disagree with this notion of a core activityset?
SJ
--
Ticket URL: <http://dev.laptop.org/ticket/2064#comment:12>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list