Thank you Anne.
On Tue, Feb 17, 2009 at 1:45 PM, Anne Kathrine Petteroe <[email protected]>wrote: > I have created an account now ;-) > > I will break up the UI tasks later tonight and post them here on the group > first as part of the UI sprint planning. > > /Anne > > > On 17. feb.. 2009, at 09.02, Hirsch, Richard wrote: > > Does each person want to add their own items to Jira or should we collect >> / discuss them via mailing list and then after a few days, I can collect >> them and add them to Jira. >> >> Does everyone have an account in the Apache Jira? If you don't have a >> user, then we can't assign tasks. You don't have to submit an iCLA to have >> a Apache Jira account. I didn't see Mrinal or Anne. Could you both create >> users on Jira. >> >> D. >> >> -----Ursprüngliche Nachricht----- >> Von: Hirsch, Richard >> Gesendet: Dienstag, 17. Februar 2009 08:54 >> An: [email protected] >> Betreff: AW: Next Sprint >> >> I agree that Jira is probably best place to base the sprints. I think the >> current tasks are too broad. >> >> For example, ESME-6 ( https://issues.apache.org/jira/browse/ESME-6 ) is >> "Support for Twitter API". Should we break this down into smaller Jira >> tasks. If you look at the official wiki from twitter ( >> http://apiwiki.twitter.com/REST+API+Documentation), there are already >> categories ("Status Methods", "User Methods", etc.). That might be easier. >> >> Ideas? >> >> P.S. I also like the way the twitter wiki is structured to document their >> REST API. Maybe we can use it as a basis for our documentation. >> >> D. >> >> -----Ursprüngliche Nachricht----- >> Von: Vassil Dichev [mailto:[email protected]] >> Gesendet: Dienstag, 17. Februar 2009 07:08 >> An: [email protected] >> Betreff: Re: Next Sprint >> >> I read that David isn't going to have a lot of time for this sprint. >>> What about Vassil and Darren? >>> >> >> As usual, I have a moderate amount of time in the hours after son goes >> to sleep :) >> >> Besides the obvious choice of work on the UI (where we are way behind), >>> REST API and Twitter API, does anyone else have other suggestions. >>> >> >> Twitter API is what I'm going to concentrate on, my todo list there is >> fairly big and I don't want to bite off more than I can chew. Besides, >> most other tasks influence all of ESME (groups, permissions), so it's >> necessary for more than one person to agree on how we want it >> implemented. >> >> To summarize my view on the topic of whether sprints are useful- like >> Darren, I also think it's beneficial to set some short-term goals, >> even if we're not 100% successful. One planning problem here is that >> everyone is moving at a different pace every sprint. Prioritized lists >> would be of real help here. JIRA could fit quite nicely in this case, >> I think. >> > >
