https://wiki.sugarlabs.org/api.php?action=feedcontributions&user=Mchua&feedformat=atomSugar Labs - User contributions [en]2024-03-29T08:39:36ZUser contributionsMediaWiki 1.35.2https://wiki.sugarlabs.org/index.php?title=User:Mchua&diff=90623User:Mchua2013-11-27T02:59:32Z<p>Mchua: "I'm no longer active" message</p>
<hr />
<div>{{TOCright}} My name is [http://blog.melchua.com/about/ Mel Chua]. I'm not active in Sugar Labs these days since returning to graduate school; this page is more an archive than anything else. Feel free to [http://blog.melchua.com/contact/ contact me] with any comments, questions, or ideas you might have.<br />
<br />
English is my native language. I have a basic understanding of [http://en.wikipedia.org/wiki/American_sign_language ASL] und mittelstufe (B1-B2) Deutsch.<br />
<br />
== Quick reference ==<br />
<br />
You might be looking for...<br />
<br />
* [[User_talk:Mchua|My talk page]] - for leaving me a message.<br />
* [http://blog.melchua.com/category/sugar/ My Planet Sugar Labs blogposts.]<br />
* [[/proposals]] - Thoughts in progress that are not yet fully formed or ready to go to main wiki. Probably inaccurate, half-baked, or some combination of the two. You have been warned.<br />
* [[/Firefox shortcuts]] that may be useful for wiki users.<br />
<br />
== Sandbox ==<br />
<br />
Things I've been playing with.<br />
<br />
* [[/Planetarium translation]]<br />
* [[/SoaS pilot]]<br />
* [[/Goals 2010]]<br />
* [[/soas notes]]<br />
<br />
== SLOBs position statement ==<br />
<br />
''I don't particularly have a position statement, but here are some materials you may find helpful in figuring out what I'm likely to bring to the table.'' The shorter summary version that recaps most of the rest of this page can be found [http://blog.melchua.com/2009/10/04/why-mel-is-running-for-slobs/ on my blog].<br />
<br />
=== Goal ===<br />
<br />
I want to be on SLOBs so that I'll never have to be on SLOBs again. The work I ''really'' want to do its capacity building within the Sugar Labs community, bringing new volunteers in and up to speed. In order to do that, Sugar Labs has to be at a point where more new volunteers ''can'' come in and get up to speed - right now it's a struggle for even experienced contributors to simultaneously keep up with what's going on, contribute in the way they want to help, ''and'' have a life outside of Sugar Labs (it was barely manageable when I was volunteering more-than-full-time at the start of 2009).<br />
<br />
Ultimately, I want to run merrily through the jungle with troops of new recruits, showing them trees and vines and berries, introducing them to people who can teach them about birds and fish and hut-building. But the paths aren't clear for running yet; someone's got to take a machete and get the underbrush out of the way. I'm willing to serve a year or two in the SLOBs Machete-Wielding Corps, hacking slowly through thorns, aching to run all the while, because I know it's what will eventually give me and many others clear routes to sprint full-tilt-ahead at where we want to go.<br />
<br />
=== Deciding to run ===<br />
<br />
After a lot of internal debate, a few long conversations, and a hard look at the calendar/project-list clearing I'd have to do, I've decided to run for SLOBs, because I think that's where my limited time for SL (and it ''is'' limited) can best be spent. (I was previously in "mehhh, I'll put my name here as a placeholder and decide later" mode, but now I'm just going to go for it full-tilt.)<br />
<br />
I'll have to give up my dream of dabbling in various bits of Sugar code for fun (it's slowly becoming apparent to me that I may never be primarily a coder again), and I'll have to apply a serious amount of discipline towards staying in the loop consistently, which has been tough as my schedule's fluctuated and I've started to travel for work (YAY!). But I think that's a fair tradeoff if it makes me more able to blast blockers out of the way of other people - including my future self, who'll be a lot more effective at SL recruiting once a framework to capacity-build atop has been put more solidly in place.<br />
<br />
Someone's got to do the non-shiny gruntwork, and the project management and capacity-building-fu I've been learning in Fedora for the past few months seem like skills SL could use at this stage in its growth. <br />
<br />
Challenges I can foresee:<br />
<br />
* consistently clearing the time to make SL stuff happen. I know that if it isn't on my schedule, I will probably not do it, so I'll need to schedule SL in and stick to it.<br />
<br />
* having the discipline to make sure the SLOBs todo list stays up to date and on track, if needed... ;)<br />
<br />
* bias - my history with OLPC and current ties with Fedora mean that I will have to be very conscious of the ways this might affect my positions on some topics, and excuse myself when needed.<br />
<br />
* restraining my tendency to want to make everything transparent Right Away, without squelching or diminishing that tendency - defaulting to open is a great setting to have, but "default" does not mean "the only option," and I still struggle to balance this desire with prudence and practicality.<br />
<br />
* not getting distracted by shiny stuff. I'm pretty sure SLOBs will take up most of my "SL time," so making sure SLOBs stuff gets done first will take more of that "discipline" stuff I've been practicing...<br />
<br />
=== On consensus ===<br />
<br />
No matter what happens, we'll be able to improvise and get through it okay; SL people are good people and smart people and stuff is going to work eventually. The question is, what values of $work and $eventually are we willing to accept?<br />
<br />
It's like having a fire drill in school. It's not that everyone wouldn't be able to get out on their own, given sufficient time. I mean, everyone is generally pretty smart, and tries to get away from fire. But because in a fire, time is precious, and people get panicked, and you can't just "get out eventually," you need to get out NOW, you have a fire drill, so everyone goes "okay, this is how it would work," and it turns into more of a known factor; you know how all the pieces would coordinate ahead of time.<br />
<br />
So I think SL could use more "fire drill" procedures, since... at some point, we may need to make a decision that we can't wait for a 5-week, 300-email thread consensus on. I think such decisions will be exceedingly rare. I'd like to have insurance that we know what we will do with them. I'd like to guide SL through the process of thinking some of these scenarios through ahead of time so that if they ever happen, we'll already have frontloaded the community consensus process, and can just proceed.<br />
<br />
== Interests ==<br />
<br />
I'm a community engineer. That means I'm something of a jack-of-all-trades - my primary interest is in making it easier for contributors (or potential contributors) to Sugar Labs to do what ''they'' want to do, and to keep radical transparency going throughout the project so that the efforts of individual volunteers are all aimed towards furthering the mission and vision of Sugar Labs as a whole as well. Basically, I try to nurture leaders into and within the community, get them to work interdependently with each other, and sledgehammer junk out of their way so they can do Real Work. Or in other words, I ask these questions all the time:<br />
<br />
# What do you want to do?<br />
# Why aren't you doing it (or what stops you from doing it better)?<br />
# Why don't you and others know (or know more) about the exact impact that you're having on how children learn?<br />
<br />
My background is in engineering, so I'll often tackle things through technical tools and the people who want to work on them, and use software-based analogies and processes to get things done. I'm a student of education (and learning) as well as business operations - I'm by no means fluent in those two domains yet, but I'm trying hard to become equally comfortable working within and with them. Help and feedback is always incredibly appreciated.<br />
<br />
== Projects ==<br />
<br />
I tend to set my goals in 6-month cycles mirroring the Sugar release schedule. This list is super-flexible; stuff changes all the time, random cool ideas come up, and so this has deliberately been planned with lots of wiggle room. As things change, I (usually remember to) edit this page to reflect that.<br />
<br />
I was sidelined with RSI for much of the previous release cycle (and am still recovering), so priorities have been adjusted accordingly. For this release cycle, I've put all my projects aside under the "future" category until after the SLOBs election when I'll know how much time I have to work on them (or if I get elected to SLOBs, how I can work on them as part of that role).<br />
<br />
'''Please feel free to steal a project if you like it, and let me know how I can help - I don't care who does this stuff so long as it gets done.'''<br />
<br />
== Future goals and projects ==<br />
<br />
Feel free to pick up on these or let me know if you would like to help!<br />
<br />
=== Entry points for all SL teams ===<br />
<br />
'''Goal: There should be at least one mapped-out-and-tested new contributor experience for every SL team - something that takes people from "I want to get involved with Sugar by working on this team" to independently contributing and able to mentor newcomers to that team themselves. This should be done by contributors who want to personally experience, improve, and document them, and encourage others to go through them and give feedback.''' (All these things would be done in partnership with and with the approval of Team leaders.)<br />
<br />
Here are projects for each team that could be picked up. I am willing to help match people with mentors for each task. The point of doing these things is not just "do this for team X," but to explore how welcoming team X is to newcomers who want to contribute, and how this experience could be improved - think of yourself as a mystery shopper, except not-so-mysterious (the fact that you're doing this to test out "newbie routes" is totally transparent).<br />
<br />
* [[Marketing Team/Sugar_stories|Interviewing Sugar Labs contributors]] for profiles for the Marketing team.<br />
* Maintain the [http://git.sugarlabs.org/projects/irc IRC Activity] for Activity Team.<br />
* Run at least one BugSquad sprint and mentor someone else in running a BugSquad sprint for BugSquad Team.<br />
* Provide a weekly feedback report to Deployment Team for the Sugar deployments I'm involved with.<br />
* Produce the next draft of a Sugar Deployment Guide with Deployment and Documentation teams, possibly at another FLOSSmanuals sprint.<br />
* Work with Documentation Team to make guides for how to get started in each community team.<br />
* Work with Design Team to design and execute an appropriate small project for this cycle (perhaps a "get swag!" listing page).<br />
* Have at least 4 accepted patches to sugar-core or SoaS for this release cycle for Development Team.<br />
* Run an [[Activity Team/Development Sprint]] with a strong focus on educator feedback for the Education Team.<br />
* Define and offer hosting service packages for Local Labs and Deployments with Infrastructure Team.<br />
* Write a monthly group profile for Marketing Team.<br />
* Make (or improve) a redirect bot for Wiki Team.<br />
* Doing QA for the [[Addons Portal]] project. The first step is to find out (or write down) testing and feedback cycles for its development.<br />
<br />
=== Well-defined open tasks ===<br />
<br />
SL's trac should include a component for each team's tasks (not just code bugs!) and also a keyword for newbies to search for, so we can tag getting-started tasks. Each of these getting-started tasks should have a mentor associated with it and information that would enable each newbie to find that mentor to shepherd and sponsor them through the beginning-contributor process. Finally, the task log should be kept populated with useful things to do and monitored through at least the first dozen newbies to see how they experience it, then passed on to one of those newcomers to maintain. I would be willing to mentor this task.<br />
<br />
One could imagine a similar (maintained) list of open projects (concrete accomplishments larger than a single task). This may actually be a better place to start. The first task would be writing up a short guide as to what constitutes a good project proposal and submitting the draft to [http://lists.sugarlabs.org/listinfo/iaep iaep] for feedback. I would be willing to mentor this task.<br />
<br />
=== Local Labs formation and communication should be easy ===<br />
<br />
There should be a guide and case studies for formation of Local Labs. The interface for participating this way should be clear - what is a Local Lab? Why would you start one? What are the requirements to do so? And so forth. This is probably best done in conjunction with groups who are in the process of starting Local Labs right now. I would be willing to help find someone to mentor this task (I imagine there are better mentors for this than me).<br />
<br />
== History ==<br />
<br />
I left this section blank for the longest time - and the best way to find out my history is still to pop on the #sugar IRC channel and ask around about who mchua is and what I'm like and what I do. But here are a few points to ask about, and folks who you could ask, to get you started.<br />
<br />
* The June 2007 Game Jam, when we went (in two days!) from no community Activity maintainers, or even co-maintaners, to 10 entirely community-created-and-maintained Activities, with 3-4 maintainers for each Activity; Brian Jordan and Wade Brainerd joined us here.<br />
* The community QA team, which I ran as part of my role as an engineer at OLPC, and how this helped us by getting testing done, but also by figuring out upstream-downstream relationships between OLPC and the newly-born Sugar Labs, and by giving new volunteers an on-ramp to get involved with development. Tabitha Roder and the Welly testers were heavily involved with this.<br />
* My presence during the first 2 Sugar Camp gatherings in Boston during fall and winter 2008, particularly the talk that Greg DeKoenigsberg and I did on community (during which I didn't actually talk - find the videos to see what happened when I used my talk time to introduce and hand the podium to new volunteers instead) and the ending cool-down discussion that most of the current SLOBs were present for.<br />
* My brief tenure as ad-hoc Marketing team lead, in the gap between when Greg DeKoenigsberg stepped down and Sean Daly came in.</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Contacts&diff=90622Summer of Code/Contacts2013-11-27T02:41:18Z<p>Mchua: no longer mentoring GSoC applications due to other life commitments</p>
<hr />
<div><noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|Summer of Code|home=Summer of Code Project Home|xbgColor=ffe792}}</noinclude>{{TOCright}}<br />
<br />
==Coordinators==<br />
* Jameson.Quinn at gmail<br />
{{:Summer of Code/Mentors | Mentors}}<br />
<br />
<br />
<br />
[[Category:GSoC]]<br />
[[Category:Contact]]</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Finance&diff=65040Finance2011-04-21T23:10:51Z<p>Mchua: /* For purchasing things */</p>
<hr />
<div>This page should answer two questions:<br />
<br />
* How much money does Sugar Labs currently have, where did it come from, and what is it being used for?<br />
* How can I ask for some of it?<br />
<br />
(We hope you'll also help us figure out how to get more resources as well!)<br />
<br />
The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.<br />
<br />
== Current finances ==<br />
<br />
All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.<br />
<br />
* The last known balance is from [[#January 2011]] and is $19,591.09 USD, held as follows:<br />
** $19,591.09 USD in a Vanguard Money Market account held by the Software Freedom Conservancy on behalf of Sugar Labs<br />
<br />
* The $19,591.09 USD is earmarked as follows:<br />
** ?? for Gould Grant<br />
** ?? unrestricted (available for future grants)<br />
<br />
''[[User:Walter|Walter Bender]] should be filling in the details above shortly.'' [[User:Mchua|Mchua]] 17:54, 21 April 2011 (EDT)<br />
<br />
== Where we get money from ==<br />
<br />
Sugar Labs doesn't have much in the way of regular income, so we can't predict when new funding will come in. We've gotten funding from a few sources in the past:<br />
<br />
* Donations from private individuals (thank you!)<br />
* Grant money to develop certain aspects of Sugar Labs - this is typically earmarked for a specific project<br />
* Google Summer of Code - Sugar Labs gets $500 of unrestricted funds for each student mentored.<br />
<br />
In particular, if you're interested in applying for an external grant to work on some aspect of Sugar Labs, let us know; we'd be happy to help.<br />
<br />
== Archive of transactions ==<br />
<br />
=== April 2011 ===<br />
<br />
Not known.<br />
<br />
=== March 2011 ===<br />
<br />
Not known.<br />
<br />
=== February 2011 ===<br />
<br />
Not known.<br />
<br />
=== January 2011 ===<br />
<br />
'''End-of-month balance:''' $19,591.09<br />
<br />
'''Net change since last month:''' -$1,679.08<br />
<br />
'''Transactions:'''<br />
<br />
{|border="1" cellspacing="0" width="100%" align="right"<br />
! Item<br />
! From/To<br />
! Income<br />
! Expenses<br />
! Notes<br />
|-<br />
| Gould Grant student developer salary<br />
| Gould Grant student employee<br />
| <br />
| -$1,680.00<br />
| Not sure if we want to put names here, so I left that information out. [[User:Mchua|Mchua]]<br />
|-<br />
| Interest from Vanguard account<br />
| Vanguard<br />
| $0.92<br />
|<br />
|<br />
|-<br />
!<br />
! Total<br />
! $0.92<br />
! -$1,680.00<br />
!<br />
|}<br />
<br />
== Requesting budget ==<br />
<br />
You may request budget for Sugar Labs related travel or project expenses. We can't fully fund every request, because we do operate on a limited budget. But we can't fund yours if we don't know you have a need -- so if you do, fill out a request and we'll get in touch with you about it.<br />
<br />
You can see the list of [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=fundingrequest&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component all open requests] and also the list of [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&component=fundingrequest&order=priority&col=id&col=summary&col=component&col=status&col=type&col=priority&col=milestone every request that's ever been made].<br />
<br />
=== How to fill out a request ===<br />
<br />
A request can be filled out in 10 minutes or less. We're trying to make this process as easy as possible! <br />
<br />
# Open a [http://bugs.sugarlabs.org/newticket new ticket] in the Sugar Labs tracker. (You'll have to log into the tracker to do this.)<br />
# Set the component to "fundingrequest." '''This is important. If the component is not set correctly, we will not see your ticket when we search for it!'''<br />
# Answer the [[#What we need to know]] questions in the description field of your ticket.<br />
# Once the ticket has been filed, Send an email to [http://lists.sugarlabs.org/listinfo/iaep iaep] (for transparency) and [http://lists.sugarlabs.org/listinfo/slobs slobs] (as the decision-making body) with the subject line "New Finance Request: <short summary of the item requested>," where <short summary of the item requested> is replaced by... well, a short summary of what you're asking for money for, and a link to the ticket in the body of your email. '''This is important. If you do not email both lists, nobody will know you've submitted a budget request!'''<br />
<br />
At this point, you should wait to hear back from SLOBs. If nobody's responded to your request within a week, feel free to ping both mailing lists again.<br />
<br />
=== What we need to know ===<br />
<br />
Each request ticket must contain answers to one of the following sets of questions, depending on the type of funding you're asking for.<br />
<br />
==== For funding travel ====<br />
<br />
If you're asking for funds to cover a trip, use this set of questions.<br />
<br />
# '''Where are you going''' (location and event)?<br />
# '''What do you need covered?''' (Please estimate the costs in USD: hotel $X, travel $Y)<br />
# '''If we cannot provide a full subsidy, will a partial subsidy be helpful?''' (Yes/No)<br />
## If Yes can you specify the minimum amount you would need covered to facilitate your attendance<br />
# If you are requesting airfare, include complete flight information such as flight numbers, desired departure and arrival airports, and times. Also let us know if you have specific time restrictions.<br />
# '''Do you need a visa or other official processing before you can travel?''' If so, approximately how long does that processing take?<br />
# '''What will you accomplish by going on this trip?''' Please be as specific as possible, since this is the most important factor in granting requests.<br />
<br />
The last question really is the most important, and will likely be the longest part of your answer. Tell us what you're going to accomplish by taking this trip. Preference is given to people who are attending an event with a goal to make Sugar Labs better, and a plan for doing it.<br />
<br />
Simply "meeting with people" or "talking about ways to do something" are not specific to Sugar Labs. Ideas can be discussed on mailing lists, after all. And although meeting face to face is a wonderful thing, that doesn't necessarily result in getting anything done.<br />
<br />
* Not specific: Meet with other people from JKL Group.<br />
* Not specific: Improve communication between Team X and Team Y.<br />
* Specific: Write a working module for Web App Q that creates a service queue for Team X to do Task Z more efficiently.<br />
* Specific: Agree on and publish a complete plan, schedule, and milestones for Project W. <br />
<br />
==== For purchasing things ====<br />
<br />
Use this template if you're requesting the purchase of equipment, a subscription, etc. <br />
<br />
# '''What is being purchased?''' If it's a product, link to the product, etc.<br />
# '''Why does this purchase benefit the operations of Sugar Labs?''' What is the blocker it resolves? <br />
# '''Who will be responsible for the item?''' Who will own it? How will it be tracked/maintained? <br />
# '''How much will it cost?''' Are there any maintenance costs associated with the purchase? How often will it have to be renewed (if at all)?<br />
# '''What other options were evaluated for purchase?''' Why did the chosen product/service/option get selected as the best one? What were the criteria or features you needed?<br />
# '''What deadlines are associated with this request?''' Do you need an answer by a certain date? Would the funding need to come by a particular point in time? Note that approving future spending is a separate action from actually spending the money - for instance, we may agree to fund something but pay for it 3 months down the line - so it's good to know both dates, if they exist.<br />
# '''Other notes?'''<br />
<br />
=== How decisions are made ===<br />
<br />
This section explains the criteria typically used to decide whether to subsidize the travel of a specific applicant. It's provided for context only - if you're requesting funding, you don't actually have to read this stuff!<br />
<br />
==== Relevance ====<br />
<br />
* ''Does this purchase/event deliver information that is pertinent to an ongoing project of concern at the event?'' For example, an event that includes a critical brainstorming session on deployment outreac could be more effective with the attendance of a teacher or engineer from a deployment.<br />
* ''Does the purchase/event provide an opportunity for this particular person to attract contribution to one or more areas in Sugar Labs?'' An event that attracts computer-based designers, for instance, might present an opportunity for a member of the Design team to attract new, skilled contributors.<br />
* ''Is the requesting person a current contributor?'' Current contributors with a proven history of involvement in some sense are a known quantity. This does not mean that sponsorship shouldn't go to new or potential contributors, but it is a factor for consideration.<br />
<br />
==== Criticality ====<br />
<br />
* (For travel only) ''Does this person have demonstrated skills in an area that will promote reaching the goals of the event?'' For example, if Sugar's speaking schedule at an event requires someone with expertise on packaging Activities for various Linux distributions, it would make sense to sponsor the travel of someone who could give those talks.<br />
* ''Are there clear deliverables attached to this purchase/event that otherwise cannot be achieved?'' Deliverables come in many forms, such as working code; completed documentation; or key decisions. For purchases, will the absence of the purchase block or negatively impact work that is already being done on the project? For events, if other contributors involved in the same area are expected to attend already, will this person's absence negatively impact their work at the event?<br />
* ''How important is this subsidy to the purchase/event?'' Without the full subsidy, will the item not be able to be purchased, or will the applicant not be able to attend the event at all? Will a partial subsidy suffice? Would a change in plans, such as attending part of the event, or getting a less full-featured item, still allow this person's goals to be achieved? Is Sugar Labs funding the ''only'' option available for this purchase?<br />
<br />
==== Specificity ====<br />
<br />
* ''Has this person provided substantial information about the specific objectives to achieve?'' We look at the proposal critically, because there are usually more requests than we can fill. The best requests tend to reflect clear vision from the applicants of exactly what they will achieve through this funding, and a link between that vision and the larger objectives of Sugar Labs or a specific team.<br />
* ''Are the objectives achievable within the time frame of the event/project?'' Sometimes it may not be possible to meet every objective despite best intentions and hard work. Nevertheless, sponsors should also carefully consider whether the deliverables can reasonably be finished by the end of the relevant time period. Setting and meeting reasonable expectations is a good habit for any project.<br />
<br />
==== Proximity ====<br />
<br />
* (For event travel only) ''Is this person located in the same region as the event?'' Regionally co-located people generally require less funding. It is not cost effective, for instance, to fund the travel of multiple people from North America to a European event. In specific cases there may be call for such subsidies, but in general regional events should reflect regional attendance and participation.<br />
<br />
==== Expense ====<br />
<br />
* ''How expensive is the request?'' A higher subsidy amount should carry with it higher expectations, more criticality, or other benefits that justify the expense. Keep in mind that the transparent approval process creates better accountability for sponsors in making decisions.<br />
<br />
''This system is based on the [https://fedorahosted.org/fudcon-planning/wiki/FundingRequest Fedora community funding request system].''</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Finance&diff=65039Finance2011-04-21T23:09:23Z<p>Mchua: /* Requesting budget */</p>
<hr />
<div>This page should answer two questions:<br />
<br />
* How much money does Sugar Labs currently have, where did it come from, and what is it being used for?<br />
* How can I ask for some of it?<br />
<br />
(We hope you'll also help us figure out how to get more resources as well!)<br />
<br />
The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.<br />
<br />
== Current finances ==<br />
<br />
All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.<br />
<br />
* The last known balance is from [[#January 2011]] and is $19,591.09 USD, held as follows:<br />
** $19,591.09 USD in a Vanguard Money Market account held by the Software Freedom Conservancy on behalf of Sugar Labs<br />
<br />
* The $19,591.09 USD is earmarked as follows:<br />
** ?? for Gould Grant<br />
** ?? unrestricted (available for future grants)<br />
<br />
''[[User:Walter|Walter Bender]] should be filling in the details above shortly.'' [[User:Mchua|Mchua]] 17:54, 21 April 2011 (EDT)<br />
<br />
== Where we get money from ==<br />
<br />
Sugar Labs doesn't have much in the way of regular income, so we can't predict when new funding will come in. We've gotten funding from a few sources in the past:<br />
<br />
* Donations from private individuals (thank you!)<br />
* Grant money to develop certain aspects of Sugar Labs - this is typically earmarked for a specific project<br />
* Google Summer of Code - Sugar Labs gets $500 of unrestricted funds for each student mentored.<br />
<br />
In particular, if you're interested in applying for an external grant to work on some aspect of Sugar Labs, let us know; we'd be happy to help.<br />
<br />
== Archive of transactions ==<br />
<br />
=== April 2011 ===<br />
<br />
Not known.<br />
<br />
=== March 2011 ===<br />
<br />
Not known.<br />
<br />
=== February 2011 ===<br />
<br />
Not known.<br />
<br />
=== January 2011 ===<br />
<br />
'''End-of-month balance:''' $19,591.09<br />
<br />
'''Net change since last month:''' -$1,679.08<br />
<br />
'''Transactions:'''<br />
<br />
{|border="1" cellspacing="0" width="100%" align="right"<br />
! Item<br />
! From/To<br />
! Income<br />
! Expenses<br />
! Notes<br />
|-<br />
| Gould Grant student developer salary<br />
| Gould Grant student employee<br />
| <br />
| -$1,680.00<br />
| Not sure if we want to put names here, so I left that information out. [[User:Mchua|Mchua]]<br />
|-<br />
| Interest from Vanguard account<br />
| Vanguard<br />
| $0.92<br />
|<br />
|<br />
|-<br />
!<br />
! Total<br />
! $0.92<br />
! -$1,680.00<br />
!<br />
|}<br />
<br />
== Requesting budget ==<br />
<br />
You may request budget for Sugar Labs related travel or project expenses. We can't fully fund every request, because we do operate on a limited budget. But we can't fund yours if we don't know you have a need -- so if you do, fill out a request and we'll get in touch with you about it.<br />
<br />
You can see the list of [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=fundingrequest&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component all open requests] and also the list of [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&component=fundingrequest&order=priority&col=id&col=summary&col=component&col=status&col=type&col=priority&col=milestone every request that's ever been made].<br />
<br />
=== How to fill out a request ===<br />
<br />
A request can be filled out in 10 minutes or less. We're trying to make this process as easy as possible! <br />
<br />
# Open a [http://bugs.sugarlabs.org/newticket new ticket] in the Sugar Labs tracker. (You'll have to log into the tracker to do this.)<br />
# Set the component to "fundingrequest." '''This is important. If the component is not set correctly, we will not see your ticket when we search for it!'''<br />
# Answer the [[#What we need to know]] questions in the description field of your ticket.<br />
# Once the ticket has been filed, Send an email to [http://lists.sugarlabs.org/listinfo/iaep iaep] (for transparency) and [http://lists.sugarlabs.org/listinfo/slobs slobs] (as the decision-making body) with the subject line "New Finance Request: <short summary of the item requested>," where <short summary of the item requested> is replaced by... well, a short summary of what you're asking for money for, and a link to the ticket in the body of your email. '''This is important. If you do not email both lists, nobody will know you've submitted a budget request!'''<br />
<br />
At this point, you should wait to hear back from SLOBs. If nobody's responded to your request within a week, feel free to ping both mailing lists again.<br />
<br />
=== What we need to know ===<br />
<br />
Each request ticket must contain answers to one of the following sets of questions, depending on the type of funding you're asking for.<br />
<br />
==== For funding travel ====<br />
<br />
If you're asking for funds to cover a trip, use this set of questions.<br />
<br />
# '''Where are you going''' (location and event)?<br />
# '''What do you need covered?''' (Please estimate the costs in USD: hotel $X, travel $Y)<br />
# '''If we cannot provide a full subsidy, will a partial subsidy be helpful?''' (Yes/No)<br />
## If Yes can you specify the minimum amount you would need covered to facilitate your attendance<br />
# If you are requesting airfare, include complete flight information such as flight numbers, desired departure and arrival airports, and times. Also let us know if you have specific time restrictions.<br />
# '''Do you need a visa or other official processing before you can travel?''' If so, approximately how long does that processing take?<br />
# '''What will you accomplish by going on this trip?''' Please be as specific as possible, since this is the most important factor in granting requests.<br />
<br />
The last question really is the most important, and will likely be the longest part of your answer. Tell us what you're going to accomplish by taking this trip. Preference is given to people who are attending an event with a goal to make Sugar Labs better, and a plan for doing it.<br />
<br />
Simply "meeting with people" or "talking about ways to do something" are not specific to Sugar Labs. Ideas can be discussed on mailing lists, after all. And although meeting face to face is a wonderful thing, that doesn't necessarily result in getting anything done.<br />
<br />
* Not specific: Meet with other people from JKL Group.<br />
* Not specific: Improve communication between Team X and Team Y.<br />
* Specific: Write a working module for Web App Q that creates a service queue for Team X to do Task Z more efficiently.<br />
* Specific: Agree on and publish a complete plan, schedule, and milestones for Project W. <br />
<br />
==== For purchasing things ====<br />
<br />
Use this template if you're requesting the purchase of equipment, a subscription, etc. <br />
<br />
# '''What is being purchased?''' If it's a product, link to the product; if it's (If it's a produ to product, etc.)<br />
# '''Why does this purchase benefit the operations of Sugar Labs?''' What is the blocker it resolves? <br />
# '''Who will be responsible for the item?''' Who will own it? How will it be tracked/maintained? <br />
# '''How much will it cost?''' Are there any maintenance costs associated with the purchase? How often will it have to be renewed (if at all)?<br />
# '''What other options were evaluated for purchase?''' Why did the chosen product/service/option get selected as the best one? What were the criteria or features you needed?<br />
# '''What deadlines are associated with this request?''' Do you need an answer by a certain date? Would the funding need to come by a particular point in time? Note that approving future spending is a separate action from actually spending the money - for instance, we may agree to fund something but pay for it 3 months down the line - so it's good to know both dates, if they exist.<br />
# '''Other notes?'''<br />
<br />
=== How decisions are made ===<br />
<br />
This section explains the criteria typically used to decide whether to subsidize the travel of a specific applicant. It's provided for context only - if you're requesting funding, you don't actually have to read this stuff!<br />
<br />
==== Relevance ====<br />
<br />
* ''Does this purchase/event deliver information that is pertinent to an ongoing project of concern at the event?'' For example, an event that includes a critical brainstorming session on deployment outreac could be more effective with the attendance of a teacher or engineer from a deployment.<br />
* ''Does the purchase/event provide an opportunity for this particular person to attract contribution to one or more areas in Sugar Labs?'' An event that attracts computer-based designers, for instance, might present an opportunity for a member of the Design team to attract new, skilled contributors.<br />
* ''Is the requesting person a current contributor?'' Current contributors with a proven history of involvement in some sense are a known quantity. This does not mean that sponsorship shouldn't go to new or potential contributors, but it is a factor for consideration.<br />
<br />
==== Criticality ====<br />
<br />
* (For travel only) ''Does this person have demonstrated skills in an area that will promote reaching the goals of the event?'' For example, if Sugar's speaking schedule at an event requires someone with expertise on packaging Activities for various Linux distributions, it would make sense to sponsor the travel of someone who could give those talks.<br />
* ''Are there clear deliverables attached to this purchase/event that otherwise cannot be achieved?'' Deliverables come in many forms, such as working code; completed documentation; or key decisions. For purchases, will the absence of the purchase block or negatively impact work that is already being done on the project? For events, if other contributors involved in the same area are expected to attend already, will this person's absence negatively impact their work at the event?<br />
* ''How important is this subsidy to the purchase/event?'' Without the full subsidy, will the item not be able to be purchased, or will the applicant not be able to attend the event at all? Will a partial subsidy suffice? Would a change in plans, such as attending part of the event, or getting a less full-featured item, still allow this person's goals to be achieved? Is Sugar Labs funding the ''only'' option available for this purchase?<br />
<br />
==== Specificity ====<br />
<br />
* ''Has this person provided substantial information about the specific objectives to achieve?'' We look at the proposal critically, because there are usually more requests than we can fill. The best requests tend to reflect clear vision from the applicants of exactly what they will achieve through this funding, and a link between that vision and the larger objectives of Sugar Labs or a specific team.<br />
* ''Are the objectives achievable within the time frame of the event/project?'' Sometimes it may not be possible to meet every objective despite best intentions and hard work. Nevertheless, sponsors should also carefully consider whether the deliverables can reasonably be finished by the end of the relevant time period. Setting and meeting reasonable expectations is a good habit for any project.<br />
<br />
==== Proximity ====<br />
<br />
* (For event travel only) ''Is this person located in the same region as the event?'' Regionally co-located people generally require less funding. It is not cost effective, for instance, to fund the travel of multiple people from North America to a European event. In specific cases there may be call for such subsidies, but in general regional events should reflect regional attendance and participation.<br />
<br />
==== Expense ====<br />
<br />
* ''How expensive is the request?'' A higher subsidy amount should carry with it higher expectations, more criticality, or other benefits that justify the expense. Keep in mind that the transparent approval process creates better accountability for sponsors in making decisions.<br />
<br />
''This system is based on the [https://fedorahosted.org/fudcon-planning/wiki/FundingRequest Fedora community funding request system].''</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Finance&diff=65038Finance2011-04-21T23:07:48Z<p>Mchua: /* How to fill out a request */</p>
<hr />
<div>This page should answer two questions:<br />
<br />
* How much money does Sugar Labs currently have, where did it come from, and what is it being used for?<br />
* How can I ask for some of it?<br />
<br />
(We hope you'll also help us figure out how to get more resources as well!)<br />
<br />
The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.<br />
<br />
== Current finances ==<br />
<br />
All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.<br />
<br />
* The last known balance is from [[#January 2011]] and is $19,591.09 USD, held as follows:<br />
** $19,591.09 USD in a Vanguard Money Market account held by the Software Freedom Conservancy on behalf of Sugar Labs<br />
<br />
* The $19,591.09 USD is earmarked as follows:<br />
** ?? for Gould Grant<br />
** ?? unrestricted (available for future grants)<br />
<br />
''[[User:Walter|Walter Bender]] should be filling in the details above shortly.'' [[User:Mchua|Mchua]] 17:54, 21 April 2011 (EDT)<br />
<br />
== Where we get money from ==<br />
<br />
Sugar Labs doesn't have much in the way of regular income, so we can't predict when new funding will come in. We've gotten funding from a few sources in the past:<br />
<br />
* Donations from private individuals (thank you!)<br />
* Grant money to develop certain aspects of Sugar Labs - this is typically earmarked for a specific project<br />
* Google Summer of Code - Sugar Labs gets $500 of unrestricted funds for each student mentored.<br />
<br />
In particular, if you're interested in applying for an external grant to work on some aspect of Sugar Labs, let us know; we'd be happy to help.<br />
<br />
== Archive of transactions ==<br />
<br />
=== April 2011 ===<br />
<br />
Not known.<br />
<br />
=== March 2011 ===<br />
<br />
Not known.<br />
<br />
=== February 2011 ===<br />
<br />
Not known.<br />
<br />
=== January 2011 ===<br />
<br />
'''End-of-month balance:''' $19,591.09<br />
<br />
'''Net change since last month:''' -$1,679.08<br />
<br />
'''Transactions:'''<br />
<br />
{|border="1" cellspacing="0" width="100%" align="right"<br />
! Item<br />
! From/To<br />
! Income<br />
! Expenses<br />
! Notes<br />
|-<br />
| Gould Grant student developer salary<br />
| Gould Grant student employee<br />
| <br />
| -$1,680.00<br />
| Not sure if we want to put names here, so I left that information out. [[User:Mchua|Mchua]]<br />
|-<br />
| Interest from Vanguard account<br />
| Vanguard<br />
| $0.92<br />
|<br />
|<br />
|-<br />
!<br />
! Total<br />
! $0.92<br />
! -$1,680.00<br />
!<br />
|}<br />
<br />
== Requesting budget ==<br />
<br />
You may request budget for Sugar Labs related travel or project expenses. We can't fully fund every request, because we do operate on a limited budget. But we can't fund yours if we don't know you have a need -- so if you do, fill out a request and we'll get in touch with you about it.<br />
<br />
=== How to fill out a request ===<br />
<br />
A request can be filled out in 10 minutes or less. We're trying to make this process as easy as possible! <br />
<br />
# Open a [http://bugs.sugarlabs.org/newticket new ticket] in the Sugar Labs tracker. (You'll have to log into the tracker to do this.)<br />
# Set the component to "fundingrequest." '''This is important. If the component is not set correctly, we will not see your ticket when we search for it!'''<br />
# Answer the [[#What we need to know]] questions in the description field of your ticket.<br />
# Once the ticket has been filed, Send an email to [http://lists.sugarlabs.org/listinfo/iaep iaep] (for transparency) and [http://lists.sugarlabs.org/listinfo/slobs slobs] (as the decision-making body) with the subject line "New Finance Request: <short summary of the item requested>," where <short summary of the item requested> is replaced by... well, a short summary of what you're asking for money for, and a link to the ticket in the body of your email. '''This is important. If you do not email both lists, nobody will know you've submitted a budget request!'''<br />
<br />
At this point, you should wait to hear back from SLOBs. If nobody's responded to your request within a week, feel free to ping both mailing lists again.<br />
<br />
=== What we need to know ===<br />
<br />
Each request ticket must contain answers to one of the following sets of questions, depending on the type of funding you're asking for.<br />
<br />
==== For funding travel ====<br />
<br />
If you're asking for funds to cover a trip, use this set of questions.<br />
<br />
# '''Where are you going''' (location and event)?<br />
# '''What do you need covered?''' (Please estimate the costs in USD: hotel $X, travel $Y)<br />
# '''If we cannot provide a full subsidy, will a partial subsidy be helpful?''' (Yes/No)<br />
## If Yes can you specify the minimum amount you would need covered to facilitate your attendance<br />
# If you are requesting airfare, include complete flight information such as flight numbers, desired departure and arrival airports, and times. Also let us know if you have specific time restrictions.<br />
# '''Do you need a visa or other official processing before you can travel?''' If so, approximately how long does that processing take?<br />
# '''What will you accomplish by going on this trip?''' Please be as specific as possible, since this is the most important factor in granting requests.<br />
<br />
The last question really is the most important, and will likely be the longest part of your answer. Tell us what you're going to accomplish by taking this trip. Preference is given to people who are attending an event with a goal to make Sugar Labs better, and a plan for doing it.<br />
<br />
Simply "meeting with people" or "talking about ways to do something" are not specific to Sugar Labs. Ideas can be discussed on mailing lists, after all. And although meeting face to face is a wonderful thing, that doesn't necessarily result in getting anything done.<br />
<br />
* Not specific: Meet with other people from JKL Group.<br />
* Not specific: Improve communication between Team X and Team Y.<br />
* Specific: Write a working module for Web App Q that creates a service queue for Team X to do Task Z more efficiently.<br />
* Specific: Agree on and publish a complete plan, schedule, and milestones for Project W. <br />
<br />
==== For purchasing things ====<br />
<br />
Use this template if you're requesting the purchase of equipment, a subscription, etc. <br />
<br />
# '''What is being purchased?''' If it's a product, link to the product; if it's (If it's a produ to product, etc.)<br />
# '''Why does this purchase benefit the operations of Sugar Labs?''' What is the blocker it resolves? <br />
# '''Who will be responsible for the item?''' Who will own it? How will it be tracked/maintained? <br />
# '''How much will it cost?''' Are there any maintenance costs associated with the purchase? How often will it have to be renewed (if at all)?<br />
# '''What other options were evaluated for purchase?''' Why did the chosen product/service/option get selected as the best one? What were the criteria or features you needed?<br />
# '''What deadlines are associated with this request?''' Do you need an answer by a certain date? Would the funding need to come by a particular point in time? Note that approving future spending is a separate action from actually spending the money - for instance, we may agree to fund something but pay for it 3 months down the line - so it's good to know both dates, if they exist.<br />
# '''Other notes?'''<br />
<br />
=== How decisions are made ===<br />
<br />
This section explains the criteria typically used to decide whether to subsidize the travel of a specific applicant. It's provided for context only - if you're requesting funding, you don't actually have to read this stuff!<br />
<br />
==== Relevance ====<br />
<br />
* ''Does this purchase/event deliver information that is pertinent to an ongoing project of concern at the event?'' For example, an event that includes a critical brainstorming session on deployment outreac could be more effective with the attendance of a teacher or engineer from a deployment.<br />
* ''Does the purchase/event provide an opportunity for this particular person to attract contribution to one or more areas in Sugar Labs?'' An event that attracts computer-based designers, for instance, might present an opportunity for a member of the Design team to attract new, skilled contributors.<br />
* ''Is the requesting person a current contributor?'' Current contributors with a proven history of involvement in some sense are a known quantity. This does not mean that sponsorship shouldn't go to new or potential contributors, but it is a factor for consideration.<br />
<br />
==== Criticality ====<br />
<br />
* (For travel only) ''Does this person have demonstrated skills in an area that will promote reaching the goals of the event?'' For example, if Sugar's speaking schedule at an event requires someone with expertise on packaging Activities for various Linux distributions, it would make sense to sponsor the travel of someone who could give those talks.<br />
* ''Are there clear deliverables attached to this purchase/event that otherwise cannot be achieved?'' Deliverables come in many forms, such as working code; completed documentation; or key decisions. For purchases, will the absence of the purchase block or negatively impact work that is already being done on the project? For events, if other contributors involved in the same area are expected to attend already, will this person's absence negatively impact their work at the event?<br />
* ''How important is this subsidy to the purchase/event?'' Without the full subsidy, will the item not be able to be purchased, or will the applicant not be able to attend the event at all? Will a partial subsidy suffice? Would a change in plans, such as attending part of the event, or getting a less full-featured item, still allow this person's goals to be achieved? Is Sugar Labs funding the ''only'' option available for this purchase?<br />
<br />
==== Specificity ====<br />
<br />
* ''Has this person provided substantial information about the specific objectives to achieve?'' We look at the proposal critically, because there are usually more requests than we can fill. The best requests tend to reflect clear vision from the applicants of exactly what they will achieve through this funding, and a link between that vision and the larger objectives of Sugar Labs or a specific team.<br />
* ''Are the objectives achievable within the time frame of the event/project?'' Sometimes it may not be possible to meet every objective despite best intentions and hard work. Nevertheless, sponsors should also carefully consider whether the deliverables can reasonably be finished by the end of the relevant time period. Setting and meeting reasonable expectations is a good habit for any project.<br />
<br />
==== Proximity ====<br />
<br />
* (For event travel only) ''Is this person located in the same region as the event?'' Regionally co-located people generally require less funding. It is not cost effective, for instance, to fund the travel of multiple people from North America to a European event. In specific cases there may be call for such subsidies, but in general regional events should reflect regional attendance and participation.<br />
<br />
==== Expense ====<br />
<br />
* ''How expensive is the request?'' A higher subsidy amount should carry with it higher expectations, more criticality, or other benefits that justify the expense. Keep in mind that the transparent approval process creates better accountability for sponsors in making decisions.<br />
<br />
''This system is based on the [https://fedorahosted.org/fudcon-planning/wiki/FundingRequest Fedora community funding request system].''</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Finance&diff=65037Finance2011-04-21T23:04:41Z<p>Mchua: /* How to fill out a request */</p>
<hr />
<div>This page should answer two questions:<br />
<br />
* How much money does Sugar Labs currently have, where did it come from, and what is it being used for?<br />
* How can I ask for some of it?<br />
<br />
(We hope you'll also help us figure out how to get more resources as well!)<br />
<br />
The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.<br />
<br />
== Current finances ==<br />
<br />
All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.<br />
<br />
* The last known balance is from [[#January 2011]] and is $19,591.09 USD, held as follows:<br />
** $19,591.09 USD in a Vanguard Money Market account held by the Software Freedom Conservancy on behalf of Sugar Labs<br />
<br />
* The $19,591.09 USD is earmarked as follows:<br />
** ?? for Gould Grant<br />
** ?? unrestricted (available for future grants)<br />
<br />
''[[User:Walter|Walter Bender]] should be filling in the details above shortly.'' [[User:Mchua|Mchua]] 17:54, 21 April 2011 (EDT)<br />
<br />
== Where we get money from ==<br />
<br />
Sugar Labs doesn't have much in the way of regular income, so we can't predict when new funding will come in. We've gotten funding from a few sources in the past:<br />
<br />
* Donations from private individuals (thank you!)<br />
* Grant money to develop certain aspects of Sugar Labs - this is typically earmarked for a specific project<br />
* Google Summer of Code - Sugar Labs gets $500 of unrestricted funds for each student mentored.<br />
<br />
In particular, if you're interested in applying for an external grant to work on some aspect of Sugar Labs, let us know; we'd be happy to help.<br />
<br />
== Archive of transactions ==<br />
<br />
=== April 2011 ===<br />
<br />
Not known.<br />
<br />
=== March 2011 ===<br />
<br />
Not known.<br />
<br />
=== February 2011 ===<br />
<br />
Not known.<br />
<br />
=== January 2011 ===<br />
<br />
'''End-of-month balance:''' $19,591.09<br />
<br />
'''Net change since last month:''' -$1,679.08<br />
<br />
'''Transactions:'''<br />
<br />
{|border="1" cellspacing="0" width="100%" align="right"<br />
! Item<br />
! From/To<br />
! Income<br />
! Expenses<br />
! Notes<br />
|-<br />
| Gould Grant student developer salary<br />
| Gould Grant student employee<br />
| <br />
| -$1,680.00<br />
| Not sure if we want to put names here, so I left that information out. [[User:Mchua|Mchua]]<br />
|-<br />
| Interest from Vanguard account<br />
| Vanguard<br />
| $0.92<br />
|<br />
|<br />
|-<br />
!<br />
! Total<br />
! $0.92<br />
! -$1,680.00<br />
!<br />
|}<br />
<br />
== Requesting budget ==<br />
<br />
You may request budget for Sugar Labs related travel or project expenses. We can't fully fund every request, because we do operate on a limited budget. But we can't fund yours if we don't know you have a need -- so if you do, fill out a request and we'll get in touch with you about it.<br />
<br />
=== How to fill out a request ===<br />
<br />
A request can be filled out in 10 minutes or less. We're trying to make this process as easy as possible! <br />
<br />
# Open a [http://bugs.sugarlabs.org/newticket new ticket] in the Sugar Labs tracker. (You'll have to log into the tracker to do this.)<br />
# Set the component to "funding." '''This is important. If the component is not set correctly, we will not see your ticket when we search for it!'''<br />
# Answer the [[#What we need to know]] questions in the description field of your ticket.<br />
# Once the ticket has been filed, Send an email to [http://lists.sugarlabs.org/listinfo/iaep iaep] (for transparency) and [http://lists.sugarlabs.org/listinfo/slobs slobs] (as the decision-making body) with the subject line "New Finance Request: <short summary of the item requested>," where <short summary of the item requested> is replaced by... well, a short summary of what you're asking for money for, and a link to the ticket in the body of your email. '''This is important. If you do not email both lists, nobody will know you've submitted a budget request!'''<br />
<br />
At this point, you should wait to hear back from SLOBs. If nobody's responded to your request within a week, feel free to ping both mailing lists again.<br />
<br />
=== What we need to know ===<br />
<br />
Each request ticket must contain answers to one of the following sets of questions, depending on the type of funding you're asking for.<br />
<br />
==== For funding travel ====<br />
<br />
If you're asking for funds to cover a trip, use this set of questions.<br />
<br />
# '''Where are you going''' (location and event)?<br />
# '''What do you need covered?''' (Please estimate the costs in USD: hotel $X, travel $Y)<br />
# '''If we cannot provide a full subsidy, will a partial subsidy be helpful?''' (Yes/No)<br />
## If Yes can you specify the minimum amount you would need covered to facilitate your attendance<br />
# If you are requesting airfare, include complete flight information such as flight numbers, desired departure and arrival airports, and times. Also let us know if you have specific time restrictions.<br />
# '''Do you need a visa or other official processing before you can travel?''' If so, approximately how long does that processing take?<br />
# '''What will you accomplish by going on this trip?''' Please be as specific as possible, since this is the most important factor in granting requests.<br />
<br />
The last question really is the most important, and will likely be the longest part of your answer. Tell us what you're going to accomplish by taking this trip. Preference is given to people who are attending an event with a goal to make Sugar Labs better, and a plan for doing it.<br />
<br />
Simply "meeting with people" or "talking about ways to do something" are not specific to Sugar Labs. Ideas can be discussed on mailing lists, after all. And although meeting face to face is a wonderful thing, that doesn't necessarily result in getting anything done.<br />
<br />
* Not specific: Meet with other people from JKL Group.<br />
* Not specific: Improve communication between Team X and Team Y.<br />
* Specific: Write a working module for Web App Q that creates a service queue for Team X to do Task Z more efficiently.<br />
* Specific: Agree on and publish a complete plan, schedule, and milestones for Project W. <br />
<br />
==== For purchasing things ====<br />
<br />
Use this template if you're requesting the purchase of equipment, a subscription, etc. <br />
<br />
# '''What is being purchased?''' If it's a product, link to the product; if it's (If it's a produ to product, etc.)<br />
# '''Why does this purchase benefit the operations of Sugar Labs?''' What is the blocker it resolves? <br />
# '''Who will be responsible for the item?''' Who will own it? How will it be tracked/maintained? <br />
# '''How much will it cost?''' Are there any maintenance costs associated with the purchase? How often will it have to be renewed (if at all)?<br />
# '''What other options were evaluated for purchase?''' Why did the chosen product/service/option get selected as the best one? What were the criteria or features you needed?<br />
# '''What deadlines are associated with this request?''' Do you need an answer by a certain date? Would the funding need to come by a particular point in time? Note that approving future spending is a separate action from actually spending the money - for instance, we may agree to fund something but pay for it 3 months down the line - so it's good to know both dates, if they exist.<br />
# '''Other notes?'''<br />
<br />
=== How decisions are made ===<br />
<br />
This section explains the criteria typically used to decide whether to subsidize the travel of a specific applicant. It's provided for context only - if you're requesting funding, you don't actually have to read this stuff!<br />
<br />
==== Relevance ====<br />
<br />
* ''Does this purchase/event deliver information that is pertinent to an ongoing project of concern at the event?'' For example, an event that includes a critical brainstorming session on deployment outreac could be more effective with the attendance of a teacher or engineer from a deployment.<br />
* ''Does the purchase/event provide an opportunity for this particular person to attract contribution to one or more areas in Sugar Labs?'' An event that attracts computer-based designers, for instance, might present an opportunity for a member of the Design team to attract new, skilled contributors.<br />
* ''Is the requesting person a current contributor?'' Current contributors with a proven history of involvement in some sense are a known quantity. This does not mean that sponsorship shouldn't go to new or potential contributors, but it is a factor for consideration.<br />
<br />
==== Criticality ====<br />
<br />
* (For travel only) ''Does this person have demonstrated skills in an area that will promote reaching the goals of the event?'' For example, if Sugar's speaking schedule at an event requires someone with expertise on packaging Activities for various Linux distributions, it would make sense to sponsor the travel of someone who could give those talks.<br />
* ''Are there clear deliverables attached to this purchase/event that otherwise cannot be achieved?'' Deliverables come in many forms, such as working code; completed documentation; or key decisions. For purchases, will the absence of the purchase block or negatively impact work that is already being done on the project? For events, if other contributors involved in the same area are expected to attend already, will this person's absence negatively impact their work at the event?<br />
* ''How important is this subsidy to the purchase/event?'' Without the full subsidy, will the item not be able to be purchased, or will the applicant not be able to attend the event at all? Will a partial subsidy suffice? Would a change in plans, such as attending part of the event, or getting a less full-featured item, still allow this person's goals to be achieved? Is Sugar Labs funding the ''only'' option available for this purchase?<br />
<br />
==== Specificity ====<br />
<br />
* ''Has this person provided substantial information about the specific objectives to achieve?'' We look at the proposal critically, because there are usually more requests than we can fill. The best requests tend to reflect clear vision from the applicants of exactly what they will achieve through this funding, and a link between that vision and the larger objectives of Sugar Labs or a specific team.<br />
* ''Are the objectives achievable within the time frame of the event/project?'' Sometimes it may not be possible to meet every objective despite best intentions and hard work. Nevertheless, sponsors should also carefully consider whether the deliverables can reasonably be finished by the end of the relevant time period. Setting and meeting reasonable expectations is a good habit for any project.<br />
<br />
==== Proximity ====<br />
<br />
* (For event travel only) ''Is this person located in the same region as the event?'' Regionally co-located people generally require less funding. It is not cost effective, for instance, to fund the travel of multiple people from North America to a European event. In specific cases there may be call for such subsidies, but in general regional events should reflect regional attendance and participation.<br />
<br />
==== Expense ====<br />
<br />
* ''How expensive is the request?'' A higher subsidy amount should carry with it higher expectations, more criticality, or other benefits that justify the expense. Keep in mind that the transparent approval process creates better accountability for sponsors in making decisions.<br />
<br />
''This system is based on the [https://fedorahosted.org/fudcon-planning/wiki/FundingRequest Fedora community funding request system].''</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Finance&diff=65036Finance2011-04-21T22:42:47Z<p>Mchua: </p>
<hr />
<div>This page should answer two questions:<br />
<br />
* How much money does Sugar Labs currently have, where did it come from, and what is it being used for?<br />
* How can I ask for some of it?<br />
<br />
(We hope you'll also help us figure out how to get more resources as well!)<br />
<br />
The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.<br />
<br />
== Current finances ==<br />
<br />
All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.<br />
<br />
* The last known balance is from [[#January 2011]] and is $19,591.09 USD, held as follows:<br />
** $19,591.09 USD in a Vanguard Money Market account held by the Software Freedom Conservancy on behalf of Sugar Labs<br />
<br />
* The $19,591.09 USD is earmarked as follows:<br />
** ?? for Gould Grant<br />
** ?? unrestricted (available for future grants)<br />
<br />
''[[User:Walter|Walter Bender]] should be filling in the details above shortly.'' [[User:Mchua|Mchua]] 17:54, 21 April 2011 (EDT)<br />
<br />
== Where we get money from ==<br />
<br />
Sugar Labs doesn't have much in the way of regular income, so we can't predict when new funding will come in. We've gotten funding from a few sources in the past:<br />
<br />
* Donations from private individuals (thank you!)<br />
* Grant money to develop certain aspects of Sugar Labs - this is typically earmarked for a specific project<br />
* Google Summer of Code - Sugar Labs gets $500 of unrestricted funds for each student mentored.<br />
<br />
In particular, if you're interested in applying for an external grant to work on some aspect of Sugar Labs, let us know; we'd be happy to help.<br />
<br />
== Archive of transactions ==<br />
<br />
=== April 2011 ===<br />
<br />
Not known.<br />
<br />
=== March 2011 ===<br />
<br />
Not known.<br />
<br />
=== February 2011 ===<br />
<br />
Not known.<br />
<br />
=== January 2011 ===<br />
<br />
'''End-of-month balance:''' $19,591.09<br />
<br />
'''Net change since last month:''' -$1,679.08<br />
<br />
'''Transactions:'''<br />
<br />
{|border="1" cellspacing="0" width="100%" align="right"<br />
! Item<br />
! From/To<br />
! Income<br />
! Expenses<br />
! Notes<br />
|-<br />
| Gould Grant student developer salary<br />
| Gould Grant student employee<br />
| <br />
| -$1,680.00<br />
| Not sure if we want to put names here, so I left that information out. [[User:Mchua|Mchua]]<br />
|-<br />
| Interest from Vanguard account<br />
| Vanguard<br />
| $0.92<br />
|<br />
|<br />
|-<br />
!<br />
! Total<br />
! $0.92<br />
! -$1,680.00<br />
!<br />
|}<br />
<br />
== Requesting budget ==<br />
<br />
You may request budget for Sugar Labs related travel or project expenses. We can't fully fund every request, because we do operate on a limited budget. But we can't fund yours if we don't know you have a need -- so if you do, fill out a request and we'll get in touch with you about it.<br />
<br />
=== How to fill out a request ===<br />
<br />
A request can be filled out in 10 minutes or less. We're trying to make this process as easy as possible! <br />
<br />
# Open a [http://bugs.sugarlabs.org/newticket new ticket] in the Sugar Labs tracker. (You'll have to log into the tracker to do this.)<br />
# Set the component to "finance." '''This is important. If the component is not set correctly, we will not see your ticket when we search for it!''' ''Note: the "finance" component has not been created as of this writing, so you can skip it for now. [[User:Mchua|Mchua]] 18:30, 21 April 2011 (EDT)''<br />
# Answer the [[#What we need to know]] questions in the description field of your ticket.<br />
# Once the ticket has been filed, Send an email to [http://lists.sugarlabs.org/listinfo/iaep iaep] (for transparency) and [http://lists.sugarlabs.org/listinfo/slobs slobs] (as the decision-making body) with the subject line "New Finance Request: <short summary of the item requested>," where <short summary of the item requested> is replaced by... well, a short summary of what you're asking for money for, and a link to the ticket in the body of your email. '''This is important. If you do not email both lists, nobody will know you've submitted a budget request!'''<br />
<br />
At this point, you should wait to hear back from SLOBs. If nobody's responded to your request within a week, feel free to ping both mailing lists again.<br />
<br />
=== What we need to know ===<br />
<br />
Each request ticket must contain answers to one of the following sets of questions, depending on the type of funding you're asking for.<br />
<br />
==== For funding travel ====<br />
<br />
If you're asking for funds to cover a trip, use this set of questions.<br />
<br />
# '''Where are you going''' (location and event)?<br />
# '''What do you need covered?''' (Please estimate the costs in USD: hotel $X, travel $Y)<br />
# '''If we cannot provide a full subsidy, will a partial subsidy be helpful?''' (Yes/No)<br />
## If Yes can you specify the minimum amount you would need covered to facilitate your attendance<br />
# If you are requesting airfare, include complete flight information such as flight numbers, desired departure and arrival airports, and times. Also let us know if you have specific time restrictions.<br />
# '''Do you need a visa or other official processing before you can travel?''' If so, approximately how long does that processing take?<br />
# '''What will you accomplish by going on this trip?''' Please be as specific as possible, since this is the most important factor in granting requests.<br />
<br />
The last question really is the most important, and will likely be the longest part of your answer. Tell us what you're going to accomplish by taking this trip. Preference is given to people who are attending an event with a goal to make Sugar Labs better, and a plan for doing it.<br />
<br />
Simply "meeting with people" or "talking about ways to do something" are not specific to Sugar Labs. Ideas can be discussed on mailing lists, after all. And although meeting face to face is a wonderful thing, that doesn't necessarily result in getting anything done.<br />
<br />
* Not specific: Meet with other people from JKL Group.<br />
* Not specific: Improve communication between Team X and Team Y.<br />
* Specific: Write a working module for Web App Q that creates a service queue for Team X to do Task Z more efficiently.<br />
* Specific: Agree on and publish a complete plan, schedule, and milestones for Project W. <br />
<br />
==== For purchasing things ====<br />
<br />
Use this template if you're requesting the purchase of equipment, a subscription, etc. <br />
<br />
# '''What is being purchased?''' If it's a product, link to the product; if it's (If it's a produ to product, etc.)<br />
# '''Why does this purchase benefit the operations of Sugar Labs?''' What is the blocker it resolves? <br />
# '''Who will be responsible for the item?''' Who will own it? How will it be tracked/maintained? <br />
# '''How much will it cost?''' Are there any maintenance costs associated with the purchase? How often will it have to be renewed (if at all)?<br />
# '''What other options were evaluated for purchase?''' Why did the chosen product/service/option get selected as the best one? What were the criteria or features you needed?<br />
# '''What deadlines are associated with this request?''' Do you need an answer by a certain date? Would the funding need to come by a particular point in time? Note that approving future spending is a separate action from actually spending the money - for instance, we may agree to fund something but pay for it 3 months down the line - so it's good to know both dates, if they exist.<br />
# '''Other notes?'''<br />
<br />
=== How decisions are made ===<br />
<br />
This section explains the criteria typically used to decide whether to subsidize the travel of a specific applicant. It's provided for context only - if you're requesting funding, you don't actually have to read this stuff!<br />
<br />
==== Relevance ====<br />
<br />
* ''Does this purchase/event deliver information that is pertinent to an ongoing project of concern at the event?'' For example, an event that includes a critical brainstorming session on deployment outreac could be more effective with the attendance of a teacher or engineer from a deployment.<br />
* ''Does the purchase/event provide an opportunity for this particular person to attract contribution to one or more areas in Sugar Labs?'' An event that attracts computer-based designers, for instance, might present an opportunity for a member of the Design team to attract new, skilled contributors.<br />
* ''Is the requesting person a current contributor?'' Current contributors with a proven history of involvement in some sense are a known quantity. This does not mean that sponsorship shouldn't go to new or potential contributors, but it is a factor for consideration.<br />
<br />
==== Criticality ====<br />
<br />
* (For travel only) ''Does this person have demonstrated skills in an area that will promote reaching the goals of the event?'' For example, if Sugar's speaking schedule at an event requires someone with expertise on packaging Activities for various Linux distributions, it would make sense to sponsor the travel of someone who could give those talks.<br />
* ''Are there clear deliverables attached to this purchase/event that otherwise cannot be achieved?'' Deliverables come in many forms, such as working code; completed documentation; or key decisions. For purchases, will the absence of the purchase block or negatively impact work that is already being done on the project? For events, if other contributors involved in the same area are expected to attend already, will this person's absence negatively impact their work at the event?<br />
* ''How important is this subsidy to the purchase/event?'' Without the full subsidy, will the item not be able to be purchased, or will the applicant not be able to attend the event at all? Will a partial subsidy suffice? Would a change in plans, such as attending part of the event, or getting a less full-featured item, still allow this person's goals to be achieved? Is Sugar Labs funding the ''only'' option available for this purchase?<br />
<br />
==== Specificity ====<br />
<br />
* ''Has this person provided substantial information about the specific objectives to achieve?'' We look at the proposal critically, because there are usually more requests than we can fill. The best requests tend to reflect clear vision from the applicants of exactly what they will achieve through this funding, and a link between that vision and the larger objectives of Sugar Labs or a specific team.<br />
* ''Are the objectives achievable within the time frame of the event/project?'' Sometimes it may not be possible to meet every objective despite best intentions and hard work. Nevertheless, sponsors should also carefully consider whether the deliverables can reasonably be finished by the end of the relevant time period. Setting and meeting reasonable expectations is a good habit for any project.<br />
<br />
==== Proximity ====<br />
<br />
* (For event travel only) ''Is this person located in the same region as the event?'' Regionally co-located people generally require less funding. It is not cost effective, for instance, to fund the travel of multiple people from North America to a European event. In specific cases there may be call for such subsidies, but in general regional events should reflect regional attendance and participation.<br />
<br />
==== Expense ====<br />
<br />
* ''How expensive is the request?'' A higher subsidy amount should carry with it higher expectations, more criticality, or other benefits that justify the expense. Keep in mind that the transparent approval process creates better accountability for sponsors in making decisions.<br />
<br />
''This system is based on the [https://fedorahosted.org/fudcon-planning/wiki/FundingRequest Fedora community funding request system].''</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Finance&diff=65035Finance2011-04-21T22:38:13Z<p>Mchua: /* Current finances */</p>
<hr />
<div>The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.<br />
<br />
== Current finances ==<br />
<br />
All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.<br />
<br />
* The last known balance is from [[#January 2011]] and is $19,591.09 USD, held as follows:<br />
** $19,591.09 USD in a Vanguard Money Market account held by the Software Freedom Conservancy on behalf of Sugar Labs<br />
<br />
* The $19,591.09 USD is earmarked as follows:<br />
** ?? for Gould Grant<br />
** ?? unrestricted (available for future grants)<br />
<br />
''[[User:Walter|Walter Bender]] should be filling in the details above shortly.'' [[User:Mchua|Mchua]] 17:54, 21 April 2011 (EDT)<br />
<br />
== Where we get money from ==<br />
<br />
Sugar Labs doesn't have much in the way of regular income, so we can't predict when new funding will come in. We've gotten funding from a few sources in the past:<br />
<br />
* Donations from private individuals (thank you!)<br />
* Grant money to develop certain aspects of Sugar Labs - this is typically earmarked for a specific project<br />
* Google Summer of Code - Sugar Labs gets $500 of unrestricted funds for each student mentored.<br />
<br />
In particular, if you're interested in applying for an external grant to work on some aspect of Sugar Labs, let us know; we'd be happy to help.<br />
<br />
== Archive of transactions ==<br />
<br />
=== April 2011 ===<br />
<br />
Not known.<br />
<br />
=== March 2011 ===<br />
<br />
Not known.<br />
<br />
=== February 2011 ===<br />
<br />
Not known.<br />
<br />
=== January 2011 ===<br />
<br />
'''End-of-month balance:''' $19,591.09<br />
<br />
'''Net change since last month:''' -$1,679.08<br />
<br />
'''Transactions:'''<br />
<br />
{|border="1" cellspacing="0" width="100%" align="right"<br />
! Item<br />
! From/To<br />
! Income<br />
! Expenses<br />
! Notes<br />
|-<br />
| Gould Grant student developer salary<br />
| Gould Grant student employee<br />
| <br />
| -$1,680.00<br />
| Not sure if we want to put names here, so I left that information out. [[User:Mchua|Mchua]]<br />
|-<br />
| Interest from Vanguard account<br />
| Vanguard<br />
| $0.92<br />
|<br />
|<br />
|-<br />
!<br />
! Total<br />
! $0.92<br />
! -$1,680.00<br />
!<br />
|}<br />
<br />
== Requesting budget ==<br />
<br />
You may request budget for Sugar Labs related travel or project expenses. We can't fully fund every request, because we do operate on a limited budget. But we can't fund yours if we don't know you have a need -- so if you do, fill out a request and we'll get in touch with you about it.<br />
<br />
=== How to fill out a request ===<br />
<br />
A request can be filled out in 10 minutes or less. We're trying to make this process as easy as possible! <br />
<br />
# Open a [http://bugs.sugarlabs.org/newticket new ticket] in the Sugar Labs tracker. (You'll have to log into the tracker to do this.)<br />
# Set the component to "finance." '''This is important. If the component is not set correctly, we will not see your ticket when we search for it!''' ''Note: the "finance" component has not been created as of this writing, so you can skip it for now. [[User:Mchua|Mchua]] 18:30, 21 April 2011 (EDT)''<br />
# Answer the [[#What we need to know]] questions in the description field of your ticket.<br />
# Once the ticket has been filed, Send an email to [http://lists.sugarlabs.org/listinfo/iaep iaep] (for transparency) and [http://lists.sugarlabs.org/listinfo/slobs slobs] (as the decision-making body) with the subject line "New Finance Request: <short summary of the item requested>," where <short summary of the item requested> is replaced by... well, a short summary of what you're asking for money for, and a link to the ticket in the body of your email. '''This is important. If you do not email both lists, nobody will know you've submitted a budget request!'''<br />
<br />
At this point, you should wait to hear back from SLOBs. If nobody's responded to your request within a week, feel free to ping both mailing lists again.<br />
<br />
=== What we need to know ===<br />
<br />
Each request ticket must contain answers to one of the following sets of questions, depending on the type of funding you're asking for.<br />
<br />
==== For funding travel ====<br />
<br />
If you're asking for funds to cover a trip, use this set of questions.<br />
<br />
# '''Where are you going''' (location and event)?<br />
# '''What do you need covered?''' (Please estimate the costs in USD: hotel $X, travel $Y)<br />
# '''If we cannot provide a full subsidy, will a partial subsidy be helpful?''' (Yes/No)<br />
## If Yes can you specify the minimum amount you would need covered to facilitate your attendance<br />
# If you are requesting airfare, include complete flight information such as flight numbers, desired departure and arrival airports, and times. Also let us know if you have specific time restrictions.<br />
# '''Do you need a visa or other official processing before you can travel?''' If so, approximately how long does that processing take?<br />
# '''What will you accomplish by going on this trip?''' Please be as specific as possible, since this is the most important factor in granting requests.<br />
<br />
The last question really is the most important, and will likely be the longest part of your answer. Tell us what you're going to accomplish by taking this trip. Preference is given to people who are attending an event with a goal to make Sugar Labs better, and a plan for doing it.<br />
<br />
Simply "meeting with people" or "talking about ways to do something" are not specific to Sugar Labs. Ideas can be discussed on mailing lists, after all. And although meeting face to face is a wonderful thing, that doesn't necessarily result in getting anything done.<br />
<br />
* Not specific: Meet with other people from JKL Group.<br />
* Not specific: Improve communication between Team X and Team Y.<br />
* Specific: Write a working module for Web App Q that creates a service queue for Team X to do Task Z more efficiently.<br />
* Specific: Agree on and publish a complete plan, schedule, and milestones for Project W. <br />
<br />
==== For purchasing things ====<br />
<br />
Use this template if you're requesting the purchase of equipment, a subscription, etc. <br />
<br />
# '''What is being purchased?''' If it's a product, link to the product; if it's (If it's a produ to product, etc.)<br />
# '''Why does this purchase benefit the operations of Sugar Labs?''' What is the blocker it resolves? <br />
# '''Who will be responsible for the item?''' Who will own it? How will it be tracked/maintained? <br />
# '''How much will it cost?''' Are there any maintenance costs associated with the purchase? How often will it have to be renewed (if at all)?<br />
# '''What other options were evaluated for purchase?''' Why did the chosen product/service/option get selected as the best one? What were the criteria or features you needed?<br />
# '''What deadlines are associated with this request?''' Do you need an answer by a certain date? Would the funding need to come by a particular point in time? Note that approving future spending is a separate action from actually spending the money - for instance, we may agree to fund something but pay for it 3 months down the line - so it's good to know both dates, if they exist.<br />
# '''Other notes?'''<br />
<br />
=== How decisions are made ===<br />
<br />
This section explains the criteria typically used to decide whether to subsidize the travel of a specific applicant. It's provided for context only - if you're requesting funding, you don't actually have to read this stuff!<br />
<br />
==== Relevance ====<br />
<br />
* ''Does this purchase/event deliver information that is pertinent to an ongoing project of concern at the event?'' For example, an event that includes a critical brainstorming session on deployment outreac could be more effective with the attendance of a teacher or engineer from a deployment.<br />
* ''Does the purchase/event provide an opportunity for this particular person to attract contribution to one or more areas in Sugar Labs?'' An event that attracts computer-based designers, for instance, might present an opportunity for a member of the Design team to attract new, skilled contributors.<br />
* ''Is the requesting person a current contributor?'' Current contributors with a proven history of involvement in some sense are a known quantity. This does not mean that sponsorship shouldn't go to new or potential contributors, but it is a factor for consideration.<br />
<br />
==== Criticality ====<br />
<br />
* (For travel only) ''Does this person have demonstrated skills in an area that will promote reaching the goals of the event?'' For example, if Sugar's speaking schedule at an event requires someone with expertise on packaging Activities for various Linux distributions, it would make sense to sponsor the travel of someone who could give those talks.<br />
* ''Are there clear deliverables attached to this purchase/event that otherwise cannot be achieved?'' Deliverables come in many forms, such as working code; completed documentation; or key decisions. For purchases, will the absence of the purchase block or negatively impact work that is already being done on the project? For events, if other contributors involved in the same area are expected to attend already, will this person's absence negatively impact their work at the event?<br />
* ''How important is this subsidy to the purchase/event?'' Without the full subsidy, will the item not be able to be purchased, or will the applicant not be able to attend the event at all? Will a partial subsidy suffice? Would a change in plans, such as attending part of the event, or getting a less full-featured item, still allow this person's goals to be achieved? Is Sugar Labs funding the ''only'' option available for this purchase?<br />
<br />
==== Specificity ====<br />
<br />
* ''Has this person provided substantial information about the specific objectives to achieve?'' We look at the proposal critically, because there are usually more requests than we can fill. The best requests tend to reflect clear vision from the applicants of exactly what they will achieve through this funding, and a link between that vision and the larger objectives of Sugar Labs or a specific team.<br />
* ''Are the objectives achievable within the time frame of the event/project?'' Sometimes it may not be possible to meet every objective despite best intentions and hard work. Nevertheless, sponsors should also carefully consider whether the deliverables can reasonably be finished by the end of the relevant time period. Setting and meeting reasonable expectations is a good habit for any project.<br />
<br />
==== Proximity ====<br />
<br />
* (For event travel only) ''Is this person located in the same region as the event?'' Regionally co-located people generally require less funding. It is not cost effective, for instance, to fund the travel of multiple people from North America to a European event. In specific cases there may be call for such subsidies, but in general regional events should reflect regional attendance and participation.<br />
<br />
==== Expense ====<br />
<br />
* ''How expensive is the request?'' A higher subsidy amount should carry with it higher expectations, more criticality, or other benefits that justify the expense. Keep in mind that the transparent approval process creates better accountability for sponsors in making decisions.<br />
<br />
''This system is based on the [https://fedorahosted.org/fudcon-planning/wiki/FundingRequest Fedora community funding request system].''</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Finance&diff=65034Finance2011-04-21T22:35:45Z<p>Mchua: /* How to fill out a request */</p>
<hr />
<div>The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.<br />
<br />
== Current finances ==<br />
<br />
All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.<br />
<br />
* The last known balance is from [[#January 2011]] and is $19,591.09 USD, held as follows:<br />
** $19,591.09 USD in a Vanguard Money Market account held by the Software Freedom Conservancy on behalf of Sugar Labs<br />
<br />
* The $19,591.09 USD is earmarked as follows:<br />
** ?? for Gould Grant<br />
** ?? for Google Summer of Code<br />
** ?? unrestricted (available for future grants)<br />
<br />
''[[User:Walter|Walter Bender]] should be filling in the details above shortly.'' [[User:Mchua|Mchua]] 17:54, 21 April 2011 (EDT)<br />
<br />
== Archive of transactions ==<br />
<br />
=== April 2011 ===<br />
<br />
Not known.<br />
<br />
=== March 2011 ===<br />
<br />
Not known.<br />
<br />
=== February 2011 ===<br />
<br />
Not known.<br />
<br />
=== January 2011 ===<br />
<br />
'''End-of-month balance:''' $19,591.09<br />
<br />
'''Net change since last month:''' -$1,679.08<br />
<br />
'''Transactions:'''<br />
<br />
{|border="1" cellspacing="0" width="100%" align="right"<br />
! Item<br />
! From/To<br />
! Income<br />
! Expenses<br />
! Notes<br />
|-<br />
| Gould Grant student developer salary<br />
| Gould Grant student employee<br />
| <br />
| -$1,680.00<br />
| Not sure if we want to put names here, so I left that information out. [[User:Mchua|Mchua]]<br />
|-<br />
| Interest from Vanguard account<br />
| Vanguard<br />
| $0.92<br />
|<br />
|<br />
|-<br />
!<br />
! Total<br />
! $0.92<br />
! -$1,680.00<br />
!<br />
|}<br />
<br />
== Requesting budget ==<br />
<br />
You may request budget for Sugar Labs related travel or project expenses. We can't fully fund every request, because we do operate on a limited budget. But we can't fund yours if we don't know you have a need -- so if you do, fill out a request and we'll get in touch with you about it.<br />
<br />
=== How to fill out a request ===<br />
<br />
A request can be filled out in 10 minutes or less. We're trying to make this process as easy as possible! <br />
<br />
# Open a [http://bugs.sugarlabs.org/newticket new ticket] in the Sugar Labs tracker. (You'll have to log into the tracker to do this.)<br />
# Set the component to "finance." '''This is important. If the component is not set correctly, we will not see your ticket when we search for it!''' ''Note: the "finance" component has not been created as of this writing, so you can skip it for now. [[User:Mchua|Mchua]] 18:30, 21 April 2011 (EDT)''<br />
# Answer the [[#What we need to know]] questions in the description field of your ticket.<br />
# Once the ticket has been filed, Send an email to [http://lists.sugarlabs.org/listinfo/iaep iaep] (for transparency) and [http://lists.sugarlabs.org/listinfo/slobs slobs] (as the decision-making body) with the subject line "New Finance Request: <short summary of the item requested>," where <short summary of the item requested> is replaced by... well, a short summary of what you're asking for money for, and a link to the ticket in the body of your email. '''This is important. If you do not email both lists, nobody will know you've submitted a budget request!'''<br />
<br />
At this point, you should wait to hear back from SLOBs. If nobody's responded to your request within a week, feel free to ping both mailing lists again.<br />
<br />
=== What we need to know ===<br />
<br />
Each request ticket must contain answers to one of the following sets of questions, depending on the type of funding you're asking for.<br />
<br />
==== For funding travel ====<br />
<br />
If you're asking for funds to cover a trip, use this set of questions.<br />
<br />
# '''Where are you going''' (location and event)?<br />
# '''What do you need covered?''' (Please estimate the costs in USD: hotel $X, travel $Y)<br />
# '''If we cannot provide a full subsidy, will a partial subsidy be helpful?''' (Yes/No)<br />
## If Yes can you specify the minimum amount you would need covered to facilitate your attendance<br />
# If you are requesting airfare, include complete flight information such as flight numbers, desired departure and arrival airports, and times. Also let us know if you have specific time restrictions.<br />
# '''Do you need a visa or other official processing before you can travel?''' If so, approximately how long does that processing take?<br />
# '''What will you accomplish by going on this trip?''' Please be as specific as possible, since this is the most important factor in granting requests.<br />
<br />
The last question really is the most important, and will likely be the longest part of your answer. Tell us what you're going to accomplish by taking this trip. Preference is given to people who are attending an event with a goal to make Sugar Labs better, and a plan for doing it.<br />
<br />
Simply "meeting with people" or "talking about ways to do something" are not specific to Sugar Labs. Ideas can be discussed on mailing lists, after all. And although meeting face to face is a wonderful thing, that doesn't necessarily result in getting anything done.<br />
<br />
* Not specific: Meet with other people from JKL Group.<br />
* Not specific: Improve communication between Team X and Team Y.<br />
* Specific: Write a working module for Web App Q that creates a service queue for Team X to do Task Z more efficiently.<br />
* Specific: Agree on and publish a complete plan, schedule, and milestones for Project W. <br />
<br />
==== For purchasing things ====<br />
<br />
Use this template if you're requesting the purchase of equipment, a subscription, etc. <br />
<br />
# '''What is being purchased?''' If it's a product, link to the product; if it's (If it's a produ to product, etc.)<br />
# '''Why does this purchase benefit the operations of Sugar Labs?''' What is the blocker it resolves? <br />
# '''Who will be responsible for the item?''' Who will own it? How will it be tracked/maintained? <br />
# '''How much will it cost?''' Are there any maintenance costs associated with the purchase? How often will it have to be renewed (if at all)?<br />
# '''What other options were evaluated for purchase?''' Why did the chosen product/service/option get selected as the best one? What were the criteria or features you needed?<br />
# '''What deadlines are associated with this request?''' Do you need an answer by a certain date? Would the funding need to come by a particular point in time? Note that approving future spending is a separate action from actually spending the money - for instance, we may agree to fund something but pay for it 3 months down the line - so it's good to know both dates, if they exist.<br />
# '''Other notes?'''<br />
<br />
=== How decisions are made ===<br />
<br />
This section explains the criteria typically used to decide whether to subsidize the travel of a specific applicant. It's provided for context only - if you're requesting funding, you don't actually have to read this stuff!<br />
<br />
==== Relevance ====<br />
<br />
* ''Does this purchase/event deliver information that is pertinent to an ongoing project of concern at the event?'' For example, an event that includes a critical brainstorming session on deployment outreac could be more effective with the attendance of a teacher or engineer from a deployment.<br />
* ''Does the purchase/event provide an opportunity for this particular person to attract contribution to one or more areas in Sugar Labs?'' An event that attracts computer-based designers, for instance, might present an opportunity for a member of the Design team to attract new, skilled contributors.<br />
* ''Is the requesting person a current contributor?'' Current contributors with a proven history of involvement in some sense are a known quantity. This does not mean that sponsorship shouldn't go to new or potential contributors, but it is a factor for consideration.<br />
<br />
==== Criticality ====<br />
<br />
* (For travel only) ''Does this person have demonstrated skills in an area that will promote reaching the goals of the event?'' For example, if Sugar's speaking schedule at an event requires someone with expertise on packaging Activities for various Linux distributions, it would make sense to sponsor the travel of someone who could give those talks.<br />
* ''Are there clear deliverables attached to this purchase/event that otherwise cannot be achieved?'' Deliverables come in many forms, such as working code; completed documentation; or key decisions. For purchases, will the absence of the purchase block or negatively impact work that is already being done on the project? For events, if other contributors involved in the same area are expected to attend already, will this person's absence negatively impact their work at the event?<br />
* ''How important is this subsidy to the purchase/event?'' Without the full subsidy, will the item not be able to be purchased, or will the applicant not be able to attend the event at all? Will a partial subsidy suffice? Would a change in plans, such as attending part of the event, or getting a less full-featured item, still allow this person's goals to be achieved? Is Sugar Labs funding the ''only'' option available for this purchase?<br />
<br />
==== Specificity ====<br />
<br />
* ''Has this person provided substantial information about the specific objectives to achieve?'' We look at the proposal critically, because there are usually more requests than we can fill. The best requests tend to reflect clear vision from the applicants of exactly what they will achieve through this funding, and a link between that vision and the larger objectives of Sugar Labs or a specific team.<br />
* ''Are the objectives achievable within the time frame of the event/project?'' Sometimes it may not be possible to meet every objective despite best intentions and hard work. Nevertheless, sponsors should also carefully consider whether the deliverables can reasonably be finished by the end of the relevant time period. Setting and meeting reasonable expectations is a good habit for any project.<br />
<br />
==== Proximity ====<br />
<br />
* (For event travel only) ''Is this person located in the same region as the event?'' Regionally co-located people generally require less funding. It is not cost effective, for instance, to fund the travel of multiple people from North America to a European event. In specific cases there may be call for such subsidies, but in general regional events should reflect regional attendance and participation.<br />
<br />
==== Expense ====<br />
<br />
* ''How expensive is the request?'' A higher subsidy amount should carry with it higher expectations, more criticality, or other benefits that justify the expense. Keep in mind that the transparent approval process creates better accountability for sponsors in making decisions.<br />
<br />
''This system is based on the [https://fedorahosted.org/fudcon-planning/wiki/FundingRequest Fedora community funding request system].''</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Finance&diff=65033Finance2011-04-21T22:30:47Z<p>Mchua: /* Requesting budget */</p>
<hr />
<div>The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.<br />
<br />
== Current finances ==<br />
<br />
All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.<br />
<br />
* The last known balance is from [[#January 2011]] and is $19,591.09 USD, held as follows:<br />
** $19,591.09 USD in a Vanguard Money Market account held by the Software Freedom Conservancy on behalf of Sugar Labs<br />
<br />
* The $19,591.09 USD is earmarked as follows:<br />
** ?? for Gould Grant<br />
** ?? for Google Summer of Code<br />
** ?? unrestricted (available for future grants)<br />
<br />
''[[User:Walter|Walter Bender]] should be filling in the details above shortly.'' [[User:Mchua|Mchua]] 17:54, 21 April 2011 (EDT)<br />
<br />
== Archive of transactions ==<br />
<br />
=== April 2011 ===<br />
<br />
Not known.<br />
<br />
=== March 2011 ===<br />
<br />
Not known.<br />
<br />
=== February 2011 ===<br />
<br />
Not known.<br />
<br />
=== January 2011 ===<br />
<br />
'''End-of-month balance:''' $19,591.09<br />
<br />
'''Net change since last month:''' -$1,679.08<br />
<br />
'''Transactions:'''<br />
<br />
{|border="1" cellspacing="0" width="100%" align="right"<br />
! Item<br />
! From/To<br />
! Income<br />
! Expenses<br />
! Notes<br />
|-<br />
| Gould Grant student developer salary<br />
| Gould Grant student employee<br />
| <br />
| -$1,680.00<br />
| Not sure if we want to put names here, so I left that information out. [[User:Mchua|Mchua]]<br />
|-<br />
| Interest from Vanguard account<br />
| Vanguard<br />
| $0.92<br />
|<br />
|<br />
|-<br />
!<br />
! Total<br />
! $0.92<br />
! -$1,680.00<br />
!<br />
|}<br />
<br />
== Requesting budget ==<br />
<br />
You may request budget for Sugar Labs related travel or project expenses. We can't fully fund every request, because we do operate on a limited budget. But we can't fund yours if we don't know you have a need -- so if you do, fill out a request and we'll get in touch with you about it.<br />
<br />
=== How to fill out a request ===<br />
<br />
A request can be filled out in 10 minutes or less. We're trying to make this process as easy as possible! <br />
<br />
# Open a [http://bugs.sugarlabs.org/newticket new ticket] in the Sugar Labs tracker. (You'll have to log into the tracker to do this.)<br />
# Set the component to "finance." '''This is important. If the component is not set correctly, we will not see your ticket when we search for it!''' ''Note: the "finance" component has not been created as of this writing, so you can skip it for now. [[User:Mchua|Mchua]] 18:30, 21 April 2011 (EDT)''<br />
# Answer the [[#What we need to know]] questions in the description field of your ticket.<br />
# Once the ticket has been filed, Send an email to [http://lists.sugarlabs.org/listinfo/iaep iaep] (for transparency) and [http://lists.sugarlabs.org/listinfo/slobs slobs] (as the decision-making body) with the subject line "New Finance Request: <short summary of the item requested>," where <short summary of the item requested> is replaced by... well, a short summary of what you're asking for money for, and a link to the ticket in the body of your email. '''This is important. If you do not email both lists, nobody will know you've submitted a budget request!'''<br />
<br />
=== What we need to know ===<br />
<br />
Each request ticket must contain answers to one of the following sets of questions, depending on the type of funding you're asking for.<br />
<br />
==== For funding travel ====<br />
<br />
If you're asking for funds to cover a trip, use this set of questions.<br />
<br />
# '''Where are you going''' (location and event)?<br />
# '''What do you need covered?''' (Please estimate the costs in USD: hotel $X, travel $Y)<br />
# '''If we cannot provide a full subsidy, will a partial subsidy be helpful?''' (Yes/No)<br />
## If Yes can you specify the minimum amount you would need covered to facilitate your attendance<br />
# If you are requesting airfare, include complete flight information such as flight numbers, desired departure and arrival airports, and times. Also let us know if you have specific time restrictions.<br />
# '''Do you need a visa or other official processing before you can travel?''' If so, approximately how long does that processing take?<br />
# '''What will you accomplish by going on this trip?''' Please be as specific as possible, since this is the most important factor in granting requests.<br />
<br />
The last question really is the most important, and will likely be the longest part of your answer. Tell us what you're going to accomplish by taking this trip. Preference is given to people who are attending an event with a goal to make Sugar Labs better, and a plan for doing it.<br />
<br />
Simply "meeting with people" or "talking about ways to do something" are not specific to Sugar Labs. Ideas can be discussed on mailing lists, after all. And although meeting face to face is a wonderful thing, that doesn't necessarily result in getting anything done.<br />
<br />
* Not specific: Meet with other people from JKL Group.<br />
* Not specific: Improve communication between Team X and Team Y.<br />
* Specific: Write a working module for Web App Q that creates a service queue for Team X to do Task Z more efficiently.<br />
* Specific: Agree on and publish a complete plan, schedule, and milestones for Project W. <br />
<br />
==== For purchasing things ====<br />
<br />
Use this template if you're requesting the purchase of equipment, a subscription, etc. <br />
<br />
# '''What is being purchased?''' If it's a product, link to the product; if it's (If it's a produ to product, etc.)<br />
# '''Why does this purchase benefit the operations of Sugar Labs?''' What is the blocker it resolves? <br />
# '''Who will be responsible for the item?''' Who will own it? How will it be tracked/maintained? <br />
# '''How much will it cost?''' Are there any maintenance costs associated with the purchase? How often will it have to be renewed (if at all)?<br />
# '''What other options were evaluated for purchase?''' Why did the chosen product/service/option get selected as the best one? What were the criteria or features you needed?<br />
# '''What deadlines are associated with this request?''' Do you need an answer by a certain date? Would the funding need to come by a particular point in time? Note that approving future spending is a separate action from actually spending the money - for instance, we may agree to fund something but pay for it 3 months down the line - so it's good to know both dates, if they exist.<br />
# '''Other notes?'''<br />
<br />
=== How decisions are made ===<br />
<br />
This section explains the criteria typically used to decide whether to subsidize the travel of a specific applicant. It's provided for context only - if you're requesting funding, you don't actually have to read this stuff!<br />
<br />
==== Relevance ====<br />
<br />
* ''Does this purchase/event deliver information that is pertinent to an ongoing project of concern at the event?'' For example, an event that includes a critical brainstorming session on deployment outreac could be more effective with the attendance of a teacher or engineer from a deployment.<br />
* ''Does the purchase/event provide an opportunity for this particular person to attract contribution to one or more areas in Sugar Labs?'' An event that attracts computer-based designers, for instance, might present an opportunity for a member of the Design team to attract new, skilled contributors.<br />
* ''Is the requesting person a current contributor?'' Current contributors with a proven history of involvement in some sense are a known quantity. This does not mean that sponsorship shouldn't go to new or potential contributors, but it is a factor for consideration.<br />
<br />
==== Criticality ====<br />
<br />
* (For travel only) ''Does this person have demonstrated skills in an area that will promote reaching the goals of the event?'' For example, if Sugar's speaking schedule at an event requires someone with expertise on packaging Activities for various Linux distributions, it would make sense to sponsor the travel of someone who could give those talks.<br />
* ''Are there clear deliverables attached to this purchase/event that otherwise cannot be achieved?'' Deliverables come in many forms, such as working code; completed documentation; or key decisions. For purchases, will the absence of the purchase block or negatively impact work that is already being done on the project? For events, if other contributors involved in the same area are expected to attend already, will this person's absence negatively impact their work at the event?<br />
* ''How important is this subsidy to the purchase/event?'' Without the full subsidy, will the item not be able to be purchased, or will the applicant not be able to attend the event at all? Will a partial subsidy suffice? Would a change in plans, such as attending part of the event, or getting a less full-featured item, still allow this person's goals to be achieved? Is Sugar Labs funding the ''only'' option available for this purchase?<br />
<br />
==== Specificity ====<br />
<br />
* ''Has this person provided substantial information about the specific objectives to achieve?'' We look at the proposal critically, because there are usually more requests than we can fill. The best requests tend to reflect clear vision from the applicants of exactly what they will achieve through this funding, and a link between that vision and the larger objectives of Sugar Labs or a specific team.<br />
* ''Are the objectives achievable within the time frame of the event/project?'' Sometimes it may not be possible to meet every objective despite best intentions and hard work. Nevertheless, sponsors should also carefully consider whether the deliverables can reasonably be finished by the end of the relevant time period. Setting and meeting reasonable expectations is a good habit for any project.<br />
<br />
==== Proximity ====<br />
<br />
* (For event travel only) ''Is this person located in the same region as the event?'' Regionally co-located people generally require less funding. It is not cost effective, for instance, to fund the travel of multiple people from North America to a European event. In specific cases there may be call for such subsidies, but in general regional events should reflect regional attendance and participation.<br />
<br />
==== Expense ====<br />
<br />
* ''How expensive is the request?'' A higher subsidy amount should carry with it higher expectations, more criticality, or other benefits that justify the expense. Keep in mind that the transparent approval process creates better accountability for sponsors in making decisions.<br />
<br />
''This system is based on the [https://fedorahosted.org/fudcon-planning/wiki/FundingRequest Fedora community funding request system].''</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Finance&diff=65032Finance2011-04-21T21:54:55Z<p>Mchua: /* Current finances */</p>
<hr />
<div>The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.<br />
<br />
== Current finances ==<br />
<br />
All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.<br />
<br />
* The last known balance is from [[#January 2011]] and is $19,591.09 USD, held as follows:<br />
** $19,591.09 USD in a Vanguard Money Market account held by the Software Freedom Conservancy on behalf of Sugar Labs<br />
<br />
* The $19,591.09 USD is earmarked as follows:<br />
** ?? for Gould Grant<br />
** ?? for Google Summer of Code<br />
** ?? unrestricted (available for future grants)<br />
<br />
''[[User:Walter|Walter Bender]] should be filling in the details above shortly.'' [[User:Mchua|Mchua]] 17:54, 21 April 2011 (EDT)<br />
<br />
== Archive of transactions ==<br />
<br />
=== April 2011 ===<br />
<br />
Not known.<br />
<br />
=== March 2011 ===<br />
<br />
Not known.<br />
<br />
=== February 2011 ===<br />
<br />
Not known.<br />
<br />
=== January 2011 ===<br />
<br />
'''End-of-month balance:''' $19,591.09<br />
<br />
'''Net change since last month:''' -$1,679.08<br />
<br />
'''Transactions:'''<br />
<br />
{|border="1" cellspacing="0" width="100%" align="right"<br />
! Item<br />
! From/To<br />
! Income<br />
! Expenses<br />
! Notes<br />
|-<br />
| Gould Grant student developer salary<br />
| Gould Grant student employee<br />
| <br />
| -$1,680.00<br />
| Not sure if we want to put names here, so I left that information out. [[User:Mchua|Mchua]]<br />
|-<br />
| Interest from Vanguard account<br />
| Vanguard<br />
| $0.92<br />
|<br />
|<br />
|-<br />
!<br />
! Total<br />
! $0.92<br />
! -$1,680.00<br />
!<br />
|}<br />
<br />
== Requesting budget ==</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Finance&diff=65031Finance2011-04-21T21:51:31Z<p>Mchua: /* January 2011 */</p>
<hr />
<div>The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.<br />
<br />
== Current finances ==<br />
<br />
All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.<br />
<br />
=== April 2011 ===<br />
<br />
Not known.<br />
<br />
=== March 2011 ===<br />
<br />
Not known.<br />
<br />
=== February 2011 ===<br />
<br />
Not known.<br />
<br />
=== January 2011 ===<br />
<br />
'''End-of-month balance:''' $19,591.09<br />
<br />
'''Net change since last month:''' -$1,679.08<br />
<br />
'''Transactions:'''<br />
<br />
{|border="1" cellspacing="0" width="100%" align="right"<br />
! Item<br />
! From/To<br />
! Income<br />
! Expenses<br />
! Notes<br />
|-<br />
| Gould Grant student developer salary<br />
| Gould Grant student employee<br />
| <br />
| -$1,680.00<br />
| Not sure if we want to put names here, so I left that information out. [[User:Mchua|Mchua]]<br />
|-<br />
| Interest from Vanguard account<br />
| Vanguard<br />
| $0.92<br />
|<br />
|<br />
|-<br />
!<br />
! Total<br />
! $0.92<br />
! -$1,680.00<br />
!<br />
|}<br />
<br />
== Requesting budget ==</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Finance&diff=65030Finance2011-04-21T21:48:34Z<p>Mchua: /* January 2011 */</p>
<hr />
<div>The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.<br />
<br />
== Current finances ==<br />
<br />
All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.<br />
<br />
=== April 2011 ===<br />
<br />
Not known.<br />
<br />
=== March 2011 ===<br />
<br />
Not known.<br />
<br />
=== February 2011 ===<br />
<br />
Not known.<br />
<br />
=== January 2011 ===<br />
<br />
'''End-of-month balance:''' $19,591.09<br />
<br />
'''Net change since last month:''' -$1,679.08<br />
<br />
'''Transactions:'''<br />
<br />
{|border="1" cellspacing="0" width="100%" align="right"<br />
! Item<br />
! From/To<br />
! Income<br />
! Expenses<br />
! Notes<br />
|-<br />
| ?<br />
| ?<br />
| x<br />
| -$1,680.00<br />
| This is listed as "Expenses:Sugar:Gould:Students:2010" in the ledger - I'm not sure where the money was paid to, or what item this was for exactly. [[User:Mchua|Mchua]]<br />
|-<br />
| Interest<br />
| ?<br />
| $0.92<br />
|<br />
| I'm not sure where this interest came from, but we saved it. [[User:Mchua|Mchua]]<br />
|-<br />
!<br />
! Total<br />
! $0.92<br />
! -$1,680.00<br />
!<br />
|}<br />
<br />
== Requesting budget ==</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Finance&diff=65029Finance2011-04-21T21:48:21Z<p>Mchua: /* January 2011 */</p>
<hr />
<div>The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.<br />
<br />
== Current finances ==<br />
<br />
All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.<br />
<br />
=== April 2011 ===<br />
<br />
Not known.<br />
<br />
=== March 2011 ===<br />
<br />
Not known.<br />
<br />
=== February 2011 ===<br />
<br />
Not known.<br />
<br />
=== January 2011 ===<br />
<br />
'''End-of-month balance:''' $19,591.09<br />
<br />
'''Net change since last month:''' -$1,679.08<br />
<br />
'''Transactions:'''<br />
<br />
{|border="1" cellspacing="0" width="100%" align="center" class="wikitable sortable"<br />
! Item<br />
! From/To<br />
! Income<br />
! Expenses<br />
! Notes<br />
|-<br />
| ?<br />
| ?<br />
| x<br />
| -$1,680.00<br />
| This is listed as "Expenses:Sugar:Gould:Students:2010" in the ledger - I'm not sure where the money was paid to, or what item this was for exactly. [[User:Mchua|Mchua]]<br />
|-<br />
| Interest<br />
| ?<br />
| $0.92<br />
|<br />
| I'm not sure where this interest came from, but we saved it. [[User:Mchua|Mchua]]<br />
|-<br />
!<br />
! Total<br />
! $0.92<br />
! -$1,680.00<br />
!<br />
|}<br />
<br />
== Requesting budget ==</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Finance&diff=65028Finance2011-04-21T21:47:34Z<p>Mchua: /* January 2011 */</p>
<hr />
<div>The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.<br />
<br />
== Current finances ==<br />
<br />
All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.<br />
<br />
=== April 2011 ===<br />
<br />
Not known.<br />
<br />
=== March 2011 ===<br />
<br />
Not known.<br />
<br />
=== February 2011 ===<br />
<br />
Not known.<br />
<br />
=== January 2011 ===<br />
<br />
'''End-of-month balance:''' $19,591.09<br />
'''Net change since last month:''' -$1,679.08<br />
<br />
'''Transactions:'''<br />
<br />
{|<br />
! Item<br />
! From/To<br />
! Income<br />
! Expenses<br />
! Notes<br />
|-<br />
| ?<br />
| ?<br />
| x<br />
| -$1,680.00<br />
| This is listed as "Expenses:Sugar:Gould:Students:2010" in the ledger - I'm not sure where the money was paid to, or what item this was for exactly. [[User:Mchua|Mchua]]<br />
|-<br />
| Interest<br />
| ?<br />
| $0.92<br />
|<br />
| I'm not sure where this interest came from, but we saved it. [[User:Mchua|Mchua]]<br />
|-<br />
!<br />
! Total<br />
! $0.92<br />
! -$1,680.00<br />
!<br />
|}<br />
<br />
== Requesting budget ==</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Finance&diff=65027Finance2011-04-21T21:39:53Z<p>Mchua: /* Current finances */</p>
<hr />
<div>The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.<br />
<br />
== Current finances ==<br />
<br />
All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.<br />
<br />
=== April 2011 ===<br />
<br />
Not known.<br />
<br />
=== March 2011 ===<br />
<br />
Not known.<br />
<br />
=== February 2011 ===<br />
<br />
Not known.<br />
<br />
=== January 2011 ===<br />
<br />
'''End-of-month balance:''' 19,591.09<br />
<br />
== Requesting budget ==</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Finance&diff=65025Finance2011-04-21T21:35:32Z<p>Mchua: Created page with "The Oversight Board is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point. == Current finances =..."</p>
<hr />
<div>The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.<br />
<br />
== Current finances ==<br />
<br />
== Requesting budget ==</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Oversight_Board&diff=65024Oversight Board2011-04-21T21:34:36Z<p>Mchua: /* Additional roles within Sugar Labs */</p>
<hr />
<div><noinclude>{{GoogleTrans-en}}{{TeamHeader|Oversight Board|roadmap_link=Oversight Board/Vision|roadmap_label=Vision}}</noinclude><br />
{{TOCright}}<br />
== The Oversight Board ==<br />
<br />
The 2009–2010 oversight board members are:<br />
<br />
* [[User:Cjb|Chris Ball]] (One Laptop per Child)<br />
* [[User:Walter|Walter Bender]]<br />
* [[User:Alsroot|Aleksey Lim]]<br />
* [[User:Mchua|Mel Chua]] (Red Hat)<br />
* [[User:Holt|Adam Holt]] (One Laptop per Child)<br />
* [[User:Bernie|Bernie Innocenti]] (Free Software Foundation)<br />
* [[User:Sebastian|Sebastian Silva]] (Somosazucar)<br />
<br />
We'd like to thank the follow former board members for their contributions:<br />
<br />
* [[User:SeanDaly|Sean Daly]] (2009-2010)<br />
* [[User:Marcopg|Marco Pesenti Gritti]] (2008–2009)<br />
* [[User:Gdk|Greg Dekoenigsberg]] (2008–2009)<br />
* [[User:Dfarning|David Farning]] (2008–2009)<br />
* [[User:Tomeu|Tomeu Vizoso]] (2008-2010)<br />
<br />
== Mission ==<br />
<br />
{{:Oversight_Board/Mission}}<br />
<br />
== Meetings ==<br />
<br />
Details of meeting times and links to the minutes can be found at [[Oversight Board/Minutes]]<br />
<br />
==Additional roles within Sugar Labs==<br />
<br />
Ombudsman: A neutral party with whom anyone (member or non-member) may consult privately. The ombudsman will make a monthly report to the Oversight Board and the community. [[User:Bert|Bert Freudenberg]] is Ombudsman (Please email ombudsman (at) sugarlabs.org).<br />
<br />
System administrator: ''ex officio'', nonvoting member of the Infrastructure Committee<br />
<br />
Treasurer: ''ex officio'', nonvoting member of the [[Finance]] Committee<br />
<br />
== Subpages ==<br />
{{Special:PrefixIndex/{{PAGENAME}}/}}<br />
<br />
[[Category:Oversight board]]<br />
[[Category:Governance]]<br />
<br />
[[Category:Team]]</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Welcome_to_the_Sugar_Labs_wiki&diff=65021Welcome to the Sugar Labs wiki2011-04-21T17:37:55Z<p>Mchua: </p>
<hr />
<div><center><div style="background:#efefef;border:1px solid #cdf; padding:0px; align:center;font-size:100%" class="linkgroup"><br />
'''[[Sugar Labs/Current Events | Weekly News]]''' &nbsp; &middot; &nbsp;<br />
'''[[Sugar Labs/Getting Involved | Join]]''' &nbsp; &middot; &nbsp;<br />
'''[[Downloads]]''' &nbsp; &middot; &nbsp;<br />
'''[[Sugar Labs/Contacts | Contact]]''' &nbsp; &middot; &nbsp;<br />
'''[[Sugar Labs | About Us]]'''<br />
</div><br />
</center><noinclude><br />
__NOEDITSECTION__<br />
__NOTOC__<br />
<br />
The Sugar Labs wiki is where our community comes together to develop and support the [[What is Sugar? | Sugar Learning Platform]].<br />
<br />
{| border="0" <!-- 2 columns x 2 rows --> <br />
|- row1<br />
|<span class="linkgroup">[[File:Download_Mirabell.png|center|link=Downloads/Landing_page]]</span><br>[[Image:Sugarlabs_mainpage_01.png|link=Sugar Labs/Getting Involved]]<br />
| <!-- column2 --><br />
== New Learners, Parents, Teachers, and Students ==<br />
Sugar users are Learners. If you are visiting for the first time, please see [http://www.sugarlabs.org www.sugarlabs.org] for an introduction to Sugar.<br />
<br />
Want to help? We're always looking for people who want to join the Sugar Labs community. We are a group of contributors of all types - teachers, writers, coders, designers, testers, and more - who work together to further the development and usage of the Sugar Learning Platform around the world. Visit the '''[[Sugar Labs/Getting Involved| Getting Involved ]]''' page, and find out how you can join in the fun of learning. We have some [[Vacancies]] and are always looking for maintainers and testers.<br />
<br />
== Current Learners ==<br />
If you have Sugar and are looking for new Activities, please see the [http://activities.sugarlabs.org Sugar Activity Library].<br />
<br />
== New and Current Community Members ==<br />
Please take a look around the wiki. Explore the menus along the left side of the page. If you ever get lost, just click on the ''Wiki'' link at the top of every page and you will return to this page. Please also visit the [[Local Labs]].<br />
|- row2<br />
<br />
|}<br />
==Community News==<br />
<br />
{{:News}}<br />
<br />
For more news about Sugar Labs, please see the [[Sugar Labs/Current Events|Current Events page]] and the [[Archive/Current Events|Sugar Digest archive]]. Press releases are on our [http://www.sugarlabs.org/index.php?template=press Press page]. There is also an [[News|archive of news links]], which were on this front page.<br />
<br />
<br />
<div style="background-color:#a0ff93; border:1px solid #cdf; padding:5px; padding-left: 1.0em; font-size:100%">[[Sugar_Labs/Governance/Trademark|Sugar Labs<sup>®</sup>]] Foundation is a non-profit association, a member project of the [http://www.sfconservancy.org/ Software Freedom Conservancy], and is supported by our generous [[Sugar Labs/Getting Involved|contributors]] and [[Sugar Labs/Thank You|sponsors]].<br />
</div><br />
<br />
<br />
<br />
[[Category:General public]]<br />
<br />
<noinclude><br />
{{Translations | [[Sugar Labs/Welcome to Sugar Labs|english]] &#124; [[Sugar Labs/Welcome to Sugar Labs/lang-es|español]] &#124; [[Sugar Labs/Welcome to Sugar Labs/lang-pt_BR|português brasil]] &#124; [[Sugar Labs/Welcome to Sugar Labs/lang-ps|پښتو]] &#124; [[Sugar Labs/Welcome to Sugar Labs/lang-ru_RU|русский]] &#124;}}<br />
</noinclude><br />
__NOTOC__<br />
__NOEDITSECTION__</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick/Documentation_SOP&diff=59087Sugar on a Stick/Documentation SOP2010-11-09T15:25:50Z<p>Mchua: /* Generating HTML or PDF output */ adding apt-get option</p>
<hr />
<div>Starting with the upcoming SoaS version (release date: ''2010-05-11''), a good amount of the related documentation will be created through [https://fedorahosted.org/publican/ publican]. This [http://en.wikipedia.org/wiki/Standard_operating_procedure SOP] describes how to contribute changes to the documentation.<br />
<br />
== Viewing the Documentation ==<br />
<br />
You can view a reasonably up-to-date version of the files here:<br />
<br />
* [http://mirrors.rit.edu/sugarlabs/soas/docs/customization-guide/index.html Customization Guide]<br />
* [http://mirrors.rit.edu/sugarlabs/soas/docs/creation-kit/index.html Creation Kit]<br />
<br />
This is not a permanent location (the URLs above will likely be moving between now and May 2010), and these files may not be completely up-to-date; we are currently obtaining a more permanent infrastructure solution, but the links should suffice at present.<br />
<br />
== Contributing Content to the Documentation ==<br />
<br />
=== Checking out the latest Version ===<br />
<br />
Clone the GIT repository with the Sugar on a Stick documentation from GIT by running:<br />
<pre>git clone git://git.sugarlabs.org/soas-docs/mainline.git soas-docs</pre><br />
<br />
=== Apply your Changes ===<br />
<br />
* Edit away! - Try to follow these conventions [https://fedorahosted.org/publican/browser/trunk/publican/datadir/Common_Content/common/en-US/Conventions.xml here].<br />
**For example, Move down to a directory you want to edit, and edit a file with gedit<br />
<pre>cd soas-docs<br />
ls<br />
cd Creation\ Kit/<br />
cd en-US<br />
ls<br />
gedit Book_Info.xml</pre><br />
<br />
<br />
* Bump the edition tag in ''Book_Info.xml'' after a major change.<br />
* Make sure to explain your change in Revision_History.xml<br />
<br />
=== Generating HTML or PDF output ===<br />
<br />
Install publican if you haven't already. If you are running a yum-based system (Fedora, SuSE, etc), this is:<br />
<br />
sudo yum install publican<br />
<br />
If you are running an apt-based system (Debian, Ubuntu, etc), this is:<br />
<br />
sudo apt-get install publican<br />
<br />
In the same directory as the file '''''publican.cfg''''' (this will almost certainly be '''''/path/to/soas-docs/Customization Guide''''' or '''''/path/to/soas-docs/Creation Kit'''''), run the following command.<br />
<br />
publican build --format=html --lang=en-US<br />
<br />
or<br />
<br />
publican build --format=pdf --lang=en-US<br />
<br />
...depending on what output format you would like. You will see output that looks like this.<br />
<br />
<pre><br />
[you@machine]$ publican build --format=html --lang=en-US<br />
Setting up en-US<br />
Processing file tmp/en-US/xml/Common_Content/Conventions.xml<br />
Processing file tmp/en-US/xml/Common_Content/Feedback.xml<br />
Processing file tmp/en-US/xml/Common_Content/Legal_Notice.xml<br />
<snip more similar stuff><br />
Beginning work on en-US<br />
Starting html<br />
Using XML::LibXSLT on /usr/share/publican/xsl/html.xsl<br />
Writing pref-Customization_Guide-Preface.html for preface(pref-Customization_Guide-Preface)<br />
Writing sect-Creation_Kit-Preparation-Getting_Started.html for section(sect-Creation_Kit-Preparation-Getting_Started)<br />
Writing chap-Customization_Guide-Preparation.html for chapter(chap-Customization_Guide-Preparation)<br />
<snip more similar stuff><br />
Writing index.html for book<br />
Finished html<br />
</pre><br />
<br />
When the publican build is finished, you will find your generated docs in a folder called '''''tmp/en-US''''' in your current directory.<br />
<br />
=== Create a Patch from your Changes ===<br />
<br />
Create a patch using the following command: <pre>git diff > product-name-change.patch</pre><br />
<br />
* ''product'' reflects the folder you made your change in, so either ''creation-kit'' or ''customization-guide''<br />
* ''name'' references to your personal name to track contributions<br />
* ''change'' should be a one or two word description of your proposed change<br />
<br />
=== Push your changes ===<br />
<br />
==== If you don't have commit access ====<br />
<br />
Send an email (with a subject line like this ''[PATCH] name-of-your-patch'') to the SoaS [http://lists.sugarlabs.org/listinfo/soas mailing list] together with your patch and an explanation of what you changed and why you think the change is necessary. Discussion will happen on list.<br />
<br />
After that, your patch will be committed and pushed. At some point, you might also be granted access to the GIT repository so that you can commit changes directly without submitting the patches to the list.<br />
<br />
==== If you have commit access ====<br />
<br />
If you need to apply someone else's patch to the file before committing it, do that first.<br />
<br />
patch -p0 < path/file.patch<br />
<br />
Once you have applied the patch and otherwise edited the files you want to commit, make the commit.<br />
<br />
git commit -a<br />
<br />
Leave a commit message describing the change. Finally, push changes back to gitorious with<br />
<br />
git push<br />
<br />
If you are doing a push for the first time, you may need to specify the origin (this is due to a weird thing in gitorious). In order to do this:<br />
<br />
git remote rm origin<br />
git remote add origin gitorious@git.sugarlabs.org:soas-docs/mainline.git<br />
git push origin master<br />
<br />
You should be able to simply use <code>git push</code> thereafter.</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_meetings/2010-08-30&diff=56356Sugar on a Stick meetings/2010-08-302010-08-30T23:17:57Z<p>Mchua: Created page with "== Minutes == * No new topics from the mailing list to bring up at this meeting. * Remix naming deferred until we have proposals as to how the remixes should be named. (HELP NEE..."</p>
<hr />
<div>== Minutes ==<br />
<br />
* No new topics from the mailing list to bring up at this meeting.<br />
* Remix naming deferred until we have proposals as to how the remixes should be named. (HELP NEEDED! Got an idea for this? Write a proposal!)<br />
* Upcoming deadline: 9/14 Beta Change - all changes must be pushed by this (Fedora-driven) deadline.<br />
* Idea for the future: (re)schedule a SoaS Test Day with Fedora QA.<br />
<br />
We spent most of our time on the next big URGENT milestone: getting testable 0.90 SoaS image out the door for upstream Sugar QA. The 0.90 Beta release is this Wednesday; here's what has to happen to make this happen.<br />
<br />
# erikos updates the sugar, sugar-toolkit, sugar-datastore, sugar-presence-service, sugar-artwork, telepathy-gabble and telepathy-salut packages in Fedorato the correct code versions.<br />
# mchua gets 3 people to test these packages and give them karma in Fedora's system, which will put them in the stable repositories. I'll be writing instructions on how to do this shortly.<br />
# erikos or pbrobinson or someone takes the next daily build and makes sure it boots, then announces the test image.<br />
<br />
What this means for you, o reader: if you run Fedora (or can run Fedora in a VM, or can follow written instructions on how to do exactly this), you (yes, you!) can help us with 0.90 testing this week. We're going to have instructions for this coming out once the code is ready to be tested; it should take less than 2 hours (hopefully less than 1) to do your setup and testing from start to finish, and you won't need any prior experience. We'll be using the same test setup for Sugar in the future, too.<br />
<br />
The catch is that because we're under intense time pressure to meet release deadlines, the time between when we can say "we're ready! We need help!" and when we need the testing finished by is going to be VERY short. So this is a heads-up letting folks know this call is going to be coming.<br />
<br />
== Logs ==<br />
<br />
<pre><br />
19:01 < mchua> #startmeeting<br />
19:01 < mchua> Hey folks. SoaS meeting time.<br />
19:01 < mchua> Er... is there a bot?<br />
19:01 < mchua> I'll mke sure logs go out, in any case.<br />
19:02 < mchua> First, I should apologize I'll be high-latency today becaues I'm on mobile broadband.<br />
19:02 < mchua> #link http://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_meetings#Agenda<br />
19:02 < mchua> Anything to add?<br />
19:02 < mchua> Otherwise this is going to be a very quick meeting, which is no problem. :)<br />
19:03 < erikos> mchua: hey<br />
19:03 < erikos> mchua: i would like to talk about testing ;p<br />
19:03 < mchua> erikos: Ok, will do.<br />
19:03 < satellit_> +1<br />
19:04 < mchua> #topic upcoming deadlines<br />
19:04 < mchua> First, let me say that there are a lot of good ongoing convos on the soas mailing list, which should continue there - I don't think there's anything specific from that we need to bring up here today.<br />
19:05 < mchua> In terms of actual deadlines, we're driven by the Fedora release calendar. The next one coming up is the Beta Change deadline (all changes will have to be pushed by this time. pending submissions are insufficient.)<br />
19:05 < mchua> This is 9/7 but I think it may have gotten pushed back a week so we may have a littl emore time.<br />
19:05 * mchua checking now<br />
19:06 < mchua> Yes, it is on 9/14 now.<br />
19:06 < mchua> #info Beta change deadline - all chnages must be pushed by 9/14<br />
19:06 < erikos> https://fedoraproject.org/wiki/Releases/14/Schedule<br />
19:06 < mchua> changes, sorry.<br />
19:06 < mchua> gah latency.<br />
19:06 < mchua> #link http://fedoraproject.org/wiki/Releases/14/Schedule<br />
19:06 < mchua> thanks erikos!<br />
19:06 -!- rgs [~rgs@77.210.18.56] has joined #sugar-meeting<br />
19:06 < mchua> #topic feature proposals<br />
19:06 < mchua> #info skipping - feature freeze is past<br />
19:06 < mchua> #topic QA<br />
19:06 < mchua> erikos: go!<br />
19:07 < erikos> mchua: a) we need a build to test on ;p<br />
19:07 < erikos> mchua: i know that peter is working on it<br />
19:07 < mchua> This is te last thing I'd like to tackle during this meeting since we don't have any proposals for remix naming and I'd like to have something to vote on for that before we actually bring it up.<br />
19:07 < mchua> (for the record.)<br />
19:07 < erikos> mchua: (latest snapshots are not loginable)<br />
19:07 < mchua> erikos: noted.<br />
19:07 < mchua> erikos: We should set a test day date so we have a milestone to aim at - deadlines help.<br />
19:08 < mchua> thoughts on when a good one would be?<br />
19:08 < mchua> maybe shortly after beta chnage?<br />
19:08 < mchua> The thursday after is 9/23<br />
19:08 < erikos> mchua: yeah - deadlines do help indeed<br />
19:08 < mchua> (wow, my typing is terrible today!)<br />
19:08 < mchua> erikos: so, 9/23 is my arbitrary proposal. How this works for anyone else, I do not know.<br />
19:09 < mchua> but it would work for me and I could help prep and show up there.<br />
19:09 < satellit_> soas-i386-20100818.16.iso http://download.sugarlabs.org/soas/test/ works can we use it?<br />
19:09 < erikos> mchua: soas - wise this sounds good<br />
19:09 < erikos> mchua: for sugar 0.90 - this would be too late<br />
19:09 < mchua> erikos: eeek. Okay, when is the deadline for that?<br />
19:09 < erikos> mchua: http://wiki.sugarlabs.org/go/0.90/Roadmap#Schedule<br />
19:09 < mchua> right-o.<br />
19:09 < erikos> mchua: actually, we would need heavy testing *now*<br />
19:09 -!- bernie_afk is now known as bernie<br />
19:10 < erikos> mchua: we will do our beta - on wednesday<br />
19:10 < mchua> erikos: Yikes. Okay, so if we get an soas image that's testable, are there people (tabs et al) waiting to attack and test that build?<br />
19:10 < mchua> whoa, wednesday. wow, the schedule totally snuck up on me this time.<br />
19:10 * mchua apologizes<br />
19:10 < erikos> mchua: at least we can announce it<br />
19:10 < erikos> mchua: and the feature owners should test etc<br />
19:11 < mchua> Okay.<br />
19:11 < mchua> Yeah.<br />
19:11 < erikos> mchua: i pinged them today<br />
19:11 < erikos> mchua: and i might get some more involved<br />
19:11 < erikos> mchua: so we need a build<br />
19:11 < erikos> mchua: that a) starts<br />
19:11 < erikos> and b) has the latest packages<br />
19:11 < mchua> Okay. Trying to figure out the best way to unblock you on that.<br />
19:11 < erikos> mchua: i work on it - that people update bodhi<br />
19:12 < mchua> If it's a matter of karma, I can call for Fedora testers and try to get it through that way.<br />
19:12 < erikos> mchua: so the packages get from updates-testing in the repo<br />
19:12 < mchua> I'm not a packager myself so I can't do much more than that, alas.<br />
19:12 < erikos> mchua: sure, that is helpful, too<br />
19:12 < mchua> erikos: do you have a list of packages you want updated?<br />
19:12 < mchua> ("all the ones in the soas kickstart file" works)<br />
19:13 < erikos> heh<br />
19:13 < mchua> (although that's sort of terrifying)<br />
19:13 < erikos> sugar, sugar-toolkit, sugar-datastore, sugar-presence-service, sugar-artwork<br />
19:13 < mchua> I'm flying mildly blind on this - not sure what you and peter talked about - what I'm trying to get at atm is a checklist of to-do items I can get people to help with<br />
19:13 < erikos> and telepathy-gabble and telepathy-salut<br />
19:13 < mchua> so it doesn't block on Peter, who is really hosed this week apparently<br />
19:14 < erikos> yeah, i can help as well building packages<br />
19:14 < mchua> Okay, and all those packages should be updated to the latest version... in the SL git, basically? The packages need to be updated and pushed to updates-testing?<br />
19:15 < erikos> once those are packaged (which is the easy part) they have to be karmadized in bodhi<br />
19:15 < erikos> to get them in the official repo<br />
19:15 * mchua can easily send out a call-to-arms saying "packagers! this is a list of packages that need to be in updates-testing at version X or later by $urgent_date" and when those are updated it's a matter of just making the .iso.<br />
19:15 < erikos> we already failed here lately, even so i made a call on that<br />
19:15 < mchua> right-o. Karma I can call for.<br />
19:15 < mchua> failed on karma-fu?<br />
19:16 < erikos> well, if i am the only one... I have only one vote ;p<br />
19:16 < satellit_> how do we solve non-booting problem?<br />
19:16 * pbrobinson is here <br />
19:16 < pbrobinson> sorry I'm late<br />
19:16 < mchua> Oh, okay. erikos, would this work - if you can get the correct versions packaged, I can recruit people to test and add karma so we can get them pushed to updates-testing. I think that wouldn't block on anyone else.<br />
19:16 < mchua> We'd just need to find 3 people who can spend an hour installing stuff, that's all.<br />
19:17 < mchua> erikos: wait, just one more person, because you can test and I can test. woo!<br />
19:17 < erikos> mchua: right<br />
19:17 < erikos> mchua: tomeu might help, too<br />
19:17 < mchua> Hey, pbrobinson. We desperately need a build to test 0.90 on<br />
19:17 < mchua> erikos: ...if so, then I think we're taken care of<br />
19:17 < mchua> erikos: if you get the packages in I can get them tested<br />
19:17 < mchua> probably within 24 hours<br />
19:18 < erikos> can we aim to have a build by the end of the week?<br />
19:18 < mchua> pbrobinson: if the packages are in updates-testing, can you pull the lever and make a build from it?<br />
19:18 < erikos> mchua: one can install the rpms as well<br />
19:19 < erikos> mchua: but for some testers this might already be a blocker<br />
19:19 < mchua> the The workflow I'm seeing right now is: (1) erikos updates the sugar, sugar-toolkit, sugar-datastore, sugar-presence-service, sugar-artwork, telepathy-gabble and telepathy-salut to the correct code versions, (2) mchua gets 3 people to test and karma them so they get into updates-testing, (3) pbrobinson makes final build<br />
19:19 < erikos> (2) they get into updates-testing automatically - with karma they go into the stable branch<br />
19:20 < mchua> I can do (2) within 24 hours of when erikos sends the "packages are all ready and need karma now!" email (erikos, if you can cc mel@melchua.com on that I'll read it faster.)<br />
19:20 < pbrobinson> mchua: we'd need to enable updates-testing in the .ks which I don't think the spins wrangler would be happy with<br />
19:20 < erikos> (3) the builds are done daily, so...<br />
19:20 < mchua> erikos: d'oh. Right. s/updates/testing/stable, then.<br />
19:20 < erikos> w only need to fix the login issue<br />
19:20 < pbrobinson> they go straight to updates-testing. With appropriate karma or a week in updates-testing they go to stable<br />
19:20 < erikos> pbrobinson: i think we should go through the normal way<br />
19:21 < mchua> Okay, then it's: (1) erikos updates the sugar, sugar-toolkit, sugar-datastore, sugar-presence-service, sugar-artwork, telepathy-gabble and telepathy-salut to the correct code versions, (2) mchua gets 3 people to test and karma them so they get into stable, (3) erikos or pbrobinson or someone takes the next daily build and makes sure it boots, then announces the test image<br />
19:21 < pbrobinson> erikos: agreed. Its easy to install them with the enable repo option<br />
19:21 < erikos> mchua: yup<br />
19:22 < mchua> erikos: Okay. Are we unblocked then?<br />
19:22 < pbrobinson> mchua: all the versions of sugar and telepathy are at the latest versions I believe (i've just built the latest ones that have hit sugar-devel)<br />
19:22 < erikos> mchua: yes<br />
19:22 < mchua> I'll draft the "plz can haz test" instructions in advance of the packages being done so you don't even have to block on me to send the call for help :)<br />
19:22 < mchua> but I will test.<br />
19:22 < erikos> pbrobinson: yeah- you are doing an excellent job! thanks very much for that<br />
19:23 < mchua> #action mchua draft howto test sugar packages in fedora, send url to list and cc erikos<br />
19:23 < erikos> mchua: excellent<br />
19:23 -!- rgs [~rgs@77.210.18.56] has quit [Quit: Leaving]<br />
19:23 < pbrobinson> erikos: no issues, it generally gives me 5 mins away from switches and SANs in the DC :-|<br />
19:23 < mchua> Okay. So I'll just wait for erikos to say "all the packages are done and ready for testing+karma!" and then go forth and test and get my testing done.<br />
19:24 < mchua> I'll watch soas, sugar-devel, and my personal (mel@melchua) inbox for the announce.<br />
19:24 < mchua> and after that we can think again about a possible test day later on.<br />
19:24 < mchua> since this is the urget stuff.<br />
19:24 < mchua> er, urgent.<br />
19:24 < mchua> erikos: how's that? :)<br />
19:24 < erikos> mchua: ok, will send pings<br />
19:24 < mchua> yay!<br />
19:24 < erikos> mchua: :)<br />
19:24 < mchua> erikos: anything else?<br />
19:25 < erikos> pbrobinson: yeah, it can be refreshing<br />
19:25 * mchua is racing her laptop battery - 13min<br />
19:25 < erikos> mchua: :)<br />
19:25 < erikos> mchua: let's focus on that - then we can take care of testing instructions<br />
19:25 < mchua> Coolness.<br />
19:25 < mchua> #chair pbrobinson <br />
19:25 < mchua> Any other business?<br />
19:26 < mchua> Then let's wrap and get to it. :)<br />
19:26 < mchua> thanks folks!<br />
19:26 < mchua> #ndmeeting<br />
19:26 < mchua> #endmeeting<br />
</pre></div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_meetings&diff=56355Sugar on a Stick meetings2010-08-30T23:03:28Z<p>Mchua: /* Minutes */</p>
<hr />
<div><noinclude><div id="contentSub">< [[Sugar on a Stick]]</div><br />
<noinclude>{{TOCright}}[[Category:Meetings]]</noinclude><br />
== Meeting details ==<br />
<br />
Regular meetings for [[Sugar on a Stick]] take place on '''[irc://irc.freenode.net irc.freenode.net]''' in '''#sugar-meeting''', every '''Monday''' at '''1900 UTC'''.<br />
<br />
We use [[IRC]] for our meetings. If you don't have an IRC client (yet), you can use webchat - go to http://webchat.freenode.net and connect to #sugar-meeting, or click the screenshot below. (Replace "your_name" or the random ID provided with your name or some other nick you'd like to be known by.)<br />
<br />
[[File:Freenode-webchat-screenshot.png|left|link=http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1]]<br />
<br />
== How we run meetings ==<br />
<br />
With as much involvement as possible at all times.<br />
<br />
The motivation is to have as many simultaneous actively participating people in the meeting as possible - ideally, at ''all times'' in the meeting, ''everyone'' in the meeting should be ''doing something really cool'' (and hopefully related to Sugar on a Stick) - not just waiting for their turn to speak. Think of it as a virtual version of the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Philosophy law of two feet].<br />
<br />
Are YOU running a SoaS meeting? Take a look at [[How to run a meeting]] for an example of how a meeting is run, with commands listed out.<br />
<br />
== Agenda ==<br />
<br />
{{Anchor|Next_Meeting}}<br />
<br />
=== Every meeting ===<br />
<br />
* [[Sugar on a Stick#Release schedule]] upcoming deadlines announcement<br />
* [[Sugar on a Stick release process#Features submitted for review]]<br />
* [[Sugar_on_a_Stick_release_process#Testing_process]]<br />
<br />
=== Upcoming meeting ===<br />
* Look at features awaiting review (from last meeting)<br />
<br />
* Discuss Naming Format for Soas Remixes <br />
# Soas-v(2-3-4)-mmddyear-(name)-Remix *<br />
# (name)-v(2-3-4)-mmddyear<br />
# Other format? ie: XFCE + sugar remix (sugar-emulator or gdm switcher) Is this still Soas? (Installed to a USB stick) liveusb-creator, script, or zyx-liveinstaller.<br />
:: *Used here http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Example_Terminal_Command_to_Build_.iso<br />
:: Is the use of "Soas" in remix name an acceptable use?<br />
:: Rules and warnings to list for Naming of Remixes.<br />
:: License?<br />
# Fedora test day<br />
<br />
* add agenda items here<br />
<br />
== Future topics ==<br />
<br />
== Procedure for Minutes and Logging ==<br />
<br />
See the instructions on [[how to run a meeting]].<br />
<br />
== Minutes ==<br />
* [[/2010-08-30|2010-08-30 (weekly meeting)]]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100726_1507.html 2010-07-26 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100726_1507.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100719_1506.html 2010-07-19 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100719_1506.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100712_1503.html 2010-07-12 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100712_1503.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100705_1502.html 2010-07-05 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100705_1502.html (log)]<br />
* 2010-06-28 (no meeting)<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100621_1502.html 2010-06-21 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100621_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100614_1502.html 2010-06-14 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100614_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100607_1510.html 2010-06-07 Sugar on a Stick v4 Planning Meeting (regular weekly time)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100531_1507.html 2010-05-31 v3 Mirabelle Release Review Meeting (regular weekly time)]</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_meetings&diff=55853Sugar on a Stick meetings2010-08-16T19:15:14Z<p>Mchua: /* Upcoming meeting */</p>
<hr />
<div><noinclude><div id="contentSub">< [[Sugar on a Stick]]</div><br />
<noinclude>{{TOCright}}[[Category:Meetings]]</noinclude><br />
== Meeting details ==<br />
<br />
Regular meetings for [[Sugar on a Stick]] take place on '''[irc://irc.freenode.net irc.freenode.net]''' in '''#sugar-meeting''', every '''Monday''' at '''1900 UTC'''.<br />
<br />
We use [[IRC]] for our meetings. If you don't have an IRC client (yet), you can use webchat - go to http://webchat.freenode.net and connect to #sugar-meeting, or click the screenshot below. (Replace "your_name" or the random ID provided with your name or some other nick you'd like to be known by.)<br />
<br />
[[File:Freenode-webchat-screenshot.png|left|link=http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1]]<br />
<br />
== How we run meetings ==<br />
<br />
With as much involvement as possible at all times.<br />
<br />
The motivation is to have as many simultaneous actively participating people in the meeting as possible - ideally, at ''all times'' in the meeting, ''everyone'' in the meeting should be ''doing something really cool'' (and hopefully related to Sugar on a Stick) - not just waiting for their turn to speak. Think of it as a virtual version of the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Philosophy law of two feet].<br />
<br />
Are YOU running a SoaS meeting? Take a look at [[How to run a meeting]] for an example of how a meeting is run, with commands listed out.<br />
<br />
== Agenda ==<br />
<br />
{{Anchor|Next_Meeting}}<br />
<br />
=== Every meeting ===<br />
<br />
* [[Sugar on a Stick#Release schedule]] upcoming deadlines announcement<br />
* [[Sugar on a Stick release process#Features submitted for review]]<br />
* [[Sugar_on_a_Stick_release_process#Testing_process]]<br />
<br />
=== Upcoming meeting ===<br />
* Look at features awaiting review (from last meeting)<br />
<br />
* Discuss Naming Format for Soas Remixes <br />
# Soas-v(2-3-4)-mmddyear-(name)-Remix *<br />
# (name)-v(2-3-4)-mmddyear<br />
# Other format? ie: XFCE + sugar remix (sugar-emulator or gdm switcher) Is this still Soas? (Installed to a USB stick) liveusb-creator, script, or zyx-liveinstaller.<br />
:: *Used here http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Example_Terminal_Command_to_Build_.iso<br />
:: Is the use of "Soas" in remix name an acceptable use?<br />
:: Rules and warnings to list for Naming of Remixes.<br />
:: License?<br />
# Fedora test day<br />
<br />
* add agenda items here<br />
<br />
== Future topics ==<br />
<br />
== Procedure for Minutes and Logging ==<br />
<br />
See the instructions on [[how to run a meeting]].<br />
<br />
== Minutes ==<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100726_1507.html 2010-07-26 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100726_1507.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100719_1506.html 2010-07-19 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100719_1506.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100712_1503.html 2010-07-12 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100712_1503.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100705_1502.html 2010-07-05 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100705_1502.html (log)]<br />
* 2010-06-28 (no meeting)<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100621_1502.html 2010-06-21 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100621_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100614_1502.html 2010-06-14 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100614_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100607_1510.html 2010-06-07 Sugar on a Stick v4 Planning Meeting (regular weekly time)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100531_1507.html 2010-05-31 v3 Mirabelle Release Review Meeting (regular weekly time)]</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_release_process&diff=55423Sugar on a Stick release process2010-08-03T03:49:23Z<p>Mchua: /* Approved features for the current release */</p>
<hr />
<div><noinclude><div id="contentSub">< [[Sugar on a Stick]]</div>{{TOCright}}[[Category:Sugar on a Stick]]</noinclude><br />
== Feature process ==<br />
<br />
The feature process for Sugar on a Stick aims at providing a structured way of implementing and keeping track of upcoming features for the next release of Sugar on a Stick. This document outlines the guidelines for submitting feature proposals. An important thing to realize is the release schedule for each release.<br />
<br />
* ''What is a feature?'' A feature is defined as a significant change or enhancement to the version of Sugar on a Stick currently under development that may or may not include new packages and also relate to features of both Fedora and Sugar<br />
* ''What are the deadlines?'' The deadlines for the release currently under development are outlined in the [[Sugar_on_a_Stick#Release_schedule|release schedule]].<br />
* ''What do I get with a feature?'' Having your feature approved not only helps everybody involved in the development and engineering process to keep track of its state, but also allows other teams - like the [[Marketing_Team|marketing team]] - to leverage your work and promote it.<br />
* ''What are my responsibilities?'' By signing up for a feature, you sign up for taking care of it. That means you'll be the one responsible for providing updates and interacting with the different teams concerned by your feature, like the release engineering for Sugar on a Stick. It does, however, not mean that you've to realize your feature all alone - go out and tell the [http://lists.sugarlabs.org lists] and the [http://planet.sugarlabs.org planet] about your work. Get people excited to help you!<br />
* ''How does evaluation happen?'' Your proposal needs a majority of ''YAY'' votes from the release team (determined for a given release by the release manager - the v4 release manager is Sebastian Dziallas, and the current relase team is formed by Peter Robinson, Mel Chua and Sebastian Dziallas) to get approval. Discussion will happen at a weekly meeting, while the decisions will be announced to the SoaS mailing list.'''<br />
* ''What if my feature got rejected?'' No worries! Features that are originally rejected can be revised and resubmitted.<br />
<br />
=== How to submit a feature for consideration ===<br />
# Fill out the [[Features/Feature_Template|template]] and stick it on a page in the wiki. ('''TODO:''' create ''Category:SoaS_v4_Feature'' so people can make their pages belong to the appropriate category so that we know which version you're targeting ).<br />
# Place a link to your proposal in the [[#Current feature ideas]] section of this page while you're working on the document.<br />
# Send an email to the SoaS [http://lists.sugarlabs.org/listinfo/soas list] and incorporate any feedback you might receive.<br />
# When you think your feature proposal is ready, move it to the [[#Features submitted for review]] section of this page. It will be brought up at the next [[Sugar on a Stick meeting]], where it'll be evaluated and voted on. We might ask you to make further adjustments and revisit it at a later point or approve the feature directly. We're looking forward to hearing about your ideas!<br />
<br />
=== Approved features for the current release ===<br />
<br />
''Features must be added to this list by a member of the release team. Place complete feature proposals in the [[#Features submitted for review]] section for consideration at the next meeting.''<br />
<br />
* [[Features/Sugar_0.90|Sugar 0.90]]<br />
* [[Features/Revised_Browse_default-bookmarks.html]]<br />
* [[Updated Activities from the Mirabelle list]]<br />
* [[Features/Soas_V4/Remixability]]<br />
* [[Features/Fructose Activities]]<br />
<br />
=== Features submitted for review ===<br />
<br />
When your feature proposal is complete and ready to review, add it to the list below. These will be considered at the next [[Sugar on a Stick meeting]].<br />
<br />
* Remixability [http://wiki.sugarlabs.org/go/Features/Soas_V4/Remixability] (still being edited)<br />
* Including Fructose Activities that are tested and known to work (still being edited)<br />
<br />
=== Current feature ideas ===<br />
<br />
These feature ideas are in various stages of development.<br />
<br />
* School server<br />
* [[Kickstart generator]]<br />
* btrfs and snapshots<br />
* systemd<br />
* Control Panel section for setting display parameters (e.g., VGA out)<br />
* Simplifying Making a Custom remix and sharing the .ksfile and the CD.iso files on the wiki[http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Build_Your_Own_Remix_-.28not_included_on_SCK.DVD.29]<br />
* Remixability [http://wiki.sugarlabs.org/go/Features/Soas_V4/Remixability]<br />
<br />
== Testing process ==<br />
<br />
Our test process, which is under construction, will consist of the following: <br />
<br />
# An agreed-upon image each week for testers to attack (the daily build on $datetime of each week, for instance)<br />
# An agreed-upon set of test cases for them to execute (iow, the "test plan" thing we haven't had before)<br />
# An agreed-upon place and format for the results from running those test cases to be reported to<br />
# An agreed-upon $datetime each week by which all test results for that week will be submitted - so that the development team has a chance to look at those results and revise the build before the next test image goes out.<br />
<br />
The first thing we are doing is getting a weekly image under test to automatically appear at a static link; see [[#Test image]] below. We are going to set up a cron job so the nightly build (from http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ - which we need to start up again from the Fedora side) grabs and archives the appropriate image-under-test each week.<br />
<br />
The last weekly testing update was 6/21/2010: http://lists.sugarlabs.org/archive/soas/2010-June/001560.html<br />
<br />
=== Test image ===<br />
<br />
<big><big><!--[http://download.sugarlabs.org/soas/test/soas-i386-test-latest.iso Download the current image under test]-->[http://people.sugarlabs.org/Tgillard/soas-v4-0725-Remix.iso Download the current (temporary) image under test]</big></big><br />
: Presence service needs to be activated by entering '''setenforce 0''' in root terminal<br />
<br />
'''SPECIAL UPDATE, July 27, 2010: This week's test image is a remix by Tom Gillard due to a [https://bugzilla.redhat.com/show_bug.cgi?id=617115 bug in upstream Fedora] that prevents the automatically generated test image from booting.''' The normal test case image is available at http://download.sugarlabs.org/soas/test/soas-i386-test-latest.iso and this page will be edited when it works once again.<br />
<br />
The test image is the most recent [http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ nightly build] as of 23:59:59 on the most recent Thursday. Past test images are available at http://download.sugarlabs.org/soas/test/.<br />
<br />
=== Test cases ===<br />
<br />
We do not yet have test cases. They will appear here when they are available.<br />
:Note: See Discussion for Notes on testing [http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick_release_process]<br />
* Prototype Tests:<br />
: Activity Testing http://wiki.sugarlabs.org/go/Features/Soas_V4/ASLOxo_Activity_Test_Table based on [http://people.sugarlabs.org/Tgillard/Activities-Index-ASLO-f13-Mirabelle-f14-rawhide-Soas-tests-GC.ods]<br />
: Install Testing http://wiki.sugarlabs.org/go/Talk:Features/Soas_V4/Install_Test_Table<br />
<br />
=== Test results ===<br />
<br />
A basic template for reporting simple smoke test results is [[Features/Soas V4/ASLOxo Activity Test Table]]. This needs to be moved to a proper namespace, and instructions need to be written. Instructions will be listed here when they are available.</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Features/SoaS_Remixability&diff=55422Features/SoaS Remixability2010-08-03T03:01:24Z<p>Mchua: </p>
<hr />
<div><noinclude>{{TOCright}}<br />
[[Category:Feature Page Incomplete]]<br />
[[Category:Feature|<Remixability>]]<br />
<!-- You can add categories to tie features back to real deployments/schools requesting them, for example <br />
[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). --><br />
</noinclude><br />
<br />
<br />
<!-- All fields on this form are required to be accepted.<br />
We also request that you maintain the same order of sections so that all of the feature pages are uniform. --><br />
<br />
<!-- The actual name of your feature page should look something like: Features/Your Feature Name. This keeps all features in the same namespace --><br />
== Summary ==<br />
<br />
The official SoaS image that is released can be used as a base to re-spin custom (unofficial and unsupported) SoaS remixes using the instructions on our official [[Sugar_on_a_Stick/Documentation_SOP|Customization Guide]] and a few additional FOSS tools outlined in the Guide.<br />
<br />
This feature proposes:<br />
<br />
* The development of a page on the SL wiki for highlighting classroom-made remixes, their kickstart files, and details on their usage<br />
* The creation of 2-4 sample remixes for specific types of classrooms to pre-populate that wiki page<br />
* An experimental remix image-building service available for the first 2 months after the Mangolassi release<br />
* Edits to the Customization Guide version for Mangolassi that reflect these changes<br />
<br />
== Owner ==<br />
<br />
* Name: [[http://wiki.sugarlabs.org/go/User:Satellit | Thomas Gilliard]]<br />
<br />
* Email: satellit <at> bendbroadband <dot> com<br />
<br />
== Current status ==<br />
* Targeted release: (Soas v4 [[Mangolassi]])<br />
* Last updated: [[User:Mchua|Mchua]] 23:01, 2 August 2010 (EDT)<br />
* Percentage of completion: 70%<br />
<br />
== Detailed Description ==<br />
<br />
=== Wiki page ===<br />
<br />
The creation of a page that:<br />
<br />
* Describes remixes<br />
* Makes it clear that remixes are unsupported<br />
* Links to the Customization Guide as the canonical resource on how to make remixes<br />
* Lists existing community-made remixes so that people can see and try what others have created, with each remix listing having...<br />
** The .iso available for download<br />
** The .ks available for download<br />
** A blog or a link to some resource that describes how this remix is being used in a live teaching setting<br />
<br />
The page might look something like this:<br />
<br />
<pre><br />
+---------------------------------------------+<br />
| Unofficial SoaS Remixes |<br />
| |<br />
| +-----------------+ +---------+---+----+ |<br />
| | SoaS Mangolassi | |remix #01|.ks|blog| |<br />
| | summary | +---------+---+----+ |<br />
| | | |remix #02|.ks|blog| |<br />
| | <link to main | +---------+---+----+ |<br />
| | SoaS project | |remix foo|.ks|blog| |<br />
| | page> | +---------+---+----+ |<br />
| +-----------------+ |remix bar|.ks|blog| |<br />
| +---------+---+----+ |<br />
| description of | Your remix here! | |<br />
| remixes, including | | |<br />
| clear text on how | Here's how: | |<br />
| they are UNSUPPORTED | <link to Custom- | |<br />
| | ization guide> | |<br />
| +------------------+ |<br />
+---------------------------------------------+<br />
</pre><br />
<br />
=== Sample remixes ===<br />
<br />
In order to pre-populate the [[#Wiki page]], we would follow the Customization Guide's instruction to create and post remixes for 2-4 deployments before Mangolassi's official release date. These would be specific, teacher-driven remixes that would be used in live deployments.<br />
<br />
The "blog" link for each of these remixes would go to a description - written either by or in conjunction with the teacher - on why the remix was designed that way, and what their plans for classroom usage are. ("Ms. Smith created this remix for her middle-school Spanish-language classes with the following localization and activities so she could do the following things with Sugar in her syllabus...")<br />
<br />
=== Image-building service ===<br />
<br />
Provide and advertise an experimental remix image-building service available for the first 2 months after the Mangolassi release. For this time period, the feature owner takes responsibility for accepting emails with .ks files attached, building the resulting images, and responding to those emails with a link to a built .iso of the remix generated by that .ks.<br />
<br />
The mechanism of this back-and-forth is up to the feature owner to determine, so long as the mechanism (and the unsupported nature of the remixes generated by it) are clear. The current proposal is as follows:<br />
<br />
::Please send e-mail to:<br />
To: soas@lists.sugarlabs.org<br />
Subject: [Custom KS]-{Name of your kickstart file}<br />
*Attach your Custom.ks file*<br />
PLEASE INCLUDE THE FOLLOWING INFORMATION in e-mail:'''<br />
Sugar Version : <br />
''(0.82; 0.86.x; 0.88.x; 0.89.x)''<br />
Country / Deployment : <br />
Build system fedora version : <br />
Number of USB's in Deployment : <br />
PC/Netbooks used : <br />
Notes and Any Bug No's submitted :<br />
<br />
=== Customization guide edits ===<br />
<br />
The Customization Guide would be edited to reflect the above changes, and reviewed and tested by a few new remixes for ease-of-use. <br />
<br />
== Benefit to Sugar ==<br />
<br />
Promotes our already-existing technical flexibility to customize Soas-v4 for Deployments and individuals.<br />
<br />
* add/delete desired applications to standard set on .iso<br />
<br />
* Targeted uses:<br />
: Multiple Language versions (Including EU Languages?)<br />
: e-book reader<br />
: Older students<br />
: Games<br />
<br />
*Shared kickstart files e-mailed to SOAS and posted to wiki allow others to learn how to make a .ks file and try various remixes.<br />
*Posted links to a Catalog of prebuilt remix.iso's, with a description of their use and contents, allows less skilled users to use them.<br />
<br />
== Scope ==<br />
<br />
The technical ability to create remixes has worked for a long time.<br />
: all entries labled xxxx-remix were built using these instructions<br />
<br />
http://wiki.sugarlabs.org/go/Talk:Features/Soas_V4/Install_Test_Table#Test_results<br />
<br />
The implementation of this feature depends on:<br />
<br />
* the editing of the Customization Guide<br />
* the creation a wiki page<br />
* the running of a Remix Image Building Service for 2 months after release<br />
<br />
==UI Design==<br />
<br />
N/A<br />
<br />
== How To Test ==<br />
{{:{{PAGENAME}}/Testing}}<br />
== User Experience ==<br />
<br />
Wider choices for users of Soas-v4 due to ability to Customize.<br />
<br />
== Dependencies ==<br />
<br />
None that I know of.<br />
<br />
== Contingency Plan ==<br />
Not Needed<br />
<br />
== Documentation ==<br />
http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Build_Your_Own_Remix_-.28not_included_on_SCK.DVD.29<br />
<br />
== Release Notes ==<br />
None Needed<br />
<br />
== Comments and Discussion ==<br />
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. --><br />
<br />
*07/27/2010 Some nice comments from lists:<br />
<br />
Caryl Bigenho:<br />
<br />
Hi Tom,<br />
I love this idea! (I hope it would also include easier SoaS creation on the Mac.) When I lent some of my "Roadshow" library machines to the University of Montana education department to help them prep for a science project, I downloaded a lot of stuff not already there (eg Bridge, Star Chart, etc), then put only them and the essentials (eg Browse, Write, Record) in the favorites and hid all the rest. It would be really nice to be able to create sticks with special focus like this for targeted projects.<br />
Caryl<br />
<br />
Christoph Derndorfer:<br />
<br />
wow, this looks like a truly amazing project!<br />
<br />
Can't wait to give it a spin at one point or another... :-)<br />
<br />
Cheers,<br />
Christoph</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_release_process&diff=55419Sugar on a Stick release process2010-08-02T20:04:09Z<p>Mchua: /* Approved features for the current release */</p>
<hr />
<div><noinclude><div id="contentSub">< [[Sugar on a Stick]]</div>{{TOCright}}[[Category:Sugar on a Stick]]</noinclude><br />
== Feature process ==<br />
<br />
The feature process for Sugar on a Stick aims at providing a structured way of implementing and keeping track of upcoming features for the next release of Sugar on a Stick. This document outlines the guidelines for submitting feature proposals. An important thing to realize is the release schedule for each release.<br />
<br />
* ''What is a feature?'' A feature is defined as a significant change or enhancement to the version of Sugar on a Stick currently under development that may or may not include new packages and also relate to features of both Fedora and Sugar<br />
* ''What are the deadlines?'' The deadlines for the release currently under development are outlined in the [[Sugar_on_a_Stick#Release_schedule|release schedule]].<br />
* ''What do I get with a feature?'' Having your feature approved not only helps everybody involved in the development and engineering process to keep track of its state, but also allows other teams - like the [[Marketing_Team|marketing team]] - to leverage your work and promote it.<br />
* ''What are my responsibilities?'' By signing up for a feature, you sign up for taking care of it. That means you'll be the one responsible for providing updates and interacting with the different teams concerned by your feature, like the release engineering for Sugar on a Stick. It does, however, not mean that you've to realize your feature all alone - go out and tell the [http://lists.sugarlabs.org lists] and the [http://planet.sugarlabs.org planet] about your work. Get people excited to help you!<br />
* ''How does evaluation happen?'' Your proposal needs a majority of ''YAY'' votes from the release team (determined for a given release by the release manager - the v4 release manager is Sebastian Dziallas, and the current relase team is formed by Peter Robinson, Mel Chua and Sebastian Dziallas) to get approval. Discussion will happen at a weekly meeting, while the decisions will be announced to the SoaS mailing list.'''<br />
* ''What if my feature got rejected?'' No worries! Features that are originally rejected can be revised and resubmitted.<br />
<br />
=== How to submit a feature for consideration ===<br />
# Fill out the [[Features/Feature_Template|template]] and stick it on a page in the wiki. ('''TODO:''' create ''Category:SoaS_v4_Feature'' so people can make their pages belong to the appropriate category so that we know which version you're targeting ).<br />
# Place a link to your proposal in the [[#Current feature ideas]] section of this page while you're working on the document.<br />
# Send an email to the SoaS [http://lists.sugarlabs.org/listinfo/soas list] and incorporate any feedback you might receive.<br />
# When you think your feature proposal is ready, move it to the [[#Features submitted for review]] section of this page. It will be brought up at the next [[Sugar on a Stick meeting]], where it'll be evaluated and voted on. We might ask you to make further adjustments and revisit it at a later point or approve the feature directly. We're looking forward to hearing about your ideas!<br />
<br />
=== Approved features for the current release ===<br />
<br />
''Features must be added to this list by a member of the release team. Place complete feature proposals in the [[#Features submitted for review]] section for consideration at the next meeting.''<br />
<br />
* [[Features/Sugar_0.90|Sugar 0.90]]<br />
* [[Features/Revised_Browse_default-bookmarks.html]]<br />
* [[Updated Activities from the Mirabelle list]]<br />
<br />
=== Features submitted for review ===<br />
<br />
When your feature proposal is complete and ready to review, add it to the list below. These will be considered at the next [[Sugar on a Stick meeting]].<br />
<br />
* Remixability [http://wiki.sugarlabs.org/go/Features/Soas_V4/Remixability] (still being edited)<br />
* Including Fructose Activities that are tested and known to work (still being edited)<br />
<br />
=== Current feature ideas ===<br />
<br />
These feature ideas are in various stages of development.<br />
<br />
* School server<br />
* [[Kickstart generator]]<br />
* btrfs and snapshots<br />
* systemd<br />
* Control Panel section for setting display parameters (e.g., VGA out)<br />
* Simplifying Making a Custom remix and sharing the .ksfile and the CD.iso files on the wiki[http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Build_Your_Own_Remix_-.28not_included_on_SCK.DVD.29]<br />
* Remixability [http://wiki.sugarlabs.org/go/Features/Soas_V4/Remixability]<br />
<br />
== Testing process ==<br />
<br />
Our test process, which is under construction, will consist of the following: <br />
<br />
# An agreed-upon image each week for testers to attack (the daily build on $datetime of each week, for instance)<br />
# An agreed-upon set of test cases for them to execute (iow, the "test plan" thing we haven't had before)<br />
# An agreed-upon place and format for the results from running those test cases to be reported to<br />
# An agreed-upon $datetime each week by which all test results for that week will be submitted - so that the development team has a chance to look at those results and revise the build before the next test image goes out.<br />
<br />
The first thing we are doing is getting a weekly image under test to automatically appear at a static link; see [[#Test image]] below. We are going to set up a cron job so the nightly build (from http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ - which we need to start up again from the Fedora side) grabs and archives the appropriate image-under-test each week.<br />
<br />
The last weekly testing update was 6/21/2010: http://lists.sugarlabs.org/archive/soas/2010-June/001560.html<br />
<br />
=== Test image ===<br />
<br />
<big><big><!--[http://download.sugarlabs.org/soas/test/soas-i386-test-latest.iso Download the current image under test]-->[http://people.sugarlabs.org/Tgillard/soas-v4-0725-Remix.iso Download the current (temporary) image under test]</big></big><br />
: Presence service needs to be activated by entering '''setenforce 0''' in root terminal<br />
<br />
'''SPECIAL UPDATE, July 27, 2010: This week's test image is a remix by Tom Gillard due to a [https://bugzilla.redhat.com/show_bug.cgi?id=617115 bug in upstream Fedora] that prevents the automatically generated test image from booting.''' The normal test case image is available at http://download.sugarlabs.org/soas/test/soas-i386-test-latest.iso and this page will be edited when it works once again.<br />
<br />
The test image is the most recent [http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ nightly build] as of 23:59:59 on the most recent Thursday. Past test images are available at http://download.sugarlabs.org/soas/test/.<br />
<br />
=== Test cases ===<br />
<br />
We do not yet have test cases. They will appear here when they are available.<br />
:Note: See Discussion for Notes on testing [http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick_release_process]<br />
* Prototype Tests:<br />
: Activity Testing http://wiki.sugarlabs.org/go/Features/Soas_V4/ASLOxo_Activity_Test_Table based on [http://people.sugarlabs.org/Tgillard/Activities-Index-ASLO-f13-Mirabelle-f14-rawhide-Soas-tests-GC.ods]<br />
: Install Testing http://wiki.sugarlabs.org/go/Talk:Features/Soas_V4/Install_Test_Table<br />
<br />
=== Test results ===<br />
<br />
A basic template for reporting simple smoke test results is [[Features/Soas V4/ASLOxo Activity Test Table]]. This needs to be moved to a proper namespace, and instructions need to be written. Instructions will be listed here when they are available.</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_release_process&diff=55418Sugar on a Stick release process2010-08-02T20:04:05Z<p>Mchua: /* Features submitted for review */ mirabelle activity update approved, more robust iso dropped</p>
<hr />
<div><noinclude><div id="contentSub">< [[Sugar on a Stick]]</div>{{TOCright}}[[Category:Sugar on a Stick]]</noinclude><br />
== Feature process ==<br />
<br />
The feature process for Sugar on a Stick aims at providing a structured way of implementing and keeping track of upcoming features for the next release of Sugar on a Stick. This document outlines the guidelines for submitting feature proposals. An important thing to realize is the release schedule for each release.<br />
<br />
* ''What is a feature?'' A feature is defined as a significant change or enhancement to the version of Sugar on a Stick currently under development that may or may not include new packages and also relate to features of both Fedora and Sugar<br />
* ''What are the deadlines?'' The deadlines for the release currently under development are outlined in the [[Sugar_on_a_Stick#Release_schedule|release schedule]].<br />
* ''What do I get with a feature?'' Having your feature approved not only helps everybody involved in the development and engineering process to keep track of its state, but also allows other teams - like the [[Marketing_Team|marketing team]] - to leverage your work and promote it.<br />
* ''What are my responsibilities?'' By signing up for a feature, you sign up for taking care of it. That means you'll be the one responsible for providing updates and interacting with the different teams concerned by your feature, like the release engineering for Sugar on a Stick. It does, however, not mean that you've to realize your feature all alone - go out and tell the [http://lists.sugarlabs.org lists] and the [http://planet.sugarlabs.org planet] about your work. Get people excited to help you!<br />
* ''How does evaluation happen?'' Your proposal needs a majority of ''YAY'' votes from the release team (determined for a given release by the release manager - the v4 release manager is Sebastian Dziallas, and the current relase team is formed by Peter Robinson, Mel Chua and Sebastian Dziallas) to get approval. Discussion will happen at a weekly meeting, while the decisions will be announced to the SoaS mailing list.'''<br />
* ''What if my feature got rejected?'' No worries! Features that are originally rejected can be revised and resubmitted.<br />
<br />
=== How to submit a feature for consideration ===<br />
# Fill out the [[Features/Feature_Template|template]] and stick it on a page in the wiki. ('''TODO:''' create ''Category:SoaS_v4_Feature'' so people can make their pages belong to the appropriate category so that we know which version you're targeting ).<br />
# Place a link to your proposal in the [[#Current feature ideas]] section of this page while you're working on the document.<br />
# Send an email to the SoaS [http://lists.sugarlabs.org/listinfo/soas list] and incorporate any feedback you might receive.<br />
# When you think your feature proposal is ready, move it to the [[#Features submitted for review]] section of this page. It will be brought up at the next [[Sugar on a Stick meeting]], where it'll be evaluated and voted on. We might ask you to make further adjustments and revisit it at a later point or approve the feature directly. We're looking forward to hearing about your ideas!<br />
<br />
=== Approved features for the current release ===<br />
<br />
''Features must be added to this list by a member of the release team. Place complete feature proposals in the [[#Features submitted for review]] section for consideration at the next meeting.''<br />
<br />
* [[Features/Sugar_0.90|Sugar 0.90]]<br />
* [[Features/Revised_Browse_default-bookmarks.html]]<br />
<br />
=== Features submitted for review ===<br />
<br />
When your feature proposal is complete and ready to review, add it to the list below. These will be considered at the next [[Sugar on a Stick meeting]].<br />
<br />
* Remixability [http://wiki.sugarlabs.org/go/Features/Soas_V4/Remixability] (still being edited)<br />
* Including Fructose Activities that are tested and known to work (still being edited)<br />
<br />
=== Current feature ideas ===<br />
<br />
These feature ideas are in various stages of development.<br />
<br />
* School server<br />
* [[Kickstart generator]]<br />
* btrfs and snapshots<br />
* systemd<br />
* Control Panel section for setting display parameters (e.g., VGA out)<br />
* Simplifying Making a Custom remix and sharing the .ksfile and the CD.iso files on the wiki[http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Build_Your_Own_Remix_-.28not_included_on_SCK.DVD.29]<br />
* Remixability [http://wiki.sugarlabs.org/go/Features/Soas_V4/Remixability]<br />
<br />
== Testing process ==<br />
<br />
Our test process, which is under construction, will consist of the following: <br />
<br />
# An agreed-upon image each week for testers to attack (the daily build on $datetime of each week, for instance)<br />
# An agreed-upon set of test cases for them to execute (iow, the "test plan" thing we haven't had before)<br />
# An agreed-upon place and format for the results from running those test cases to be reported to<br />
# An agreed-upon $datetime each week by which all test results for that week will be submitted - so that the development team has a chance to look at those results and revise the build before the next test image goes out.<br />
<br />
The first thing we are doing is getting a weekly image under test to automatically appear at a static link; see [[#Test image]] below. We are going to set up a cron job so the nightly build (from http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ - which we need to start up again from the Fedora side) grabs and archives the appropriate image-under-test each week.<br />
<br />
The last weekly testing update was 6/21/2010: http://lists.sugarlabs.org/archive/soas/2010-June/001560.html<br />
<br />
=== Test image ===<br />
<br />
<big><big><!--[http://download.sugarlabs.org/soas/test/soas-i386-test-latest.iso Download the current image under test]-->[http://people.sugarlabs.org/Tgillard/soas-v4-0725-Remix.iso Download the current (temporary) image under test]</big></big><br />
: Presence service needs to be activated by entering '''setenforce 0''' in root terminal<br />
<br />
'''SPECIAL UPDATE, July 27, 2010: This week's test image is a remix by Tom Gillard due to a [https://bugzilla.redhat.com/show_bug.cgi?id=617115 bug in upstream Fedora] that prevents the automatically generated test image from booting.''' The normal test case image is available at http://download.sugarlabs.org/soas/test/soas-i386-test-latest.iso and this page will be edited when it works once again.<br />
<br />
The test image is the most recent [http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ nightly build] as of 23:59:59 on the most recent Thursday. Past test images are available at http://download.sugarlabs.org/soas/test/.<br />
<br />
=== Test cases ===<br />
<br />
We do not yet have test cases. They will appear here when they are available.<br />
:Note: See Discussion for Notes on testing [http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick_release_process]<br />
* Prototype Tests:<br />
: Activity Testing http://wiki.sugarlabs.org/go/Features/Soas_V4/ASLOxo_Activity_Test_Table based on [http://people.sugarlabs.org/Tgillard/Activities-Index-ASLO-f13-Mirabelle-f14-rawhide-Soas-tests-GC.ods]<br />
: Install Testing http://wiki.sugarlabs.org/go/Talk:Features/Soas_V4/Install_Test_Table<br />
<br />
=== Test results ===<br />
<br />
A basic template for reporting simple smoke test results is [[Features/Soas V4/ASLOxo Activity Test Table]]. This needs to be moved to a proper namespace, and instructions need to be written. Instructions will be listed here when they are available.</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Updated_Activities_from_the_Mirabelle_list&diff=55417Updated Activities from the Mirabelle list2010-08-02T20:02:33Z<p>Mchua: </p>
<hr />
<div>[[Category:Feature|<Feature Name>]]<br />
<br />
== Summary ==<br />
<br />
All Activities shipped in the [[Mirabelle]] release will continue to be shipped in [[Mangolassi]] if they pass a basic smoke test. These Activities will be updated so that Mangolassi ships the latest stable version of their code, which may mean that some Activities that were in Mirabelle will have improvements or new features in their Mangolassi version.<br />
<br />
== Owner ==<br />
* Name: [[User:Mchua|Mel Chua]] (I would ''love'' to do this feature with someone else and mentor them through the feature process, so if you'd like to learn how this works with guidance, please contact me and I'll help you with it through the entire release cycle.)<br />
* Email: mel at sugarlabs dot org<br />
<br />
== Current status ==<br />
* Targeted release: [[Mangolassi]]<br />
* Last updated: [[User:Mchua|Mchua]] 16:02, 2 August 2010 (EDT)<br />
* Percentage of completion: 50%<br />
<br />
== Detailed Description ==<br />
<br />
I think [[#Summary]] pretty much covers it.<br />
<br />
== Benefit to Sugar ==<br />
<br />
More recent version of Activities get deployed and used, and hopefully feedback on those more recent version will be received.<br />
<br />
== Scope ==<br />
<br />
For each Activity shipped in Mirabelle...<br />
<br />
# Get the latest stable version of the Activity from either ASLO or git<br />
# Smoke-test to see if that version of the Activity works. If yes, move on; if no, roll back a stable version until it does.<br />
# Update the Fedora package for that Activity to that version of its code.<br />
# Document (for Marketing, on a talking-points list when there is one for the Mangolassi version of SoaS) any significant feature improvements for that Activity that have occurred between its Mirabelle version and its Mangolassi version.<br />
<br />
That's it; the updated packages will be automatically pulled into the Mangolassi image.<br />
<br />
==UI Design==<br />
<br />
Not applicable.<br />
<br />
== How To Test ==<br />
<br />
Using the image under test, run each Activity from Mirabelle through the standard SoaS Activity smoke-test (which needs to be written).<br />
<br />
== User Experience ==<br />
<br />
Users who have experienced the prior Mirabelle release of SoaS will notice that their old familiar Activities are still there, but that some have new features.<br />
<br />
== Dependencies ==<br />
<br />
This feature depends on individual Activities, as it is a pull of their updated code.<br />
<br />
== Contingency Plan ==<br />
<br />
None necessary, revert to previous release behaviour.<br />
<br />
== Documentation ==<br />
<br />
No documentation, though we can and probably should link to individual usage documentation for each of these Activities being shipped.<br />
<br />
== Release Notes ==<br />
<br />
We can't write this section until we have release notes for each upstream (Activity) being updated.<br />
<br />
== Comments and Discussion ==<br />
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Updated_Activities_from_the_Mirabelle_list&diff=55416Updated Activities from the Mirabelle list2010-08-02T19:39:58Z<p>Mchua: /* Owner */</p>
<hr />
<div>[[Category:Feature|<Feature Name>]]<br />
<!-- You can add categories to tie features back to real deployments/schools requesting them, for example <br />
[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). --><br />
</noinclude><br />
<br />
'''Comments and Explanations:'''<br />
<br />
There are comments (in italic) providing guidance to fill out each section, see also the [[Features/Policy|Feature Policy Page]] for a more detailed explanation of the new-feature process. '''Copy the source to a ''new page'' named Features/''Your Feature Name'' before making changes! DO NOT EDIT THIS TEMPLATE.'''<br />
<br />
<!-- All fields on this form are required to be accepted.<br />
We also request that you maintain the same order of sections so that all of the feature pages are uniform. --><br />
<br />
<!-- The actual name of your feature page should look something like: Features/Your Feature Name. This keeps all features in the same namespace --><br />
<br />
== Summary ==<br />
<br />
All Activities shipped in the [[Mirabelle]] release will continue to be shipped in [[Mangolassi]] if they pass a basic smoke test. These Activities will be updated so that Mangolassi ships the latest stable version of their code, which may mean that some Activities that were in Mirabelle will have improvements or new features in their Mangolassi version.<br />
<br />
== Owner ==<br />
* Name: [[User:Mchua|Mel Chua]] (I would ''love'' to do this feature with someone else and mentor them through the feature process, so if you'd like to learn how this works with guidance, please contact me and I'll help you with it through the entire release cycle.)<br />
* Email: mel at sugarlabs dot org<br />
<br />
== Current status ==<br />
* Targeted release: (SUGAR_VERSION)<br />
* Last updated: (DATE)<br />
* Percentage of completion: XX%<br />
<br />
== Detailed Description ==<br />
''Expand on the summary, if appropriate. A couple of sentences suffices to explain the goal, but the more details you can provide the better.''<br />
<br />
== Benefit to Sugar ==<br />
''What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''<br />
<br />
''Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.''<br />
<br />
== Scope ==<br />
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''<br />
<br />
==UI Design==<br />
''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.''<br />
<br />
== How To Test ==<br />
{{:{{PAGENAME}}/Testing}}<br />
== User Experience ==<br />
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''<br />
<br />
== Dependencies ==<br />
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''<br />
<br />
== Contingency Plan ==<br />
''If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''<br />
<br />
== Documentation ==<br />
''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''<br />
<br />
== Release Notes ==<br />
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''<br />
<br />
== Comments and Discussion ==<br />
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. --></div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Updated_Activities_from_the_Mirabelle_list&diff=55415Updated Activities from the Mirabelle list2010-08-02T19:33:07Z<p>Mchua: /* Summary */</p>
<hr />
<div>[[Category:Feature|<Feature Name>]]<br />
<!-- You can add categories to tie features back to real deployments/schools requesting them, for example <br />
[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). --><br />
</noinclude><br />
<br />
'''Comments and Explanations:'''<br />
<br />
There are comments (in italic) providing guidance to fill out each section, see also the [[Features/Policy|Feature Policy Page]] for a more detailed explanation of the new-feature process. '''Copy the source to a ''new page'' named Features/''Your Feature Name'' before making changes! DO NOT EDIT THIS TEMPLATE.'''<br />
<br />
<!-- All fields on this form are required to be accepted.<br />
We also request that you maintain the same order of sections so that all of the feature pages are uniform. --><br />
<br />
<!-- The actual name of your feature page should look something like: Features/Your Feature Name. This keeps all features in the same namespace --><br />
<br />
== Summary ==<br />
<br />
All Activities shipped in the [[Mirabelle]] release will continue to be shipped in [[Mangolassi]] if they pass a basic smoke test. These Activities will be updated so that Mangolassi ships the latest stable version of their code, which may mean that some Activities that were in Mirabelle will have improvements or new features in their Mangolassi version.<br />
<br />
== Owner ==<br />
''This should link to your home wiki page so we know who you are''<br />
* Name: [[User:AcountName| Your Name]]<br />
<br />
''Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved''<br />
* Email: <your email address so we can contact you, invite you to meetings, etc.><br />
<br />
== Current status ==<br />
* Targeted release: (SUGAR_VERSION)<br />
* Last updated: (DATE)<br />
* Percentage of completion: XX%<br />
<br />
== Detailed Description ==<br />
''Expand on the summary, if appropriate. A couple of sentences suffices to explain the goal, but the more details you can provide the better.''<br />
<br />
== Benefit to Sugar ==<br />
''What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''<br />
<br />
''Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.''<br />
<br />
== Scope ==<br />
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''<br />
<br />
==UI Design==<br />
''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.''<br />
<br />
== How To Test ==<br />
{{:{{PAGENAME}}/Testing}}<br />
== User Experience ==<br />
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''<br />
<br />
== Dependencies ==<br />
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''<br />
<br />
== Contingency Plan ==<br />
''If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''<br />
<br />
== Documentation ==<br />
''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''<br />
<br />
== Release Notes ==<br />
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''<br />
<br />
== Comments and Discussion ==<br />
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. --></div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_release_process&diff=55154Sugar on a Stick release process2010-07-28T06:49:20Z<p>Mchua: /* Features submitted for review */</p>
<hr />
<div><noinclude><div id="contentSub">< [[Sugar on a Stick]]</div>{{TOCright}}[[Category:Sugar on a Stick]]</noinclude><br />
== Feature process ==<br />
<br />
The feature process for Sugar on a Stick aims at providing a structured way of implementing and keeping track of upcoming features for the next release of Sugar on a Stick. This document outlines the guidelines for submitting feature proposals. An important thing to realize is the release schedule for each release.<br />
<br />
* ''What is a feature?'' A feature is defined as a significant change or enhancement to the version of Sugar on a Stick currently under development that may or may not include new packages and also relate to features of both Fedora and Sugar<br />
* ''What are the deadlines?'' The deadlines for the release currently under development are outlined in the [[Sugar_on_a_Stick#Release_schedule|release schedule]].<br />
* ''What do I get with a feature?'' Having your feature approved not only helps everybody involved in the development and engineering process to keep track of its state, but also allows other teams - like the [[Marketing_Team|marketing team]] - to leverage your work and promote it.<br />
* ''What are my responsibilities?'' By signing up for a feature, you sign up for taking care of it. That means you'll be the one responsible for providing updates and interacting with the different teams concerned by your feature, like the release engineering for Sugar on a Stick. It does, however, not mean that you've to realize your feature all alone - go out and tell the [http://lists.sugarlabs.org lists] and the [http://planet.sugarlabs.org planet] about your work. Get people excited to help you!<br />
* ''How does evaluation happen?'' Your proposal needs a majority of ''YAY'' votes from the release team (determined for a given release by the release manager - the v4 release manager is Sebastian Dziallas, and the current relase team is formed by Peter Robinson, Mel Chua and Sebastian Dziallas) to get approval. Discussion will happen at a weekly meeting, while the decisions will be announced to the SoaS mailing list.'''<br />
* ''What if my feature got rejected?'' No worries! Features that are originally rejected can be revised and resubmitted.<br />
<br />
=== How to submit a feature for consideration ===<br />
# Fill out the [[Features/Feature_Template|template]] and stick it on a page in the wiki. ('''TODO:''' create ''Category:SoaS_v4_Feature'' so people can make their pages belong to the appropriate category so that we know which version you're targeting ).<br />
# Place a link to your proposal in the [[#Current feature ideas]] section of this page while you're working on the document.<br />
# Send an email to the SoaS [http://lists.sugarlabs.org/listinfo/soas list] and incorporate any feedback you might receive.<br />
# When you think your feature proposal is ready, move it to the [[#Features submitted for review]] section of this page. It will be brought up at the next [[Sugar on a Stick meeting]], where it'll be evaluated and voted on. We might ask you to make further adjustments and revisit it at a later point or approve the feature directly. We're looking forward to hearing about your ideas!<br />
<br />
=== Approved features for the current release ===<br />
<br />
''Features must be added to this list by a member of the release team. Place complete feature proposals in the [[#Features submitted for review]] section for consideration at the next meeting.''<br />
<br />
* [[Features/Sugar_0.90|Sugar 0.90]]<br />
* [[Features/Revised_Browse_default-bookmarks.html]]<br />
<br />
=== Features submitted for review ===<br />
<br />
When your feature proposal is complete and ready to review, add it to the list below. These will be considered at the next [[Sugar on a Stick meeting]].<br />
<br />
* [[Updated Activities from the Mirabelle list]] (still being edited)<br />
* Remixability [http://wiki.sugarlabs.org/go/Features/Soas_V4/Remixability] (still being edited)<br />
* Including Fructose Activities that are tested and known to work (still being edited)<br />
* [[More robust iso]] (still being edited)<br />
<br />
=== Current feature ideas ===<br />
<br />
These feature ideas are in various stages of development.<br />
<br />
* School server<br />
* [[Kickstart generator]]<br />
* btrfs and snapshots<br />
* systemd<br />
* Control Panel section for setting display parameters (e.g., VGA out)<br />
* Simplifying Making a Custom remix and sharing the .ksfile and the CD.iso files on the wiki[http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Build_Your_Own_Remix_-.28not_included_on_SCK.DVD.29]<br />
* Remixability [http://wiki.sugarlabs.org/go/Features/Soas_V4/Remixability]<br />
<br />
== Testing process ==<br />
<br />
Our test process, which is under construction, will consist of the following: <br />
<br />
# An agreed-upon image each week for testers to attack (the daily build on $datetime of each week, for instance)<br />
# An agreed-upon set of test cases for them to execute (iow, the "test plan" thing we haven't had before)<br />
# An agreed-upon place and format for the results from running those test cases to be reported to<br />
# An agreed-upon $datetime each week by which all test results for that week will be submitted - so that the development team has a chance to look at those results and revise the build before the next test image goes out.<br />
<br />
The first thing we are doing is getting a weekly image under test to automatically appear at a static link; see [[#Test image]] below. We are going to set up a cron job so the nightly build (from http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ - which we need to start up again from the Fedora side) grabs and archives the appropriate image-under-test each week.<br />
<br />
The last weekly testing update was 6/21/2010: http://lists.sugarlabs.org/archive/soas/2010-June/001560.html<br />
<br />
=== Test image ===<br />
<br />
<big><big><!--[http://download.sugarlabs.org/soas/test/soas-i386-test-latest.iso Download the current image under test]-->[http://people.sugarlabs.org/Tgillard/soas-v4-0725-Remix.iso Download the current (temporary) image under test]</big></big><br />
: Presence service needs to be activated by entering '''setenforce 0''' in root terminal<br />
<br />
'''SPECIAL UPDATE, July 27, 2010: This week's test image is a remix by Tom Gillard due to a [https://bugzilla.redhat.com/show_bug.cgi?id=617115 bug in upstream Fedora] that prevents the automatically generated test image from booting.''' The normal test case image is available at http://download.sugarlabs.org/soas/test/soas-i386-test-latest.iso and this page will be edited when it works once again.<br />
<br />
The test image is the most recent [http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ nightly build] as of 23:59:59 on the most recent Thursday. Past test images are available at http://download.sugarlabs.org/soas/test/.<br />
<br />
=== Test cases ===<br />
<br />
We do not yet have test cases. They will appear here when they are available.<br />
:Note: See Discussion for Notes on testing<br />
* Prototype Tests:<br />
: Activity Testing http://wiki.sugarlabs.org/go/Features/Soas_V4/ASLOxo_Activity_Test_Table based on [http://people.sugarlabs.org/Tgillard/Activities-Index-ASLO-f13-Mirabelle-f14-rawhide-Soas-tests-GC.ods]<br />
: Install Testing http://wiki.sugarlabs.org/go/Talk:Features/Soas_V4/Install_Test_Table<br />
: http://wiki.sugarlabs.org/go/0.90/Testing<br />
<br />
=== Test results ===<br />
<br />
A basic template for reporting simple smoke test results is [[Features/Soas V4/ASLOxo Activity Test Table]]. This needs to be moved to a proper namespace, and instructions need to be written. Instructions will be listed here when they are available.</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_release_process&diff=55153Sugar on a Stick release process2010-07-28T06:48:51Z<p>Mchua: /* Current feature ideas */</p>
<hr />
<div><noinclude><div id="contentSub">< [[Sugar on a Stick]]</div>{{TOCright}}[[Category:Sugar on a Stick]]</noinclude><br />
== Feature process ==<br />
<br />
The feature process for Sugar on a Stick aims at providing a structured way of implementing and keeping track of upcoming features for the next release of Sugar on a Stick. This document outlines the guidelines for submitting feature proposals. An important thing to realize is the release schedule for each release.<br />
<br />
* ''What is a feature?'' A feature is defined as a significant change or enhancement to the version of Sugar on a Stick currently under development that may or may not include new packages and also relate to features of both Fedora and Sugar<br />
* ''What are the deadlines?'' The deadlines for the release currently under development are outlined in the [[Sugar_on_a_Stick#Release_schedule|release schedule]].<br />
* ''What do I get with a feature?'' Having your feature approved not only helps everybody involved in the development and engineering process to keep track of its state, but also allows other teams - like the [[Marketing_Team|marketing team]] - to leverage your work and promote it.<br />
* ''What are my responsibilities?'' By signing up for a feature, you sign up for taking care of it. That means you'll be the one responsible for providing updates and interacting with the different teams concerned by your feature, like the release engineering for Sugar on a Stick. It does, however, not mean that you've to realize your feature all alone - go out and tell the [http://lists.sugarlabs.org lists] and the [http://planet.sugarlabs.org planet] about your work. Get people excited to help you!<br />
* ''How does evaluation happen?'' Your proposal needs a majority of ''YAY'' votes from the release team (determined for a given release by the release manager - the v4 release manager is Sebastian Dziallas, and the current relase team is formed by Peter Robinson, Mel Chua and Sebastian Dziallas) to get approval. Discussion will happen at a weekly meeting, while the decisions will be announced to the SoaS mailing list.'''<br />
* ''What if my feature got rejected?'' No worries! Features that are originally rejected can be revised and resubmitted.<br />
<br />
=== How to submit a feature for consideration ===<br />
# Fill out the [[Features/Feature_Template|template]] and stick it on a page in the wiki. ('''TODO:''' create ''Category:SoaS_v4_Feature'' so people can make their pages belong to the appropriate category so that we know which version you're targeting ).<br />
# Place a link to your proposal in the [[#Current feature ideas]] section of this page while you're working on the document.<br />
# Send an email to the SoaS [http://lists.sugarlabs.org/listinfo/soas list] and incorporate any feedback you might receive.<br />
# When you think your feature proposal is ready, move it to the [[#Features submitted for review]] section of this page. It will be brought up at the next [[Sugar on a Stick meeting]], where it'll be evaluated and voted on. We might ask you to make further adjustments and revisit it at a later point or approve the feature directly. We're looking forward to hearing about your ideas!<br />
<br />
=== Approved features for the current release ===<br />
<br />
''Features must be added to this list by a member of the release team. Place complete feature proposals in the [[#Features submitted for review]] section for consideration at the next meeting.''<br />
<br />
* [[Features/Sugar_0.90|Sugar 0.90]]<br />
* [[Features/Revised_Browse_default-bookmarks.html]]<br />
<br />
=== Features submitted for review ===<br />
<br />
When your feature proposal is complete and ready to review, add it to the list below. These will be considered at the next [[Sugar on a Stick meeting]].<br />
<br />
* [[Updated Activities from the Mirabelle list]] (still being edited)<br />
* Remixability [http://wiki.sugarlabs.org/go/Features/Soas_V4/Remixability] (still being edited)<br />
* Including Fructose Activities that are tested and known to work<br />
<br />
=== Current feature ideas ===<br />
<br />
These feature ideas are in various stages of development.<br />
<br />
* School server<br />
* [[Kickstart generator]]<br />
* btrfs and snapshots<br />
* systemd<br />
* Control Panel section for setting display parameters (e.g., VGA out)<br />
* Simplifying Making a Custom remix and sharing the .ksfile and the CD.iso files on the wiki[http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Build_Your_Own_Remix_-.28not_included_on_SCK.DVD.29]<br />
* Remixability [http://wiki.sugarlabs.org/go/Features/Soas_V4/Remixability]<br />
<br />
== Testing process ==<br />
<br />
Our test process, which is under construction, will consist of the following: <br />
<br />
# An agreed-upon image each week for testers to attack (the daily build on $datetime of each week, for instance)<br />
# An agreed-upon set of test cases for them to execute (iow, the "test plan" thing we haven't had before)<br />
# An agreed-upon place and format for the results from running those test cases to be reported to<br />
# An agreed-upon $datetime each week by which all test results for that week will be submitted - so that the development team has a chance to look at those results and revise the build before the next test image goes out.<br />
<br />
The first thing we are doing is getting a weekly image under test to automatically appear at a static link; see [[#Test image]] below. We are going to set up a cron job so the nightly build (from http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ - which we need to start up again from the Fedora side) grabs and archives the appropriate image-under-test each week.<br />
<br />
The last weekly testing update was 6/21/2010: http://lists.sugarlabs.org/archive/soas/2010-June/001560.html<br />
<br />
=== Test image ===<br />
<br />
<big><big><!--[http://download.sugarlabs.org/soas/test/soas-i386-test-latest.iso Download the current image under test]-->[http://people.sugarlabs.org/Tgillard/soas-v4-0725-Remix.iso Download the current (temporary) image under test]</big></big><br />
: Presence service needs to be activated by entering '''setenforce 0''' in root terminal<br />
<br />
'''SPECIAL UPDATE, July 27, 2010: This week's test image is a remix by Tom Gillard due to a [https://bugzilla.redhat.com/show_bug.cgi?id=617115 bug in upstream Fedora] that prevents the automatically generated test image from booting.''' The normal test case image is available at http://download.sugarlabs.org/soas/test/soas-i386-test-latest.iso and this page will be edited when it works once again.<br />
<br />
The test image is the most recent [http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ nightly build] as of 23:59:59 on the most recent Thursday. Past test images are available at http://download.sugarlabs.org/soas/test/.<br />
<br />
=== Test cases ===<br />
<br />
We do not yet have test cases. They will appear here when they are available.<br />
:Note: See Discussion for Notes on testing<br />
* Prototype Tests:<br />
: Activity Testing http://wiki.sugarlabs.org/go/Features/Soas_V4/ASLOxo_Activity_Test_Table based on [http://people.sugarlabs.org/Tgillard/Activities-Index-ASLO-f13-Mirabelle-f14-rawhide-Soas-tests-GC.ods]<br />
: Install Testing http://wiki.sugarlabs.org/go/Talk:Features/Soas_V4/Install_Test_Table<br />
: http://wiki.sugarlabs.org/go/0.90/Testing<br />
<br />
=== Test results ===<br />
<br />
A basic template for reporting simple smoke test results is [[Features/Soas V4/ASLOxo Activity Test Table]]. This needs to be moved to a proper namespace, and instructions need to be written. Instructions will be listed here when they are available.</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_release_process&diff=55152Sugar on a Stick release process2010-07-28T06:48:40Z<p>Mchua: /* Features submitted for review */</p>
<hr />
<div><noinclude><div id="contentSub">< [[Sugar on a Stick]]</div>{{TOCright}}[[Category:Sugar on a Stick]]</noinclude><br />
== Feature process ==<br />
<br />
The feature process for Sugar on a Stick aims at providing a structured way of implementing and keeping track of upcoming features for the next release of Sugar on a Stick. This document outlines the guidelines for submitting feature proposals. An important thing to realize is the release schedule for each release.<br />
<br />
* ''What is a feature?'' A feature is defined as a significant change or enhancement to the version of Sugar on a Stick currently under development that may or may not include new packages and also relate to features of both Fedora and Sugar<br />
* ''What are the deadlines?'' The deadlines for the release currently under development are outlined in the [[Sugar_on_a_Stick#Release_schedule|release schedule]].<br />
* ''What do I get with a feature?'' Having your feature approved not only helps everybody involved in the development and engineering process to keep track of its state, but also allows other teams - like the [[Marketing_Team|marketing team]] - to leverage your work and promote it.<br />
* ''What are my responsibilities?'' By signing up for a feature, you sign up for taking care of it. That means you'll be the one responsible for providing updates and interacting with the different teams concerned by your feature, like the release engineering for Sugar on a Stick. It does, however, not mean that you've to realize your feature all alone - go out and tell the [http://lists.sugarlabs.org lists] and the [http://planet.sugarlabs.org planet] about your work. Get people excited to help you!<br />
* ''How does evaluation happen?'' Your proposal needs a majority of ''YAY'' votes from the release team (determined for a given release by the release manager - the v4 release manager is Sebastian Dziallas, and the current relase team is formed by Peter Robinson, Mel Chua and Sebastian Dziallas) to get approval. Discussion will happen at a weekly meeting, while the decisions will be announced to the SoaS mailing list.'''<br />
* ''What if my feature got rejected?'' No worries! Features that are originally rejected can be revised and resubmitted.<br />
<br />
=== How to submit a feature for consideration ===<br />
# Fill out the [[Features/Feature_Template|template]] and stick it on a page in the wiki. ('''TODO:''' create ''Category:SoaS_v4_Feature'' so people can make their pages belong to the appropriate category so that we know which version you're targeting ).<br />
# Place a link to your proposal in the [[#Current feature ideas]] section of this page while you're working on the document.<br />
# Send an email to the SoaS [http://lists.sugarlabs.org/listinfo/soas list] and incorporate any feedback you might receive.<br />
# When you think your feature proposal is ready, move it to the [[#Features submitted for review]] section of this page. It will be brought up at the next [[Sugar on a Stick meeting]], where it'll be evaluated and voted on. We might ask you to make further adjustments and revisit it at a later point or approve the feature directly. We're looking forward to hearing about your ideas!<br />
<br />
=== Approved features for the current release ===<br />
<br />
''Features must be added to this list by a member of the release team. Place complete feature proposals in the [[#Features submitted for review]] section for consideration at the next meeting.''<br />
<br />
* [[Features/Sugar_0.90|Sugar 0.90]]<br />
* [[Features/Revised_Browse_default-bookmarks.html]]<br />
<br />
=== Features submitted for review ===<br />
<br />
When your feature proposal is complete and ready to review, add it to the list below. These will be considered at the next [[Sugar on a Stick meeting]].<br />
<br />
* [[Updated Activities from the Mirabelle list]] (still being edited)<br />
* Remixability [http://wiki.sugarlabs.org/go/Features/Soas_V4/Remixability] (still being edited)<br />
* Including Fructose Activities that are tested and known to work<br />
<br />
=== Current feature ideas ===<br />
<br />
These feature ideas are in various stages of development.<br />
<br />
* School server<br />
* [[Kickstart generator]]<br />
* btrfs and snapshots<br />
* systemd<br />
* [[More robust iso]]<br />
* Control Panel section for setting display parameters (e.g., VGA out)<br />
* Simplifying Making a Custom remix and sharing the .ksfile and the CD.iso files on the wiki[http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Build_Your_Own_Remix_-.28not_included_on_SCK.DVD.29]<br />
* Remixability [http://wiki.sugarlabs.org/go/Features/Soas_V4/Remixability]<br />
<br />
== Testing process ==<br />
<br />
Our test process, which is under construction, will consist of the following: <br />
<br />
# An agreed-upon image each week for testers to attack (the daily build on $datetime of each week, for instance)<br />
# An agreed-upon set of test cases for them to execute (iow, the "test plan" thing we haven't had before)<br />
# An agreed-upon place and format for the results from running those test cases to be reported to<br />
# An agreed-upon $datetime each week by which all test results for that week will be submitted - so that the development team has a chance to look at those results and revise the build before the next test image goes out.<br />
<br />
The first thing we are doing is getting a weekly image under test to automatically appear at a static link; see [[#Test image]] below. We are going to set up a cron job so the nightly build (from http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ - which we need to start up again from the Fedora side) grabs and archives the appropriate image-under-test each week.<br />
<br />
The last weekly testing update was 6/21/2010: http://lists.sugarlabs.org/archive/soas/2010-June/001560.html<br />
<br />
=== Test image ===<br />
<br />
<big><big><!--[http://download.sugarlabs.org/soas/test/soas-i386-test-latest.iso Download the current image under test]-->[http://people.sugarlabs.org/Tgillard/soas-v4-0725-Remix.iso Download the current (temporary) image under test]</big></big><br />
: Presence service needs to be activated by entering '''setenforce 0''' in root terminal<br />
<br />
'''SPECIAL UPDATE, July 27, 2010: This week's test image is a remix by Tom Gillard due to a [https://bugzilla.redhat.com/show_bug.cgi?id=617115 bug in upstream Fedora] that prevents the automatically generated test image from booting.''' The normal test case image is available at http://download.sugarlabs.org/soas/test/soas-i386-test-latest.iso and this page will be edited when it works once again.<br />
<br />
The test image is the most recent [http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ nightly build] as of 23:59:59 on the most recent Thursday. Past test images are available at http://download.sugarlabs.org/soas/test/.<br />
<br />
=== Test cases ===<br />
<br />
We do not yet have test cases. They will appear here when they are available.<br />
:Note: See Discussion for Notes on testing<br />
* Prototype Tests:<br />
: Activity Testing http://wiki.sugarlabs.org/go/Features/Soas_V4/ASLOxo_Activity_Test_Table based on [http://people.sugarlabs.org/Tgillard/Activities-Index-ASLO-f13-Mirabelle-f14-rawhide-Soas-tests-GC.ods]<br />
: Install Testing http://wiki.sugarlabs.org/go/Talk:Features/Soas_V4/Install_Test_Table<br />
: http://wiki.sugarlabs.org/go/0.90/Testing<br />
<br />
=== Test results ===<br />
<br />
A basic template for reporting simple smoke test results is [[Features/Soas V4/ASLOxo Activity Test Table]]. This needs to be moved to a proper namespace, and instructions need to be written. Instructions will be listed here when they are available.</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_release_process&diff=54845Sugar on a Stick release process2010-07-27T11:27:19Z<p>Mchua: /* Testing process */</p>
<hr />
<div><noinclude><div id="contentSub">< [[Sugar on a Stick]]</div>{{TOCright}}[[Category:Sugar on a Stick]]</noinclude><br />
== Feature process ==<br />
<br />
The feature process for Sugar on a Stick aims at providing a structured way of implementing and keeping track of upcoming features for the next release of Sugar on a Stick. This document outlines the guidelines for submitting feature proposals. An important thing to realize is the release schedule for each release.<br />
<br />
* ''What is a feature?'' A feature is defined as a significant change or enhancement to the version of Sugar on a Stick currently under development that may or may not include new packages and also relate to features of both Fedora and Sugar<br />
* ''What are the deadlines?'' The deadlines for the release currently under development are outlined in the [[Sugar_on_a_Stick#Release_schedule|release schedule]].<br />
* ''What do I get with a feature?'' Having your feature approved not only helps everybody involved in the development and engineering process to keep track of its state, but also allows other teams - like the [[Marketing_Team|marketing team]] - to leverage your work and promote it.<br />
* ''What are my responsibilities?'' By signing up for a feature, you sign up for taking care of it. That means you'll be the one responsible for providing updates and interacting with the different teams concerned by your feature, like the release engineering for Sugar on a Stick. It does, however, not mean that you've to realize your feature all alone - go out and tell the [http://lists.sugarlabs.org lists] and the [http://planet.sugarlabs.org planet] about your work. Get people excited to help you!<br />
* ''How does evaluation happen?'' Your proposal needs a majority of ''YAY'' votes from the release team (determined for a given release by the release manager - the v4 release manager is Sebastian Dziallas, and the current relase team is formed by Peter Robinson, Mel Chua and Sebastian Dziallas) to get approval. Discussion will happen at a weekly meeting, while the decisions will be announced to the SoaS mailing list.'''<br />
* ''What if my feature got rejected?'' No worries! Features that are originally rejected can be revised and resubmitted.<br />
<br />
=== How to submit a feature for consideration ===<br />
# Fill out the [[Features/Feature_Template|template]] and stick it on a page in the wiki. ('''TODO:''' create ''Category:SoaS_v4_Feature'' so people can make their pages belong to the appropriate category so that we know which version you're targeting ).<br />
# Place a link to your proposal in the [[#Current feature ideas]] section of this page while you're working on the document.<br />
# Send an email to the SoaS [http://lists.sugarlabs.org/listinfo/soas list] and incorporate any feedback you might receive.<br />
# When you think your feature proposal is ready, move it to the [[#Features submitted for review]] section of this page. It will be brought up at the next [[Sugar on a Stick meeting]], where it'll be evaluated and voted on. We might ask you to make further adjustments and revisit it at a later point or approve the feature directly. We're looking forward to hearing about your ideas!<br />
<br />
=== Approved features for the current release ===<br />
<br />
''Features must be added to this list by a member of the release team. Place complete feature proposals in the [[#Features submitted for review]] section for consideration at the next meeting.''<br />
<br />
* [[Features/Sugar_0.90|Sugar 0.90]]<br />
* [[Features/Revised_Browse_default-bookmarks.html]]<br />
<br />
=== Features submitted for review ===<br />
<br />
When your feature proposal is complete and ready to review, add it to the list below. These will be considered at the next [[Sugar on a Stick meeting]].<br />
<br />
* [[Updated Activities from the Mirabelle list]]<br />
* Remixability [http://wiki.sugarlabs.org/go/Features/Soas_V4/Remixability]<br />
* Add feature here<br />
<br />
=== Current feature ideas ===<br />
<br />
These feature ideas are in various stages of development.<br />
<br />
* School server<br />
* [[Kickstart generator]]<br />
* btrfs and snapshots<br />
* systemd<br />
* [[More robust iso]]<br />
* Control Panel section for setting display parameters (e.g., VGA out)<br />
* Simplifying Making a Custom remix and sharing the .ksfile and the CD.iso files on the wiki[http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Build_Your_Own_Remix_-.28not_included_on_SCK.DVD.29]<br />
* Remixability [http://wiki.sugarlabs.org/go/Features/Soas_V4/Remixability]<br />
<br />
== Testing process ==<br />
<br />
Our test process, which is under construction, will consist of the following: <br />
<br />
# An agreed-upon image each week for testers to attack (the daily build on $datetime of each week, for instance)<br />
# An agreed-upon set of test cases for them to execute (iow, the "test plan" thing we haven't had before)<br />
# An agreed-upon place and format for the results from running those test cases to be reported to<br />
# An agreed-upon $datetime each week by which all test results for that week will be submitted - so that the development team has a chance to look at those results and revise the build before the next test image goes out.<br />
<br />
The first thing we are doing is getting a weekly image under test to automatically appear at a static link; see [[#Test image]] below. We are going to set up a cron job so the nightly build (from http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ - which we need to start up again from the Fedora side) grabs and archives the appropriate image-under-test each week.<br />
<br />
The last weekly testing update was 6/21/2010: http://lists.sugarlabs.org/archive/soas/2010-June/001560.html<br />
<br />
=== Test image ===<br />
<br />
<big><big><!--[http://download.sugarlabs.org/soas/test/soas-i386-test-latest.iso Download the current image under test]-->[http://people.sugarlabs.org/Tgillard/soas-v4-0725-Remix.iso Download the current (temporary) image under test]</big></big><br />
<br />
'''SPECIAL UPDATE, July 27, 2010: This week's test image is a remix by Tom Gillard due to a [https://bugzilla.redhat.com/show_bug.cgi?id=617115 bug in upstream Fedora] that prevents the automatically generated test image from booting.''' The normal test case image is available at http://download.sugarlabs.org/soas/test/soas-i386-test-latest.iso and this page will be edited when it works once again.<br />
<br />
The test image is the most recent [http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ nightly build] as of 23:59:59 on the most recent Thursday. We're currently pulling it manually, but ticket [http://bugs.sugarlabs.org/ticket/2058 #2058] is for a cron job to automate this (if you know bash scripting, please help!) Past test images are available at http://download.sugarlabs.org/soas/test/.<br />
<br />
=== Test cases ===<br />
<br />
We do not yet have test cases. They will appear here when they are available.<br />
:Note: See Discussion for Notes on testing<br />
* Prototype Tests:<br />
: Activity Testing http://wiki.sugarlabs.org/go/Features/Soas_V4/ASLOxo_Activity_Test_Table based on [http://people.sugarlabs.org/Tgillard/Activities-Index-ASLO-f13-Mirabelle-f14-rawhide-Soas-tests-GC.ods]<br />
: Install Testing http://wiki.sugarlabs.org/go/Talk:Features/Soas_V4/Install_Test_Table<br />
: http://wiki.sugarlabs.org/go/0.90/Testing<br />
<br />
=== Test results ===<br />
<br />
A basic template for reporting simple smoke test results is [[Features/Soas V4/ASLOxo Activity Test Table]]. This needs to be moved to a proper namespace, and instructions need to be written. Instructions will be listed here when they are available.</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_meetings&diff=54826Sugar on a Stick meetings2010-07-26T20:10:44Z<p>Mchua: /* Minutes */</p>
<hr />
<div><noinclude><div id="contentSub">< [[Sugar on a Stick]]</div><br />
<noinclude>{{TOCright}}[[Category:Meetings]]</noinclude><br />
== Meeting details ==<br />
<br />
Regular meetings for [[Sugar on a Stick]] take place on '''[irc://irc.freenode.net irc.freenode.net]''' in '''#sugar-meeting''', every '''Monday''' at '''1900 UTC'''.<br />
<br />
We use [[IRC]] for our meetings. If you don't have an IRC client (yet), you can use webchat - go to http://webchat.freenode.net and connect to #sugar-meeting, or click the screenshot below. (Replace "your_name" or the random ID provided with your name or some other nick you'd like to be known by.)<br />
<br />
[[File:Freenode-webchat-screenshot.png|left|link=http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1]]<br />
<br />
== How we run meetings ==<br />
<br />
With as much involvement as possible at all times.<br />
<br />
The motivation is to have as many simultaneous actively participating people in the meeting as possible - ideally, at ''all times'' in the meeting, ''everyone'' in the meeting should be ''doing something really cool'' (and hopefully related to Sugar on a Stick) - not just waiting for their turn to speak. Think of it as a virtual version of the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Philosophy law of two feet].<br />
<br />
Are YOU running a SoaS meeting? Take a look at [[How to run a meeting]] for an example of how a meeting is run, with commands listed out.<br />
<br />
== Agenda ==<br />
<br />
{{Anchor|Next_Meeting}}<br />
<br />
=== Every meeting ===<br />
<br />
* [[Sugar on a Stick#Release schedule]] upcoming deadlines announcement<br />
* [[Sugar on a Stick release process#Features submitted for review]]<br />
* [[Sugar_on_a_Stick_release_process#Testing_process]]<br />
<br />
=== Upcoming meeting ===<br />
<br />
* add agenda items here<br />
<br />
== Future topics ==<br />
<br />
== Procedure for Minutes and Logging ==<br />
<br />
See the instructions on [[how to run a meeting]].<br />
<br />
== Minutes ==<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100726_1507.html 2010-07-26 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100726_1507.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100719_1506.html 2010-07-19 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100719_1506.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100712_1503.html 2010-07-12 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100712_1503.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100705_1502.html 2010-07-05 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100705_1502.html (log)]<br />
* 2010-06-28 (no meeting)<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100621_1502.html 2010-06-21 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100621_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100614_1502.html 2010-06-14 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100614_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100607_1510.html 2010-06-07 Sugar on a Stick v4 Planning Meeting (regular weekly time)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100531_1507.html 2010-05-31 v3 Mirabelle Release Review Meeting (regular weekly time)]</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_meetings&diff=54825Sugar on a Stick meetings2010-07-26T20:09:45Z<p>Mchua: /* Every meeting */</p>
<hr />
<div><noinclude><div id="contentSub">< [[Sugar on a Stick]]</div><br />
<noinclude>{{TOCright}}[[Category:Meetings]]</noinclude><br />
== Meeting details ==<br />
<br />
Regular meetings for [[Sugar on a Stick]] take place on '''[irc://irc.freenode.net irc.freenode.net]''' in '''#sugar-meeting''', every '''Monday''' at '''1900 UTC'''.<br />
<br />
We use [[IRC]] for our meetings. If you don't have an IRC client (yet), you can use webchat - go to http://webchat.freenode.net and connect to #sugar-meeting, or click the screenshot below. (Replace "your_name" or the random ID provided with your name or some other nick you'd like to be known by.)<br />
<br />
[[File:Freenode-webchat-screenshot.png|left|link=http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1]]<br />
<br />
== How we run meetings ==<br />
<br />
With as much involvement as possible at all times.<br />
<br />
The motivation is to have as many simultaneous actively participating people in the meeting as possible - ideally, at ''all times'' in the meeting, ''everyone'' in the meeting should be ''doing something really cool'' (and hopefully related to Sugar on a Stick) - not just waiting for their turn to speak. Think of it as a virtual version of the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Philosophy law of two feet].<br />
<br />
Are YOU running a SoaS meeting? Take a look at [[How to run a meeting]] for an example of how a meeting is run, with commands listed out.<br />
<br />
== Agenda ==<br />
<br />
{{Anchor|Next_Meeting}}<br />
<br />
=== Every meeting ===<br />
<br />
* [[Sugar on a Stick#Release schedule]] upcoming deadlines announcement<br />
* [[Sugar on a Stick release process#Features submitted for review]]<br />
* [[Sugar_on_a_Stick_release_process#Testing_process]]<br />
<br />
=== Upcoming meeting ===<br />
<br />
* add agenda items here<br />
<br />
== Future topics ==<br />
<br />
== Procedure for Minutes and Logging ==<br />
<br />
See the instructions on [[how to run a meeting]].<br />
<br />
== Minutes ==<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100719_1506.html 2010-07-19 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100719_1506.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100712_1503.html 2010-07-12 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100712_1503.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100705_1502.html 2010-07-05 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100705_1502.html (log)]<br />
* 2010-06-28 (no meeting)<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100621_1502.html 2010-06-21 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100621_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100614_1502.html 2010-06-14 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100614_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100607_1510.html 2010-06-07 Sugar on a Stick v4 Planning Meeting (regular weekly time)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100531_1507.html 2010-05-31 v3 Mirabelle Release Review Meeting (regular weekly time)]</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_meetings&diff=54824Sugar on a Stick meetings2010-07-26T20:07:02Z<p>Mchua: /* Upcoming meeting */</p>
<hr />
<div><noinclude><div id="contentSub">< [[Sugar on a Stick]]</div><br />
<noinclude>{{TOCright}}[[Category:Meetings]]</noinclude><br />
== Meeting details ==<br />
<br />
Regular meetings for [[Sugar on a Stick]] take place on '''[irc://irc.freenode.net irc.freenode.net]''' in '''#sugar-meeting''', every '''Monday''' at '''1900 UTC'''.<br />
<br />
We use [[IRC]] for our meetings. If you don't have an IRC client (yet), you can use webchat - go to http://webchat.freenode.net and connect to #sugar-meeting, or click the screenshot below. (Replace "your_name" or the random ID provided with your name or some other nick you'd like to be known by.)<br />
<br />
[[File:Freenode-webchat-screenshot.png|left|link=http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1]]<br />
<br />
== How we run meetings ==<br />
<br />
With as much involvement as possible at all times.<br />
<br />
The motivation is to have as many simultaneous actively participating people in the meeting as possible - ideally, at ''all times'' in the meeting, ''everyone'' in the meeting should be ''doing something really cool'' (and hopefully related to Sugar on a Stick) - not just waiting for their turn to speak. Think of it as a virtual version of the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Philosophy law of two feet].<br />
<br />
Are YOU running a SoaS meeting? Take a look at [[How to run a meeting]] for an example of how a meeting is run, with commands listed out.<br />
<br />
== Agenda ==<br />
<br />
{{Anchor|Next_Meeting}}<br />
<br />
=== Every meeting ===<br />
<br />
* [[Sugar on a Stick#Release schedule]] upcoming deadlines announcement<br />
* [[Sugar on a Stick release process#Features submitted for review]]<br />
<br />
=== Upcoming meeting ===<br />
<br />
* add agenda items here<br />
<br />
== Future topics ==<br />
<br />
== Procedure for Minutes and Logging ==<br />
<br />
See the instructions on [[how to run a meeting]].<br />
<br />
== Minutes ==<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100719_1506.html 2010-07-19 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100719_1506.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100712_1503.html 2010-07-12 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100712_1503.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100705_1502.html 2010-07-05 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100705_1502.html (log)]<br />
* 2010-06-28 (no meeting)<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100621_1502.html 2010-06-21 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100621_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100614_1502.html 2010-06-14 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100614_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100607_1510.html 2010-06-07 Sugar on a Stick v4 Planning Meeting (regular weekly time)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100531_1507.html 2010-05-31 v3 Mirabelle Release Review Meeting (regular weekly time)]</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Updated_Activities_from_the_Mirabelle_list&diff=54816Updated Activities from the Mirabelle list2010-07-26T19:16:15Z<p>Mchua: Created page with '<Feature Name> <!-- You can add categories to tie features back to real deployments/schools requesting them, for example [[Category:Features requested by Sc...'</p>
<hr />
<div>[[Category:Feature|<Feature Name>]]<br />
<!-- You can add categories to tie features back to real deployments/schools requesting them, for example <br />
[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). --><br />
</noinclude><br />
<br />
'''Comments and Explanations:'''<br />
<br />
There are comments (in italic) providing guidance to fill out each section, see also the [[Features/Policy|Feature Policy Page]] for a more detailed explanation of the new-feature process. '''Copy the source to a ''new page'' named Features/''Your Feature Name'' before making changes! DO NOT EDIT THIS TEMPLATE.'''<br />
<br />
<!-- All fields on this form are required to be accepted.<br />
We also request that you maintain the same order of sections so that all of the feature pages are uniform. --><br />
<br />
<!-- The actual name of your feature page should look something like: Features/Your Feature Name. This keeps all features in the same namespace --><br />
<br />
== Summary ==<br />
''A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release.''<br />
<br />
== Owner ==<br />
''This should link to your home wiki page so we know who you are''<br />
* Name: [[User:AcountName| Your Name]]<br />
<br />
''Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved''<br />
* Email: <your email address so we can contact you, invite you to meetings, etc.><br />
<br />
== Current status ==<br />
* Targeted release: (SUGAR_VERSION)<br />
* Last updated: (DATE)<br />
* Percentage of completion: XX%<br />
<br />
== Detailed Description ==<br />
''Expand on the summary, if appropriate. A couple of sentences suffices to explain the goal, but the more details you can provide the better.''<br />
<br />
== Benefit to Sugar ==<br />
''What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''<br />
<br />
''Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.''<br />
<br />
== Scope ==<br />
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''<br />
<br />
==UI Design==<br />
''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.''<br />
<br />
== How To Test ==<br />
{{:{{PAGENAME}}/Testing}}<br />
== User Experience ==<br />
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''<br />
<br />
== Dependencies ==<br />
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''<br />
<br />
== Contingency Plan ==<br />
''If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''<br />
<br />
== Documentation ==<br />
''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''<br />
<br />
== Release Notes ==<br />
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''<br />
<br />
== Comments and Discussion ==<br />
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. --></div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_release_process&diff=54815Sugar on a Stick release process2010-07-26T19:15:25Z<p>Mchua: /* Features submitted for review */</p>
<hr />
<div><noinclude><div id="contentSub">< [[Sugar on a Stick]]</div>{{TOCright}}[[Category:Sugar on a Stick]]</noinclude><br />
== Feature process ==<br />
<br />
The feature process for Sugar on a Stick aims at providing a structured way of implementing and keeping track of upcoming features for the next release of Sugar on a Stick. This document outlines the guidelines for submitting feature proposals. An important thing to realize is the release schedule for each release.<br />
<br />
* ''What is a feature?'' A feature is defined as a significant change or enhancement to the version of Sugar on a Stick currently under development that may or may not include new packages and also relate to features of both Fedora and Sugar<br />
* ''What are the deadlines?'' The deadlines for the release currently under development are outlined in the [[Sugar_on_a_Stick#Release_schedule|release schedule]].<br />
* ''What do I get with a feature?'' Having your feature approved not only helps everybody involved in the development and engineering process to keep track of its state, but also allows other teams - like the [[Marketing_Team|marketing team]] - to leverage your work and promote it.<br />
* ''What are my responsibilities?'' By signing up for a feature, you sign up for taking care of it. That means you'll be the one responsible for providing updates and interacting with the different teams concerned by your feature, like the release engineering for Sugar on a Stick. It does, however, not mean that you've to realize your feature all alone - go out and tell the [http://lists.sugarlabs.org lists] and the [http://planet.sugarlabs.org planet] about your work. Get people excited to help you!<br />
* ''How does evaluation happen?'' Your proposal needs a majority of ''YAY'' votes from the release team (determined for a given release by the release manager - the v4 release manager is Sebastian Dziallas, and the current relase team is formed by Peter Robinson, Mel Chua and Sebastian Dziallas) to get approval. Discussion will happen at a weekly meeting, while the decisions will be announced to the SoaS mailing list.'''<br />
* ''What if my feature got rejected?'' No worries! Features that are originally rejected can be revised and resubmitted.<br />
<br />
=== How to submit a feature for consideration ===<br />
# Fill out the [[Features/Feature_Template|template]] and stick it on a page in the wiki. ('''TODO:''' create ''Category:SoaS_v4_Feature'' so people can make their pages belong to the appropriate category so that we know which version you're targeting ).<br />
# Place a link to your proposal in the [[#Current feature ideas]] section of this page while you're working on the document.<br />
# Send an email to the SoaS [http://lists.sugarlabs.org/listinfo/soas list] and incorporate any feedback you might receive.<br />
# When you think your feature proposal is ready, move it to the [[#Features submitted for review]] section of this page. It will be brought up at the next [[Sugar on a Stick meeting]], where it'll be evaluated and voted on. We might ask you to make further adjustments and revisit it at a later point or approve the feature directly. We're looking forward to hearing about your ideas!<br />
<br />
=== Approved features for the current release ===<br />
<br />
''Features must be added to this list by a member of the release team. Place complete feature proposals in the [[#Features submitted for review]] section for consideration at the next meeting.''<br />
<br />
* [[Features/Sugar_0.90|Sugar 0.90]]<br />
* [[Features/Revised_Browse_default-bookmarks.html]]<br />
<br />
=== Features submitted for review ===<br />
<br />
When your feature proposal is complete and ready to review, add it to the list below. These will be considered at the next [[Sugar on a Stick meeting]].<br />
<br />
* [[Updated Activities from the Mirabelle list]]<br />
* Add feature here<br />
<br />
=== Current feature ideas ===<br />
<br />
These feature ideas are in various stages of development.<br />
<br />
* School server<br />
* [[Kickstart generator]]<br />
* btrfs and snapshots<br />
* systemd<br />
* [[More robust iso]]<br />
* Control Panel section for setting display parameters (e.g., VGA out)<br />
* Simplifying Making a Custom remix and sharing the .ksfile and the CD.iso files on the wiki[http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Build_Your_Own_Remix_-.28not_included_on_SCK.DVD.29]<br />
<br />
== Testing process ==<br />
<br />
Our test process, which is under construction, will consist of the following: <br />
<br />
# An agreed-upon image each week for testers to attack (the daily build on $datetime of each week, for instance)<br />
# An agreed-upon set of test cases for them to execute (iow, the "test plan" thing we haven't had before)<br />
# An agreed-upon place and format for the results from running those test cases to be reported to<br />
# An agreed-upon $datetime each week by which all test results for that week will be submitted - so that the development team has a chance to look at those results and revise the build before the next test image goes out.<br />
<br />
The first thing we are doing is getting a weekly image under test to automatically appear at a static link; see [[#Test image]] below. We are going to set up a cron job so the nightly build (from http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ - which we need to start up again from the Fedora side) grabs and archives the appropriate image-under-test each week.<br />
<br />
The last weekly testing update was 6/21/2010: http://lists.sugarlabs.org/archive/soas/2010-June/001560.html<br />
<br />
=== Test image ===<br />
<br />
<big><big>[http://download.sugarlabs.org/soas/test/soas-i386-test-latest.iso Download the current image under test]</big></big><br />
<br />
The test image is the most recent [http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ nightly build] as of 23:59:59 on the most recent Thursday. We're currently pulling it manually, but ticket [http://bugs.sugarlabs.org/ticket/2058 #2058] is for a cron job to automate this (if you know bash scripting, please help!) Past test images are available at http://download.sugarlabs.org/soas/test/.<br />
<br />
*Note than only the first entry on http://download.sugarlabs.org/soas/test/ Boots due to a bug [https://bugzilla.redhat.com/show_bug.cgi?id=617115]<br />
::The only one that boots is: http://download.sugarlabs.org/soas/test/soas-i386-20100623.16.iso<br />
<br />
::'''Test this recent remix''' (generic logos fixes booting): http://people.sugarlabs.org/Tgillard/soas-v4-0725-Remix.iso<br />
<br />
::::satellit 07/26/2010<br />
<br />
=== Test cases ===<br />
<br />
We do not yet have test cases. They will appear here when they are available.<br />
:Note: See Discussion for Notes on testing<br />
* Prototype Tests:<br />
: Activity Testing http://wiki.sugarlabs.org/go/Features/Soas_V4/ASLOxo_Activity_Test_Table based on [http://people.sugarlabs.org/Tgillard/Activities-Index-ASLO-f13-Mirabelle-f14-rawhide-Soas-tests-GC.ods]<br />
: Install Testing http://wiki.sugarlabs.org/go/Talk:Features/Soas_V4/Install_Test_Table<br />
: http://wiki.sugarlabs.org/go/0.90/Testing<br />
<br />
=== Test results ===<br />
<br />
A basic template for reporting simple smoke test results is [[Features/Soas V4/ASLOxo Activity Test Table]]. This needs to be moved to a proper namespace, and instructions need to be written. Instructions will be listed here when they are available.</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_meetings&diff=54812Sugar on a Stick meetings2010-07-26T19:04:10Z<p>Mchua: /* Upcoming meeting */</p>
<hr />
<div><noinclude><div id="contentSub">< [[Sugar on a Stick]]</div><br />
<noinclude>{{TOCright}}[[Category:Meetings]]</noinclude><br />
== Meeting details ==<br />
<br />
Regular meetings for [[Sugar on a Stick]] take place on '''[irc://irc.freenode.net irc.freenode.net]''' in '''#sugar-meeting''', every '''Monday''' at '''1900 UTC'''.<br />
<br />
We use [[IRC]] for our meetings. If you don't have an IRC client (yet), you can use webchat - go to http://webchat.freenode.net and connect to #sugar-meeting, or click the screenshot below. (Replace "your_name" or the random ID provided with your name or some other nick you'd like to be known by.)<br />
<br />
[[File:Freenode-webchat-screenshot.png|left|link=http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1]]<br />
<br />
== How we run meetings ==<br />
<br />
With as much involvement as possible at all times.<br />
<br />
The motivation is to have as many simultaneous actively participating people in the meeting as possible - ideally, at ''all times'' in the meeting, ''everyone'' in the meeting should be ''doing something really cool'' (and hopefully related to Sugar on a Stick) - not just waiting for their turn to speak. Think of it as a virtual version of the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Philosophy law of two feet].<br />
<br />
Are YOU running a SoaS meeting? Take a look at [[How to run a meeting]] for an example of how a meeting is run, with commands listed out.<br />
<br />
== Agenda ==<br />
<br />
{{Anchor|Next_Meeting}}<br />
<br />
=== Every meeting ===<br />
<br />
* [[Sugar on a Stick#Release schedule]] upcoming deadlines announcement<br />
* [[Sugar on a Stick release process#Features submitted for review]]<br />
<br />
=== Upcoming meeting ===<br />
<br />
<pre><br />
#topic Today's agenda<br />
#note * Upcoming deadlines<br />
#note * Features submitted for review<br />
#note * Ticket status<br />
#note * QA update<br />
#note * post-processing scripts for the iso, update<br />
#note * SoaS remixes<br />
#note * Action items from last week<br />
#note * Feature freeze<br />
<br />
#topic Upcoming deadlines<br />
#info July 27, 2010 (tomorrow!) is feature freeze, meaning that the list of approved features for the Mangolassi release will be finalized at the end of tomorrow.<br />
#link http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Approved_features_for_the_current_release<br />
#note We'll come back to feature freeze at the end of this meeting: need to decide what to prioritize to push through in the next 24h<br />
<br />
#topic Features submitted for review<br />
#link http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Features_submitted_for_review<br />
#info None in the queue right now, skipping this agenda item<br />
<br />
#topic Ticket status<br />
#link http://tinyurl.com/soas-tickets<br />
#note This list needs triaging, and we probably want to put this release's <br />
#action mchua to make sure Trac cleanup happens immediately following feature freeze (due: next meeting)<br />
<br />
#topic QA update<br />
#link http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Testing_process<br />
satellit_, can you summarize what's going on with the current test image?<br />
<br />
#topic post-processing scripts for the iso, update<br />
pbrobinson, mtd: did you folks reach a conclusion? (this is re: "someone should just ask sdziallas and pbrobinson nicely if they'd mind terribly if someone suggested some patches / post-processing scripts for the soas spin .iso and promised to help maintain those patches / scripts for at least a few releases.")<br />
Just wanted to make sure this got wrapped up.<br />
<br />
#topic SoaS remixes<br />
<br />
#topic Action items from last week<br />
#note * sdziallas to email the lists about walter's improved first screen.<br />
#note * sdziallas kick off convo about how to lower the entry barrier to activity development and releases<br />
#note * sdziallas and pbrobinson to start activity inclusion discussion to happen on list <br />
Any updates on any of these tasks?<br />
<br />
#topic Feature freeze<br />
</pre><br />
<br />
* http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Testing_process<br />
* post-processing scripts for the iso, update (mtd: "someone should just ask sdziallas and pbrobinson nicely if they'd mind terribly if someone suggested some patches / post-processing scripts for the soas spin .iso and promised to help maintain those patches / scripts for at least a few releases.")<br />
* Possibly Simplifying Making a Custom remix and sharing the .ks file and the CD.iso files on the wiki [http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Build_Your_Own_Remix_-.28not_included_on_SCK.DVD.29]<br />
<br />
== Future topics ==<br />
<br />
== Procedure for Minutes and Logging ==<br />
<br />
See the instructions on [[how to run a meeting]].<br />
<br />
== Minutes ==<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100719_1506.html 2010-07-19 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100719_1506.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100712_1503.html 2010-07-12 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100712_1503.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100705_1502.html 2010-07-05 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100705_1502.html (log)]<br />
* 2010-06-28 (no meeting)<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100621_1502.html 2010-06-21 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100621_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100614_1502.html 2010-06-14 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100614_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100607_1510.html 2010-06-07 Sugar on a Stick v4 Planning Meeting (regular weekly time)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100531_1507.html 2010-05-31 v3 Mirabelle Release Review Meeting (regular weekly time)]</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_meetings&diff=54811Sugar on a Stick meetings2010-07-26T18:54:56Z<p>Mchua: /* Upcoming meeting */</p>
<hr />
<div><noinclude><div id="contentSub">< [[Sugar on a Stick]]</div><br />
<noinclude>{{TOCright}}[[Category:Meetings]]</noinclude><br />
== Meeting details ==<br />
<br />
Regular meetings for [[Sugar on a Stick]] take place on '''[irc://irc.freenode.net irc.freenode.net]''' in '''#sugar-meeting''', every '''Monday''' at '''1900 UTC'''.<br />
<br />
We use [[IRC]] for our meetings. If you don't have an IRC client (yet), you can use webchat - go to http://webchat.freenode.net and connect to #sugar-meeting, or click the screenshot below. (Replace "your_name" or the random ID provided with your name or some other nick you'd like to be known by.)<br />
<br />
[[File:Freenode-webchat-screenshot.png|left|link=http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1]]<br />
<br />
== How we run meetings ==<br />
<br />
With as much involvement as possible at all times.<br />
<br />
The motivation is to have as many simultaneous actively participating people in the meeting as possible - ideally, at ''all times'' in the meeting, ''everyone'' in the meeting should be ''doing something really cool'' (and hopefully related to Sugar on a Stick) - not just waiting for their turn to speak. Think of it as a virtual version of the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Philosophy law of two feet].<br />
<br />
Are YOU running a SoaS meeting? Take a look at [[How to run a meeting]] for an example of how a meeting is run, with commands listed out.<br />
<br />
== Agenda ==<br />
<br />
{{Anchor|Next_Meeting}}<br />
<br />
=== Every meeting ===<br />
<br />
* [[Sugar on a Stick#Release schedule]] upcoming deadlines announcement<br />
* [[Sugar on a Stick release process#Features submitted for review]]<br />
<br />
=== Upcoming meeting ===<br />
<br />
<pre><br />
#topic Today's agenda<br />
#note 1) Upcoming deadlines<br />
#note 2) Features submitted for review<br />
#note 3) QA update<br />
<br />
#topic Upcoming deadlines<br />
#info July 27, 2010 (tomorrow!) is feature freeze, meaning that the list of approved features for the Mangolassi release will be finalized at the end of tomorrow.<br />
#link http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Approved_features_for_the_current_release<br />
<br />
#topic Features submitted for review<br />
#link http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Features_submitted_for_review<br />
#info None in the queue right now, skipping this agenda item<br />
<br />
#topic QA update<br />
#link http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Testing_process<br />
satellit_, can you summarize what's going on with the current test image?<br />
<br />
#topic post-processing scripts for the iso, update<br />
pbrobinson, mtd: did you folks reach a conclusion? (this is re: "someone should just ask sdziallas and pbrobinson nicely if they'd mind terribly if someone suggested some patches / post-processing scripts for the soas spin .iso and promised to help maintain those patches / scripts for at least a few releases.")<br />
Just wanted to make sure this got wrapped up.<br />
<br />
#topic SoaS remixes<br />
</pre><br />
<br />
* http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Testing_process<br />
* post-processing scripts for the iso, update (mtd: "someone should just ask sdziallas and pbrobinson nicely if they'd mind terribly if someone suggested some patches / post-processing scripts for the soas spin .iso and promised to help maintain those patches / scripts for at least a few releases.")<br />
* Possibly Simplifying Making a Custom remix and sharing the .ks file and the CD.iso files on the wiki [http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Build_Your_Own_Remix_-.28not_included_on_SCK.DVD.29]<br />
<br />
== Future topics ==<br />
<br />
== Procedure for Minutes and Logging ==<br />
<br />
See the instructions on [[how to run a meeting]].<br />
<br />
== Minutes ==<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100719_1506.html 2010-07-19 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100719_1506.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100712_1503.html 2010-07-12 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100712_1503.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100705_1502.html 2010-07-05 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100705_1502.html (log)]<br />
* 2010-06-28 (no meeting)<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100621_1502.html 2010-06-21 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100621_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100614_1502.html 2010-06-14 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100614_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100607_1510.html 2010-06-07 Sugar on a Stick v4 Planning Meeting (regular weekly time)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100531_1507.html 2010-05-31 v3 Mirabelle Release Review Meeting (regular weekly time)]</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_meetings&diff=54810Sugar on a Stick meetings2010-07-26T18:53:41Z<p>Mchua: /* Upcoming meeting */ updating agenda for this week</p>
<hr />
<div><noinclude><div id="contentSub">< [[Sugar on a Stick]]</div><br />
<noinclude>{{TOCright}}[[Category:Meetings]]</noinclude><br />
== Meeting details ==<br />
<br />
Regular meetings for [[Sugar on a Stick]] take place on '''[irc://irc.freenode.net irc.freenode.net]''' in '''#sugar-meeting''', every '''Monday''' at '''1900 UTC'''.<br />
<br />
We use [[IRC]] for our meetings. If you don't have an IRC client (yet), you can use webchat - go to http://webchat.freenode.net and connect to #sugar-meeting, or click the screenshot below. (Replace "your_name" or the random ID provided with your name or some other nick you'd like to be known by.)<br />
<br />
[[File:Freenode-webchat-screenshot.png|left|link=http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1]]<br />
<br />
== How we run meetings ==<br />
<br />
With as much involvement as possible at all times.<br />
<br />
The motivation is to have as many simultaneous actively participating people in the meeting as possible - ideally, at ''all times'' in the meeting, ''everyone'' in the meeting should be ''doing something really cool'' (and hopefully related to Sugar on a Stick) - not just waiting for their turn to speak. Think of it as a virtual version of the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Philosophy law of two feet].<br />
<br />
Are YOU running a SoaS meeting? Take a look at [[How to run a meeting]] for an example of how a meeting is run, with commands listed out.<br />
<br />
== Agenda ==<br />
<br />
{{Anchor|Next_Meeting}}<br />
<br />
=== Every meeting ===<br />
<br />
* [[Sugar on a Stick#Release schedule]] upcoming deadlines announcement<br />
* [[Sugar on a Stick release process#Features submitted for review]]<br />
<br />
=== Upcoming meeting ===<br />
<br />
* http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Testing_process<br />
* post-processing scripts for the iso, update (mtd: "someone should just ask sdziallas and pbrobinson nicely if they'd mind terribly if someone suggested some patches / post-processing scripts for the soas spin .iso and promised to help maintain those patches / scripts for at least a few releases.")<br />
* Possibly Simplifying Making a Custom remix and sharing the .ks file and the CD.iso files on the wiki [http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Build_Your_Own_Remix_-.28not_included_on_SCK.DVD.29]<br />
<br />
== Future topics ==<br />
<br />
== Procedure for Minutes and Logging ==<br />
<br />
See the instructions on [[how to run a meeting]].<br />
<br />
== Minutes ==<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100719_1506.html 2010-07-19 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100719_1506.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100712_1503.html 2010-07-12 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100712_1503.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100705_1502.html 2010-07-05 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100705_1502.html (log)]<br />
* 2010-06-28 (no meeting)<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100621_1502.html 2010-06-21 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100621_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100614_1502.html 2010-06-14 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100614_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100607_1510.html 2010-06-07 Sugar on a Stick v4 Planning Meeting (regular weekly time)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100531_1507.html 2010-05-31 v3 Mirabelle Release Review Meeting (regular weekly time)]</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Internet_Relay_Chat&diff=54462Internet Relay Chat2010-07-18T20:56:28Z<p>Mchua: Changing prompt to autopick nick - less confusing for new users (I believe)</p>
<hr />
<div><noinclude>{{TOCright}}[[Category:Contact]][[Category:Resource]]<br />
</noinclude>== IRC, [[Internet Relay Chat]] ==<br />
Most Sugar Labs chat takes place on IRC (see [[wikipedia:IRC|Internet Relay Chat]]).<br />
* You can use a computer-based client to log in to IRC (such as [http://activities.sugarlabs.org/en-US/sugar/addon/4029 Sugar IRC activity], [http://www.pidgin.im/ Pidgin], [[wikipedia:X-Chat|X-Chat]]). This link should work for such clients, irc://irc.freenode.net#sugar.<br />
* Or, use a browser add-on (like [http://addons.mozilla.org/en-US/firefox/addon/16 ChatZilla] for the FireFox web browser, where the above link will also work).<br />
* Easiest, might be this web browser-based service provided by freenode through qwebirc to [http://webchat.freenode.net/?randomnick=1&channels=sugar&prompt=0 chat on #sugar now].<br />
<br />
IRC is mainly designed for group communication in discussion 'channels', but allows for personal chat and data transfer as well. <br />
<br />
The Sugar Labs Community uses a series of ''channels'' in the '''<tt>irc.freenode.net</tt>''' network.<br />
==== irc.freenode.net channels ====<br />
<br />
<!-- FORMAT FOR URLS: <br />
http://webchat.freenode.net/?randomnick=1&channels=sugar&prompt=1<br />
--><br />
{|<br />
| colspan=2 style="background:lightyellow; border:1px solid black;" | '''General:'''<br />
|- valign="top"<br />
|<tt>[http://webchat.freenode.net/?randomnick=1&channels=olpc-help&prompt=1 #olpc-help] or irc://irc.freenode.net#olpc-help</tt> || Community help. If you need help using an XO or with Sugar, and you haven't asked anywhere else: try here first.<br />
|-<br />
|- valign="top"<br />
|<tt>[http://webchat.freenode.net/?randomnick=1&channels=sugar&prompt=1 #sugar]</tt> or <tt>irc://irc.freenode.net#sugar</tt> || For day-to-day [[What is Sugar? | Sugar]] development&mdash;a casual, friendly place where Sugar developers collaborate.<br />
|- valign="top"<br />
| <tt>[http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1 #sugar-meeting]</tt> or <tt>irc://irc.freenode.net#sugar-meeting</tt>|| A channel for scheduled Sugar Labs meetings. See the [[Sugar Labs/Events | Sugar Labs event calendar]].<br />
|- valign="top"<br />
| <tt>[http://webchat.freenode.net/?randomnick=1&channels=fedora-olpc&prompt=1 #fedora-olpc]</tt> or <tt>irc://irc.freenode.net#fedora-olpc</tt> || A channel for the Fedora development project for OLPC XOs and a Sugar distribution. See the [http://fedoraproject.org/wiki/OLPC project page].<br />
<br />
|}<br />
<br />
==== irc.oftc.net channels ====<br />
{|<br />
|-<br />
| colspan=2 style="background:lightyellow; border:1px solid black;" | '''General:'''<br />
|- valign="top"<br />
|- valign="top"<br />
| <tt>[http://embed.mibbit.com/?server=irc.oftc.net&channel=%23schoolserver&noServerTab=false #schoolserver]</tt> or <tt>irc://irc.oftc.net#schoolserver</tt> || The meeting channel for the XS, the '''X'''O school '''S'''erver.<br>(Not active in September 2009.)<br />
|- valign="top"<br />
|}<br />
<br />
* See also [[OLPC:Communication channels]].<br />
<br />
=== How to use IRC channels ===<br />
* A web-based chat for freenode.net channels is [http://webchat.freenode.net qwebirc], with nickname: (whatever you like), and channel: #sugar (or whatever other channel you're trying to get into).<br />
* A web-based chat for other channels is [http://www.mibbit.com Mibbit], with nickname: (whatever you like), server: irc.oftc.net, and channel: #schoolserver (or whatever other channel you're trying to get into). It also includes an in-line '''translation''' service that is helpful when other languages are used. (Connections via mibbit are no longer supported on freenode. You may wish to consider using http://webchat.freenode.net instead. Further information over at http://bit.ly/19JILF.)<br />
* Some helpful resources are [http://www.mirc.com/irc.html here], and [http://www.irchelp.org/irchelp/irctutorial.html this tutorial], which also includes basic commands.<br />
* Learn about IRC etiquette. Try [http://www.ircbeginner.com/ircinfo/etiquette.html here], [http://www.livinginternet.com/r/ru_chatq.htm here], or [http://www.wxwidgets.org/wiki/index.php/IRC_Etiquette here]. <br />
* For IRC under sugar, install the latest '''[http://activities.sugarlabs.org/en-US/sugar/addon/4029 Sugar IRC]''' activity.<br />
* In Pidgin you can configure IRC and then Add a Chat to your Buddy list. Select the IRC channel from the drop-down menu, and enter the name of the channel. You can set Pidgin to open channels automatically whenever it starts up.<br />
* In a traditional IRC client, you join a channel with the /join command, for example, enter <code>/join #sugar</code> in the input box.<br />
* Connect to one of the above channels, and say hello. You will see a list of the handles (on-line names) of the people in the channel, and the conversation will appear in a scrolling window. Type your message in the command entry area, and press return.<br />
* Instructions for using the meeting log robot are [[OLPC:User:Dogi/meeting | here]].</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_meetings&diff=54224Sugar on a Stick meetings2010-07-12T19:39:20Z<p>Mchua: /* Minutes */</p>
<hr />
<div><noinclude>{{TOCright}}<br />
[[Category:Sugar on a Stick]]<br />
[[Category:Meetings]]<br />
</noinclude><br />
== Meeting details ==<br />
<br />
Regular meetings for [[Sugar on a Stick]] take place on '''[irc://irc.freenode.net irc.freenode.net]''' in '''#sugar-meeting''', every '''Monday''' at '''1900 UTC'''.<br />
<br />
We use [[IRC]] for our meetings. If you don't have an IRC client (yet), you can use webchat - go to http://webchat.freenode.net and connect to #sugar-meeting, or click the screenshot below. (Replace "your_name" or the random ID provided with your name or some other nick you'd like to be known by.)<br />
<br />
[[File:Freenode-webchat-screenshot.png|left|link=http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1]]<br />
<br />
== How we run meetings ==<br />
<br />
With as much involvement as possible at all times.<br />
<br />
The motivation is to have as many simultaneous actively participating people in the meeting as possible - ideally, at ''all times'' in the meeting, ''everyone'' in the meeting should be ''doing something really cool'' (and hopefully related to Sugar on a Stick) - not just waiting for their turn to speak. Think of it as a virtual version of the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Philosophy law of two feet].<br />
<br />
Are YOU running a SoaS meeting? Take a look at [[How to run a meeting]] for an example of how a meeting is run, with commands listed out.<br />
<br />
== Agenda ==<br />
<br />
{{Anchor|Next_Meeting}}<br />
<br />
=== Every meeting ===<br />
<br />
* [[Sugar on a Stick#Release schedule]] upcoming deadlines announcement<br />
* [[Sugar on a Stick release process#Features submitted for review]]<br />
<br />
=== Upcoming meeting ===<br />
<br />
* http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Testing_process<br />
* mtd: "someone should just ask sdziallas and pbrobinson nicely if they'd mind terribly if someone suggested some patches / post-processing scripts for the soas spin .iso and promised to help maintain those patches / scripts for at least a few releases."<br />
* what people plan to work on for the v4 cycle<br />
<br />
== Future topics ==<br />
<br />
== Procedure for Minutes and Logging ==<br />
<br />
See the instructions on [[how to run a meeting]].<br />
<br />
== Minutes ==<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100712_1503.html 2010-07-12 (weekly meeting)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100705_1502.html 2010-07-05 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100705_1502.html (log)]<br />
* 2010-06-28 (no meeting)<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100621_1502.html 2010-06-21 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100621_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100614_1502.html 2010-06-14 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100614_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100607_1510.html 2010-06-07 Sugar on a Stick v4 Planning Meeting (regular weekly time)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100531_1507.html 2010-05-31 v3 Mirabelle Release Review Meeting (regular weekly time)]</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Oversight_Board/Minutes&diff=54207Oversight Board/Minutes2010-07-11T11:35:28Z<p>Mchua: /* Agenda items */</p>
<hr />
<div><noinclude>{{GoogleTrans-en}}{{TeamHeader|Oversight Board|roadmap_link=Oversight Board/Vision|roadmap_label=Vision}}</noinclude><br />
__NOTOC__<br />
<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>The Oversight board will be holding regular bi-weekly meetings on Fridays at 15 UTC on irc.freenode.net (channel: #sugar-meeting).<br />
Please add to the agenda below and please join in with your ideas.<br />
<br />
Hint: You can use an [http://www.timeanddate.com/worldclock/converter.html online time calculator] to convert from UTC to your local time zone or back.<br />
<br />
The Sugar Labs Meetings calendar is available in a variety of formats at these links: <span class="plainlinks"> [http://www.google.com/calendar/feeds/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic {{filepath:XML.gif}}] [http://www.google.com/calendar/ical/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic.ics {{filepath:ICal.gif}}] [http://www.google.com/calendar/embed?src=h9cfuk10894em7a8moemquusmg%40group.calendar.google.com&ctz=America/New_York {{filepath:HTML.gif}}].</span><br />
</div><br />
<br />
<br />
==About==<br />
The Sugar Labs [[Oversight_Board|Oversight Board]] "shall meet at least once per quarter to discuss various topics pertaining to the regular activities of the Sugar Labs Project and Sugar. (It is expected that more frequent meeting will be required in the early stages of the program.) The minutes to these meetings shall be posted publicly on the Sugar Labs wiki,"<br />
<br />
[[Sugar Labs/Governance/Committees|Committee]] reports will be a regular part of the meetings.<br />
<br />
==Who==<br />
<br />
The meeting is mainly targeted to Sugar Oversight Board, but everyone interested is welcome to join. It's primary purpose is to discuss general issues related to Sugar and the Sugar community; however, it is not intended as a replacement for the weekly developer meetings.<br />
<br />
==How to add topics==<br />
The discussion topics for upcoming meetings are listed [[#Agenda items|below]]. Please contact an oversight-board member if you have additional topics you would like to add. Topics will be collected between meetings, triaged by the meeting chair, and send out in the meeting announcement on ~24 hours before the meeting. A reminder to add topics will be announced in the [[Sugar_Labs/Current_Events|Sugar Digest]]. Please consider including the following data when making a request:<br />
<br />
# a link to existing discussion thread(s) on public mailing list;<br />
# a ''brief'' summary of each option or alternative being proposed; and<br />
# a rationale for why this issue needs to escalate to the oversight board.<br />
<br />
==Meetings ==<br />
<br />
=== Next meeting===<br />
<br />
==== Not scheduled. Email slobs at lists dot sugarlabs dot org to propose a time, if you want the topic queue to be brought up. ====<br />
<br />
==== Agenda items ====<br />
<br />
* [http://wiki.sugarlabs.org/go/Sugar_Labs/Project_Guidelines "What is a SL project?" discussion] - see [http://lists.sugarlabs.org/archive/iaep/2010-July/011345.html email thread with motion].<br />
* What are our biggest issues right now? How are we doing towards our goals? (What are they?)<br />
<br />
Please contact an oversight-board member to add topics to be considered for the meeting.<br />
<br />
=== Open discussion topics===<br />
<br />
{|<br />
|width=50%; valign=top|<br />
Administrative<br />
* Committee reports<br />
** Local Labs<br />
** Membership/Sponsorship<br />
** Events<br />
***FOSDEM<br />
***Others<br />
** Deployment<br />
** Infrastructure<br />
<br />
* Funding<br />
** Grant status<br />
** Donations to our supporting partners<br />
<br />
|width=50%; valign=top|<br />
* Partnerships<br />
** Pangaean<br />
** Gitorious<br />
** Qt Software<br />
** Bicocca<br />
** Relationship with OLPC<br />
<br />
* Misc<br />
** Babson program<br />
** Website/wiki<br />
** Release names<br />
|}<br />
<br />
=== Past meetings ===<br />
<br />
Meetings were held on Friday and at 15:00 UTC except where specified.<br />
<br />
{|<br />
|width="33%" valign="top"|<br />
'''2010'''<br />
<br />
11 July<br />
<small>[http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100711_0446.html discussion minutes (not official SLOBs meeting)]<br />
</small><br />
<br />
25 June (15UTC)<br />
<small>[http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100625_1103.html discussion log (not official SLOBs meeting)]</small><br />
<br />
04 June (15UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-06-04|minutes]], [[Oversight Board/Meeting Log-2010-06-04|log]])</small><br />
<br />
14 May (15UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-05-14|minutes]], [[Oversight Board/Meeting Log-2010-05-14|log]])</small><br />
<br />
07 May (15UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-05-07|minutes]], [[Oversight Board/Meeting Log-2010-05-07|log]])</small><br />
<br />
26 Mar (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-03-26|minutes]], [[Oversight Board/Meeting Log-2010-03-26|log]])</small><br />
<br />
12 Mar (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-03-12|minutes]], [[Oversight Board/Meeting Log-2010-03-12|log]])</small><br />
<br />
5 Mar (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-03-05|minutes]], [[Oversight Board/Meeting Log-2010-03-05|log]])</small><br />
<br />
26 Feb (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-02-26|minutes]], [[Oversight Board/Meeting Log-2010-02.26|log]])</small><br />
<br />
5 Feb (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-02-05|minutes]], [[Oversight Board/Meeting Log-2010-02-05|log]])</small><br />
<br />
29 Jan (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-01-29|minutes]], [[Oversight Board/Meeting Log-2010-01-29|log]])</small><br />
<br />
22 Jan (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-01-22|minutes]], [[Oversight Board/Meeting Log-2010-01-22|log]])</small><br />
<br />
15 Jan (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-01-15|minutes]], [[Oversight Board/Meeting Log-2010-01-15|log]])</small><br />
<br />
8 Jan<br />
<small>([[Oversight Board/Meeting Minutes-2010-01-08|minutes]], [[Oversight Board/Meeting Log-2010-01-08|log]])</small><br />
<br />
|width="33%" valign="top"|<br />
'''2009'''<br />
<br />
30 Dec (Wed)<br />
<small>([[Oversight Board/Meeting Minutes-2009-12-30|minutes]], [[Oversight Board/Meeting Log-2009-12-30|log]])</small><br />
<br />
23 Dec (Wed)<br />
<small>([[Oversight Board/Meeting Minutes-2009-12-23|minutes]], [[Oversight Board/Meeting Log-2009-12-23|log]])</small><br />
<br />
18 Dec<br />
<small>([[Oversight Board/Meeting Minutes-2009-12-18|minutes]], [[Oversight Board/Meeting Log-2009-12-18|log]])</small><br />
<br />
11 Dec<br />
<small>([[Oversight Board/Meeting Minutes-2009-12-11|minutes]], [[Oversight Board/Meeting Log-2009-12-11|log]])</small><br />
<br />
4 Dec<br />
<small>([[Oversight Board/Meeting Minutes-2009-12-04|minutes]], [[Oversight Board/Meeting Log-2009-12-04|log]])</small><br />
<br />
20 Nov<br />
<small>([[Oversight Board/Meeting Minutes-2009-11-20|minutes]], [[Oversight_Board/Meeting_Log-2009-11-20|log]])</small><br />
<br />
13 Nov<br />
<small>([[Oversight Board/Meeting Minutes-2009-11-13|minutes]], [[Oversight_Board/Meeting_Log-2009-11-13|log]])</small><br />
<br />
6 Nov<br />
<small>([[Oversight Board/Meeting Minutes-2009-11-06|minutes]], [[Oversight_Board/Meeting_Log-2009-11-06|log]])</small><br />
<br />
30 Oct<br />
<small>([[Oversight Board/Meeting Minutes-2009-10-30|minutes]], [[Oversight_Board/Meeting_Log-2009-10-30|log]])</small><br />
<br />
25 Sep <br />
<small>([[Oversight Board/Meeting Minutes-2009-09-25|minutes]], [[Oversight Board/Meeting Log-2009-09-25|log]])<br />
</small><br />
<br />
28 Aug <br />
<small>([[Oversight Board/Meeting Minutes-2009-08-28|minutes]], [[Oversight Board/Log-2009-08-28|log]])<br />
</small><br />
<br />
10 Jul<br />
<small>([http://meeting.sugarlabs.org/sugar-meeting.minutes.20090710_0905.html minutes], <br />
[http://meeting.sugarlabs.org/sugar-meeting.log.20090710_0905.html log])<br />
</small><br />
<br />
06 Mar<br />
<small>([[Oversight Board/Meeting Minutes-2009-03-06|minutes]])<br />
</small><br />
<br />
13 Feb <br />
<small>([[Oversight Board/Meeting Minutes-2009-02-13|minutes]], [[Oversight Board/Log-2009-02-13|log]])<br />
</small><br />
<br />
02 Feb (Mon)<br />
<small>([[Oversight Board/Meeting Minutes-2009-02-02|minutes]], [[Oversight Board/Log-2009-02-02|log]])<br />
</small><br />
<br />
<br />
|width="33%" valign="top"|<br />
<br />
'''2008'''<br />
<br />
12 Dec <br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-12-12|minutes]], [[Oversight Board/Log-2008-12-12|log]])<br />
</small><br />
<br />
31 Oct<br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-10-31|minutes]], [[Oversight Board/Log-2008-10-31|log]])<br />
</small><br />
<br />
17 Oct <br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-10-17|minutes]], [[Oversight Board/Log-2008-10-17|log]])<br />
</small><br />
<br />
03 Oct <br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-10-03|minutes]], [[Oversight Board/Log-2008-10-03|log]])<br />
</small><br />
<br />
19 Sep <br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-09-19|minutes]], [[Oversight Board/Log-2008-09-19|log]])<br />
</small><br />
<br />
5 Sep <br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-09-05|minutes]], [[Oversight Board/Log-2008-09-05|log]])<br />
</small><br />
<br />
1 Aug<br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-08-01|minutes]], [[Oversight Board/Log-2008-08-01|log]])<br />
</small><br />
<br />
18 Jul (17.00 UTC)<br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-07-18|minutes]], [[Oversight Board/Log-2008-07-18|log]])<br />
</small><br />
<br />
30 Jun (Mon, 17.00 UTC)<br />
<small><br />
([[Oversight Board/Meeting_Minutes-2008-06-30|minutes]], [[Oversight Board/Log-2008-06-30|log]])<br />
</small><br />
<br />
|}<br />
<br />
[[Category:Oversight board]]<br />
[[Category:Meetings]]<br />
[[Category:Meeting minutes]]<br />
[[Category:Governance]]</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Oversight_Board/Minutes&diff=54206Oversight Board/Minutes2010-07-11T10:56:28Z<p>Mchua: /* Agenda items */</p>
<hr />
<div><noinclude>{{GoogleTrans-en}}{{TeamHeader|Oversight Board|roadmap_link=Oversight Board/Vision|roadmap_label=Vision}}</noinclude><br />
__NOTOC__<br />
<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>The Oversight board will be holding regular bi-weekly meetings on Fridays at 15 UTC on irc.freenode.net (channel: #sugar-meeting).<br />
Please add to the agenda below and please join in with your ideas.<br />
<br />
Hint: You can use an [http://www.timeanddate.com/worldclock/converter.html online time calculator] to convert from UTC to your local time zone or back.<br />
<br />
The Sugar Labs Meetings calendar is available in a variety of formats at these links: <span class="plainlinks"> [http://www.google.com/calendar/feeds/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic {{filepath:XML.gif}}] [http://www.google.com/calendar/ical/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic.ics {{filepath:ICal.gif}}] [http://www.google.com/calendar/embed?src=h9cfuk10894em7a8moemquusmg%40group.calendar.google.com&ctz=America/New_York {{filepath:HTML.gif}}].</span><br />
</div><br />
<br />
<br />
==About==<br />
The Sugar Labs [[Oversight_Board|Oversight Board]] "shall meet at least once per quarter to discuss various topics pertaining to the regular activities of the Sugar Labs Project and Sugar. (It is expected that more frequent meeting will be required in the early stages of the program.) The minutes to these meetings shall be posted publicly on the Sugar Labs wiki,"<br />
<br />
[[Sugar Labs/Governance/Committees|Committee]] reports will be a regular part of the meetings.<br />
<br />
==Who==<br />
<br />
The meeting is mainly targeted to Sugar Oversight Board, but everyone interested is welcome to join. It's primary purpose is to discuss general issues related to Sugar and the Sugar community; however, it is not intended as a replacement for the weekly developer meetings.<br />
<br />
==How to add topics==<br />
The discussion topics for upcoming meetings are listed [[#Agenda items|below]]. Please contact an oversight-board member if you have additional topics you would like to add. Topics will be collected between meetings, triaged by the meeting chair, and send out in the meeting announcement on ~24 hours before the meeting. A reminder to add topics will be announced in the [[Sugar_Labs/Current_Events|Sugar Digest]]. Please consider including the following data when making a request:<br />
<br />
# a link to existing discussion thread(s) on public mailing list;<br />
# a ''brief'' summary of each option or alternative being proposed; and<br />
# a rationale for why this issue needs to escalate to the oversight board.<br />
<br />
==Meetings ==<br />
<br />
=== Next meeting===<br />
<br />
==== Not scheduled. Email slobs at lists dot sugarlabs dot org to propose a time, if you want the topic queue to be brought up. ====<br />
<br />
==== Agenda items ====<br />
<br />
* [http://wiki.sugarlabs.org/go/Sugar_Labs/Project_Guidelines "What is a SL project?" discussion]<br />
* What are our biggest issues right now? How are we doing towards our goals? (What are they?)<br />
<br />
Please contact an oversight-board member to add topics to be considered for the meeting.<br />
<br />
=== Open discussion topics===<br />
<br />
{|<br />
|width=50%; valign=top|<br />
Administrative<br />
* Committee reports<br />
** Local Labs<br />
** Membership/Sponsorship<br />
** Events<br />
***FOSDEM<br />
***Others<br />
** Deployment<br />
** Infrastructure<br />
<br />
* Funding<br />
** Grant status<br />
** Donations to our supporting partners<br />
<br />
|width=50%; valign=top|<br />
* Partnerships<br />
** Pangaean<br />
** Gitorious<br />
** Qt Software<br />
** Bicocca<br />
** Relationship with OLPC<br />
<br />
* Misc<br />
** Babson program<br />
** Website/wiki<br />
** Release names<br />
|}<br />
<br />
=== Past meetings ===<br />
<br />
Meetings were held on Friday and at 15:00 UTC except where specified.<br />
<br />
{|<br />
|width="33%" valign="top"|<br />
'''2010'''<br />
<br />
11 July<br />
<small>[http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100711_0446.html discussion minutes (not official SLOBs meeting)]<br />
</small><br />
<br />
25 June (15UTC)<br />
<small>[http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100625_1103.html discussion log (not official SLOBs meeting)]</small><br />
<br />
04 June (15UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-06-04|minutes]], [[Oversight Board/Meeting Log-2010-06-04|log]])</small><br />
<br />
14 May (15UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-05-14|minutes]], [[Oversight Board/Meeting Log-2010-05-14|log]])</small><br />
<br />
07 May (15UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-05-07|minutes]], [[Oversight Board/Meeting Log-2010-05-07|log]])</small><br />
<br />
26 Mar (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-03-26|minutes]], [[Oversight Board/Meeting Log-2010-03-26|log]])</small><br />
<br />
12 Mar (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-03-12|minutes]], [[Oversight Board/Meeting Log-2010-03-12|log]])</small><br />
<br />
5 Mar (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-03-05|minutes]], [[Oversight Board/Meeting Log-2010-03-05|log]])</small><br />
<br />
26 Feb (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-02-26|minutes]], [[Oversight Board/Meeting Log-2010-02.26|log]])</small><br />
<br />
5 Feb (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-02-05|minutes]], [[Oversight Board/Meeting Log-2010-02-05|log]])</small><br />
<br />
29 Jan (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-01-29|minutes]], [[Oversight Board/Meeting Log-2010-01-29|log]])</small><br />
<br />
22 Jan (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-01-22|minutes]], [[Oversight Board/Meeting Log-2010-01-22|log]])</small><br />
<br />
15 Jan (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-01-15|minutes]], [[Oversight Board/Meeting Log-2010-01-15|log]])</small><br />
<br />
8 Jan<br />
<small>([[Oversight Board/Meeting Minutes-2010-01-08|minutes]], [[Oversight Board/Meeting Log-2010-01-08|log]])</small><br />
<br />
|width="33%" valign="top"|<br />
'''2009'''<br />
<br />
30 Dec (Wed)<br />
<small>([[Oversight Board/Meeting Minutes-2009-12-30|minutes]], [[Oversight Board/Meeting Log-2009-12-30|log]])</small><br />
<br />
23 Dec (Wed)<br />
<small>([[Oversight Board/Meeting Minutes-2009-12-23|minutes]], [[Oversight Board/Meeting Log-2009-12-23|log]])</small><br />
<br />
18 Dec<br />
<small>([[Oversight Board/Meeting Minutes-2009-12-18|minutes]], [[Oversight Board/Meeting Log-2009-12-18|log]])</small><br />
<br />
11 Dec<br />
<small>([[Oversight Board/Meeting Minutes-2009-12-11|minutes]], [[Oversight Board/Meeting Log-2009-12-11|log]])</small><br />
<br />
4 Dec<br />
<small>([[Oversight Board/Meeting Minutes-2009-12-04|minutes]], [[Oversight Board/Meeting Log-2009-12-04|log]])</small><br />
<br />
20 Nov<br />
<small>([[Oversight Board/Meeting Minutes-2009-11-20|minutes]], [[Oversight_Board/Meeting_Log-2009-11-20|log]])</small><br />
<br />
13 Nov<br />
<small>([[Oversight Board/Meeting Minutes-2009-11-13|minutes]], [[Oversight_Board/Meeting_Log-2009-11-13|log]])</small><br />
<br />
6 Nov<br />
<small>([[Oversight Board/Meeting Minutes-2009-11-06|minutes]], [[Oversight_Board/Meeting_Log-2009-11-06|log]])</small><br />
<br />
30 Oct<br />
<small>([[Oversight Board/Meeting Minutes-2009-10-30|minutes]], [[Oversight_Board/Meeting_Log-2009-10-30|log]])</small><br />
<br />
25 Sep <br />
<small>([[Oversight Board/Meeting Minutes-2009-09-25|minutes]], [[Oversight Board/Meeting Log-2009-09-25|log]])<br />
</small><br />
<br />
28 Aug <br />
<small>([[Oversight Board/Meeting Minutes-2009-08-28|minutes]], [[Oversight Board/Log-2009-08-28|log]])<br />
</small><br />
<br />
10 Jul<br />
<small>([http://meeting.sugarlabs.org/sugar-meeting.minutes.20090710_0905.html minutes], <br />
[http://meeting.sugarlabs.org/sugar-meeting.log.20090710_0905.html log])<br />
</small><br />
<br />
06 Mar<br />
<small>([[Oversight Board/Meeting Minutes-2009-03-06|minutes]])<br />
</small><br />
<br />
13 Feb <br />
<small>([[Oversight Board/Meeting Minutes-2009-02-13|minutes]], [[Oversight Board/Log-2009-02-13|log]])<br />
</small><br />
<br />
02 Feb (Mon)<br />
<small>([[Oversight Board/Meeting Minutes-2009-02-02|minutes]], [[Oversight Board/Log-2009-02-02|log]])<br />
</small><br />
<br />
<br />
|width="33%" valign="top"|<br />
<br />
'''2008'''<br />
<br />
12 Dec <br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-12-12|minutes]], [[Oversight Board/Log-2008-12-12|log]])<br />
</small><br />
<br />
31 Oct<br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-10-31|minutes]], [[Oversight Board/Log-2008-10-31|log]])<br />
</small><br />
<br />
17 Oct <br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-10-17|minutes]], [[Oversight Board/Log-2008-10-17|log]])<br />
</small><br />
<br />
03 Oct <br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-10-03|minutes]], [[Oversight Board/Log-2008-10-03|log]])<br />
</small><br />
<br />
19 Sep <br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-09-19|minutes]], [[Oversight Board/Log-2008-09-19|log]])<br />
</small><br />
<br />
5 Sep <br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-09-05|minutes]], [[Oversight Board/Log-2008-09-05|log]])<br />
</small><br />
<br />
1 Aug<br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-08-01|minutes]], [[Oversight Board/Log-2008-08-01|log]])<br />
</small><br />
<br />
18 Jul (17.00 UTC)<br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-07-18|minutes]], [[Oversight Board/Log-2008-07-18|log]])<br />
</small><br />
<br />
30 Jun (Mon, 17.00 UTC)<br />
<small><br />
([[Oversight Board/Meeting_Minutes-2008-06-30|minutes]], [[Oversight Board/Log-2008-06-30|log]])<br />
</small><br />
<br />
|}<br />
<br />
[[Category:Oversight board]]<br />
[[Category:Meetings]]<br />
[[Category:Meeting minutes]]<br />
[[Category:Governance]]</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Oversight_Board/Minutes&diff=54205Oversight Board/Minutes2010-07-11T10:55:34Z<p>Mchua: /* Meetings */</p>
<hr />
<div><noinclude>{{GoogleTrans-en}}{{TeamHeader|Oversight Board|roadmap_link=Oversight Board/Vision|roadmap_label=Vision}}</noinclude><br />
__NOTOC__<br />
<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>The Oversight board will be holding regular bi-weekly meetings on Fridays at 15 UTC on irc.freenode.net (channel: #sugar-meeting).<br />
Please add to the agenda below and please join in with your ideas.<br />
<br />
Hint: You can use an [http://www.timeanddate.com/worldclock/converter.html online time calculator] to convert from UTC to your local time zone or back.<br />
<br />
The Sugar Labs Meetings calendar is available in a variety of formats at these links: <span class="plainlinks"> [http://www.google.com/calendar/feeds/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic {{filepath:XML.gif}}] [http://www.google.com/calendar/ical/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic.ics {{filepath:ICal.gif}}] [http://www.google.com/calendar/embed?src=h9cfuk10894em7a8moemquusmg%40group.calendar.google.com&ctz=America/New_York {{filepath:HTML.gif}}].</span><br />
</div><br />
<br />
<br />
==About==<br />
The Sugar Labs [[Oversight_Board|Oversight Board]] "shall meet at least once per quarter to discuss various topics pertaining to the regular activities of the Sugar Labs Project and Sugar. (It is expected that more frequent meeting will be required in the early stages of the program.) The minutes to these meetings shall be posted publicly on the Sugar Labs wiki,"<br />
<br />
[[Sugar Labs/Governance/Committees|Committee]] reports will be a regular part of the meetings.<br />
<br />
==Who==<br />
<br />
The meeting is mainly targeted to Sugar Oversight Board, but everyone interested is welcome to join. It's primary purpose is to discuss general issues related to Sugar and the Sugar community; however, it is not intended as a replacement for the weekly developer meetings.<br />
<br />
==How to add topics==<br />
The discussion topics for upcoming meetings are listed [[#Agenda items|below]]. Please contact an oversight-board member if you have additional topics you would like to add. Topics will be collected between meetings, triaged by the meeting chair, and send out in the meeting announcement on ~24 hours before the meeting. A reminder to add topics will be announced in the [[Sugar_Labs/Current_Events|Sugar Digest]]. Please consider including the following data when making a request:<br />
<br />
# a link to existing discussion thread(s) on public mailing list;<br />
# a ''brief'' summary of each option or alternative being proposed; and<br />
# a rationale for why this issue needs to escalate to the oversight board.<br />
<br />
==Meetings ==<br />
<br />
=== Next meeting===<br />
<br />
==== Not scheduled. Email slobs at lists dot sugarlabs dot org to propose a time, if you want the topic queue to be brought up. ====<br />
<br />
==== Agenda items ====<br />
<br />
* [http://lists.sugarlabs.org/archive/iaep/2010-June/011241.html F11+0.88+XO-1.* as a SL project]<br />
* [http://lists.sugarlabs.org/archive/iaep/2010-June/011240.html Ooo4Kids logo display request]<br />
* [http://lists.sugarlabs.org/archive/iaep/2010-June/011237.html TM usage applications]<br />
* Review of RM search<br />
* Motion and possible vote on Sugar certification<br />
<br />
Please contact an oversight-board member to add topics to be considered for the meeting.<br />
<br />
=== Open discussion topics===<br />
<br />
{|<br />
|width=50%; valign=top|<br />
Administrative<br />
* Committee reports<br />
** Local Labs<br />
** Membership/Sponsorship<br />
** Events<br />
***FOSDEM<br />
***Others<br />
** Deployment<br />
** Infrastructure<br />
<br />
* Funding<br />
** Grant status<br />
** Donations to our supporting partners<br />
<br />
|width=50%; valign=top|<br />
* Partnerships<br />
** Pangaean<br />
** Gitorious<br />
** Qt Software<br />
** Bicocca<br />
** Relationship with OLPC<br />
<br />
* Misc<br />
** Babson program<br />
** Website/wiki<br />
** Release names<br />
|}<br />
<br />
=== Past meetings ===<br />
<br />
Meetings were held on Friday and at 15:00 UTC except where specified.<br />
<br />
{|<br />
|width="33%" valign="top"|<br />
'''2010'''<br />
<br />
11 July<br />
<small>[http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100711_0446.html discussion minutes (not official SLOBs meeting)]<br />
</small><br />
<br />
25 June (15UTC)<br />
<small>[http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100625_1103.html discussion log (not official SLOBs meeting)]</small><br />
<br />
04 June (15UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-06-04|minutes]], [[Oversight Board/Meeting Log-2010-06-04|log]])</small><br />
<br />
14 May (15UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-05-14|minutes]], [[Oversight Board/Meeting Log-2010-05-14|log]])</small><br />
<br />
07 May (15UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-05-07|minutes]], [[Oversight Board/Meeting Log-2010-05-07|log]])</small><br />
<br />
26 Mar (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-03-26|minutes]], [[Oversight Board/Meeting Log-2010-03-26|log]])</small><br />
<br />
12 Mar (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-03-12|minutes]], [[Oversight Board/Meeting Log-2010-03-12|log]])</small><br />
<br />
5 Mar (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-03-05|minutes]], [[Oversight Board/Meeting Log-2010-03-05|log]])</small><br />
<br />
26 Feb (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-02-26|minutes]], [[Oversight Board/Meeting Log-2010-02.26|log]])</small><br />
<br />
5 Feb (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-02-05|minutes]], [[Oversight Board/Meeting Log-2010-02-05|log]])</small><br />
<br />
29 Jan (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-01-29|minutes]], [[Oversight Board/Meeting Log-2010-01-29|log]])</small><br />
<br />
22 Jan (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-01-22|minutes]], [[Oversight Board/Meeting Log-2010-01-22|log]])</small><br />
<br />
15 Jan (16UTC)<br />
<small>([[Oversight Board/Meeting Minutes-2010-01-15|minutes]], [[Oversight Board/Meeting Log-2010-01-15|log]])</small><br />
<br />
8 Jan<br />
<small>([[Oversight Board/Meeting Minutes-2010-01-08|minutes]], [[Oversight Board/Meeting Log-2010-01-08|log]])</small><br />
<br />
|width="33%" valign="top"|<br />
'''2009'''<br />
<br />
30 Dec (Wed)<br />
<small>([[Oversight Board/Meeting Minutes-2009-12-30|minutes]], [[Oversight Board/Meeting Log-2009-12-30|log]])</small><br />
<br />
23 Dec (Wed)<br />
<small>([[Oversight Board/Meeting Minutes-2009-12-23|minutes]], [[Oversight Board/Meeting Log-2009-12-23|log]])</small><br />
<br />
18 Dec<br />
<small>([[Oversight Board/Meeting Minutes-2009-12-18|minutes]], [[Oversight Board/Meeting Log-2009-12-18|log]])</small><br />
<br />
11 Dec<br />
<small>([[Oversight Board/Meeting Minutes-2009-12-11|minutes]], [[Oversight Board/Meeting Log-2009-12-11|log]])</small><br />
<br />
4 Dec<br />
<small>([[Oversight Board/Meeting Minutes-2009-12-04|minutes]], [[Oversight Board/Meeting Log-2009-12-04|log]])</small><br />
<br />
20 Nov<br />
<small>([[Oversight Board/Meeting Minutes-2009-11-20|minutes]], [[Oversight_Board/Meeting_Log-2009-11-20|log]])</small><br />
<br />
13 Nov<br />
<small>([[Oversight Board/Meeting Minutes-2009-11-13|minutes]], [[Oversight_Board/Meeting_Log-2009-11-13|log]])</small><br />
<br />
6 Nov<br />
<small>([[Oversight Board/Meeting Minutes-2009-11-06|minutes]], [[Oversight_Board/Meeting_Log-2009-11-06|log]])</small><br />
<br />
30 Oct<br />
<small>([[Oversight Board/Meeting Minutes-2009-10-30|minutes]], [[Oversight_Board/Meeting_Log-2009-10-30|log]])</small><br />
<br />
25 Sep <br />
<small>([[Oversight Board/Meeting Minutes-2009-09-25|minutes]], [[Oversight Board/Meeting Log-2009-09-25|log]])<br />
</small><br />
<br />
28 Aug <br />
<small>([[Oversight Board/Meeting Minutes-2009-08-28|minutes]], [[Oversight Board/Log-2009-08-28|log]])<br />
</small><br />
<br />
10 Jul<br />
<small>([http://meeting.sugarlabs.org/sugar-meeting.minutes.20090710_0905.html minutes], <br />
[http://meeting.sugarlabs.org/sugar-meeting.log.20090710_0905.html log])<br />
</small><br />
<br />
06 Mar<br />
<small>([[Oversight Board/Meeting Minutes-2009-03-06|minutes]])<br />
</small><br />
<br />
13 Feb <br />
<small>([[Oversight Board/Meeting Minutes-2009-02-13|minutes]], [[Oversight Board/Log-2009-02-13|log]])<br />
</small><br />
<br />
02 Feb (Mon)<br />
<small>([[Oversight Board/Meeting Minutes-2009-02-02|minutes]], [[Oversight Board/Log-2009-02-02|log]])<br />
</small><br />
<br />
<br />
|width="33%" valign="top"|<br />
<br />
'''2008'''<br />
<br />
12 Dec <br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-12-12|minutes]], [[Oversight Board/Log-2008-12-12|log]])<br />
</small><br />
<br />
31 Oct<br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-10-31|minutes]], [[Oversight Board/Log-2008-10-31|log]])<br />
</small><br />
<br />
17 Oct <br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-10-17|minutes]], [[Oversight Board/Log-2008-10-17|log]])<br />
</small><br />
<br />
03 Oct <br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-10-03|minutes]], [[Oversight Board/Log-2008-10-03|log]])<br />
</small><br />
<br />
19 Sep <br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-09-19|minutes]], [[Oversight Board/Log-2008-09-19|log]])<br />
</small><br />
<br />
5 Sep <br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-09-05|minutes]], [[Oversight Board/Log-2008-09-05|log]])<br />
</small><br />
<br />
1 Aug<br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-08-01|minutes]], [[Oversight Board/Log-2008-08-01|log]])<br />
</small><br />
<br />
18 Jul (17.00 UTC)<br />
<small><br />
([[Oversight Board/Meeting Minutes-2008-07-18|minutes]], [[Oversight Board/Log-2008-07-18|log]])<br />
</small><br />
<br />
30 Jun (Mon, 17.00 UTC)<br />
<small><br />
([[Oversight Board/Meeting_Minutes-2008-06-30|minutes]], [[Oversight Board/Log-2008-06-30|log]])<br />
</small><br />
<br />
|}<br />
<br />
[[Category:Oversight board]]<br />
[[Category:Meetings]]<br />
[[Category:Meeting minutes]]<br />
[[Category:Governance]]</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick&diff=53901Sugar on a Stick2010-06-30T03:02:45Z<p>Mchua: /* Related work */</p>
<hr />
<div><noinclude><!--{{ Translations | [[Sugar_on_a_Stick|english]] &#124; [[Sugar_on_a_Stick/lang-es|español]] &#124; [[Sugar_on_a_Stick/lang-fr|français]]}}--><br />
[[Category:Project]]<br />
[[Category:Live USB]]<br />
[[Category:Sugar on a Stick]]<br />
</noinclude><br />
<br />
== What is Sugar on a Stick? ==<br />
<br />
{|<br />
|-<br />
| style="border: 0; border-width: 0; width: 350px;" | [[File:SugaronastickMirabelle.png |300px|left|link=http://spins.fedoraproject.org/soas]]<br />
| style="border: 0; border-width: 0;" | '''[[Sugar on a Stick]]''' is a [http://fedoraproject.org Fedora-based] [[wikipedia:Live USB|Live USB]] operating system featuring the award-winning [[What is Sugar?|Sugar Learning Platform]] and designed to fit on an ordinary USB thumbdrive ("stick"). Learn more about [http://spins.fedoraproject.org/soas/#home the project] and the [http://spins.fedoraproject.org/soas/#about principles] behind it at our [http://spins.fedoraproject.org/soas Spin webpage]. The most recent version is version 3, code-named '''[[Sugar on a Stick/Mirabelle|Mirabelle]]''' and was released on '''May 25, 2010.'''<br />
<br />
'''Turn your computer into a Sugar on a Stick Creation Station:''' A related project is the [[Sugar Creation Kit]], a downloadable DVD which includes the materials you need to create Mirabelle sticks and install additional Activities on it, along with documentation and previous versions of Sugar on a Stick.<br />
|}<br />
<br />
__TOC__<br />
<br />
=== Want to use Sugar on a Stick? ===<br />
<br />
{|<br />
|-<br />
| rowspan="3" style="border: 0; border-width: 0; width: 350px;" | [[File:Cici-maze.jpg |300px|left|link=http://spins.fedoraproject.org/soas]]<br />
|-<br />
|<br />
|style="border: 0; border-width: 0;" align="center" | [[File:Download Mirabell.png|center|link=http://spins.fedoraproject.org/soas/#downloads]]<br />
|-<br />
|<br />
|If you'd like to try out Sugar on a Stick, check out the [http://spins.fedoraproject.org/soas Sugar on a Stick Spin Page] - it's where our software downloads, installation and usage instructions, and support information lives.<br />
<br />
After you've tried out Sugar on a Stick, we hope you'll come back here and join our community of contributors to help us make the next release even better.<br />
|}<br />
<br />
=== Want to contribute to Sugar on a Stick? ===<br />
<br />
{|<br />
|-<br />
| style="border: 0; border-width: 0; width: 350px;" | [[File:SoaS-contributors.jpg |300px|left|link=Sugar_on_a_Stick]]<br />
| style="border: 0; border-width: 0;" |<br />
You're in the right place! This page is a contributors portal to the project, and contains everything you need to get started in becoming part of the Sugar on a Stick community.<br />
|}<br />
<br />
== New contributors start here! ==<br />
<br />
Welcome! We're excited that you want to help us bring the Sugar Learning Platform to children around the world. No prior experience with computers or educational technology is required - in fact, we actively encourage a diversity of backgrounds, ages, and perspectives. See the [[Joining Sugar on a Stick]] page for instructions on how to get started. You may also want to check out the [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Sugar on a Stick project page] on [http://openhatch.org OpenHatch], or attend one of our [[Sugar on a Stick meetings]].<br />
<br />
== What can you do? ==<br />
<br />
There are three main ways you can contribute to the Sugar on a Stick community. We work closely with our upstreams, [http://sugarlabs.org Sugar Labs] and [http://fedoraproject.org the Fedora Project].<br />
<br />
=== Get Activities on the Stick ===<br />
<br />
{|<br />
|-<br />
| style="border: 0; border-width: 0;" | <br />
<br />
We're always looking for help with all aspects of the [[Sugar on a Stick release process]]. Here are a few things you can do:<br />
<br />
* [[Sugar on a Stick QA|Test Sugar on a Stick]] and help us find bugs and think of ways the project could be better. When you find a bug or think of an enhancement, [[How to file a ticket|file a ticket!]] ''No technical experience required.''<br />
* Help make it easier for others to test Sugar on a Stick by writing [[Sugar on a Stick QA#Test cases|test cases]]. ''If you've run a test case, you can write a test case.''<br />
* [http://bugs.sugarlabs.org Fix a bug or add a feature] to an existing Activity, to [[Development Team|sugar-core itself]], or to [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=SoaS&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component Sugar on a Stick]. See [[How to fix an Activity bug]] and [[How to fix a sugar-core bug]] to get started. ''Basic Python programming skills - or the desire to learn - are all that's needed.''<br />
* [https://fedoraproject.org/wiki/Sugar_Activities Package Sugar Activities for Fedora]. ''If you're a [https://fedoraproject.org/wiki/PackageMaintainers/Join Fedora Packager] or want to become one, help in this area is something we desperately need - it's a trickier thing to learn, but rewarding once you get the hang of it.''<br />
* [[Sugar on a Stick release process#Review|Review Activities for inclusion in the build]] - check submitted Activities against our [[SoaS Activity Criteria]] and help us choose what gets included in the next release! ''No prior experience needed - we do reviews during our [[Sugar on a Stick meetings|weekly meetings]] and will teach you how.''<br />
* Have an idea for a technical feature that isn't an Activity? Check out our [[Sugar on a Stick release process#Feature process|feature process]].<br />
<br />
| style="border: 0; border-width: 0; width: 150px;" |[[Image:SoaS-netbook-1.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-2.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-3.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]]<br />
|}<br />
<br />
=== Get Sticks into Schools ===<br />
<br />
{|<br />
|-<br />
| style="border: 0; border-width: 0; width: 250px;" | [[File:Cici-stick.jpg |200px|left|link=Sugar_on_a_Stick_deployment_process]]<br />
| style="border: 0; border-width: 0;" | <br />
Deployments all over the world need many different types of help as they work through the [[Sugar on a Stick deployment process]] - we need help building resources for all deployments to use, supporting those deployments, and helping new deployments start, as well as gathering stories and feedback from deployments so that we can make the next version of Sugar on a Stick even better.<br />
<br />
Some things you can do to help:<br />
<br />
* ''"It's a wiki: Edit away!"'' is often said in open source communities. Almost nothing is set in stone and can't be undone. So if you've got ideas how to make instructions clearer and more accessible, just go for it!<br />
* We produce official documentation such as the [http://download.sugarlabs.org/soas/docs/creation-kit/ Creation Kit] or the [http://download.sugarlabs.org/soas/docs/customization-guide/ Customization Guide]. If you've an idea how to make them better, why don't you jump in and create a patch? Creating these nifty text files is simple - instructions live in the [[Sugar_on_a_Stick/Documentation_SOP|Documentation SOP]].<br />
* Unofficial documentation for unsupported workarounds for [[Sugar on a Stick/Installation|installation]] and [[Sugar on a Stick/Sugar Clone|customization]] need to be edited, tested, and submitted for approval for official support. Check them out and leave comments and improvements; just jump in and edit the page.<br />
* Interested in starting a deployment or helping a specific one (with anything from pedagogical design to technical support to funding logistics)? Introduce yourself on the deployment lists for [http://lists.sugarlabs.org/ Sugar Labs] and [http://lists.laptop.org/listinfo/ One Laptop Per Child] and we'll get you connected with some teachers on the ground.<br />
* We're looking for some people to help us assemble tools for our support team to use. Email the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] if you're interested.<br />
|}<br />
<br />
=== Get Contributors ===<br />
<br />
{|<br />
|-<br />
| style="border: 0; border-width: 0;" | <br />
<br />
Contributors are the lifeblood of the Sugar on a Stick community - we work hard to bring a playful mindset of teaching, learning, and meaningful work to the children we aim to reach, and we aim to keep that mindset in our own work and community as well. Welcoming and teaching new contributors or all types, building the resources they need, and teaching them how to empower others in their turn is one of the most important things you can do; it is ''everyone's'' responsibility to help build our community, one person at a time.<br />
<br />
Some things you can do:<br />
<br />
* Edit this page and [[Joining Sugar on a Stick]]. Is there something we could do to make the "getting started" process easier? You don't have to ask permission to edit; just do it!<br />
* Help us fill in our remaining task-starter pages: [[Sugar on a Stick release process]], [[How to fix an Activity bug]], [[How to fix a sugar-core bug]], and [[Sugar on a Stick deployment process]]/<br />
* [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Point out starter tasks on OpenHatch] - fill in questions and ideas for beginner jobs, and point newcomers towards them.<br />
* [http://lists.sugarlabs.org/listinfo/soas Watch for introductions on the mailing list], and send welcome emails to new contributors (copy the list, so we can see what advice a newcomer has gotten so far).<br />
* Hang out with us on IRC: [http://webchat.freenode.net?channels=sugar #sugar]. This is where the [http://activities.sugarlabs.org/en-US/sugar/addon/4029 IRC Activity] starts off. Help new joiners past initial questions and provide instant help!<br />
<br />
| style="border: 0; border-width: 0; width: 200px;" |[[Image:Cici-netbook.jpg|200px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick]]<br />
|}<br />
<br />
== What's happening? ==<br />
<br />
=== Meetings ===<br />
<br />
We have weekly meetings on IRC - see [[Sugar on a Stick meetings]] for more information, including logs from past meetings. Attending a meeting is a great way for newcomers to get started.<br />
<br />
=== Release schedule ===<br />
<br />
Our release schedule is based on the [[fedora:Releases/Schedule | Fedora release schedule]]. The most recent release was v.3, code-named [[Mirabelle]], shipped on '''May 25, 2010''' and based on the Fedora 13 release schedule. The next Sugar on a Stick version will be based on the [[fedora:Releases/14/Schedule | Fedora 14 release schedule]].<br />
<br />
{|border="1" cellspacing="0" width="100%"<br />
|-<br />
|rowspan="2"| 2010-05-25 || Sugar on a Stick v.3.0 Mirabelle released<br />
|-<br />
| Planning & Development Begins<br />
|-<br />
| 2010-07-27 || Feature Freeze (all features have to be ''approved'' and in a satisfying state.)<br />
|-<br />
| 2010-08-03 || Alpha Change deadline (all changes will have to be ''pushed'' by this time. pending submissions are insufficient.)<br />
|-<br />
| 2010-08-17 || Alpha Release<br />
|-<br />
| 2010-09-07 || Beta Change deadline (all changes will have to be ''pushed'' by this time. pending submissions are insufficient.)<br />
|-<br />
| 2010-09-21 || Beta Release<br />
|-<br />
| 2010-10-12 || Final Freeze (all changes have to be ''pushed''. no further changes permitted.)<br />
|-<br />
| 2010-10-14 || Compose Release Candidate<br />
|-<br />
| 2010-10-26 || Sugar on a Stick v.4.0 Final Release<br />
|-<br />
|}<br />
<br />
=== Contributor stories ===<br />
<br />
To find out what other contributors are doing, check out [http://planet.sugarlabs.org Planet Sugar Labs], where contributors to Sugar Labs and the Sugar on a Stick project aggregate their blogs. You can also [[Sysadmin/Planet syndication request|add your own blog to the Planet]].<br />
<br />
== Related work ==<br />
<br />
While the projects listed below are not part of Sugar on a Stick, we watch them closely and try to work with them when possible (or at least we're trying to learn!)<br />
<br />
* [[Talk:Sugar_Creation_Kit#Introduction_to_Soas-v3_Mirabelle|Introduction to Mirabelle]]<br />
* [[Sugar_on_a_Stick/Installation/Variations#SugarCreationKit_DVD|SugarCreationKit DVD]] - Complete DVD containing all the resources required to create all 3 versions of Sugar-on-a-Stick without requiring Internet access<br />
* Other [[:Category:Live USB|portable Sugar distributions]] - Live USB work based on other Linux distributions.<br />
* [[The undiscoverable]] is an unofficial FAQ for tips, tricks, and solutions to common problems that may otherwise be tricky to find. These are being considered for inclusion in the official SoaS documentation.<br />
<br />
== Previous versions and subpage index ==<br />
{{Show|Earlier versions of Sugar on a Stick can be reviewed at these pages: |{{Special:PrefixIndex/Sugar on a Stick}}}}</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_meetings&diff=53831Sugar on a Stick meetings2010-06-28T07:17:14Z<p>Mchua: /* Upcoming meeting */</p>
<hr />
<div><noinclude>{{TOCright}}<br />
[[Category:Sugar on a Stick]]<br />
[[Category:Meetings]]<br />
</noinclude><br />
== Meeting details ==<br />
<br />
Regular meetings for [[Sugar on a Stick]] take place on '''[irc://irc.freenode.net irc.freenode.net]''' in '''#sugar-meeting''', every '''Monday''' at '''1900 UTC'''.<br />
<br />
We use [[IRC]] for our meetings. If you don't have an IRC client (yet), you can use webchat - go to http://webchat.freenode.net and connect to #sugar-meeting, or click the screenshot below. (Replace "your_name" or the random ID provided with your name or some other nick you'd like to be known by.)<br />
<br />
[[File:Freenode-webchat-screenshot.png|left|link=http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1]]<br />
<br />
== How we run meetings ==<br />
<br />
With as much involvement as possible at all times.<br />
<br />
The motivation is to have as many simultaneous actively participating people in the meeting as possible - ideally, at ''all times'' in the meeting, ''everyone'' in the meeting should be ''doing something really cool'' (and hopefully related to Sugar on a Stick) - not just waiting for their turn to speak. Think of it as a virtual version of the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Philosophy law of two feet].<br />
<br />
Are YOU running a SoaS meeting? Take a look at [[How to run a meeting]] for an example of how a meeting is run, with commands listed out.<br />
<br />
== Agenda ==<br />
<br />
{{Anchor|Next_Meeting}}<br />
<br />
=== Every meeting ===<br />
<br />
* [[Sugar on a Stick#Release schedule]] upcoming deadlines announcement<br />
* [[Sugar on a Stick release process#Features submitted for review]]<br />
<br />
=== Upcoming meeting ===<br />
<br />
* http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Testing_process<br />
* mtd: "someone should just ask sdziallas and pbrobinson nicely if they'd mind terribly if someone suggested some patches / post-processing scripts for the soas spin .iso and promised to help maintain those patches / scripts for at least a few releases."<br />
* what people plan to work on for the v4 cycle<br />
<br />
== Future topics ==<br />
<br />
== Procedure for Minutes and Logging ==<br />
<br />
See the instructions on [[how to run a meeting]].<br />
<br />
== Minutes ==<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100621_1502.html 2010-06-21 (weekly meeting)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100614_1502.html 2010-06-14 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100614_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100607_1510.html 2010-06-07 Sugar on a Stick v4 Planning Meeting (regular weekly time)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100531_1507.html 2010-05-31 v3 Mirabelle Release Review Meeting (regular weekly time)]</div>Mchuahttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_meetings&diff=53830Sugar on a Stick meetings2010-06-28T07:16:19Z<p>Mchua: /* Minutes */</p>
<hr />
<div><noinclude>{{TOCright}}<br />
[[Category:Sugar on a Stick]]<br />
[[Category:Meetings]]<br />
</noinclude><br />
== Meeting details ==<br />
<br />
Regular meetings for [[Sugar on a Stick]] take place on '''[irc://irc.freenode.net irc.freenode.net]''' in '''#sugar-meeting''', every '''Monday''' at '''1900 UTC'''.<br />
<br />
We use [[IRC]] for our meetings. If you don't have an IRC client (yet), you can use webchat - go to http://webchat.freenode.net and connect to #sugar-meeting, or click the screenshot below. (Replace "your_name" or the random ID provided with your name or some other nick you'd like to be known by.)<br />
<br />
[[File:Freenode-webchat-screenshot.png|left|link=http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1]]<br />
<br />
== How we run meetings ==<br />
<br />
With as much involvement as possible at all times.<br />
<br />
The motivation is to have as many simultaneous actively participating people in the meeting as possible - ideally, at ''all times'' in the meeting, ''everyone'' in the meeting should be ''doing something really cool'' (and hopefully related to Sugar on a Stick) - not just waiting for their turn to speak. Think of it as a virtual version of the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Philosophy law of two feet].<br />
<br />
Are YOU running a SoaS meeting? Take a look at [[How to run a meeting]] for an example of how a meeting is run, with commands listed out.<br />
<br />
== Agenda ==<br />
<br />
{{Anchor|Next_Meeting}}<br />
<br />
=== Every meeting ===<br />
<br />
* [[Sugar on a Stick#Release schedule]] upcoming deadlines announcement<br />
* [[Sugar on a Stick release process#Features submitted for review]]<br />
<br />
=== Upcoming meeting ===<br />
* ASLOxo-USB-Installer: http://wiki.sugarlabs.org/go/Features/Soas_V4/ASLOxo-USB-Installer<br />
* [[Features/Revised_Browse_default-bookmarks.html]] - feature for consideration<br />
:: Suggested that this use link to Wiki Page '''Introduction_to_Soas-v3_Mirabelle''' [http://wiki.sugarlabs.org/go/Talk:Sugar_Creation_Kit#Introduction_to_Soas-v3_Mirabelle]-To be updated for v4 when it is released<br />
* dev-test-release cycle.<br />
* Testing Suggestions Outline for Discussion:(satellit) <br />
1- '''Bootable USB''' Windows/linux/Mac<br />
a- livecd-iso-to-disk - script<br />
b- liveusb-creator - application<br />
c- unetbootin - application<br />
e- dd=? - direct write to USB (probably unsupported)<br />
f- Direct creation of an .img file for distribution ala Bernie's Blueberry-Direct (probably unsupported)<br />
2- '''CD works?'''<br />
a-i386<br />
b-i386-64<br />
3- '''Install to Virtualbox (Virtualization)''' Windows/linux/Mac<br />
a- Re institute Distribution of Virtual box appliances: http://download.sugarlabs.org/soas/appliances/ <br />
4- '''Test against Activities'''<br />
- Ooo Spreadsheet ?[http://people.sugarlabs.org/Tgillard/Activities-Index-ASLO-f13-Mirabelle-f14-rawhide-Soas-tests-GC.ods]<br />
a- How share it?<br />
b- Move this information to the Sugarlabs Wiki in a shared Spreadsheet format?<br />
Done: http://wiki.sugarlabs.org/go/Features/Soas_V4/ASLOxo_Activity_Test_Table<br />
c-.xo vs rpm installs and many activities on ASLO vs in Repository- where to draw the line.<br />
5- '''Collaboration between:'''<br />
a- XO--1<br />
b- XO-1.5<br />
c- 0.84<br />
d- 0.86<br />
e- 0.88 and 0.88.1<br />
6- '''Wireless works?'''<br />
- Models of Netbook yes/no<br />
- wireless drivers used<br />
7-Testing 0.90.0: http://wiki.sugarlabs.org/go/0.90/Testing#SoaS<br />
<br />
* mtd: "someone should just ask sdziallas and pbrobinson nicely if they'd mind terribly if someone suggested some patches / post-processing scripts for the soas spin .iso and promised to help maintain those patches / scripts for at least a few releases."<br />
* what people plan to work on for the v4 cycle<br />
<br />
== Future topics ==<br />
<br />
== Procedure for Minutes and Logging ==<br />
<br />
See the instructions on [[how to run a meeting]].<br />
<br />
== Minutes ==<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100621_1502.html 2010-06-21 (weekly meeting)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100614_1502.html 2010-06-14 (weekly meeting)] [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100614_1502.html (log)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100607_1510.html 2010-06-07 Sugar on a Stick v4 Planning Meeting (regular weekly time)]<br />
* [http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100531_1507.html 2010-05-31 v3 Mirabelle Release Review Meeting (regular weekly time)]</div>Mchua