8,288
edits
Changes
mLine 1:
Line 1: − + − + − + + + + + + + + + + + + + + + + + + + Line 39:
Line 57: − =========================================================================== − Future of Sugar – Support, triaging and quality assurance– Famework for 0.86 − + + + Line 55:
Line 73: − + Line 61:
Line 79: − + − + − Autopackaging – We can define this as the process of going from the − + Line 85:
Line 102: − ======================================================================= − + − ======================================================================= Line 116:
Line 131: − ======================================================================= − + − ======================================================================= − a. The user finds a bug in the latest release and then puts it into track.+ − b. The bugsquad does triage. Triage means assessing the bug,+ − + − + − c. At some time, someone will try to fix it, usually a core developer.+ − + − − d. Next step is peer review. − e. Patch gets improved, turned down, or accepted. This loop will − − f. Someone with commit access commits the patch. − ====================================================================== − + − + − − − + − − − − − − =================================================================== − + − + − ====================================================================== − Auto testing of activities − + Line 167:
Line 164: − ======================================================================
moved Talk:Community/Distributions/OpenSUSE to Talk:OpenSUSE: restructure
General observations of the Sugar Camp meeting in Paris, France held
{{TOCright}}
16th and 17th of May 2009.
::[http://wiki.sugarlabs.org/go/Community/Distributions/OpenSUSE return to openSUSE]
====================================================================
=One Click Install of Sugar=
: {{Warning | Not working yet-IN DEVELOPMENT 08/22/2011}}
:'''[http://software.opensuse.org/search?q=sugar&baseproject=openSUSE%3A11.4&lang=en&exclude_debug=true 11-4 One Click Install of Sugar]''':
:TESTING 08/22/2011
*sugar 0.84.2 one step installs:
:: sugar-cellulose Basic install
:: sugar-sucrose activities
:: sugar-honey 10 more activites
:: sugar-desktop 39 packages
* Terminal: sugar-emulator (produces blank xephyr)
::logout:gdm will not login sugar
:software manager-install evince; openSuse edu branding
* Terminal: sugar-emulator (produces blank xephyr)
*'''This Procedure Does Not work at this time'''
=General observations of the Sugar Camp meeting in Paris=
:16th and 17th of May 2009.=
==Introduction==
Massive strides were made in community integration and community
Massive strides were made in community integration and community
assurance. The following is a report of what we came up with:
assurance. The following is a report of what we came up with:
===========================================================================
==Future of Sugar – Support, triaging and quality assurance– Famework for 0.86==
There were various discussion topics that included various subtopics.
There were various discussion topics that included various subtopics.
R – Roadmap
R – Roadmap
Sadly, the School Environment topic got cancelled, though it is of
Sadly, the School Environment topic got canceled, though it is of
particular importance to larger deployments and anything including the
particular importance to larger deployments and anything including the
school server. The subtopics for that group included: Teacher
school server. The subtopics for that group included: Teacher
for deployments and Mass deployments
for deployments and Mass deployments
==========================================================================
===Autopackaging===
We can define this as the process of going from the
code that developers write going into the git version control system
code that developers write going into the git version control system
to the public. There is an easy way of automating this without
to the public. There is an easy way of automating this without
spending too much time on the development. This is currently a task
spending too much time on the development. This is currently a task
being taken up by Aleksy Lin, who sadly could not be at Sugar Camp but
being taken up by Aleksey Lim, who sadly could not be at Sugar Camp but
is pretty much a core developer at this point.
is pretty much a core developer at this point.
distros and all platforms automatically.
distros and all platforms automatically.
Method of communication between wishers/bugsquad and core development team
==Method of communication between wishers/bugsquad and core development team==
At the moment, the centralised programmers upload their stuff and
At the moment, the centralised programmers upload their stuff and
OLPC, or support forums.
OLPC, or support forums.
Methodology for bug tracking and triaging – to peer reviewing and fixing:
===Methodology for bug tracking and triaging – to peer reviewing and fixing:===
# The user finds a bug in the latest release and then puts it into track.
# The bugsquad does triage. Triage means assessing the bug, validating it, and giving it a priority, and milestone (which release its going to be fixed in.)
validating it, and giving it a priority, and milestone (which release
# At some time, someone will try to fix it, usually a core developer. If it’s not a core developer, it will always be attached as a patch and reviewed.
its going to be fixed in.)
# Next step is peer review.
# Patch gets improved, turned down, or accepted. This loop will continue until the parties are happy with the code status.
If it’s not a core developer, it will always be attached as a patch
# Someone with commit access commits the patch.
and reviewed.
continue until the parties are happy with the code status.
When will 0.82 be end of life? – There is no answer to this currently
* When will 0.82 be end of life?
as it is to early to know what people in the field need. Should it be
*: There is no answer to this currently as it is to early to know what people in the field need. Should it be long term, short term, very long term? These answers will come at some stage, but not right now.
long term, short term, very long term? These answers will come at some
stage, but not right now.
Currently packaging happens to fructose and glucose only. This will
::Currently packaging happens to fructose and glucose only. This will not be the issue in the next release. RPMS will be automatically created, though it will be the decision of the distribution in question whether and how to use them. The .xo bundles will still be there but will be overwritten (basically put into a different place and given priority over the older relkease.)
not be the issue in the next release. RPMS will be automatically
created, though it will be the decision of the distribution in
question whether and how to use them. The .xo bundles will still be
there but will be overwritten (basically put into a different place
and given priority over the older relkease.)
Should we use package kit to standardize the packaging? This was a
* Should we use package kit to standardize the packaging?
question that came up and it is an interesting proposal, what do we think?
*:This was a question that came up and it is an interesting proposal, what do we think?
======================================================================
===Auto testing of activities===
There is something called sugarbot that should auto test activities.
There is something called sugarbot that should auto test activities.
there any other ideas on how to do this?
there any other ideas on how to do this?
Buildbot will not run on the current hardware. We need to find a
Buildbot will not run on the current hardware. We need to find a