Onboarding Tracker for Bitol

[lucyhyde]

The following tasks are required to complete onboarding for a Sandbox level project joining the LF AI & Data Foundation. LF Staff will engage with the technical project lead via this issue and work through the checklist to completion.

LF AI & Data Staff: Review each item, confirm completion, and add any relevant notes.

Note: (ED) Executive Director, (Tech) Technical Lead, (PM) Program Management & Operations Lead, (Mktg) Marketing Lead

TECHNICAL PROJECT DETAILS

--Maturity Level Proposed: Sandbox --Company Sponsor (Full Legal Name): AIDA User Group --Project Sponsor Contact:Jean-Georges Perrin --Technical Contact:Jean-Georges Perrin --Legal Contact:Jean-Georges Perrin --TAC Sponsor:Jean-Georges Perrin --TAC/GB Approval Date: September 28, 2023 --Project License: Apache 2.0 --Project Presentation:URL to Presentation --Project Proposal per LF AI & Data: TBD --Project Artwork: Artwork is available here --Note: Project renamed to Bitol : https://github.com/orgs/bitol-io

LICENSING

• [x] (Tech/ED) Project license exists and is OSI-approved
• [x] (Tech/ED) Proposed license inline with umbrella's IP Policy
• [x] (Tech/ED) Pre-intake FOSSology scan complete, shared with project, and no major incompatible licenses detected
• [x] (Tech/ED) Determine known components/dependencies not under compatible license

CONTRIBUTION

• [x] (Tech/ED) Deactivation of CLA/DCO in place and adopt GitHub's DCO at https://github.com/apps/dco
• [x] (Tech/ED) Share/Discuss Project Charter Template and Finalize with Project (update New Projects Onboarding with Legal Status Tracking) Note: The technical charter is tailored for LF AI & Data - Copy is to be created for each project - The technical charter will always need the following information dropped in place: the short name of the project (where [Community Name] appears); a short mission statement following the "The mission of the project is to..." convention; and confirmation of the specific licenses in Section 7 for code and/or data (many projects will not need data and this subjection regarding data licensing in those cases can be removed)
• [x] (Tech/ED) Share/Discuss Account & Trademark Assignment Template and Finalize with Project // not required new name and logo
• [x] (Tech/ED) Verify OpenSSF Best Practices Badge (passing) ticket has been started + add ticket to this issue for reference -Project will be responsible for ensuring completion as per hosted project requirements // in progress https://www.bestpractices.dev/en/projects/8149

PROJECT ASSETS

• [x] (Tech/ED) Logos confirmation // If logos exist post to GitHub Artwork repo and save in Project Logos in LF internal Google Drive folder
• [x] (Tech/ED) Domain name confirmation // If one exists, it must be transferred using https://jira.linuxfoundation.org/servicedesk/customer/kb/view/28485232 // Reference: https://confluence.linuxfoundation.org/display/LID/Domain+Registration+and+Transfers // Bought bitol.io
• [x] (Tech/ED) Project website tracking // Add link and name/email of authorized user for website to LF internal tracking // in progress @NSouthernLF to open a ticket with Creative and track

TAC & GOVERNING BOARD REVIEW

