Onboarding Tracker for CLAIMED

[ibrahimhaddad]

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): IBM --Project Sponsor Contact: Romeo Kienzler --Technical Contact: Romeo Kienzler --Legal Contact: --TAC Sponsor: Ibrahim Haddad --TAC/GB Approval Date: 11/17/2022 --Project in SFDC: --Project License: Apache 2.0 --Project Presentation: URL to presentation --Project Proposal per LF AI & Data: URL to proposal --Project Artwork: logos available from https://github.com/lfai/artwork/tree/main/projects/claimed

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)
• [x] (Tech/ED) Share/Discuss Account & Trademark Assignment Template and Finalize with Project (update New Projects Onboarding with Legal Status Tracking)
• [x] (Tech/ED) Verify OpenSSF Best Practices Badge: https://bestpractices.coreinfrastructure.org/en/projects/6718

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 // We bought claimed-framework.org
• [x] (Tech/ED) Project website tracking // Add link and name/email of authorized user for website to LF internal tracking

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
• [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] (PM) Post final technical charter to GH Project Charters repo and ensure it is saved in LF internal Projects Google Drive folder - pending
• [x] (PM) Add project to Current Projects section on LF AI & Data wiki
• [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) Request project to be added to LFX Insights via Jira Service Desk for request
• [x] (PM) Request project to be added to LFX Security via Ibrahim Haddad (Admin on GH repo for project) OR via Jira Service Desk for request (will need to first confirm LF ID for project lead for access to be granted for bot installation on GitHub repo)
• [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 Getting Involved Guide" deck
• [x] (PM) Update "LF AI & Data Overview" deck
• [x] (PM) Upload "LF AI Getting Involved Guide" and "LF AI 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

MARKETING

• [x] (PM) Update LF AI & Data Timeline with new project - https://app.asana.com/0/1201265796032457/1203511775324675 - 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 Jira ticket required (Reference) --https://app.asana.com/0/1201187889631310/1203558875791580
• [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)
• [x] (Mktg) 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 --none identified in proposal

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 filings are done through legal via ticket at https://www.linuxfoundation.org/export/ (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

[romeokienzler]

TASKS for IBM/CLAIMED team

1) Please fill out the Project Intake Form to provide basic needed info for our project formation team

DONE

2) Please submit a GH PR proposal similar to other projects in this repo.

DONE

3) Review and be ready to sign the project contribution agreement

DONE, we are ready

4) Review and provide feedback on the standard Project Charter - template attached

Please send in any questions along with information about the company, address, and signatory name/title/email. On the above items, please connect with @Scott Nicholas who is our VP of Project Formation and Senior Counsel.

DONE, looks good to us

5) a. Create a new GH Org for the project such as https://github.com/claimed-ai b. Transfer the CLAIMED repo from the IBM GH org to the new org c. Add @IbrahimHaddad and @thelinuxfoundation as owners of the new GH org

DONE https://github.com/claimed-framework @IbrahimHaddad accepted the invitation @thelinuxfoundation not

6) Please activate the GitHub DCO app on all repos.- https://github.com/apps/dco

DONE

7) Domain -- do you have a domain name for the project? If yes, we need to transfer it to the LF. Please share the domain names and I will issue a ticket for the transfer. Otherwise, please let me know what domain name should we reserve for the project. We will use that domain to host a website for the project or to simply lock the domain and we can do a FW to the GH org

I'd go for claimed-framework.org, what you think?

8) Does the project have a logo? If yes, please send us a high-resolution version project's logo. Otherwise, we will introduce you to our Creative team that will help design a logo for the project.

Yes, here is the logo https://raw.githubusercontent.com/claimed-framework/component-library/master/images/claimed_logo.png

9) Let me know what sub-category on https://l.lfai.foundation/ the project fits under best. I will then add the project to the landscape as a Sandbox project.

DONE

10) Does the project have any social media accounts? LI? TW? FB? etc. If yes, please coordinate with @Erin Thacker on facilitating access to these accounts.

Space with attached rooms on Matrix.org => claimed:matrix.org No other social media accounts yet

Thanks so much!

[romeokienzler]

@ibrahimhaddad also for this list we are happy to announce that we're already covering everything but 15 and 16

[romeokienzler]

• [ ] Use the REPOLINTER tool created by the TODO Group to identify common issues in GitHub repos.

• [x] Secure your GitHub account with two-factor authentication.

• [x] Ensure that every repo includes a LICENSE file.

• [ ] Add a README file to your repos welcoming new community members to the project and explaining why the project is useful and how to get started.

