You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Identify and document other core project infrastructure
If choosing to use a Contributor License Agreement (CLA) or Developer Certificate of Origin (DCO), make selection and implement appropriate tool blocked pending lang from board, See Update/move jsf-clabot for new fdn cross-project-council#124
Add or Update Governance.md document (required for Impact stage)
Confirm required files in place (CODE_OF_CONDUCT.md, LICENSE.md)
@jorydotcom for the following requirement: Confirm required files in place (CODE_OF_CONDUCT.md, LICENSE.md)
Do we need specific language in those files? Or do we just need them in general. Appium already has a code of conduct and a license.
Is the exact filename important? Right now it's CONDUCT.md and LICENSE. I can rename them if we want uniformity.
Great questions, @Jonahss - The Code of Conduct does have to match the OpenJS Foundation Code of Conduct. I'm not sure about the file names matching; we should raise that in the CPC meeting.
jorydotcom
transferred this issue from openjs-foundation/cross-project-council
Nov 5, 2019
Project Onboarding Checklist - Appium
Stage: Impact
blocked pending CPC & Board Approval, see Add process for handling reports cross-project-council#271
blocked pending CPC & Board Approval, see Add process for handling reports cross-project-council#271
blocked pending lang from board, See Update/move jsf-clabot for new fdn cross-project-council#124
blocked pending lang from board, See Update/move jsf-clabot for new fdn cross-project-council#124
blocked pending lang from board, See Define & document a style guide for the foundation's name cross-project-council#280
The text was updated successfully, but these errors were encountered: