-
Type: Task
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Component/s: Start TC
-
Labels:None
-
Environment:
VEL
-
Proposal:Hide
TC startup tasks:
[ X ] Convener - Submit final new TC proposal to OASIS
Michael Schulze submitted the charter Sunday 16 September 2018. Text of the submitted charter is in the following comment.
[ X ] TC Admin - Open a TCATKTS JIRA ticket to manage the execution of remaining tasks. Include the proposed schedule to TC launch.
[ X ] TC Admin & Biz dev - Conduct final review of the new TC proposal for technical compliance with TC Process requirements, typos, etc.
[ X ] TC Admin - If the charter submission fails for any reason (for example, the minimum membership requirement isn't met), return the submission to the proposers with a list of the corrections needed.
No corrections needed. The charter is ready to go.
[ X ] TC Admin - Distribute Call for Comment to OASIS lists, Biz dev, and any contacts provided by the proposers.
https://lists.oasis-open.org/archives/oasis-charter-discuss/201809/msg00000.html
Also sent .docx and .pdf to Dee and Carol
[ X ] TC Admin - Send email to Bitlancer Support for first communication on new TC startup (support@bitlancer.com ) with a link to the call for comments, the proposed schedule, long name, abbreviation, IPR mode
[ X ] TC Admin - Schedule the convener call
scheduled for October 9th - https://lists.oasis-open.org/archives/oasis-charter-discuss/201809/msg00001.html
[ X ] TC Admin - Create the Kavi workgroup (Add New Group) with initial setup defaults: notes page content, Join, Approval, Denial templates.
https://www.oasis-open.org/apps/org/workgroup/vel/
[ X ] IT - Notify Bitlancer to set up files needed to enable public access to the TC webpage
[ X ] TC Admin - Create MarkMail aliases
- Register the new lists with Markmail. Visit the following URL where the `<listname>` has been set appropriately and record the address in the response. DONE`http://markmail.org/manage/list/add?auth=3015816119515239844&list=org.oasis-open.lists.vel` = marva.velasquez.herrera@a.markmail.org
http://markmail.org/manage/list/add?auth=3015816119515239844&list=org.oasis-open.lists.vel-chair = marguerite.cochran.wilkins@a.markmail.org
http://markmail.org/manage/list/add?auth=3015816119515239844&list=org.oasis-open.lists.vel-comment = ricardo.dejesus.rios@a.markmail.org
- Update the `ezmlm-forcesub.pl` file stored at https://github.com/oasisorg/kavi-hosted/blob/master/bin/custom/ezmlm-forcesub.pl. Add a new entry to the `forceSubscribers` hash using the other entries as an example. Note that if you're configuring archiving for a new TC comment list, you should also add the `tc-comment-catchall@oasis-open.org` address. DONE
- Notify Kavi of the change. Email helpdesk@kavi.com asking them to update the file on their end and attach the updated file to the email. DONE - however, the email was bounced by Kavi. Forwarded the bounce message to Scott and Jesse and asked for help. Per Scott, the address is now WorkspaceSupport@higherlogic.com
---------------------
- Markmail archiving
-
- Summary
Markmail is an external service that handles mail archiving. Oasis uses this service for archiving technical committee emails.
Archiving is setup by registering a new list with Markmail and adding the provided email address to the distribution list.-
- Setup archiving for a new list
-
-
- Register a new list with Markmail
-
Visit the following URL where the `<listname>` has been set appropriately and record the address in the response.
`http://markmail.org/manage/list/add?auth=3015816119515239844&list=org.oasis-open.lists.<listname>`
-
-
- Subscribe the Markmail archive address to the distribution list
-
- Update the `ezmlm-forcesub.pl` file stored here, https://github.com/oasisorg/kavi-hosted/blob/master/bin/custom/ezmlm-forcesub.pl,
and add a new entry to the `forceSubscribers` hash using the other entries as an example. Note that if you're configuring archiving for a new TC comment list, you should also add the `tc-comment-catchall@oasis-open.org` address.
- Notify Kavi of the change. Email helpdesk@kavi.com asking them to update the file on their end and attach the updated file
to the email.
--------------------
[ X ] TC Admin - Create initial content for TC website: Notes, Description
[ X ] TC - Manage / assign TC categories for the new TC
- Added to Supply Chain and Lifecycle Integration
[ X ] TC Admin - Hold convener call
[ X ] Convener - If any changes identified, submit final TC proposal to OASIS
[ X ] TC Admin - If charter is updated, circulate the final TC proposal to Biz dev for sanity check review
No need. No changes to text beyond new co-proposers needed.
[ X ] TC Admin - Update bitlancer with final plain text of the proposal (for entry into Kavi), final First Meeting date and "latest date to join with voting rights."
[ X ] IT - Publish charter (part 1 of submitted proposal) on TC public page (bitlancer)
[ X ] IS - Update the details in the Kavi Group to reflect first meeting date, last date to join+vote, per agreed details
[ X ] TC Admin - Modify the Kavi workgroup configuration to make the TC public home page visible to membership and the public.
[ X ] TC Admin - Issue Call for Participation
[ X ] TC Admin - Notify Bitlancer with request to update the Charter with link to CFP announcement
[X] TC Admin - Check MarkMail archives to ensure that archiving/indexing is working, per Kavi work order
[X] Convener and TC Administration - Schedule TC first meeting on calendar
[X] TC Admin - Issue call for nominations for Chair
https://lists.oasis-open.org/archives/vel/201810/msg00002.html
[X] TC Admin - Issue reminder of deadline to join in order to be eligible to vote at the first meeting
Copy to all co-proposers, OASIS members[X] TC Admin - Publish list of members eligible to vote at first meeting to TC mailing list and co-proposers
[X] Convener and TC Administration - Convene first meeting
[X ] TC Admin - reset the TC obligation counter
[X ] TC Admin - Create and test the comment list on the day of first meeting or ASAP thereafter(+ OASIS/MarkMail archives) and notify TC members
[X ] TC - Change the TC page content in "Announcements" section after first meeting
[X ] TC Admin - Set role(s) for [Co-]Chair after election
[X ] Chair - Set signed-up+actuallyAttended "Members" to "Voting Member"
[X] TC Admin - send welcome and list of useful links to the TC
ShowTC startup tasks: [ X ] Convener - Submit final new TC proposal to OASIS Michael Schulze submitted the charter Sunday 16 September 2018. Text of the submitted charter is in the following comment. [ X ] TC Admin - Open a TCATKTS JIRA ticket to manage the execution of remaining tasks. Include the proposed schedule to TC launch. [ X ] TC Admin & Biz dev - Conduct final review of the new TC proposal for technical compliance with TC Process requirements, typos, etc. [ X ] TC Admin - If the charter submission fails for any reason (for example, the minimum membership requirement isn't met), return the submission to the proposers with a list of the corrections needed. No corrections needed. The charter is ready to go. [ X ] TC Admin - Distribute Call for Comment to OASIS lists, Biz dev, and any contacts provided by the proposers. https://lists.oasis-open.org/archives/oasis-charter-discuss/201809/msg00000.html Also sent .docx and .pdf to Dee and Carol [ X ] TC Admin - Send email to Bitlancer Support for first communication on new TC startup (support@bitlancer.com ) with a link to the call for comments, the proposed schedule, long name, abbreviation, IPR mode [ X ] TC Admin - Schedule the convener call scheduled for October 9th - https://lists.oasis-open.org/archives/oasis-charter-discuss/201809/msg00001.html [ X ] TC Admin - Create the Kavi workgroup (Add New Group) with initial setup defaults: notes page content, Join, Approval, Denial templates. https://www.oasis-open.org/apps/org/workgroup/vel/ [ X ] IT - Notify Bitlancer to set up files needed to enable public access to the TC webpage [ X ] TC Admin - Create MarkMail aliases - Register the new lists with Markmail. Visit the following URL where the `<listname>` has been set appropriately and record the address in the response. DONE ` http://markmail.org/manage/list/add?auth=3015816119515239844&list=org.oasis-open.lists .vel` = marva.velasquez.herrera@a.markmail.org http://markmail.org/manage/list/add?auth=3015816119515239844&list=org.oasis-open.lists.vel-chair = marguerite.cochran.wilkins@a.markmail.org http://markmail.org/manage/list/add?auth=3015816119515239844&list=org.oasis-open.lists.vel-comment = ricardo.dejesus.rios@a.markmail.org - Update the `ezmlm-forcesub.pl` file stored at https://github.com/oasisorg/kavi-hosted/blob/master/bin/custom/ezmlm-forcesub.pl . Add a new entry to the `forceSubscribers` hash using the other entries as an example. Note that if you're configuring archiving for a new TC comment list, you should also add the `tc-comment-catchall@oasis-open.org` address. DONE - Notify Kavi of the change. Email helpdesk@kavi.com asking them to update the file on their end and attach the updated file to the email. DONE - however, the email was bounced by Kavi. Forwarded the bounce message to Scott and Jesse and asked for help. Per Scott, the address is now WorkspaceSupport@higherlogic.com --------------------- Markmail archiving Summary Markmail is an external service that handles mail archiving. Oasis uses this service for archiving technical committee emails. Archiving is setup by registering a new list with Markmail and adding the provided email address to the distribution list. Setup archiving for a new list Register a new list with Markmail Visit the following URL where the `<listname>` has been set appropriately and record the address in the response. ` http://markmail.org/manage/list/add?auth=3015816119515239844&list=org.oasis-open.lists .<listname>` Subscribe the Markmail archive address to the distribution list Update the `ezmlm-forcesub.pl` file stored here, https://github.com/oasisorg/kavi-hosted/blob/master/bin/custom/ezmlm-forcesub.pl , and add a new entry to the `forceSubscribers` hash using the other entries as an example. Note that if you're configuring archiving for a new TC comment list, you should also add the `tc-comment-catchall@oasis-open.org` address. Notify Kavi of the change. Email helpdesk@kavi.com asking them to update the file on their end and attach the updated file to the email. -------------------- [ X ] TC Admin - Create initial content for TC website: Notes, Description [ X ] TC - Manage / assign TC categories for the new TC Added to Supply Chain and Lifecycle Integration [ X ] TC Admin - Hold convener call [ X ] Convener - If any changes identified, submit final TC proposal to OASIS [ X ] TC Admin - If charter is updated, circulate the final TC proposal to Biz dev for sanity check review No need. No changes to text beyond new co-proposers needed. [ X ] TC Admin - Update bitlancer with final plain text of the proposal (for entry into Kavi), final First Meeting date and "latest date to join with voting rights." [ X ] IT - Publish charter (part 1 of submitted proposal) on TC public page (bitlancer) [ X ] IS - Update the details in the Kavi Group to reflect first meeting date, last date to join+vote, per agreed details [ X ] TC Admin - Modify the Kavi workgroup configuration to make the TC public home page visible to membership and the public. [ X ] TC Admin - Issue Call for Participation [ X ] TC Admin - Notify Bitlancer with request to update the Charter with link to CFP announcement [X] TC Admin - Check MarkMail archives to ensure that archiving/indexing is working, per Kavi work order [X] Convener and TC Administration - Schedule TC first meeting on calendar [X] TC Admin - Issue call for nominations for Chair https://lists.oasis-open.org/archives/vel/201810/msg00002.html [X] TC Admin - Issue reminder of deadline to join in order to be eligible to vote at the first meeting Copy to all co-proposers, OASIS members [X] TC Admin - Publish list of members eligible to vote at first meeting to TC mailing list and co-proposers [X] Convener and TC Administration - Convene first meeting [X ] TC Admin - reset the TC obligation counter [X ] TC Admin - Create and test the comment list on the day of first meeting or ASAP thereafter(+ OASIS/MarkMail archives) and notify TC members [X ] TC - Change the TC page content in "Announcements" section after first meeting [X ] TC Admin - Set role(s) for [Co-] Chair after election [X ] Chair - Set signed-up+actuallyAttended "Members" to "Voting Member" [X] TC Admin - send welcome and list of useful links to the TC
Michael Schulze of Pure Systems is preparing to submit a new TC charter to OASIS. This ticket is to track the steps in launching the TC.