• [x] (Tech/ED) Provide project proposal process/template to project sponsor (https://github.com/LFDLFoundation/proposing-projects/tree/master/proposal-process)
• [x] (Tech/ED) Confirm/Schedule presentation date during TAC meeting - Add to TAC Mtg Agenda Tracking
• [x] (Tech/ED) Review and confirm final proposal and presentation deck
• [x] (Tech/ED) Add project presentation to TAC agenda/deck and send to tac-general mail list with agenda info
• [x] (Tech/ED)Send project presentation and proposal to tac-private mail list with reminder on attendance and quorum requirements for voting members
• [x] (PM) Verify TAC minutes with project TAC vote results

INFRASTRUCTURE

• [x] (Tech/ED) Update proposal to show project accepted in GitHub Project List // this was by-passed
• [x] (Tech/ED) Setup org in Github, add 'thelinuxfoundation' as an owner - Allows us to maintain continuity of GH ownership
• [x] (Tech/ED) Migrate code repository to new GH org
• [x] (Tech/ED) Add project to LF AI & Data Landscape and mark it as an LF AI & Data project

OPERATIONS

• [x] (PM) Add project technical lead contact info (name/email) to internal tracking
• [x] #70
• [x] (PM) Add project to Current Projects section on LF AI & Data wiki. Get the project description from LFX.
• [x] (PM) Set up other misc collaboration tools agreed upon during proposal/acceptance, if any
• [x] (PM) Set up project mail lists (announce, tsc, technical-discuss, security) under LF AI & Data Groups.io
• [x] (PM) Add initial project lead(s) to applicable mail lists (main, announce, events, tac-general, project mail lists, technical-projects)
• [x] (PM) Set project lead as moderator for mail lists as applicable for ongoing management
• [x] (PM) Add LF AI & Data marketing manager to project announce mail list as moderator for sending announcements
• [x] (PM) Send onboarding email with next steps info and resources - Includes Technical Getting Started Checklist
• [x] (PM) Set up project wiki space under LF AI wiki - Upon request only per onboarding email info provided to project
• [x] (PM) Set up project in LFX Insights by adding project repo name to Source Control under Development and then adding connection in LFX Insights under LFX Tools
• [x] (PM) Set up project in LFX Security by ensuring that the security bot is installed in project GitHub repo, once that is confirmed, add connect the repo in LFX Security
• [x] (PM)Share new project update w/Outreach Committee (Chair) to include in upcoming committee meeting
• [x] (PM) Include update on new project in upcoming GB meeting agenda
• [x] (PM) Update "LF AI & Data Overview" deck - slides 38 & 39 and update timeline slide
• [x] (PM) Upload "LF AI & Data Overview Deck" on LF AI & Data GH presentations repo
• [x] (PM) Verify project is added to Project Website Access tracking + verify all information is added per details under "Project Assets" section in this issue
• [x] (PM) Transfer social account domain ownership to LF AI & Data shared account use set up, if applicable - Projects retain ongoing management of accounts - Reference internal process documentation

MARKETING

• [x] (PM) Update LF AI & Data Timeline with new project - Creative Services Asana ticket required (Reference) - Save updated file in internal LF AI & Data G Drive and on LF AI & Data GH
• [x] (PM) Build landing page on LF AI & Data website and add to All Projects section - Creative Services Asana ticket required (Reference)
• [x] (Mktg) Coordinate announcement (press release or blog post) and social promotion with project company - Add to internal LF AI & Data PR/Comms tracker - Sandbox projects are announced via social followed by blog announcement on a quarterly basis
• [x] (Mktg) Follow project and member company on Twitter/LinkedIn from LF AI & Data accounts, if applicable
• [x] (Mktg) Publish announcement (Blog/PR+Social+Mail Lists)

LEGAL FOLLOW UP

• [x] (PM) Confirm ongoing license scanning is set up through legal - Add to internal LF AI & Data tracker
• [x] (PM) Confirm Export Control Notice (ECN) filings are completed through legal via ticket at https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2 (trademark/contribution agreement + website needed for filing request via Legal Jira ticket ) + Add to internal LF AI & Data tracker for future scans planned through Software Freedom Law Center for Graduate level projects
• [x] (PM) Include all projects in Trademark Registrations review cycles - Graduate level projects addressed at start of each calendar year - Add to internal LF AI & Data tracker

[NSouthernLF]

Per conversation with Jean-Georges just now - no additional collaborative tools needed. They are set on this.

[NSouthernLF]

For insights and security - submitted an email to project formation just now to move the request forward; will also be discussing with Scott Nicholas on Mon. 11/6

[NSouthernLF]

Regarding the transfer of social media accounts, Bitol has none.

[NSouthernLF]

Bitol does not use software subject to export control restrictions.

[NSouthernLF]

Website has been finalized - https://bitol.dev-lfprojects5.linuxfoundation.org/ Craig Ross is coordinating with IT on the cutover to push it out to bitol.io