OASIS Open Document Format for Office Applications (OpenDocument) TC

OASIS OpenDocument TC The OpenDocument Technical Committee will have its next TC Coordination Call on September 26th 1330 UTC(6:30am PDT, 9:30am EDT, 2:30PM BST 3:30pm CEST, 9:30pm China). The call counts towards voter eligibility. Participant Code: 84367726 Access Numbers -------------------------- USA Toll-Free: 888-426-6840 USA Caller Paid: 215-861-6239 Belgium: 0800-3-9022 Canada: 888-426-6840 China: 10-800-711-1071 (CHINA NETCOM GROUP USERS ) China: 10-800-110-0996 (CHINA TELECOM SOUTH USERS) Finland: 0800-9-18357 Germany: 0800-000-1018 Netherlands: 0-800-363-6036 Norway: 800-16771 UK: 0800-368-0638 Codes for other countries are listed here: https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=84367726&accessNumber=2158616239 Press *6 to mute/unmute line Chat room for meeting is at: http://webconf.soaphub.org/conf/room/odf Agenda ------ 1. Dial-In, Roll Call, Determination of Quorum and Voting Rights 2. Motion (simple majority): Approve the Agenda 3. Motion (simple majority): Approve the Minutes from September 19th meeting 4. ODF maintenance 5. ODF 1.2 6. ODF-Next 7. Adjournment Attachment: smime.p7s Description: S/MIME Cryptographic Signature

Rob, Apologies for the late request but I have two items I would like to add to the agenda: 1) Inline JIRA links in working drafts - To more tightly bind the editorial work to resolution of JIRA issues, I propose to create a JIRA type for note, the content of which will be a hyperlink (text will be a JIRA number) that points to a JIRA issue. Easy enough to strip out for Committee drafts/specifications, while retaining in the working draft. 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. B. Resolution fields will have to be just that, fields that hold the change *made in the working draft.* The resolution cannot appear in some other part of the JIRA issue. C. Create an ODF1.3 (Next?) folder for working drafts. Question: What happens if we decide this is a 2.0 release instead of 1.3? Will that create confusion? Should the name be: ODF-June2013? So that we know all the drafts in the folder were placed there before June 2013? 2) Under Action Items in JIRA, http://www.oasis-open.org/apps/org/workgroup/office/members/action_items.php - Do we have a volunteer to take and clear items assigned to Michael Brauer? 3) Likewise under issues, we have 12 unresolved issues assigned to Michael Brauer (watch for line wrap): http://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?assigneeSelect=specificuser&sorter/field=priority&mode=hide&reset=true&resolution=-1&assignee=michael.brauer&pid=10027&sorter/order=DESC Any takers? 4) Same for Bob Joliffe, haven't seen Bob since Jan. 2011, but he has 11 issues: http://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?assigneeSelect=specificuser&sorter/field=priority&mode=hide&reset=true&resolution=-1&assignee=bobj&pid=10027&sorter/order=DESC Any takers? 5) Don't be bashful, we have 179 *unassigned* issues as well. You can probably find something that interests you. 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. Apologies for the late posting. I will try in the future to get such items to you before the agenda goes out. Hope you are looking forward to a great weekend! Patrick On 09/22/2011 03:16 PM, robert_weir@us.ibm.com wrote: OASIS OpenDocument TC The OpenDocument Technical Committee will have its next TC Coordination Call on September 26th 1330 UTC(6:30am PDT, 9:30am EDT, 2:30PM BST 3:30pm CEST, 9:30pm China). The call counts towards voter eligibility. Participant Code: 84367726 Access Numbers -------------------------- USA Toll-Free: 888-426-6840 USA Caller Paid: 215-861-6239 Belgium: 0800-3-9022 Canada: 888-426-6840 China: 10-800-711-1071 (CHINA NETCOM GROUP USERS ) China: 10-800-110-0996 (CHINA TELECOM SOUTH USERS) Finland: 0800-9-18357 Germany: 0800-000-1018 Netherlands: 0-800-363-6036 Norway: 800-16771 UK: 0800-368-0638 Codes for other countries are listed here: https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=84367726&accessNumber=2158616239 Press *6 to mute/unmute line Chat room for meeting is at: http://webconf.soaphub.org/conf/room/odf Agenda ------ 1. Dial-In, Roll Call, Determination of Quorum and Voting Rights 2. Motion (simple majority): Approve the Agenda 3. Motion (simple majority): Approve the Minutes from September 19th meeting 4. ODF maintenance 5. ODF 1.2 6. ODF-Next 7. Adjournment -- 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

