Re: Software Status Meeting Tomorrow @ 1400 EDT, 1800 UTC in #olpc-meeting on freenode
On Wed, Jun 18, 2008 at 07:45:22AM -0700, Deepak Saxena wrote: > Do you mean today? Yes, apologies. I'm on autopilot. Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Software Status Meeting Tomorrow @ 1400 EDT, 1800 UTC in #olpc-meeting on freenode
On Jun 18 2008, at 11:15, Michael Stone was caught saying: > Hey folks, > > My sincere apologies for the short notice. If you're around, please join > us at the usual time and place: #olpc-meeting on irc.freenode.org for > our software status update. Michael, Do you mean today? ~Deepak -- Deepak Saxena <[EMAIL PROTECTED]> ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Software Status Meeting Tomorrow @ 1400 EDT, 1800 UTC in #olpc-meeting on freenode
Hey folks, My sincere apologies for the short notice. If you're around, please join us at the usual time and place: #olpc-meeting on irc.freenode.org for our software status update. Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Software Status Meeting Tomorrow @ 1400 EDT, 1800 UTC in #olpc-meeting on freenode
On Tue, Jun 10, 2008 at 6:55 PM, Michael Stone <[EMAIL PROTECTED]> wrote: > Note the return to original time: 2:00 PM EST, 6:00 PM UTC. > > Let's chat about G1G1 and our goals for August. Please reply with any > other topics that are on your mind. OLPC-3 status. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Software Status Meeting Tomorrow @ 1400 EDT, 1800 UTC in #olpc-meeting on freenode
Note the return to original time: 2:00 PM EST, 6:00 PM UTC. Let's chat about G1G1 and our goals for August. Please reply with any other topics that are on your mind. Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Software Status Meeting Tomorrow @ 1400 EDT, 1800 UTC in #olpc-meeting on freenode
great idea. -walter On Wed, May 28, 2008 at 6:39 PM, David Farning <[EMAIL PROTECTED]> wrote: > On Wed, 2008-05-28 at 19:40 +0200, Marco Pesenti Gritti wrote: > >> > Finally, there is the issue of work queues. I still have no clue how to >> > represent, using either either Trac or the wiki, the fact that every >> > individual has a work queue which differs from the Global Ticket >> > Priority ordering. People clearly have personal queues for all sorts of >> > reasons including: >> > >> > * people process several tickets concurrently to avoid waiting on one >> >another >> > >> > * individuals often prefer to fix easy, hard, or well-understood >> >things first >> > >> > * people barter work among themselves in order to help one another >> >finish things off; this causes people to work on surprising things >> > >> > (I want to know about personal queues because I want to pay attention to >> > the instantaneous velocity of development [i.e. in order to predict >> > where the code base will have moved to after the next \epsilon units of >> > time have elapsed].) >> >> Couple of random ideas: >> >> * Several people started to add a TODO to their User wiki page on >> sugarlabs.org. We might encourage something like that. It's unlikely >> that everyone will do it and keep it updated though. >> * At Red Hat all the engineers are sending in weekly status reports, >> which also contains a "Plans for this week" section. >> >> Marco > If you go with individuals keeping a personal TODO list on their user > pages, it is very easy to create a master User:TODO list that aggregates > all of the individual todo list. > > This is how I am setting http://wiki.sugarlabs.org/go/Community/TODO . > > thanks > David Farning > > ___ > Sugar mailing list > [EMAIL PROTECTED] > http://lists.laptop.org/listinfo/sugar > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Software Status Meeting Tomorrow @ 1400 EDT, 1800 UTC in #olpc-meeting on freenode
On Wed, 2008-05-28 at 19:40 +0200, Marco Pesenti Gritti wrote: > > Finally, there is the issue of work queues. I still have no clue how to > > represent, using either either Trac or the wiki, the fact that every > > individual has a work queue which differs from the Global Ticket > > Priority ordering. People clearly have personal queues for all sorts of > > reasons including: > > > > * people process several tickets concurrently to avoid waiting on one > >another > > > > * individuals often prefer to fix easy, hard, or well-understood > >things first > > > > * people barter work among themselves in order to help one another > >finish things off; this causes people to work on surprising things > > > > (I want to know about personal queues because I want to pay attention to > > the instantaneous velocity of development [i.e. in order to predict > > where the code base will have moved to after the next \epsilon units of > > time have elapsed].) > > Couple of random ideas: > > * Several people started to add a TODO to their User wiki page on > sugarlabs.org. We might encourage something like that. It's unlikely > that everyone will do it and keep it updated though. > * At Red Hat all the engineers are sending in weekly status reports, > which also contains a "Plans for this week" section. > > Marco If you go with individuals keeping a personal TODO list on their user pages, it is very easy to create a master User:TODO list that aggregates all of the individual todo list. This is how I am setting http://wiki.sugarlabs.org/go/Community/TODO . thanks David Farning ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Software Status Meeting Tomorrow @ 1400 EDT, 1800 UTC in #olpc-meeting on freenode
On Wed, May 28, 2008 at 4:08 PM, Michael Stone <[EMAIL PROTECTED]> wrote: > On Wed, May 28, 2008 at 03:02:17PM +0200, Marco Pesenti Gritti wrote: >> Relying on email and irc for this seems fragile to me. If a trac query >> would reveal the packages which are staged for inclusion in a certain >> release, it would be pretty much impossible that they go unnoticed. >> >> Marco > > That's fair. Suppose we make tickets for each release contract. The > relevant properties of the contracts that we want to represent include > their risk of slippage, the people who are responsible for seeing them > to fruition, and some material about the terms of the contract like > links to test cases, test results, and which bugs/features are supposed > to be finished upon successful completion of the contract. > > Some of these things are easy to represent with existing Trac features. > For example, we might represent slippage risk with a simple tag scheme > like > > :+, :?, and :- > > Example interpretation: If we saw a ticket labeled > > rel-8.1.1:- rel-8.2:? > > then we should conclude that this was a contract which had slipped from > 8.1.1 to 8.2 and which was in question in 8.2. (The advantage of this > scheme over regular milestones is that my example ticket would be > represented in proper context in displays about either 8.1.1 or 8.2). > > We also need some way of recording what actual people are responsible > for bringing the contract to fruition. Trac only permits one Owner but > it permits many tags. It seems that tags like > > : (e.g. tester:erikos) > > would suffice for this purpose. > > What to do about test cases and test results? Perhaps we should > establish a convention that all release contracts will have a test cases > wiki page and a test results wiki page at specific names, e.g. > > wiki.laptop.org/go/Test Cases/ > wiki.laptop.org/go/Test Results/ > > and modify Trac to automatically insert prominent hyperlinks on tickets > tagged "rel-contract"? All of this sounds pretty good to me. > Finally, there is the issue of work queues. I still have no clue how to > represent, using either either Trac or the wiki, the fact that every > individual has a work queue which differs from the Global Ticket > Priority ordering. People clearly have personal queues for all sorts of > reasons including: > > * people process several tickets concurrently to avoid waiting on one >another > > * individuals often prefer to fix easy, hard, or well-understood >things first > > * people barter work among themselves in order to help one another >finish things off; this causes people to work on surprising things > > (I want to know about personal queues because I want to pay attention to > the instantaneous velocity of development [i.e. in order to predict > where the code base will have moved to after the next \epsilon units of > time have elapsed].) Couple of random ideas: * Several people started to add a TODO to their User wiki page on sugarlabs.org. We might encourage something like that. It's unlikely that everyone will do it and keep it updated though. * At Red Hat all the engineers are sending in weekly status reports, which also contains a "Plans for this week" section. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Software Status Meeting Tomorrow @ 1400 EDT, 1800 UTC in #olpc-meeting on freenode
Including the testing ml as well. Items that are scheduled for testing (and might have issues for the 2pm edt meeting): 1 - Build 706, candidate 8.1.1, with fixes as described by Michael (I still see almost all the same problems with kreyol as were written up in #6973; and there are still some issues with Amharic. It is being tested in a network environment, what other testing is needed?) 2 - Build 703-2, peru image with activities (available from Scott today; needs discussion on how to name and store these 'country specific' images) 3 - Build 703-2, g1g1 image with activities (not available yet, but the support and mfg group are anxious to get it) 4 - Joyride and/or what we decide to use as the base for 8.2.0, August release. (Michael, I will be in another meeting at the same time, but I will try to get together with you later on these). Kim On Wed, May 28, 2008 at 12:18 AM, Michael Stone <[EMAIL PROTECTED]> wrote: > Let's talk tomorrow about #7014, build 706 (which everyone ought to > test; olpc-update -f update.1-706), and what we should take away from > the fact that Blake and Ricardo were the only people who contributed > patches/packages for inclusion in our bugfix release. > > Please reply to this mail with any other subjects that you would like us > to discuss. I'll see if we can fit them in. > > Michael > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Software Status Meeting Tomorrow @ 1400 EDT, 1800 UTC in #olpc-meeting on freenode
On Wed, May 28, 2008 at 03:02:17PM +0200, Marco Pesenti Gritti wrote: > Relying on email and irc for this seems fragile to me. If a trac query > would reveal the packages which are staged for inclusion in a certain > release, it would be pretty much impossible that they go unnoticed. > > Marco That's fair. Suppose we make tickets for each release contract. The relevant properties of the contracts that we want to represent include their risk of slippage, the people who are responsible for seeing them to fruition, and some material about the terms of the contract like links to test cases, test results, and which bugs/features are supposed to be finished upon successful completion of the contract. Some of these things are easy to represent with existing Trac features. For example, we might represent slippage risk with a simple tag scheme like :+, :?, and :- Example interpretation: If we saw a ticket labeled rel-8.1.1:- rel-8.2:? then we should conclude that this was a contract which had slipped from 8.1.1 to 8.2 and which was in question in 8.2. (The advantage of this scheme over regular milestones is that my example ticket would be represented in proper context in displays about either 8.1.1 or 8.2). We also need some way of recording what actual people are responsible for bringing the contract to fruition. Trac only permits one Owner but it permits many tags. It seems that tags like : (e.g. tester:erikos) would suffice for this purpose. What to do about test cases and test results? Perhaps we should establish a convention that all release contracts will have a test cases wiki page and a test results wiki page at specific names, e.g. wiki.laptop.org/go/Test Cases/ wiki.laptop.org/go/Test Results/ and modify Trac to automatically insert prominent hyperlinks on tickets tagged "rel-contract"? Finally, there is the issue of work queues. I still have no clue how to represent, using either either Trac or the wiki, the fact that every individual has a work queue which differs from the Global Ticket Priority ordering. People clearly have personal queues for all sorts of reasons including: * people process several tickets concurrently to avoid waiting on one another * individuals often prefer to fix easy, hard, or well-understood things first * people barter work among themselves in order to help one another finish things off; this causes people to work on surprising things (I want to know about personal queues because I want to pay attention to the instantaneous velocity of development [i.e. in order to predict where the code base will have moved to after the next \epsilon units of time have elapsed].) Comments? Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Software Status Meeting Tomorrow @ 1400 EDT, 1800 UTC in #olpc-meeting on freenode
Relying on email and irc for this seems fragile to me. If a trac query would reveal the packages which are staged for inclusion in a certain release, it would be pretty much impossible that they go unnoticed. Marco On Wed, May 28, 2008 at 2:25 PM, Michael Stone <[EMAIL PROTECTED]> wrote: > On Wed, May 28, 2008 at 10:15:07AM +0200, Tomeu Vizoso wrote: >> Hi, >> >> the sugar team built a new rpm to be included in the 8.1.1 release, see: >> >> http://lists.laptop.org/pipermail/sugar/2008-May/005935.html >> >> Should I enter a ticket or something? > > Don't bother; this reminder email is fine - I'll see what I can do. Is > anyone from the Sugar team able to help out with testing this week? > > Michael > > P.S. - In the future, please ping me directly if you write threads like > the one you cited and I haven't replied to them within, say, two days. > I apologize that this one escaped my notice since I remember requesting > a block of changes like this one from you around when this thread was > written. > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Software Status Meeting Tomorrow @ 1400 EDT, 1800 UTC in #olpc-meeting on freenode
On Wed, May 28, 2008 at 10:15:07AM +0200, Tomeu Vizoso wrote: > Hi, > > the sugar team built a new rpm to be included in the 8.1.1 release, see: > > http://lists.laptop.org/pipermail/sugar/2008-May/005935.html > > Should I enter a ticket or something? Don't bother; this reminder email is fine - I'll see what I can do. Is anyone from the Sugar team able to help out with testing this week? Michael P.S. - In the future, please ping me directly if you write threads like the one you cited and I haven't replied to them within, say, two days. I apologize that this one escaped my notice since I remember requesting a block of changes like this one from you around when this thread was written. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Software Status Meeting Tomorrow @ 1400 EDT, 1800 UTC in #olpc-meeting on freenode
On Wed, May 28, 2008 at 6:18 AM, Michael Stone <[EMAIL PROTECTED]> wrote: > Please reply to this mail with any other subjects that you would like us > to discuss. I'll see if we can fit them in. Release process for August. Unless we want to start tackling that after the stable release is out... Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Software Status Meeting Tomorrow @ 1400 EDT, 1800 UTC in #olpc-meeting on freenode
On Wed, May 28, 2008 at 6:18 AM, Michael Stone <[EMAIL PROTECTED]> wrote: > Let's talk tomorrow about #7014, build 706 (which everyone ought to > test; olpc-update -f update.1-706), and what we should take away from > the fact that Blake and Ricardo were the only people who contributed > patches/packages for inclusion in our bugfix release. Hi, the sugar team built a new rpm to be included in the 8.1.1 release, see: http://lists.laptop.org/pipermail/sugar/2008-May/005935.html Should I enter a ticket or something? Thanks, Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Software Status Meeting Tomorrow @ 1400 EDT, 1800 UTC in #olpc-meeting on freenode
Let's talk tomorrow about #7014, build 706 (which everyone ought to test; olpc-update -f update.1-706), and what we should take away from the fact that Blake and Ricardo were the only people who contributed patches/packages for inclusion in our bugfix release. Please reply to this mail with any other subjects that you would like us to discuss. I'll see if we can fit them in. Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Software Status Meeting Tomorrow @ 1400 EDT, 1800 UTC in #olpc-meeting on freenode
On Wed, May 7, 2008 at 11:32 AM, Michael Stone <[EMAIL PROTECTED]> wrote: > Let's spend an hour tomorrow at 2:00 PM (1400 EDT, 1800 UTC) describing > the tasks that we are presently working on and the technical Hi Michael, apologies in advance. I probably won't make it - this week I am taking it slow (and 6am meetings don't fit in my definition of "slow" ;-) ). When I get back on track (~tuesday next week), I'll be working on - fixing some installation bugs on the XS image - backup backup backup Apologies to Tomeu & Dennis Gilmore - I dropped out of plans to work together on various things. I'll be onto it next week and I will get in touch with you ;-) cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- 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
Software Status Meeting Tomorrow @ 1400 EDT, 1800 UTC in #olpc-meeting on freenode
Folks, Let's spend an hour tomorrow at 2:00 PM (1400 EDT, 1800 UTC) describing the tasks that we are presently working on and the technical frustrations we are presently encountering or the progress that we have recently made. Thanks, Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
