Re: [IAEP] Announce: OLPC software strategy.
You're asking me to rejustify decisions made in November 2009 when the environment was somewhat different. We had informal unpublished plans to release but we had no release name chosen. The change I made months ago was to facilitate testers and bug reporters ... to increase the data quality by removing the version numbers from a popup list, and encouraging use of the keywords field. The naming scheme was chosen because people had been logging tickets using the milestone as a version field. So I wanted to deprive them of that option in the long run. This also gave us the flexibility to use any version number we like for a release. On Sun, Jul 11, 2010 at 09:05:45PM -0400, Martin Langhoff wrote: > On Sun, Jul 11, 2010 at 8:45 PM, James Cameron wrote: > > Use 1.x-software-update for tickets you plan to have fixed for the next > > release. ?(Choose these tickets based on the intent of the release). > > That's not how Trac is designed to work, however. And not how most > (all minus olpc? ;-) ) use it. > > You are using the milestones as a "sliding window", so > 'sofrware-update' means "whatever the next release is". Trac allows any use of the milestone field; in software project management one does not always map a milestone to a release name. Conflating the two was causing confusion. I wanted to be rid of the old milestone values too, but the argument against that was that the old data was harmless and occasionally useful. > > Use 1.x-software-later for tickets you intend to delay until after the > > next release. ?(Choose these tickets where the effort required exceeds > > the available time and there are more important tickets). > > So everytime we have a release you reset all the 1.x-software-later > tickets to 1.x-software-update? Certainly not. Instead you should cherry pick those tickets that you plan to fix. This is how we've been doing it. > That is literally backwards from the normal usage. > > By using it this way we completely miss the ability to query trac thus: > - show me the changelog for 10.1.1 (status=closed and > milestone=10.1.1) > - what release was bug X fixed in? (all tasks are fixed in > 'software-update'!) I'm not missing either of those abilities. I make sure that I enter the build number when I've tested a problem to confirm it is solved. I really really dislike the idea of building a changelog by capturing a list of tickets closed that had a milestone of a particular value: - tickets are often closed during the window leading up to a release without their milestone reflecting anything useful. I don't want to have to add procedures to check for this. - the actual changes made by developers should be captured instead. > Why don't we use it in the way it was designed to be used...? Might > even work ;-) Your arguments are not sufficiently compelling. The changed environment does suggest some changes to bug tracking ... 1. we need to track tickets that are cross platform (XO-1 and XO-1.5), and currently we only have "milestone is either 1.0-software-update or 1.5-software-update" [2] 2. we need new milestones for the as yet unnamed Fedora 13 for XO-1.75 work. Ideally we would migrate to a more flexible bug tracking solution, such as Launchpad. It better supports multiple teams and multiple goals. But I don't think the situation warrants that level of investment yet. [1] http://lists.laptop.org/pipermail/devel/2009-November/026444.html [2] http://dev.laptop.org/query?status=assigned&status=new&status=reopened&max=1000&order=priority&col=id&col=summary&col=milestone&col=priority&col=component&milestone=1.0-software-update&milestone=1.5-software-update&report=43#no1 -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [IAEP] Announce: OLPC software strategy.
On Sun, Jul 11, 2010 at 8:45 PM, James Cameron wrote: > Use 1.x-software-update for tickets you plan to have fixed for the next > release. (Choose these tickets based on the intent of the release). Ok. That's not how Trac is designed to work, however. And not how most (all minus olpc? ;-) ) use it. You are using the milestones as a "sliding window", so 'sofrware-update' means "whatever the next release is". > Use 1.x-software-later for tickets you intend to delay until after the > next release. (Choose these tickets where the effort required exceeds > the available time and there are more important tickets). So everytime we have a release you reset all the 1.x-software-later tickets to 1.x-software-update? That is literally backwards from the normal usage. By using it this way we completely miss the ability to query trac thus: - show me the changelog for 10.1.1 (status=closed and milestone=10.1.1) - what release was bug X fixed in? (all tasks are fixed in 'software-update'!) ... ... Why don't we use it in the way it was designed to be used...? Might even work ;-) m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [IAEP] Announce: OLPC software strategy.
On Fri, Jul 09, 2010 at 05:33:54PM -0400, Martin Langhoff wrote: > On Wed, Jul 7, 2010 at 6:01 PM, Chris Ball wrote: > > XO-1.5: > > === > > > > We'll be continuing to work on XO-1.5 improvements, incorporating > > fixes to the "Known Problems" section of the 10.1.1 release notes? > > into the 10.1.2 release. > > Chris, James, > > can we rename the upcoming milestone to 10.1.2? :-) If you mean the trac milestone, no. Use 1.x-software-update for tickets you plan to have fixed for the next release. (Choose these tickets based on the intent of the release). Use 1.x-software-later for tickets you intend to delay until after the next release. (Choose these tickets where the effort required exceeds the available time and there are more important tickets). Use "Future Release" or "Opportunity" for tickets that you expect won't be done in the release after next. Usually because there is nobody willing to fix this now. Feel free to use the keywords field though. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: NetworkManager time sync
El Wed, 07-07-2010 a las 12:20 -0400, Martin Langhoff escribió: > Apparently the ntp protocol supports some server-signing of the > messages -- we could use an OATS key for that. But it looks rickety. Authenticated NTP sounds like a good solution. NTP4 supports public key cryptography based on SSL certificates. We don't have to reuse the OATS keys for authentication and we also don't have to use the same server for OATS and NTP. Any trusted public ntp server should be fine. Maybe also the school servers. So, how about setting up a public ntp server and publishing the keys? I've already been running two public servers for one year or so: time1.sugarlabs.org time2.sugarlabs.org These are registered with ntp.org. I could generate keys and use them with py builds. Anyone else would be welcome to use our servers, of course. Alternatively, we could simply distribute ntp keys to our xs with puppet. However, this would stop working once the kids leave the school system. In case we opt for using public ntp servers with no authentication, I've also registered olpc.ntp.org (as recommended by someone in this thread). -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
In 2 Hrs! "Virtual Field Trip Realness (Classrooms ain't in Kansas Nomore)"
Speaker's PDF slides: http://wiki.laptop.org/go/File:OLPC_2010Jul11VirtuaFieldTrip.pdf Please join us in 2 hrs (4PM Sunday, Eastern Time in Boston/NYC) by calling: +1 (712) 432-3030 Conference Code: 637497 Live Chat Backchannel: http://forum.laptop.org/chat (that's *#olpc-help* on irc.freenode.net) *Sunday July 11 - Virtual Field Trip Realness (Classrooms ain't in Kansas Nomore)* By Laura Susan Bell, Virtual Field Trip Facilitator & OLPC Support Volunteer. Laura will explain how she administers classrooms in Upper NY State, taking her students on virtual field trips will real-live NASA engineers etc, who ship her in-classroom supplies in-advance to dramatically liven the experience for all kids. *Sunday July 18 - Eleven Years Deploying Computers in South African Schools* By Alan Field & Donna Wainwright, in person at OLPC in Cambridge, MA. Alan will discuss the many deep lessons he's learned along the way, over the 11 years he and his wife Donna have spent teaching & training using Macs across 30 schools 300KM SE of Johannesburg. Towards both "Creative Learning" and "Drill and K^hThrill" -- come learn some tough and vital lessons on where Mandela's post-World Cup nation is heading: http://web.mac.com/donita27/EndumeniLearningMachines/Home.html *Sunday July 25 NOON - East Africa and West Africa OLPC Community Public Brunch* NYC/Bronx Location announced hereunder -- plz RSVP now to holt @ laptop dot org, thx! http://wiki.laptop.org/go/OLPC_NYC http://lists.laptop.org/pipermail/olpc-nyc/ http://twitter.com/olpcnyc *Sunday Aug 1 - From Viet Cong to Venture Capital to Vietnam Community (TENTATIVE)* Location/Parti-Pants to be announced. How has OLPC's Vietnam Community progressed so far, so fast, in just 1 year? http://olpc.vn http://saigonolpc.wordpress.com http://wiki.laptop.org/go/OLPC_Vietnam http://groups.google.com/group/olpc-vietnam/ http://web.me.com/seanlaurence/olpc/olpc.html http://www.travelpod.com/travel-blog/nsevers/4/tpod.html http://wiki.laptop.org/go/Projects/Vung_Vieng_Fishing_Vietnam * Sunday Aug 8 - What's Really Happening in India, at the Grassroots Level? (TENTATIVE) *Locations to be announced. The astonishing number of volunteers and informal community projects in India makes it hard to keep track of them all. Professor Sameer Verma in San Francisco will explain how these amazing community volunteers and corporate professionals scattered across the Indian subcontinent can now take their contributions to the next level. /REMINDER: while meetings are generally for OLPC volunteers/staff only, accompanying friends are welcome if personally introduce, and are willing to help Make S---^h^h^hUPPORT Happen!!/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Announce: OLPC software strategy.
On Sat, Jul 10, 2010 at 9:21 AM, Andrew van der Stock wrote: > waiting for more dev boards to arrive The SoC is similar to the Sheeva Plug so the CPU/platform porting can be done on one of those. Driver stuff is a different matter, of course - m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