<office@lists.oasis-open.org> wrote on 09/23/2011 01:34:09 PM: > Rob, > > Apologies for the late request but I have two items I would like to add > to the agenda: > Sure. > 1) Inline JIRA links in working drafts - To more tightly bind the > editorial work to resolution of JIRA issues, I propose to create a JIRA > type for note, the content of which will be a hyperlink (text will be a > JIRA number) that points to a JIRA issue. Easy enough to strip out for > Committee drafts/specifications, while retaining in the working draft. > This would allow a reviewer (a TC member, but not for public review if we're stripping it out) to jump from a Note to the underlying JIRA issue. And if a single JIRA issues required several changes in widely scattered parts of the spec? Several notes? Or you take this case-by-case? Might be able to have XSLT or ODF Toolkit code that adds the hyperlinks for you. In other words, search for the pattern OFFICE-NNNN and automatically add hyperlink. Would not even need a note. > 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. > Current practice is for the minutes to just mention the issue numbers of the JIRA issues we've discussed in a given meeting and then to state that "resolutions are recorded in JIRA", or words to that effect. So a link from the minutes to the JIRA issue might be useful. But I don't see what you would get from a link fro JIRA back to the minutes. > B. Resolution fields will have to be just that, fields that hold the > change *made in the working draft.* The resolution cannot appear in some > other part of the JIRA issue. > So who would enter the resolution? Just the editor? And other members use the proposal field? In other words, is the resolution intended to be the proposed resolution, the TC-approved editing resolution or the actual editing change? These often differ in subtle ways, and sometimes in important ways. > C. Create an ODF1.3 (Next?) folder for working drafts. Question: What > happens if we decide this is a 2.0 release instead of 1.3? Will that > create confusion? Should the name be: ODF-June2013? So that we know all > the drafts in the folder were placed there before June 2013? > I'm fine with ODF 1.3. > 2) Under Action Items in JIRA, > http://www.oasis-open.org/apps/org/workgroup/office/members/action_items.php > - Do we have a volunteer to take and clear items assigned to Michael > Brauer? > > 3) Likewise under issues, we have 12 unresolved issues assigned to > Michael Brauer (watch for line wrap): > http://tools.oasis-open.org/issues/secure/IssueNavigator.jspa ? > assigneeSelect=specificuser&sorter/ > field=priority&mode=hide&reset=true&resolution=-1&assignee=michael.brauer&pid=10027&sorter/ > order=DESC > > Any takers? > > 4) Same for Bob Joliffe, haven't seen Bob since Jan. 2011, but he has 11 > issues: > > http://tools.oasis-open.org/issues/secure/IssueNavigator.jspa ? > assigneeSelect=specificuser&sorter/ > field=priority&mode=hide&reset=true&resolution=-1&assignee=bobj&pid=10027&sorter/ > order=DESC > > Any takers? > > 5) Don't be bashful, we have 179 *unassigned* issues as well. You can > probably find something that interests you. > > 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. > > Apologies for the late posting. I will try in the future to get such > items to you before the agenda goes out. > > Hope you are looking forward to a great weekend! > > Patrick > > > On 09/22/2011 03:16 PM, robert_weir@us.ibm.com wrote: > > OASIS OpenDocument TC > > > > The OpenDocument Technical Committee will have its next TC Coordination > > Call on September 26th 1330 UTC(6:30am PDT, 9:30am EDT, 2:30PM BST 3:30pm > > CEST, 9:30pm China). > > > > The call counts towards voter eligibility. > > > > Participant Code: 84367726 > > > > Access Numbers > > -------------------------- > > USA Toll-Free: 888-426-6840 > > USA Caller Paid: 215-861-6239 > > > > Belgium: 0800-3-9022 > > Canada: 888-426-6840 > > China: 10-800-711-1071 (CHINA NETCOM GROUP USERS ) > > China: 10-800-110-0996 (CHINA TELECOM SOUTH USERS) > > Finland: 0800-9-18357 > > Germany: 0800-000-1018 > > Netherlands: 0-800-363-6036 > > Norway: 800-16771 > > UK: 0800-368-0638 > > > > Codes for other countries are listed here: > > > > https://www.teleconference.att.com/servlet/glbAccess ? > process=1&accessCode=84367726&accessNumber=2158616239 > > > > Press *6 to mute/unmute line > > > > Chat room for meeting is at: http://webconf.soaphub.org/conf/room/odf > > > > Agenda > > ------ > > 1. Dial-In, Roll Call, Determination of Quorum and Voting Rights > > > > 2. Motion (simple majority): Approve the Agenda > > > > 3. Motion (simple majority): Approve the Minutes from September 19th > > meeting > > > > 4. ODF maintenance > > > > 5. ODF 1.2 > > > > 6. ODF-Next > > > > 7. Adjournment > > > -- > 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 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: office-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: office-help@lists.oasis-open.org > Attachment: smime.p7s Description: S/MIME Cryptographic Signature