• [x] Add a CONTRIBUTING file to your repos explaining to other developers and your community of users how to contribute to the project. At a high level, the file would explain what types of contributions are needed and how the process works.

• [x] Add CODEOWNERS file to define individuals or teams that are responsible for code in a repository.

• [x] Add a CODE_OF_CONDUCT file that sets the ground rules for participants’ behavior associated and helps to facilitate a friendly, welcoming environment. While not every project has a CODE_OF_CONDUCT file, its presence signals that this is a welcoming project to contribute to, and defines standards for how to engage with the project’s community. You are welcome to use the Linux Foundation’s Code of Conduct if project specific CoC does not exist.

• [x] Provide documentation on the release methodology, cadence, criteria, etc.

• [ ] Document your project governance and make it available on the project’s repo.

• [x] Add a SUPPORT file to let users and developers know about ways to get help with your project. You can either add in this file how and where security issues are handled, or put it at the top level readme for the project, or alternatively refer to security documentation.

• [x] Archive inactive repos to flag to your users and other developers that you’re not maintaining them.

• [x] Setup issue template and pull request templates that help you customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository.

• [x] Achieve and maintain the OpenSSF Best Practices Badge (previousely called the Core Infrastructure Initiative Best Practices Badge) for your project.

• [x] Identify who on the project will be handling security issues (could be a team) and set up a separate email account. Consider having the project become a CNA (CVE Numbering Authority).

• [ ] Include an SPDX short-form identifier in a comment at the top of each file in the repo, wherever reasonably possible.

• [ ] Depending on whether your project uses the DCO and/or CLAs:

  DCO: Include a copy of or reference to the Developer Certificate of Origin (DCO) in your CONTRIBUTING file. Set up a bot to enforce a “Signed-off-by:” tag in each commit (https://github.com/apps/dco) CLAs: Use the Linux Foundation’s EasyCLA tool (https://lfcla.com/) to enforce signed CLAs before contributions are accepted. In either case: Configure the Github repo settings so that administrators are not able to bypass the DCO or CLA checks.

• [x] Use English as the default universal language for anything you publish on GitHub. You can support a second language but English should be the primary language of communication towards a universal audience.

[romeokienzler]

@ibrahimhaddad there are four issues open still in the description of this task, three of them seem to require JIRA, I've signed in to JIRA but the only project I'm seeing there is IT: Release Engineering

[ErinThacker]

@romeokienzler - let me take a look at this for you. To be clear, are you referring to the checklist in the issue itself or the checklist you provided on Dec. 9th in the comments above?

[romeokienzler]

@ErinThacker thanks a lot, I'm referring to the issue's checklist, the one provided by myself I can handle

[ErinThacker]

@romeokienzler - it appears that the only remaining item is LFX Security, which takes installing a security bot on GitHub to finish out. You can see the instructions below:

Log in to LFX, navigate to this link and enter your GitHub repository name: [( (https://projectadmin.lfx.linuxfoundation.org/project/a092M00001NVodlQAD/tools/security/overview ))]

These instructions should then pop up: How to install the Security Bot on GitHub App

  1. Click on "Install Security Bot" below. You will be directed to your organization's GitHub page. 

  2. Ensure you are logged into GitHub. 

  3. Click the "Configure" button, located on the top-right corner of your organization's GitHub page. 

  4. Select the Organization that you have added in Project Control Center. 

  5. You can select all repositories or some repositories from the GitHub Organization. 

  After completing all these steps you have successfully authorized Security to view your GitHub Organization. 

Let me know if you have any questions!

[romeokienzler]

Dear @ErinThacker sorry, completely missed this, will work (and finish) this by end of next week!

[NSouthernLF]

No response from project on website, head user or assets after over a year. Closing out that item.

[NSouthernLF]

@romeokienzler is there a website on this project?

[romeokienzler]

@NSouthernLF

Yes, claimed-framework.github.io/

[NSouthernLF]

thanks

On Tue, Dec 5, 2023 at 12:09 AM Romeo Kienzler @.***> wrote:

@NSouthernLF https://github.com/NSouthernLF

Yes, claimed-framework.github.io/

— Reply to this email directly, view it on GitHub https://github.com/lfai/foundation/issues/48#issuecomment-1840073500, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYDSBZ72OERDUZL6PYO4ZCLYH23CZAVCNFSM6AAAAAASERVXPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBQGA3TGNJQGA . You are receiving this because you were mentioned.Message ID: @.***>