Ticket #9786 (closed defect: wontfix)

Opened 4 years ago

Last modified 4 years ago

XO 1.5 Add Activities (GCompris)

Reported by: reuben Owned by: dsd
Priority: high Milestone: 1.5-software-later
Component: sugar Version: not specified
Keywords: Cc:
Action Needed: add to build Verified: no
Deployments affected: Blocked By:
Blocking:

Change History

  Changed 4 years ago by cjb

(Reuben, FWIW, you could do this yourself -- the activities in the build are pulled from http://wiki.laptop.org/go/Activities/G1G1/11.0 )

follow-up: ↓ 3   Changed 4 years ago by reuben

Great. I'll do that now. I have programs people would like added to the Gnome side, how should I go about that?

in reply to: ↑ 2   Changed 4 years ago by cjb

Replying to reuben:

Great. I'll do that now. I have programs people would like added to the Gnome side, how should I go about that?

I think just mentioning their Fedora package names here is fine.

  Changed 4 years ago by cjb

  • next_action changed from add to build to test in build

Done in os53. (Although you didn't seem to add gcompris..)

  Changed 4 years ago by reuben

In regards to GCompris, I couldn't find the full bundle (1) equivalent on ASLO and I didn't have time to test to the WLO link below on Sugar 0.84.

(1) http://wiki.laptop.org/go/GCompris#The_GCompris_bundles

If anyone knows of the equivalent on ASLO, I'd love to know.

  Changed 4 years ago by Quozl

  • next_action changed from test in build to add to build

Tested on os54 (due to the test in build next action), indeed GCompris is not present, pushing back to add to build.

  Changed 4 years ago by cjb

I don't think the gcompris bundles are sugarized (journal/collaboration support), which suggests to me that we shouldn't be including them by default in Sugar.

  Changed 4 years ago by dsd

agreed. should we close this ticket?

  Changed 4 years ago by reuben

disagree

I'd like to point out that CJB's set of criteria does not include sugarization (1). I also do not believe the test for inclusion should be: is this program sugarized or not but rather does the activity provide increased value to the XO. However, I realize "value" is subjective.

If sugarization is a requirement then why are we including Scratch? Scratch, by the way, is by far one of the most often demoed activities we have on the XO.

Reasons to include GCompris (2) :

-It was one of the activities most discussed and requested in the respective thread on devel.

-Our largest deployment includes it in their build. Which means over one third of the XO-1 laptops built uses, GCompris.

-On the first page of 20 popular activities at ASLO, a GCompris activity is listed 6 times(3).

(1) http://lists.laptop.org/pipermail/devel/2009-November/026486.html

(2) http://activities.sugarlabs.org/en-US/sugar/collection/gcompris

(3) http://activities.sugarlabs.org/en-US/sugar/browse/type:1/cat:all?sort=popular

  Changed 4 years ago by Quozl

Tested on os64 that one can visit activities.sugarlabs.org, download and use a random GCompris based activity. Chose GComprisMazeInvisible-12.xo. Worked fine. No collaboration features present.

  Changed 4 years ago by Quozl

  • milestone changed from 1.5-software-later to 1.5-software-update

  Changed 4 years ago by Quozl

Review. We're lacking direction on this one, I suspect.

  Changed 4 years ago by Quozl

  • summary changed from XO 1.5 Add Activities to XO 1.5 Add Activities (GCompris)
  • milestone changed from 1.5-software-update to 1.5-software-later

Review again. I don't think this needs addressing before next release.

  Changed 4 years ago by cjb

  • status changed from new to closed
  • resolution set to wontfix

Going to close this one. Deployments are welcome to ship GCompris activities, but I'd rather not include activities that have no journal or collaboration integration, and no way to gain them, in the default build.

Note: See TracTickets for help on using tickets.