Project Intake checklist

This is a checklist for TSC's to review as part of the intake process. The TSC should review this entire list during the kickoff meeting. For anything outstanding, create an issue to track and link to it in the list

• TSC Record Keeping
  • Location for TSC documents and meeting notes ( recommendation is tsc directory in main repo, and then meetings under the tsc directory )
  • Copy this checklist to the above location for tracking
• Existing Project Governance
  • README.md file exists ( example at example_readme.md )
  • Project License exists ( LICENSE.md ) and is OSI-approved
  • Any third-party components/dependencies included are listed along with thier licenses ( THIRD_PARTY.md )
  • Governamce defined, outlining community roles and how decsions are made ( GOVERNANCE.md - leverage example_governance.md as a starting point if needed )
  • Contribution Policy defined ( CONTRIBUTING.md )
  • Code of Conduct defined ( existing or leverage code of conduct )
  • Release methodology defined ( RELEASE.md )
• New Project Goverance
  • TSC members identified
  • First TSC meeting held
  • TSC meeting cadence set and added to project calendar
• Current tools
  • Source Control (Github, GitLab, something else )
    • Issue/feature tracker (JIRA, GitHub issues)
  • Collaboration tools
    • Mailing lists
      • Move to groups.io ( create [issue on foundation repo] to setup/transfer
    • Slack or IRC ( create [issue on foundation repo] to setup project channel on OMP Slack
    • Forums
  • Website
  • CI/build environment
• Project assets
  • Domain name ( create [issue on foundation repo] to setup/transfer
    • Social media accounts ( create [issue on foundation repo] to setup/transfer
    • Logo(s) ( create pull request against artwork repo to add in SVG and PNG format and color/black/white )
    • Trademarks/mark ownership rights ( complete LF Projects - Form of Trademark and Account Assignment )
• Outreach
  • New project annoucement done ( create [issue on foundation repo] to trigger )
  • Project added to Open Mainframe Project website and Open Mainframe Project landscape
• Graduation
  • CII Badge achieved
  • Committer Diversity established
    • Commit/Contribution growth during incubation
    • Committers defined in the project ( COMMITTERS.csv or COMMITTERS.yml )
  • TAC representative appointed
  • License scan completed and no issues found
  • Code repository imported to Open Mainframe Project GitHub organization
    • Developer Certificate of Origin past commit signoff done and DCO Probot enabled.

PR #15 added some guideline for contribution to the project. However, DCO signoff was not mentioned and it seems that many commits had been manually signed-off.

I would propose that we add DCO signoff as a requirement for future contribution to ensure that those who are submitting work only do so when they have the rights to do so.

This would be as simple as adding the --signoff option to git commit. Furthermore, I would propose the adoption of CONTRIBUTING.md to ensure that all the styles and requirements for contributions are followed.

I will be happy to submit a PR to add these materials :)

Attendees

• Deborah Carbo
• Guilherme Cartier
• Viviane Padua
• Lauren Valenti
• Yvette Lamar

Agenda

• General status check
• Discuss go to market strategy

Action items

Notes

• Where https://zoom.us/j/91850205494
• When 10/08/2020 3PM EST to 4PM EST

Attendance

• Bob Dahlberg
• Deborah Carbo
• Guilherme Cartier
• Lauren Valenti
• Nick Said
• Viviane Padua
• Yvette Lamar

Agenda

• Preparation for the European Open mini-Summit
• Status check of pending points

Mainframe Open Education TSC Meeting 09/10/2020

• Where: https://zoom.us/j/91850205494
• When: 3:00pm to 4:00pm EST time

Attendance

• Deborah Carbo
• Guilherme Cartier
• Viviane Padua
• Lauren Valenti
• Yvette Lamar

Agenda

• Officialization of new TSC members
• Status check of pending points

Hello -
"Open Mainframe Project Education" link from below is returning '404 Error'.