OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [office] OpenDocument TC Coordination Call Agenda September 26th


Dennis,

On 09/23/2011 03:09 PM, Dennis E. Hamilton wrote:
A. Having Minutes as Documents

Meeting minutes in the archive have URLs and can be linked in the resolution of JIRA issues.

My practice as Secretary on the OIC TC and the TAG TC is to put minutes on the list and then create a document in the document repository that links to the minutes on the list.  That is how I capture the approval status.   Also, if there is a revision of the minutes, it goes to the list and that is captured as a revision in the document repository.

When I post minutes to the document repository I do not send an announcement to the group, simply to keep down the list chatter.

Linking to the minutes on the list is much more convenient for following links from JIRA.  If a link to the minutes entry is used in the document repository, it is necessary to remember to use a public identifier and these are now a little harder to obtain.  (To see the details, it is necessary to click the Actions pulldown at the right of the entry in the document index.)  There is apparently no way to give a member of the general public access to the folder of minutes, in contrast to the office list archive.

Sorry, even with the example you lost me.

Linking to the minutes on the list is much more convenient for following links from JIRA.

I have read that two or three times and have no idea what you mean. Sorry.

Do you mean it is easier to link to minutes if they are in email? But that doesn't have anything to do with JIRA.

Does that help show my confusion?

For example, here is the last-posted OIC TC minutes,<  http://www.oasis-open.org/committees/document.php?document_id=43533>.  It is also incorrect.  The member view is correct.  The document has been marked as approved and the description has been updated accordingly.  The public view is lagging for some reason.  It is also peculiar that the Document Details title line includes the URL, not the Title or Name. (sigh).

I don't have anything useful to say about this difficulty.

I don't know any way to point anyone from the general public to the folder of meeting minutes, so researching previous minutes is a pain.  I suppose the list of a block of minutes could be posted to the list from time to time, with a link to the previous-block listing.

??? Minute folders are no longer public?

Of course minutes can refer to documents that are submitted and approved, when the text being approved needs to be in a formatted document.  Likewise with JIRA issues.

AGENDAS

The calendar entry for a meeting provides a place for an agenda.  It provides a place for minutes too, though I don't know that that anyone uses that.

Even for a block-reservation of meeting dates, one way to send an agenda is to go to the calendar entry, enter the agenda, and allow the calendar-entry modification to be reported to the list.

Changes to the agenda can be accounted for in the minutes.  I suppose one could link calendar entries for meetings to the minutes for the meeting, although that is more manual work to coordinate.

Hmmmm.

Hope you are looking forward to a great weekend!

Patrick


  - Dennis


-----Original Message-----
From: office@lists.oasis-open.org [mailto:office@lists.oasis-open.org] On Behalf Of Patrick Durusau
Sent: Friday, September 23, 2011 10:34
To: office@lists.oasis-open.org
Subject: Re: [office] OpenDocument TC Coordination Call Agenda September 26th

[ ... ]

The reason for bringing this to the TC's attention is that to be useful
it will require:

A. Committee minutes being posted as documents and not in the email
archives. JIRA resolutions will have a pointer to the committee minutes
where the issue was resolved.

[ ... ]

6) BTW, we probably need a folder for agenda's as well. They are likely
to grow more specific as we get into the technical work.

[ ... ]



--
Patrick Durusau
patrick@durusau.net
Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]