Start CES-TC

sTASKS:

[ X ] Proj admin - prepare charter template for proposers https://docs.google.com/document/d/1CN6WTVes-9v5ltJvDHUECQ8uzzRd0Rc333bil6DF9Rk/edit?

[ X] Convener - Submit final new TC charter to OASIS
[ 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.  
[ 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/members/202305/msg00003.html
[ 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, and IPR mode 
[ X ] TC Admin - Schedule the convener call. Prepare the slide deck to be used on the call.
[ X ] TC Admin - Create the Kavi workgroup (Add New Group) with initial setup defaults: notes page content, Join, Approval, Denial templates.
[ X ] TC Admin - Create MarkMail aliases
-  Register the 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>`

• 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.
• 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.
  • • • • • • • • • • • • • • • • • • 1. Markmail archiving
  1. 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.
     Requires logon to github.com/oasisorg
  2. Setup archiving for a new list
     1. 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>`
     2. 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] Collect comment resolution log from proposers
• [ / ] TC Admin - Create initial content for TC website: Notes, Description
  [X] TC Admin - Add TC to the project list for Wordpress website
  [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
  [X] IT - Publish charter (part 1 of submitted proposal) and set IPR mode on TC public pages 
  [ X] TC Admin - Update the details in the Kavi Group to reflect first meeting date, last date to join+vote, per agreed details
  [ X] TC Admin - Add convener to Roster
  [X] TC Admin - Modify the Kavi workgroup configuration settings 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 
  [N/A ] 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
  [X] TC Admin - Issue reminder of deadline to join in order to be eligible to vote at the first meetingCopy 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 Admin - 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+actually attended "Members" to "Voting Member"