From ffc707cc627dc6bcc46b5ea571d9768c904ca1fc Mon Sep 17 00:00:00 2001 From: watare Date: Mon, 22 Nov 2021 15:48:16 +0100 Subject: [PATCH] Delete THIRD_PARTY.md (#2) * Delete THIRD_PARTY.md * Delete COMMITTERS.csv * Delete CHANGELOG.md * Delete SUPPORT.md * Delete SECURITY.md * Update README.md * Delete CONTRIBUTING.md * Delete GOVERNANCE.md * Delete README.md * Delete INSTRUCTIONS.md * Delete tsc directory * Delete tests directory --- CHANGELOG.md | 14 --------- COMMITTERS.csv | 1 - CONTRIBUTING.md | 34 -------------------- GOVERNANCE.md | 70 ------------------------------------------ INSTRUCTIONS.md | 15 --------- README.md | 38 ----------------------- SECURITY.md | 21 ------------- SUPPORT.md | 27 ---------------- THIRD_PARTY.md | 1 - tests/README.md | 1 - tsc/CHARTER.md | 69 ----------------------------------------- tsc/README.md | 68 ---------------------------------------- tsc/meetings/README.md | 3 -- 13 files changed, 362 deletions(-) delete mode 100644 CHANGELOG.md delete mode 100644 COMMITTERS.csv delete mode 100644 CONTRIBUTING.md delete mode 100644 GOVERNANCE.md delete mode 100644 INSTRUCTIONS.md delete mode 100644 README.md delete mode 100644 SECURITY.md delete mode 100644 SUPPORT.md delete mode 100644 THIRD_PARTY.md delete mode 100644 tests/README.md delete mode 100644 tsc/CHARTER.md delete mode 100644 tsc/README.md delete mode 100644 tsc/meetings/README.md diff --git a/CHANGELOG.md b/CHANGELOG.md deleted file mode 100644 index fd2a62f..0000000 --- a/CHANGELOG.md +++ /dev/null @@ -1,14 +0,0 @@ -# Changelog - -All notable changes to this project will be documented in this file. - -The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), -and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). - -## [Unreleased] - -### Added - -### Changed - -### Removed diff --git a/COMMITTERS.csv b/COMMITTERS.csv deleted file mode 100644 index 4824ee9..0000000 --- a/COMMITTERS.csv +++ /dev/null @@ -1 +0,0 @@ -Name, Email, Github ID diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index 03da6c5..0000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,34 +0,0 @@ -_Use this file to detail how to make a contribution to the project. The structure below is generally recommended, but can be changed to meet the needs of the project_ - -# Contributing to SEAPATH - -Thank you for your interest in contributing to PROJECT NAME. This document explains our contribution process and procedures: - -* [How to Contribute a Bug Fix or Change](#How-to-Contribute-a-Bug-Fix-or-Change) -* [Development Workflow](#Development-Workflow) -* [Coding Style](#Coding-Style) - -For a description of the roles and responsibilities of the various members of the PROJECT NAME community, see the [governance policies], and for further details, see the project's [Technical Charter]. Briefly, Contributors are anyone who submits content to the project, Committers review and approve such submissions, and the Technical Steering Committee provides general project oversight. - -If you just need help or have a question, refer to [SUPPORT.md](SUPPORT.md). - -## How to Contribute a Bug Fix or Change - -To contribute code to the project, first read over the [governance policies] page to understand the roles involved. - -Each contribution must meet the [coding style] and include.. - -* Tests and documentation to explain the functionality. -* Any new files have [copyright and license headers] -* A [Developer Certificate of Origin signoff]. -* Submitted to the project as a pull request. - -PROJECT NAME is licensed under the [LICENSE NAME](LICENSE.md) license. Contributions should abide by that standard license. - -Project committers will review the contribution in a timely manner, and advise of any changes needed to merge the request. - - -[governance policies]: GOVERNANCE.md -[Technical Charter]: tsc/CHARTER.md -[copyright and license headers]: https://github.com/lf-energy/tac/blob/main/process/contribution_guidelines.md#license -[Developer Certificate of Origin signoff]: https://github.com/lf-energy/tac/blob/main/process/contribution_guidelines.md#contribution-sign-off diff --git a/GOVERNANCE.md b/GOVERNANCE.md deleted file mode 100644 index 11a7936..0000000 --- a/GOVERNANCE.md +++ /dev/null @@ -1,70 +0,0 @@ -*NOTE: This document is intended to provide an example governance structure for any LF Energy Foundation project to consider as a starting point. All projects hosted by LF Energy Foundation are not bound by these governance polices, but in absence of any prior governance structure should consider this as a recommended structure* - -# Overview - -This project aims to be governed in a transparent, accessible way for the benefit of the community. All participation in this project is open and not bound to corporate affilation. Participants are bound to the project's [Code of Conduct]. - -# Project roles - -## Contributor - -The contributor role is the starting role for anyone participating in the project and wishing to contribute code. - -# Process for becoming a contributor - -* Review the [Contribution Guidelines] to ensure your contribution is inline with the project's coding and styling guidelines. -* Submit your code as a PR with the appropriate DCO signoff -* Have your submission approved by the committer(s) and merged into the codebase. - -## Committer - -The committer role enables the contributor to commit code directly to the repository, but also comes with the responsibility of being a responsible leader in the community. - -### Process for becoming a committer - -* Show your experience with the codebase through contributions and engagement on the community channels. -* Request to become a committer. To do this, create a new pull request that adds your name and details to the [Committers File] file and request existing committers to approve. -* After the majority of committers approve you, merge in the PR. Be sure to tag the whomever is managing the GitHub permissions to update the committers team in GitHub. - -### Committer responsibilities - -* Monitor email aliases (if any). -* Monitor Slack (delayed response is perfectly acceptable). -* Triage GitHub issues and perform pull request reviews for other committers and the community. -* Make sure that ongoing PRs are moving forward at the right pace or closing them. -* In general continue to be willing to spend at least 25% of ones time working on the project (~1.25 business days per week). - -### When does a committer lose committer status - -If a committer is no longer interested or cannot perform the committer duties listed above, they -should volunteer to be moved to emeritus status. In extreme cases this can also occur by a vote of -the committers per the voting process below. - -## Lead - -The project committers will elect a lead ( and optionally a co-lead ) which will be the primary point of contact for the project and representative to the TAC upon becoming an Active stage project. The lead(s) will be responsible for the overall project health and direction, coordination of activities, and working with other projects and committees as needed for the continuted growth of the project. - -# Release Process - -Project releases will occur on a scheduled basis as agreed to by the committers. - -# Conflict resolution and voting - -In general, we prefer that technical issues and committer membership are amicably worked out -between the persons involved. If a dispute cannot be decided independently, the committers can be -called in to decide an issue. If the committers themselves cannot decide an issue, the issue will -be resolved by voting. The voting process is a simple majority in which each committer receives one vote. - -# Communication - -This project, just like all of open source, is a global community. In addition to the [Code of Conduct], this project will: - -* Keep all communucation on open channels ( mailing list, forums, chat ). -* Be respectful of time and language differences between community members ( such as scheduling meetings, email/issue responsiveness, etc ). -* Ensure tools are able to be used by community members regardless of their region. - -If you have concerns about communication challenges for this project, please contact the committers. - -[Code of Conduct]: CODE_OF_CONDUCT.md -[Committers File]: COMMITTERS.csv -[Contribution Guidelines]: CONTRIBUTING.md diff --git a/INSTRUCTIONS.md b/INSTRUCTIONS.md deleted file mode 100644 index 4343cf4..0000000 --- a/INSTRUCTIONS.md +++ /dev/null @@ -1,15 +0,0 @@ -# Instructions for using this template - -1) Review and update (README.md) and (tsc/README.md) with the [PROJECT NAME] and [PROJECT LOGO], as well as the contents for the various sections. -2) To enable creating meeting agendas from GitHub issues, follow steps 3-5. -3) In the [meeting agenda template](.github/ISSUE_TEMPLATE/meeting.md), update `[PROJECT NAME]` and add the TSC members under the ['Attendance' section](.github/ISSUE_TEMPLATE/meeting.md#attendance). -4) Set the meeting date and time, along with the cadence in the [build agenda workflow](.github/workflows/build_agenda.yml) in the key `schedules:` that specifies a ISO-8601 interval. Examples for repeating: - -``` -# start 2020-04-22 at 16:00, repeat every 2 weeks -schedules: 2020-04-22T16:00:00.0Z/P2W -# start 2020-04-22 at 16:00, repeat every 7 days -schedules: 2020-06-22T16:00:00.0Z/P7D -``` -5) In the [send agenda workflow](.github/workflows/send_agenda.yml), update `[PROJECT NAME]` and `[MAILING LIST EMAIL]`. -6) Any items with the label `meeting` will be added to the agenda automatically when it is built the day prior to the meeting. diff --git a/README.md b/README.md deleted file mode 100644 index 2ce8f7a..0000000 --- a/README.md +++ /dev/null @@ -1,38 +0,0 @@ -```gfm -# insert project logo - replace the below logo location with the location of your logo -![](https://github.com/lf-energy/artwork/blob/master/projects/PROJECT NAME/PROJECT NAME-color.svg) -``` - -```gfm -# Add badges that point to your LICENSE, CII status, and build environment (if it exists). Check out other badges to add at https://shields.io/ -![GitHub](https://img.shields.io/github/license/lfenergy/PROJECT NAME) -[![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/CII ID/badge)](https://bestpractices.coreinfrastructure.org/projects/CII ID) -``` - -# PROJECT NAME - -_2-3 sentence description of the project_ - -## Install - -_Provide install instructions here or point to an INSTALL.md file_ - -## Build - -_Provide build instructions here or point to an BUILD.md file_ - -## Discussion - -You can connect with the community in a variety of ways... - -- [LINK TO MAILING LIST](https://lists.lfenergy.org/g/xxxx-discussion) -- [#PROJECT NAME channel on LF Energy Slack](https://slack.lfenergy.org) - -## Contributing -Anyone can contribute to the PROJECT NAME project - learn more at [CONTRIBUTING.md](CONTRIBUTING.md) - -## Governance -PROJECT NAME is a project hosted by the [LF Energy Foundation](https://lfenergy.org). This project's techincal charter is located in [CHARTER.md](tsc/CHARTER.md) and has established it's own processes for managing day-to-day processes in the project at [GOVERNANCE.md](GOVERNANCE.md). - -## Reporting Issues -To report a problem, you can open an [issue](https://github.com/lf-energy/PROJECT NAME/issues) in repository against a specific workflow. If the issue is senstive in nature or a security related issue, please do not report in the issue tracker but instead email PROJECT NAME-private@lists.lfenergy.org. diff --git a/SECURITY.md b/SECURITY.md deleted file mode 100644 index 034e848..0000000 --- a/SECURITY.md +++ /dev/null @@ -1,21 +0,0 @@ -# Security Policy - -## Supported Versions - -Use this section to tell people about which versions of your project are -currently being supported with security updates. - -| Version | Supported | -| ------- | ------------------ | -| 5.1.x | :white_check_mark: | -| 5.0.x | :x: | -| 4.0.x | :white_check_mark: | -| < 4.0 | :x: | - -## Reporting a Vulnerability - -Use this section to tell people how to report a vulnerability. - -Tell them where to go, how often they can expect to get an update on a -reported vulnerability, what to expect if the vulnerability is accepted or -declined, etc. diff --git a/SUPPORT.md b/SUPPORT.md deleted file mode 100644 index fbd2a7e..0000000 --- a/SUPPORT.md +++ /dev/null @@ -1,27 +0,0 @@ -_Use this file to detail how to make get support forthe project. The structure below is generally recommended, but can be changed to meet the needs of the project_ - -# Getting Help - -There are a few ways to connect with the PROJECT NAME project: - -* _provide email list details_ -* _provide Slack details_ -* _provide link to submit issue_ - -## How to Ask for Help - -If you have trouble installing, building, or using PROJECT NAME, but there's not yet reason to suspect you've encountered a genuine bug, -start by posting a question to the mailing list or Slack channel. This is the place for question such has "How do I...". - -## How to report a bug or request an enhancement - -PROJECT NAME manages bug and enhancement using it's [issue tracker]. The issue template will guide you on making an effective report. - -## How to report a security vulnerability - -If you think you've found a potential vulnerability in PROJECT NAME, please -email security@PROJECT DOMAIN to responsibly disclose it. - -## Contributing a fix - -Please refer to [CONTRIBUTING.md](CONTRIBUTING.md) to make a project contribution. diff --git a/THIRD_PARTY.md b/THIRD_PARTY.md deleted file mode 100644 index 920c29f..0000000 --- a/THIRD_PARTY.md +++ /dev/null @@ -1 +0,0 @@ -_Use this file to list out any third-party dependencies used by this project. You may choose to point to a Gemfile or other language specific packaging file for details._ diff --git a/tests/README.md b/tests/README.md deleted file mode 100644 index f28541f..0000000 --- a/tests/README.md +++ /dev/null @@ -1 +0,0 @@ -Any test for this project go in this folder. If there are no tests, please keep this folder to avoid repolinter errors and notate in this field why. diff --git a/tsc/CHARTER.md b/tsc/CHARTER.md deleted file mode 100644 index 420b987..0000000 --- a/tsc/CHARTER.md +++ /dev/null @@ -1,69 +0,0 @@ -_Template - update with Adopted Date when TSC approves and send to operations@lfenergy.org to file_ - -# Technical Charter (the "Charter") for [PROJECT NAME] a Series of LF Projects, LLC - -**Adopted [DATE]** - -This charter (the "Charter") sets forth the responsibilities and procedures for technical contribution to, and oversight of, the [PROJECT NAME] project, which has been established as [PROJECT NAME] a Series of LF Projects, LLC (the "Project"). LF Projects, LLC ("LF Projects") is a Delaware series limited liability company. All Contributors to the Project must comply with the terms of this Charter. - -## 1. Mission and Scope of the Project - * **a.** The mission of the Project is [MISSION]. - * **b.** The scope of the Project includes software development under an OSI-approved open source license supporting the mission, including documentation, testing, integration and the creation of other artifacts that aid the development, deployment, operation or adoption of the open source software project. - -## 2. Technical Steering Committee - * **a.** The Technical Steering Committee (the "TSC") will be responsible for all technical oversight of the open source Project. - * **b.** The TSC voting members are initially the Project's Committers. At the inception of the project, the Committers of the Project will be as set forth within the "CONTRIBUTING" file within the Project's code repository. The TSC may choose an alternative approach for determining the voting members of the TSC, and any such alternative approach will be documented in the CONTRIBUTING file. Any meetings of the Technical Steering Committee are intended to be open to the public, and can be conducted electronically, via teleconference, or in person. - * **c.** TSC projects generally will involve Contributors and Committers. The TSC may adopt or modify roles so long as the roles are documented in the CONTRIBUTING file. Unless otherwise documented: - * **i.** Contributors include anyone in the technical community that contributes code, documentation, or other technical artifacts to the Project; - * **ii.** Committers are Contributors who have earned the ability to modify ("commit") source code, documentation or other technical artifacts in a project's repository; and - * **iii.** A Contributor may become a Committer by a majority approval of the existing Committers. A Committer may be removed by a majority approval of the other existing Committers. - * **d.** Participation in the Project through becoming a Contributor and Committer is open to anyone so long as they abide by the terms of this Charter. - * **e.** The TSC may (1) establish work flow procedures for the submission, approval, and closure/archiving of projects, (2) set requirements for the promotion of Contributors to Committer status, as applicable, and (3) amend, adjust, refine and/or eliminate the roles of Contributors, and Committers, and create new roles, and publicly document any TSC roles, as it sees fit. - * **f.** The TSC may elect a TSC Chair, who will preside over meetings of the TSC and will serve until their resignation or replacement by the TSC. The TSC Chair, or any other TSC member so designated by the TSC, will serve as the primary communication contact between the Project and the Technical Advisory Council of the Academy Software Foundation of The Linux Foundation. - * **g.** Responsibilities: The TSC will be responsible for all aspects of oversight relating to the Project, which may include: - * **i.** coordinating the technical direction of the Project; - * **ii.** approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to a sub-project's scope); - * **iii.** organizing sub-projects and removing projects; - * **iv.** creating sub-committees or working groups to focus on cross-project technical issues and requirements; - * **v.** appointing representatives to work with other open source or open standards communities; - * **vi.** establishing community norms, workflows, issuing releases, and security issue reporting policies; - * **vii.** approving and implementing policies and processes for contributing (to be published in the CONTRIBUTING file) and coordinating with the Series Manager to resolve matters or concerns that may arise as set forth in Section 7 of this Charter; - * **viii.** discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; and - * **ix.** coordinating any marketing, events, or communications regarding the Project with the LF Projects Manager or their designee. - -## 3. TSC Voting - * **a.** While the Project aims to operate as a consensus based community, if any TSC decision requires a vote to move the Project forward, the voting members of the TSC will vote on a one vote per voting member basis. - * **b.** Quorum for TSC meetings requires at least two-thirds of all voting members of the TSC to be present. The TSC may continue to meet if quorum is not met, but will be prevented from making any decisions at the meeting. - * **c.** Except as provided in Section 7.c. and 8.a, decisions by vote at a meeting require a majority vote of those in attendance, provided quorum is met. Decisions made by electronic vote without a meeting require a majority vote of all voting members of the TSC. - * **d.** In the event a vote cannot be resolved by the TSC, any voting member of the TSC may refer the matter to the Series Manager for assistance in reaching a resolution. - -## 4. Compliance with Policies - * **a.** This Charter is subject to the Series Agreement for the Project and the Operating Agreement of LF Projects. Contributors will comply with the policies of LF Projects as may be adopted and amended by LF Projects, including, without limitation the policies listed at https://lfprojects.org/policies/. - * **b.** The TSC may adopt a code of conduct ("CoC") for the Project, which is subject to approval by the Series Manager. Contributors to the Project will comply with the CoC or, in the event that a Project-specific CoC has not been approved, the LF Projects Code of Conduct listed at https://lfprojects.org/policies/. - * **c.** When amending or adopting any policy applicable to the Project, LF Projects will publish such policy, as to be amended or adopted, on its web site at least 30 days prior to such policy taking effect; provided, however, that in the case of any amendment of the Trademark Policy or Terms of Use of LF Projects, any such amendment is effective upon publication on LF Projects web site. - * **d.** All participants must allow open participation from any individual or organization meeting the requirements for contributing under this Charter and any policies adopted for all participants by the TSC, regardless of competitive interests. Put another way, the Project community must not seek to exclude any participant based on any criteria, requirement, or reason other than those that are reasonable and applied on a non-discriminatory basis to all participants in the Project community. - * **e.** The Project will operate in a transparent, open, collaborative, and ethical manner at all times. The output of all Project discussions, proposals, timelines, decisions, and status should be made open and easily visible to all. Any potential violations of this requirement should be reported immediately to the LF Projects Manager. - -## 5. Community Assets - * **a.** LF Projects shall hold title to all trade or service marks used by the Project ("Project Trademarks"), whether based on common law or registered rights. Project Trademarks shall be transferred and assigned to LF Projects to hold on behalf of the Project. Any use of any Project Trademarks by participants in the Project shall be in accordance with the license from LF Projects and inure to the benefit of LF Projects. - * **b.** The Project shall, as permitted and in accordance with such license from LF Projects, develop and own all Project GitHub and social media accounts, and domain name registrations created by the Project community. - * **c.** Under no circumstances shall LF Projects be expected or required to undertake any action on behalf of the Project that is inconsistent with the tax-exempt status or purpose, as applicable, of LFP, Inc. or LF Projects, LLC. - -## 6. General Rules and Operations. - * **a.** The Project will: - * **i.** engage in the work of the project in a professional manner consistent with maintaining a cohesive community, while also maintaining the goodwill and esteem of LF Projects, LFP, Inc. and other partner organizations in the open source software community; and - * **ii.** respect the rights of all trademark owners, including any branding and trademark usage guidelines. - -## 7. Intellectual Property Policy - * **a.** Participants acknowledge that the copyright in all new contributions shall be retained by the copyright holder as independent works of authorship and that no contributor or copyright holder will be required to assign copyrights to the Project. - * **b.** Except as described in Section 7.c., all code contributions to the Project are subject to the following: - * **i.** All new inbound code contributions to the Project must be made using the **[Apache License, Version 2.0 (available here: https://www.apache.org/licenses/LICENSE-2.0)]** (the "Project License"). - * **ii.** All new inbound code contributions must be accompanied by a Developer Certificate of Origin (http://developercertificate.org) sign-off in the source code system that is submitted through a TSC-approved contribution process which will bind the authorized contributor and, if not self-employed, their employer to the applicable license; - * **iii.** All outbound code will be made available under the Project License. - * **iv.** Documentation will be received and made available by the Project under the Creative Commons Attribution 4.0 International License (available at http://creativecommons.org/licenses/by/4.0/). - * **v.** The Project may seek to integrate and contribute back to other open source projects ("Upstream Projects"). In such cases, the Project will conform to all license requirements of the Upstream Projects, including dependencies, leveraged by the Project. Upstream Project code contributions not stored within the Project's main code repository shall comply with the contribution process and license terms for the applicable Upstream Project. - * **c.** If an alternative inbound or outbound license is required for compliance with the license for a leveraged open source project or is otherwise required to achieve the Project's mission, the Governing Board of the Academy Software Foundation of The Linux Foundation ("Governing Board") or the Governing Board's designated committee may approve the use of an alternative license for specific inbound or outbound contributions on an exception basis. Any exceptions must be approved by a vote of the Governing Board and must be limited in scope to what is required for such purpose. To request an exception, please describe the contribution, the alternative open source license(s), and the justification for using an alternative open source license for the Project. - * **d.** Contributed files should contain license information, such as SPDX short form identifiers, indicating the open source license or licenses pertaining to the file. - -## 8. Amendments - * **a.** This charter may be amended by a two-thirds vote of the entire TSC and is subject to approval by LF Projects. diff --git a/tsc/README.md b/tsc/README.md deleted file mode 100644 index 104fd7d..0000000 --- a/tsc/README.md +++ /dev/null @@ -1,68 +0,0 @@ -# TSC Materials for [PROJECT NAME] - -This directory contains the meeting notes, process documentations, and other materials related to this project. - -## 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](../issues) to track and link to it in the list - -- Codebase - - [ ] Project license identified and exists in root directory of all repos ( named LICENSE ) - - [ ] Code scan completed and any recommendations remedyed. -- 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 ( template started at [README.md](../README.md) ) - - [ ] Any third-party components/dependencies included are listed along with thier licenses ( example template at [THIRD_PARTY.md](../THIRD_PARTY.md) ) - - [ ] Governamce defined, outlining community roles and how decsions are made ( starting point at [GOVERNANCE.md](../GOVERNANCE.md) if needed ). - - [ ] Contribution Policy defined ( CONTRIBUTING.md ) - - [ ] Code of Conduct defined ( default is at [CODE_OF_CONDUCT.md](../CODE_OF_CONDUCT.md) - if using a different code of conduct please contact [LFE Staff](mailto:operations@lfenergy.org) ). - - [ ] Release methodology defined ( [RELEASE.md](../RELEASE.md) ) -- New Project Goverance - - [ ] TSC members identified, added to [GOVERNANCE.md](../GOVERNANCE.md). - - [ ] First TSC meeting held ( [agenda](meetings) ) - - [ ] TSC meeting cadence set and added to project calendar (https://lists.lfenergy.org/calendar) -- Infrastructure - - [ ] Source Control (Github, GitLab, something else ) and LFE Staff is an administrator. - - [ ] Developer Certificate of Origin past commit signoff done and DCO Probot enabled. - - [ ] Issue/feature tracker (JIRA, GitHub issues) and LFE Staff is an administrator. - - Collaboration tools - - [ ] Mailing lists - one of: - - [ ] Create new list(s) ( default is -discussion@ and -private@ - create [service desk request] to provision ) - - [ ] Move to groups.io ( create [service desk request] to setup/transfer ) - - [ ] Establish project calendar on groups.io ( refer to [tac guidelines]) - - [ ] Slack or IRC ( create [service desk request] to setup Slack project channel ) - - [ ] Website ( refer to [tac guidelines] ) - - [ ] CI/build environment - - [ ] Add project to [Dev Anayltics](https://lfanalytics.io/projects/lf-energy) ( create [service desk request] to trigger ) -- Project assets - - [ ] Domain name ( create [service desk request] to setup/transfer ) - - [ ] Social media accounts ( create [service desk request] to setup/transfer ) - - [ ] Logo(s) ( create [service desk request] to create]; will be added to [artwork repo](https://artwork.lfenergy.org) in SVG and PNG format and color/black/white ) - - [ ] Trademarks/mark ownership rights ( complete [LF Projects - Form of Trademark and Account Assignment](lf_projects_trademark_assignment.md) ) -- Outreach - - [ ] New project annoucement done ( create [service desk request] to trigger ) - - [ ] Project added to LF Energy website and LF Energy landscape -- Early Adoption requirements - - [ ] CII Badge achieved ( apply at https://bestpractices.coreinfrastructure.org/en ) - - [ ] Elect TSC Chairperson - - [ ] Regular cadence of TSC meetings being held. - - [ ] Governance defined at [GOVERNANCE.md](../GOVERNANCE.md). - - [ ] Used in production by 2 organizations ( identify in [ADOPTERS.csv](../ADOPTERS.csv) ) - - Growth plan - - [ ] Growth plan created ( put in [growth-plan.md](growth-plan.md)) - - [ ] Growth plan submitted to TAC ( create [tac issue] to request - link to [growth-plan.md](growth-plan.md) - - [ ] Growth plan approved by TAC ( link to meeting minutes or email thread ) - - [ ] Commit/Contribution growth during incubation - - [ ] Schedule presentation to TAC - - [ ] TAC approval (2/3 required) -- Graduated Project requirements - - [ ] TSC established with 5+ members, with no more than 1/2 of members at the same organization. - - [ ] Release/Testing process defined ( [RELEASE.md](../RELEASE.md) )ocumented zCommitters defined in the project ( [COMMITTERS.csv](COMMITTERS.csv) or [COMMITTERS.yml](COMMITTERS.yml) ) - - [ ] Maintainers/committers from at least 2 organizations. - - [ ] Schedule presentation to TAC - - [ ] TAC approval (2/3 required) - -[service desk request]: https://github.com/lf-energy/foundation/issues/new/choose -[tac guidelines]: https://github.com/lf-energy/tac diff --git a/tsc/meetings/README.md b/tsc/meetings/README.md deleted file mode 100644 index 1d269fc..0000000 --- a/tsc/meetings/README.md +++ /dev/null @@ -1,3 +0,0 @@ -# TSC Meeting notes - -All TSC meeting notes are stored here in YYYY-MM-DD.md format. Recordings and other assets from conference calls systems can also be stored in YYYY-MM-DD.XXX format.