Rob, On 09/23/2011 02:18 PM, robert_weir@us.ibm.com wrote: <office@lists.oasis-open.org> wrote on 09/23/2011 01:34:09 PM: Rob, Apologies for the late request but I have two items I would like to add to the agenda: Sure. 1) Inline JIRA links in working drafts - To more tightly bind the editorial work to resolution of JIRA issues, I propose to create a JIRA type for note, the content of which will be a hyperlink (text will be a JIRA number) that points to a JIRA issue. Easy enough to strip out for Committee drafts/specifications, while retaining in the working draft. This would allow a reviewer (a TC member, but not for public review if we're stripping it out) to jump from a Note to the underlying JIRA issue. Aren't working drafts accessible to the public? And if a single JIRA issues required several changes in widely scattered parts of the spec? Several notes? Or you take this case-by-case? Probably case-by-case because we should not have bulk JIRA issues for the most part. Could happen but should be unusual. Might be able to have XSLT or ODF Toolkit code that adds the hyperlinks for you. In other words, search for the pattern OFFICE-NNNN and automatically add hyperlink. Would not even need a note. Good suggestion! But it would still need to be a "note" or some other ODF markup that the XSLT inserts. Hmmm, probably could create a field that inserts the URL when I insert the OFFICE-NNNN. 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. Current practice is for the minutes to just mention the issue numbers of the JIRA issues we've discussed in a given meeting and then to state that "resolutions are recorded in JIRA", or words to that effect. So a link from the minutes to the JIRA issue might be useful. But I don't see what you would get from a link fro JIRA back to the minutes. Its completes the circle, that is I can start from the minutes and find the issue, but I can also start from the issue and find the minutes. B. Resolution fields will have to be just that, fields that hold the change *made in the working draft.* The resolution cannot appear in some other part of the JIRA issue. So who would enter the resolution? Just the editor? And other members use the proposal field? In other words, is the resolution intended to be the proposed resolution, the TC-approved editing resolution or the actual editing change? These often differ in subtle ways, and sometimes in important ways. Good point and one of the reasons I wanted to bring this to the TC. Clearly we want a "place" for the editing resolution (not scattered at various locations in JIRA) but what should that be? I think the "resolution" field needs to be reserved for: 1) editing resolution, or 2) actual editing change but only one of those two. I don't have a fixed preference, but do want a common practice to the extent we can do that. C. Create an ODF1.3 (Next?) folder for working drafts. Question: What happens if we decide this is a 2.0 release instead of 1.3? Will that create confusion? Should the name be: ODF-June2013? So that we know all the drafts in the folder were placed there before June 2013? I'm fine with ODF 1.3. OK - Let's see what Monday brings and if no other suggestions, I don't know if I can create a folder or if you need to. Hope everyone is looking forward to a great weekend and enjoying the new OASIS site as much as I am! ;-) Patrick 2) Under Action Items in JIRA, http://www.oasis-open.org/apps/org/workgroup/office/members/action_items.php - Do we have a volunteer to take and clear items assigned to Michael Brauer? 3) Likewise under issues, we have 12 unresolved issues assigned to Michael Brauer (watch for line wrap): http://tools.oasis-open.org/issues/secure/IssueNavigator.jspa ? assigneeSelect=specificuser&sorter/ field=priority&mode=hide&reset=true&resolution=-1&assignee=michael.brauer&pid=10027&sorter/ order=DESC Any takers? 4) Same for Bob Joliffe, haven't seen Bob since Jan. 2011, but he has 11 issues: http://tools.oasis-open.org/issues/secure/IssueNavigator.jspa ? assigneeSelect=specificuser&sorter/ field=priority&mode=hide&reset=true&resolution=-1&assignee=bobj&pid=10027&sorter/ order=DESC Any takers? 5) Don't be bashful, we have 179 *unassigned* issues as well. You can probably find something that interests you. 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. Apologies for the late posting. I will try in the future to get such items to you before the agenda goes out. Hope you are looking forward to a great weekend! Patrick On 09/22/2011 03:16 PM, robert_weir@us.ibm.com wrote: OASIS OpenDocument TC The OpenDocument Technical Committee will have its next TC Coordination Call on September 26th 1330 UTC(6:30am PDT, 9:30am EDT, 2:30PM BST 3:30pm CEST, 9:30pm China). The call counts towards voter eligibility. Participant Code: 84367726 Access Numbers -------------------------- USA Toll-Free: 888-426-6840 USA Caller Paid: 215-861-6239 Belgium: 0800-3-9022 Canada: 888-426-6840 China: 10-800-711-1071 (CHINA NETCOM GROUP USERS ) China: 10-800-110-0996 (CHINA TELECOM SOUTH USERS) Finland: 0800-9-18357 Germany: 0800-000-1018 Netherlands: 0-800-363-6036 Norway: 800-16771 UK: 0800-368-0638 Codes for other countries are listed here: https://www.teleconference.att.com/servlet/glbAccess ? process=1&accessCode=84367726&accessNumber=2158616239 Press *6 to mute/unmute line Chat room for meeting is at: http://webconf.soaphub.org/conf/room/odf Agenda ------ 1. Dial-In, Roll Call, Determination of Quorum and Voting Rights 2. Motion (simple majority): Approve the Agenda 3. Motion (simple majority): Approve the Minutes from September 19th meeting 4. ODF maintenance 5. ODF 1.2 6. ODF-Next 7. Adjournment -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: office-unsubscribe@lists.oasis-open.org For additional commands, e-mail: office-help@lists.oasis-open.org -- 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

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. 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 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. 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. - 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. [ ... ]

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

OK, let's keep it simple. Here's the detail page for the latest OIC Minutes in the OIC Meeting Reports folder: < http://www.oasis-open.org/committees/document.php?document_id=43533 > Note that the document link (under Name for some reason), is a hyperlink. The hyperlink is to the list archive copy of the minutes that were posted on the list. It is easier to have the minutes on the list, because URLs to minutes on the list are easy, and they can be used wherever they need to be (e.g., in resolutions of JIRA issues, whatever). I know of no way to make the folder of meeting notes visible to the Public. The view available to the public is a composite of everything. In my browser it shows them in reverse chronological order and the names are not used in the case of links, so it is not very useful. See < http://www.oasis-open.org/committees/documents.php?wg_abbrev=oic >. There does not appear to be any by-folder public access. I also don't see those nice lists of version history on the summary page any longer. - 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 12:39 To: dennis.hamilton@acm.org Cc: office@lists.oasis-open.org 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 --------------------------------------------------------------------- To unsubscribe, e-mail: office-unsubscribe@lists.oasis-open.org For additional commands, e-mail: office-help@lists.oasis-open.org