Component/s: Start TC
[ ] Convener - Submit final new TC proposal to OASIS
[ ] TC Admin - Open a TCATKTS JIRA ticket to manage the execution of remaining tasks.
JIRA ticket: https://issues.oasis-open.org/browse/TCADMIN-4206https://issues.oasis-open.org/browse/TCADMIN-4206
[ ] TC Admin - Capture initial best-guess TC data
TC ShortName: idpf
TC Name: OASIS Infrastructure Data-Plane Function (IDPF) TC
Note who submitted: Michael Orr
The projected timeline for basic milestones is:
set up TC assets (Kavi, etc.):
c4p (latest possible date)
first mtg, conference call (earliest possible date)
[ ] TC Admin / Biz dev - Conduct final review of the submitted new TC proposal technical compliance with TC Process requirements, typos, etc.
[ ] TC Admin - Distribute Call for Comment (announcement) to OASIS lists
[ ] IS - Send email to Myles Support for first communication on new TC startup (firstname.lastname@example.org )
Include link to call for comment, agreed-upon tc shortname and target dates for convener call, call for participation, first meeting.
[ ] TC Admin - Schedule the convener call
[ ] IS - Create the Kavi workgroup (Add New Group) with initial setup defaults
[ ] IS - Add OASIS Staff representatives to Roster. Add the pseudo user "Web Master" as an OASIS Staff rep to create link between JIRA and TC mailing list so TC Admin requests get to the TC.
[ ] IS - Create new TC startup files, e.g., .php/.shtml upon notification/request; notify Myles. *Prerequisites: immutable tc-shortName and tc-fullName, TC IPR Mode
[ ] IT/IS - Create MarkMail aliases via update of ezmlm-forcesub.pl and alert Matt Olson (KaviCorp) via email or file or Git repo notification, for deployment in the Kavi backend, upon notification/request (Bitlancer) *Prerequisite: immutable tc-shortName
[ ] IS - Create initial content for TC website: Notes, Description
[ ] IS - Manage / assign TC categories for the new TC and add to new website list
[ ] TC Admin - Hold convener call
[ ] Convener - If any changes identified, submit final TC proposal to OASIS
[ ] IS Convey the Charter text (charter proper, Section 1) to Bitlancer for preparation of the file "charter.php"
[ ] TC Admin - If charter is updated, circulate the final TC proposal for sanity check review
[ ] IS - Update Myles with final plain text of the proposal (for entry into Kavi), final First Meeting date and "latest date to join with voting rights."
[ ] IT - Publish charter (part 1 of submitted proposal) on TC public page
[ ] IS - Update the details in the Kavi Group to reflect first meeting date, last date to join+vote, per agreed details
[ ] IS - Modify the Kavi workgroup configuration to make the TC public home page visible to membership and the public. Notify Chet [TC Admin] that all CFP prerequisites have been met
[ ] TC Admin - Issue Call for Participation
[ ] IS - Notify Bitlancer with request to update the Charter with link to CFP announcement
[ ] IS - Check MarkMail archives to ensure that archiving/indexing is working, per Kavi work order
[ ] IT - Update Kavi Charter page to include CFP link (Robin to notify Bitlancer with URI reference)
[ ] Convener and TC Administration - Schedule TC first meeting on calendar
[ ] TC Admin - Issue call for nominations for Chair
[ ] TC Admin - Issue reminder of deadline to join in order to be eligible to vote at the first meeting
[ ] TC Admin - Publish list of members eligible to vote at first meeting to TC mailing list and co-proposers
[ ] Convener and TC Administration - Convene first meeting
[ ] IS - Create and test the comment list function (+ OASIS/MarkMail archives) on the day of first meeting or ASAP thereafter, and notify the TC members
[ ] IS - Change the TC page content in "Announcements" section after first meeting
[ ] TC Admin - Perform obligation counter update on day of first meeting - or just check/confirm correctness if this is automated
[ ] TC Admin - Set role(s) for [Co-]Chair after election
[ ] Chair - Set signed-up+actuallyAttended "Members" to "Voting Member"