8,288
edits
Changes
Jump to navigation
Jump to search
mLine 2:
Line 2: − + Line 17:
Line 17: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − + − :Not yet ... (Tom might be a GCompris user / learner-contributor?)+ − : Shall we expect visitors from this community? http://www.raspberrypi.org/. They will be interested to see if Sugar will cross-compile to ARM. (I think)+ − − + − + − --[[User:Inkyfingers|Inkyfingers]] 03:13, 4 December 2011 (EST) − ::I find [[Community/Distributions/Sweets_Distribution |Sweets Distribution]] easier to use for Ubuntu' and its Derivatives (Adding an additional Repository to synaptic) as the packages are pre-configured, ready to use.+ − + − + − + − + Line 44:
Line 82: − + + + + + + + + + + + +
Platform Team/Package Management System/Getting started (view source)
Revision as of 15:56, 3 July 2012
, 15:56, 3 July 2012link update
[[User:Alsroot|Aleksey]] has prepared a new distribution model for Sugar called [[Platform_Team/Guide/Sweets_Usage|Sweets]], and asks about introducing it to non developers, {{Bug|3249}}.
[[User:Alsroot|Aleksey]] has prepared a new distribution model for Sugar called [[Platform_Team/Guide/Sweets_Usage|Sweets]], and asks about introducing it to non developers, {{Bug|3249}}.
:: Sorry, but the ticket was about [[Platform_Team/Guide/Sweets_Usage|Sweets Usage]], not about [[Community/Distributions/Sweets_Distribution |Sweets Distribution]]. [[User:Alsroot|alsroot]] 01:18, 3 December 2011 (EST)
:: Sorry, but the ticket was about [[Platform_Team/Guide/Sweets_Usage|Sweets Usage]], not about [[Sweets Distribution]]. [[User:Alsroot|alsroot]] 01:18, 3 December 2011 (EST)
::: OK, good example of the confusion possible. From [[Platform Team/Sweets]], the assumption is made that,
::: OK, good example of the confusion possible. From [[Platform Team/Sweets]], the assumption is made that,
::: "It is important to stimulate users into becoming doers—to modify existing activities, and to share the results of their experiments with other people, viz., a distribution method should handle different variants of the same project.";
::: "It is important to stimulate users into becoming doers—to modify existing activities, and to share the results of their experiments with other people, viz., a distribution method should handle different variants of the same project.";
*Here is my log for fedora 16 gnome3-shell install of sweets-sugar:
*Here is my log for fedora 16 gnome3-shell install of sweets-sugar:
::http://wiki.sugarlabs.org/go/Talk:Platform_Team/Guide/Sugar_via_Sweets#Installing_sweets-sugar_in_Fedora-16_gnome3-shell -- [[User:Satellit|satellit_]] 8:03 3 December 2011 (PST)
::http://wiki.sugarlabs.org/go/Talk:Platform_Team/Guide/Sugar_via_Sweets#Installing_sweets-sugar_in_Fedora-16_gnome3-shell -- [[User:Satellit|satellit_]] 8:03 3 December 2011 (PST)
----
''My introduction to the Package Management System might be a brief summary of these pages:''
These pages could be very roughly classified as
<span style="background:#ccffcc;">overview</span>,
<span style="background:#cce5ff;">conceptual</span>,
<span style="background:#ffccfe;">technical</span>,
or <span style="background:#ffe6cc;">Let's try it</span>
<span style="background:#ffe6cc;">Introductory page, Sweets is a [[Platform Team/Package Management System|Package Management System]]</span>
<span style="background:#ccffcc;">[[Platform_Team/Infrastructure|Infrastructure]]</span> This page describes the infrastructure map that the Platform Team provides.
<span style="background:#ffccfe;">[[Platform Team/Package Management System/Architecture|Architecture]]</span> This guide covers basic Sweets concepts.
<span style="background:#ffccfe;">[[Platform_Team/Guide/Sweets_Packaging|Sweets Packaging]]</span>,This guide describes how to prepare software projects for sweets.
<span style="background:#cce5ff;">[[Platform Team/Glossary|Sweets glossary]]</span> Some useful terms.
This guide describes how to run Sugar using Sugar via sweets
<span style="background:#ffe6cc;">[[Platform_Team/Guide/Sugar_via_Sweets|Sugar via Sweets]]</span>
This guide describes how to use Sugar Labs' Packaging Management System
<span style="background:#ffe6cc;">[[Platform_Team/Guide/Sweets_Usage|Sweets Usage]].</span>
<span style="background:#cce5ff;">[[Platform_Team/Harmonic_Distribution|Harmonic_Distribution]]</span> is a systems approach to provide all software tools.
This page, and all its sub-pages, covers implementation of
<span style="background:#cce5ff;">[[Sugar Network]]</span>.
These are overview and usage pages regarding the
<span style="background:#ffe6cc;">[[Sweets Distribution]]</span>.
These are technical pages regarding the
<span style="background:#ffccfe;">[[Platform_Team/Sweets_Distribution|Sweets Distribution]]</span>.
: But that might not actually cover in detail, Sweets Usage. I do see a need to provide further entry level explanation of the difference between sweets and sweets distribution.
:: I would put in a suggestion for the eventual removal of duplication between [[Platform_Team/Guide/Sugar_via_Sweets|Sugar via Sweets]] and [[Platform_Team/Guide/Sweets_Usage|Sweets Usage]]. --[[User:Inkyfingers|Inkyfingers]] 05:16, 28 June 2012 (EDT)
== Target Audience ==
== Target Audience ==
What sort of presentation to use? As a "can opener" can I identify three people in my target audience?
What sort of presentation to use?
'''Features''' Just to record my first impressions, these three links got me up to speed....http://0install.net/why.html ... http://packages.debian.org/wheezy/gnome-packagekit ... [[Platform Team/Guide]]. Followed by {{code | sweets --help}} and {{code | man 0install}}
'''Features''' will be the same for all three audience members. Just to record my first impressions, these three links got me up to speed....http://0install.net/why.html ... http://packages.debian.org/wheezy/gnome-packagekit ... [[Platform_Team/Guide]].
'''Advantages''' - What are the advantages for Tom Dick and Harry? Are we talking educational or productive?
'''Advantages''' - What are the advantages? Are we talking educational or productive?
'''Benefits''' - Are the benefits different for each? Does Sweets open different doors for each?
'''Benefits''' - What are the benefits?
:I find [[Sweets Distribution]] easier to use for Ubuntu' and its Derivatives (Adding an additional Repository to synaptic) as the packages are pre-configured, ready to use.
::[[Platform_Team/Guide/Sugar_via_Sweets|Sugar via Sweets]] has a wider applicability to linux OS's but requires a more experienced user. [[User:Satellit|satellit_]] 7:17 4 December 2011 (PST)
::[[Platform_Team/Guide/Sugar_via_Sweets|Sugar via Sweets]] has a wider applicability to linux OS's but requires a more experienced user. [[User:Satellit|satellit_]] 7:17 4 December 2011 (PST)
::: " For now, sweets knows only enough about the glucose dependencies to install them from native packages in Debian, Ubuntu, Fedora, Mandriva, openSUSE, and Gentoo."
::: " For now, sweets knows only enough about the glucose dependencies to install them from native packages in Debian, Ubuntu, Fedora, Mandriva, openSUSE, and Gentoo."
In case of "Target Audience" current Sweets have only one high level entrance for non-doers for now:
In terms of "Target Audience", currently Sweets has only one high-level entrance for non-doers for now:
* relatively simple (e.g., regarding jhbuild) run any (within reasonable limits) Sugar Shell version,
* it is relatively simple (e.g., compared to jhbuild) to run any (within reasonable limits) Sugar Shell version,
* including the one that is in development, i.e., help developers to test it,
* including the one that is in development, e.g., to help developers to test it,
* besides, run Sugar Shell versions that are modified by doers, e.g., Dextrose,
* additionally, it can run Sugar Shell versions that are modified by doers, e.g., Dextrose,
* on any (see TODO) major GNU/Linux distribution.
* on any (see TODO) major GNU/Linux distribution.
* what major distros we have,
* what major distros we have,
* test current Sweets there,
* test current Sweets there,
* make Sugar Shell launch as simple and obvious as possible for early adopters,
* make Sugar Shell launch as simply and obviously as possible for early adopters,
* add new entrance for non-doers, the way to run activities via Sweets (big task that requires special treatment).
* add new entrance for non-doers, the way to run activities via Sweets (big task that requires special treatment).
:Perhaps the new web page could help to point the 'way in'. --[[User:Inkyfingers|Inkyfingers]] 18:08, 9 January 2012 (EST)
== Explore further documentation ==
Based on my limited experience of installing sweets on only two distros, Mint-12 and Debian, testing, Wheezy I have two possible suggestions for improved documentation.
# To write man sweets. I looked up man 0install and found it quite helpful. I liked the tone, style and layout. It seemed well balanced in delivering entry-level material at the start. Could a working start to man sweets be made by just replacing '0install' with 'sweets' in man 0install?
# Worked example / human testing page. Aim to actually encourage non-tech users to try installing sweets. A set of instructions covering only download, install and test one variant of sweets on any distro, in the form of an entry-level worked example. The text would aim to demonstrate just a few commands, including use of a few diagnostic commands if known to work on a partially installed sweets project. Try to flag up the point where a less experienced user should file a help enquiry. Include - how to generate a 'log', 'request-help-enquiry', or Bug report in order to report any difficulties or ask for help.
This approach would hope to encourage testing and exploration by less experienced users. How this page is flagged up to those users is a different matter.
With an entry level 'install page' to support [[Platform_Team/Guide/Sugar_via_Sweets | Sugar via Sweets]], [[Platform_Team/Guide/Sweets_Usage | Sweets Usage]] could be more focused on covering usage once sweets was up and running. --[[User:Inkyfingers|Inkyfingers]] 17:51, 9 January 2012 (EST)