RE: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference (August 17))
Hi Ravi,
I used 'a-z' at the end instead of a number for contrast. Also I have yet to see a meeting produce more than 26 actions but if we ever manage to do it we could always append another letter at the end. :-)
I thought about putting in the year but chose not to because an action continuing for that long is either obsolete or it is a project. In either case it shouldn't stay on this list! In other words, this list in intended for short, one-off actions that don't need much tracking but which we don't want to forget between meetings.
If the result of an action is to start a document then the action is closed and we track issues relating to that document more formally in that document's tracker. It's not the intention here to re-invent
Thanks. I am ok with Andreas' rationale too. Just a quick clarification though: The "resolution" I was referring to was not the resolution of the action item but noting any resolutions that were made/taken in the meeting, for example, if we decided that "All documents will be in 12 point font". It would be good to record such resolutions taken (or maybe there is a better word than 'resolution'). These will likely be around for a while and so the 'year' may be required here :-). Ravi -----Original Message----- From: Hiro Kishimoto [mailto:hiro.kishimoto@jp.fujitsu.com] Sent: Thursday, August 17, 2006 11:42 PM To: Andreas Savva Cc: Subramaniam, Ravi; OGSA-WG ML Subject: Re: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference (August 17)) Hi Andreas and Ravi, Andreas's suggestions work for me. Thanks, ---- Hiro Kishimoto Andreas Savva wrote: trackers.
Until now this list lived at the bottom of the minutes and stuff got deleted once closed, with some explanation in the minutes. I think we could have a heading (I like RS :-) but 'Done' would also be good) at the end of the wiki page and move closed/resolved items under it with
a
link to the relevant minutes; much like what Hiro does with the teleconference schedule wiki page.
Andreas
Subramaniam, Ravi wrote:
Hi Andreas,
A small suggestion, if I may - would it make sense to augment the AI numbering from AI-mmdd'a-z' to AI-yymmdd-'number'. I think we need to think in terms of clarity since we can have AIs that span years especially near the end of the year. Also a - z means 26; could we not have more? :-).
Since this trend has been started, could you also introduce RS (not Ravi Subramaniam :-) or RT for 'resolutions or resolution taken'.
Ravi
-----Original Message----- From: owner-ogsa-wg@ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Andreas Savva Sent: Tuesday, August 15, 2006 11:31 PM To: 'OGSA-WG ML' Subject: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference (August 17))
Donal's email motivated me to put the existing action list on the wiki. (This might make it easier to refer to and for other people--besides Hiro--to maintain.)
https://forge.gridforum.org/sf/wiki/do/viewPage/projects.ogsa-wg/wiki/Ac
tionItems or http://tinyurl.com/pzqs2
(This wiki page is not intended to replace trackers! Trackers record issues on documents.)
I seem to recall that there was an action item (on me) from the August 10 telecon relating to review and updating of the EMS scenario document. It's important that we don't lose track of these things...
Donal.
Ravi, I still feel that what you are asking is too fine-grain and would not work in the long run. What is really needed is to document what the approach is on important topics. Taking the 'font' example below it would not be very useful on a general list of resolutions if that list also included stuff on information modeling, execution management, data access, security, etc. Instead if someone thinks a topic is important and they want to maintain a short (or long) document explaining what the group consensus is, and *keep it up-to-date* I would be all for it. I'll just point out that I did set up an "Architecture Notes" forum some time back and we still only have one note there. But it's a very good note and I later used it to write up one subsection in OGSA 1.5. Andreas Subramaniam, Ravi wrote:
Thanks. I am ok with Andreas' rationale too.
Just a quick clarification though: The "resolution" I was referring to was not the resolution of the action item but noting any resolutions that were made/taken in the meeting, for example, if we decided that "All documents will be in 12 point font". It would be good to record such resolutions taken (or maybe there is a better word than 'resolution'). These will likely be around for a while and so the 'year' may be required here :-).
Ravi
-- Andreas Savva Fujitsu Laboratories Ltd
Hi Andreas and Ravi, I think OGSA-WG should preserve a delicate balance between light & doable process and precise discussion record which avoids repeated arguments. I agree with Andreas to use current very light-weight AIs maintenance process. WRT. resolutions Ravi mentioned, we may create new wiki pages to keep resolutions if we have volunteers. Thanks, ---- Hiro Kishimoto Andreas Savva wrote:
Ravi,
I still feel that what you are asking is too fine-grain and would not work in the long run. What is really needed is to document what the approach is on important topics.
Taking the 'font' example below it would not be very useful on a general list of resolutions if that list also included stuff on information modeling, execution management, data access, security, etc. Instead if someone thinks a topic is important and they want to maintain a short (or long) document explaining what the group consensus is, and *keep it up-to-date* I would be all for it.
I'll just point out that I did set up an "Architecture Notes" forum some time back and we still only have one note there. But it's a very good note and I later used it to write up one subsection in OGSA 1.5.
Andreas
Subramaniam, Ravi wrote:
Thanks. I am ok with Andreas' rationale too.
Just a quick clarification though: The "resolution" I was referring to was not the resolution of the action item but noting any resolutions that were made/taken in the meeting, for example, if we decided that "All documents will be in 12 point font". It would be good to record such resolutions taken (or maybe there is a better word than 'resolution'). These will likely be around for a while and so the 'year' may be required here :-).
Ravi
participants (3)
-
Andreas Savva -
Hiro Kishimoto -
Subramaniam, Ravi