├── .github ├── ISSUE_TEMPLATE │ ├── Agenda.yml │ ├── application.yml │ ├── code-signing-certificate-request.yml │ ├── membership.yml │ ├── project-spotlight.md │ └── project-support-request.yml └── workflows │ └── add-new-projects-to-board.yml ├── .gitignore ├── OnBoardingQuestionaire.docx ├── meetings ├── 2020-04-09.md ├── 2020-05-14.md ├── 2020-06-11.md ├── 2020-07-09.md ├── 2020-08-13.md ├── 2020-09-10.md ├── 2020-10-08.md ├── 2020-11-12.md ├── 2020-12-10.md ├── 2021-01-14.md ├── 2021-02-11.md ├── 2021-03-11.md ├── 2021-04-08.md ├── 2021-05-13.md ├── 2021-06-10.md └── 2021-07-08.md ├── new-projects.md └── readme.md /.github/ISSUE_TEMPLATE/Agenda.yml: -------------------------------------------------------------------------------- 1 | name: Agenda 2 | description: Add the agenda for a upcoming Project Committee Meeting 3 | title: "[Agenda]: " 4 | labels: ["agenda", "triage"] 5 | assignees: 6 | - nicoleabuhakmeh 7 | body: 8 | - type: markdown 9 | attributes: 10 | value: | 11 | The Project Committee will be having their monthly meeting on DATE at 5pm Eastern. 12 | - type: textarea 13 | id: agenda-items 14 | attributes: 15 | label: Agenda Items 16 | description: The issues in the agenda 17 | placeholder: | 18 | 1. Item 1 19 | 2. Item 2 20 | validations: 21 | required: true 22 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/application.yml: -------------------------------------------------------------------------------- 1 | name: New .NET Foundation Project Application 2 | description: Creates a public issue to track your projects application to join the .NET Foundation. 3 | title: "Issue: New .NET Foundation Project Application" 4 | labels: ["project application", "project support"] 5 | assignees: 6 | - sbwalker 7 | - ChrisSfanos 8 | body: 9 | - type: markdown 10 | attributes: 11 | value: | 12 | ## Instructions: 13 | Thanks for your application to join the .NET Foundation! 14 | 15 | 1. Here is a checklist of steps we'll follow during the process: [New Project Onboarding](https://github.com/dotnet-foundation/projects/blob/master/new-projects.md) 16 | 2. Please review the [Eligibility Criteria](https://github.com/dotnet-foundation/projects#eligibility-criteria) before completing the application 17 | 3. Please fill out the application in the template below. If you have any issues with using the template, please reach out to the team at contact@dotnetfoundation.org and we will follow up directly with you. 18 | 4. After review and comment by the advisory council, we will submit your questionnaire to the board of directors recommending we add your project. 19 | 5. We will send you a contribution agreement via DocuSign and configure the CLA bot. 20 | 6. Finally, we will send you a on-boarding checklist with a set of work items to perform to complete the process. 21 | 22 | 23 | Some common questions that come up on the questionnaire: 24 | 25 | **Project Transfer Signatories.**: List the top contributors, with __contact e-mail__. For most projects, this is the top 1-5 contributors who have contributed more than a few hundred lines of code. 26 | **Contribution Model.** Under the .NET Foundation contribution model, a project retains ownership of the copyright, but grants .NET Foundation a broad license to the project's code and other intellectual property. The project also confirms that the project's submissions to .NET Foundation are its own original work (there are also instructions for any third party materials that might be included). 27 | **Project Trademarks - Licensed vs Disclaimed.** When signing the CLA you are asked to describe and choose how you want to handle any trademarks for the project. These include the project name, at a minimum, and potentially any logos or other recognizable, non-descriptive titles used within the project - these do not need to be formally registered trademarks. 28 | 29 | By default, the .NET Foundation selects **Licensed** in the CLA 30 | 31 | |Type|What it Means|Why you'd select it | 32 | -----|-------------|------------------- 33 | |Licensed|Project retains ownership of any trademarks and licenses the .NET Foundation to use them.|This follows the same ownership/license structure as the copyright in the project. The project keeps ownership in the trademarks and .NET Foundation only has the rights that are specifically granted in the license. The project still retains the rights to enforce its rights in the trademarks. | 34 | |Disclaimed|Project agrees not to enforce the trademark against the .NET Foundation or anyone else.|The project doesn't claim any ownership rights to the trademarks and does not plan to control how .NET Foundation decides to use the trademarks. | 35 | 36 | ## 1. General Information: 37 | Please provide the following information about your project. 38 | 39 | - type: input 40 | id: projectName 41 | attributes: 42 | label: Project Name 43 | description: The name of your project 44 | placeholder: My Awesome Project 45 | validations: 46 | required: true 47 | 48 | - type: input 49 | id: license 50 | attributes: 51 | label: License 52 | description: The license your project is under. 53 | placeholder: MIT 54 | validations: 55 | required: true 56 | 57 | - type: input 58 | id: contributor 59 | attributes: 60 | label: Contributor 61 | description: The name of the contributor(s) 62 | placeholder: Company, Organization or individual name(s) 63 | validations: 64 | required: true 65 | 66 | - type: dropdown 67 | id: existingOSSProject 68 | attributes: 69 | label: Existing OSS Project? 70 | description: Select if the application is for an existing OSS project or not. 71 | options: 72 | - "Yes" 73 | - "No" 74 | validations: 75 | required: true 76 | 77 | - type: input 78 | id: sourceCodeURL 79 | attributes: 80 | label: Source Code URL 81 | description: The URL to the source code for your project. 82 | placeholder: https://github.com// 83 | validations: 84 | required: true 85 | 86 | - type: input 87 | id: projectHomepageURL 88 | attributes: 89 | label: Project Homepage URL 90 | description: The URL to the homepage for your project if different from the Source Code URL. 91 | validations: 92 | required: false 93 | 94 | - type: textarea 95 | id: projectTransferSignatories 96 | attributes: 97 | label: Project Transfer Signatories 98 | description: Full legal name and __email address__ required of the individual(s) with authority to transfer or contribute the project to the .NET Foundation. Note that if you'd prefer not to include this in the public application, it can be submitted via e-mail to contact@dotnetfoundation.org (referencing this issue number). Note this likely should include the contributors listed above. 99 | placeholder: | 100 | * John Doe 101 | * Jane Doe 102 | validations: 103 | required: true 104 | 105 | - type: markdown 106 | attributes: 107 | value: | 108 | ## 2. Description 109 | Please provide a brief statement about your project in terms that are understandable to the target consumer of the library or project, i.e. an elevator pitch for the project. 110 | 111 | - type: textarea 112 | id: description 113 | attributes: 114 | label: Description 115 | description: Please provide a 1 sentence (<140 character) summary of your project to help users when searching the .NET Foundation projects. 116 | validations: 117 | required: true 118 | 119 | - type: markdown 120 | attributes: 121 | value: | 122 | ## 3. Project Governance 123 | Please complete this section about who will be maintaining the open source project and how it will run. 124 | ### Project Lead 125 | Primary contact point for the community and the .NET Foundation when discussing governance of the project. 126 | 127 | - type: input 128 | id: projectLeadName 129 | attributes: 130 | label: Name 131 | description: Name of the project lead. 132 | validations: 133 | required: true 134 | 135 | - type: input 136 | id: projectLeadEmail 137 | attributes: 138 | label: Email 139 | description: Email of the project lead. 140 | validations: 141 | required: true 142 | 143 | - type: input 144 | id: projectLeadGitHubUrl 145 | attributes: 146 | label: GitHub Profile URL 147 | description: GitHub profile URL of the project lead. 148 | placeholder: https://github.com/ 149 | validations: 150 | required: false 151 | 152 | - type: textarea 153 | id: commiters 154 | attributes: 155 | label: Committers 156 | description: Which individuals have commit/write access to the repository, what is their GitHub ID and who is their employer (if contributions are on behalf of an employer). 157 | validations: 158 | required: false 159 | 160 | - type: textarea 161 | id: discord-ids 162 | attributes: 163 | label: Discord Ids 164 | description: What are the discord IDs for the major contributors that should be listed as project maintainers on discord? We use discord for all foundation communications and have maintainer roles. 165 | validations: 166 | required: false 167 | 168 | - type: textarea 169 | id: governanceModel 170 | attributes: 171 | label: Governance Model 172 | description: Please describe how new code changes are proposed to the project, how those changes are reviewed, and how a decision is made to accept proposed changes. Also describe the process for identifying and appointing new committers. 173 | validations: 174 | required: true 175 | 176 | - type: checkboxes 177 | id: cla 178 | attributes: 179 | label: CLA 180 | options: 181 | - label: If already an OSS project, was a Contribution License Agreement in place for contributions accepted? 182 | required: false 183 | 184 | - type: textarea 185 | id: claDescription 186 | attributes: 187 | label: How does the project check who has signed one? 188 | description: Please describe how the project checks who has signed a CLA. 189 | validations: 190 | required: false 191 | 192 | - type: input 193 | id: claNotificationAlias 194 | attributes: 195 | label: CLA Notification Alias 196 | description: Provide an email address that will receive CLA related notifications from the .NET Foundation CLA automation. 197 | validations: 198 | required: false 199 | 200 | - type: dropdown 201 | id: projectTransferType 202 | attributes: 203 | label: Select the Project Transfer Agreement model 204 | description: Select either Assignment or Contribution model for transferring the project to the .NET Foundation. 205 | options: 206 | - "Assignment" 207 | - "Contribution" 208 | validations: 209 | required: true 210 | 211 | 212 | - type: markdown 213 | attributes: 214 | value: | 215 | #### Assignment Model 216 | > Under the .NET Foundation assignment model, project ownership and other intellectual property is assigned to the .NET Foundation and the .NET Foundation agrees to grantback a license to the contributor(s). 217 | 218 | #### Contribution Model 219 | > Under the .NET Foundation contribution model, a project retains ownership of the copyright, but grants the .NET Foundation a broad license to the project’s code and other intellectual property. The project also confirms that the project’s submissions to .NET Foundation are its own original work (there are also instructions for any third party materials that might be included). 220 | 221 | ## 4. Repository Layout 222 | 223 | The .NET Foundation host guidance for new projects and details on recommended structure here: 224 | [https://github.com/dotnet/home/tree/master/guidance](https://github.com/dotnet/home/tree/master/guidance) 225 | 226 | Note that the open source repository should be the master where changes are made by the core development team using the same PR process that is used for non-committer contributions. 227 | 228 | 229 | - type: textarea 230 | id: repositoryLayout 231 | attributes: 232 | label: Repository Layout 233 | description: Please define below any changes you would want to make to your repositories as part of the process of joining the .NET Foundation 234 | validations: 235 | required: false 236 | 237 | - type: markdown 238 | attributes: 239 | value: | 240 | ## 5. Eligibility Criteria 241 | Please complete the following for your project 242 | 243 | - type: checkboxes 244 | id: elegibilityCriteria 245 | attributes: 246 | label: Eligibility Criteria 247 | options: 248 | - label: The project is built on the .NET platform and/or creates value within the .NET ecosystem. 249 | required: false 250 | - label: The project produces source code for distribution to the public at no charge. 251 | required: false 252 | - label: The project's code is easily discoverable and publicly accessible (preferably on GitHub). 253 | required: false 254 | - label: The project contains a build script that can produce deployable artifacts that are identical to the official deployable artifacts, with the exception of code signing (Exception may be granted for strong name keys, though strongly encouraged to be committed. Exception relies on OSS signing being in the build script for public builds). 255 | required: false 256 | - label: When applicable, project must use reproducible build settings in its toolchain. 257 | required: false 258 | - label: The project uses [Source Link.](https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/sourcelink) 259 | required: false 260 | - label: The project uses either embedded PDBs or publish symbol packages to NuGet (if applicable). 261 | required: false 262 | - label: The project code signs their artifacts as appropriate. 263 | required: false 264 | - label: The project organization has 2FA enabled. Requiring 2FA must be done as part of onboarding if not already enabled. 265 | required: false 266 | - label: Libraries that are mandatory dependencies of the project are offered under a standard, permissive open source license which has been approved by the .NET Foundation (exceptions include a dependency that is required by the target platform where no alternative open source dependency is available such as the .NET Framework or a hardware specific library). 267 | required: false 268 | - label: Committers are bound by a Contributor License Agreement (CLA) and/or are willing to embrace the .NET Foundation's CLA when the project becomes a Member. 269 | required: false 270 | - label: The copyright ownership of everything that the project produces is clearly defined and documented. 271 | required: false 272 | - label: The project has a public issue tracker where the status of any defect can be easily obtained. 273 | required: false 274 | - label: The project has a published Security Policy. 275 | required: false 276 | - label: The project has a home page which provides high level information about its status and purpose. 277 | required: false 278 | - label: The project has a public communication channel where community members can engage with maintainers. 279 | required: false 280 | - label: The project has a publicly available location where members can review and contribute to documentation. 281 | required: false 282 | 283 | - type: markdown 284 | attributes: 285 | value: | 286 | ## 6. Why are you applying to add your project to the Foundation? 287 | - type: textarea 288 | id: whyPlanSummary 289 | attributes: 290 | label: Describe why you are applying for Project Membership. 291 | description: Please summarize your reason for joining the Foundation 292 | validations: 293 | required: true 294 | 295 | - type: markdown 296 | attributes: 297 | value: | 298 | ## 7. Infrastructure Requirements 299 | Please describe any infrastructure requirements for the project. 300 | For example: 301 | - How will build servers be operated? 302 | - Any web hosting or service hosting requirements? 303 | - Do we need to set up SSL certificates or provide Authenticode Code Signing arrangement for releases? 304 | 305 | - type: textarea 306 | id: infrastructureRequirements 307 | attributes: 308 | label: Infrastructure Requirements Summary 309 | validations: 310 | required: false 311 | 312 | - type: markdown 313 | attributes: 314 | value: | 315 | ## 8. Additional Notes 316 | Please provide any additional information required or use this area for notes during the onboarding process. If this open source project has similarities with any other projects in this space then please detail them and why this project is different. If there are any potential issues that you feel the project might need help with early on then also state them here and discuss with your .NET Foundation Contact. 317 | 318 | - type: textarea 319 | id: notes 320 | attributes: 321 | label: Additional Notes 322 | validations: 323 | required: false 324 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/code-signing-certificate-request.yml: -------------------------------------------------------------------------------- 1 | name: Code Signing Certificate Request 2 | description: Request code signing certificate for an existing .NET Foundation project 3 | title: "[Code Signing Certificate]: " 4 | labels: ["project support", "triage"] 5 | assignees: 6 | - ChrisSfanos 7 | body: 8 | - type: markdown 9 | attributes: 10 | value: | 11 | Please fill in the information below to request a code signing certificate for your existing .NET Foundation project. 12 | 13 | You can ping on discord for status, but GitHub issues is the primary way to request support to allow for tracking 14 | and involving the project support team. 15 | - type: input 16 | id: project-name 17 | attributes: 18 | label: Project Name 19 | description: What is the name of the project 20 | placeholder: ex. email@example.com 21 | validations: 22 | required: true 23 | - type: checkboxes 24 | id: onboarding 25 | attributes: 26 | label: Onboarding Checklist 27 | description: Certificate onboarding checklist - Used by Staff 28 | options: 29 | - label: Register trade name @ChrisSfanos 30 | - label: Create configuration in Code Signing Service 31 | - label: Create organization with DigiCert 32 | - label: Request certificate from DigiCert 33 | - label: Received certificate and finalize sign service configuration 34 | 35 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/membership.yml: -------------------------------------------------------------------------------- 1 | name: Membership Request 2 | description: Membership request to the Projects Working Group 3 | title: "[Membership Application]: " 4 | labels: ["membership", "triage"] 5 | body: 6 | - type: markdown 7 | attributes: 8 | value: | 9 | ## Please note all meetings and communications are now conducted through Discord. It is a requirement to have a discord account. 10 | - type: input 11 | id: name 12 | attributes: 13 | label: What is your name? 14 | placeholder: "Joe Blogs" 15 | validations: 16 | required: true 17 | - type: input 18 | id: email 19 | attributes: 20 | label: Email 21 | description: "What email should we use?" 22 | placeholder: ex. email@example.com 23 | validations: 24 | required: true 25 | - type: input 26 | id: discord 27 | attributes: 28 | label: discord 29 | description: "Your discord ID" 30 | placeholder: id 31 | validations: 32 | required: true 33 | - type: textarea 34 | id: notes 35 | attributes: 36 | label: Notes 37 | description: Anything you'd like us to know about why you're joining the Projects Working Group 38 | validations: 39 | required: false 40 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/project-spotlight.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Project Spotlight Request 3 | about: Request highlighting an existing .NET Foundation project 4 | title: 'Project Spotlight Request: [Project Name]' 5 | labels: '' 6 | assignees: isaacrlevin 7 | 8 | --- 9 | 10 | ## General Information 11 | 12 | **Project Name:** 13 | 14 | **Contributor (Company, Organization or individual name(s)):** 15 | 16 | **Source Code URL:** 17 | 18 | **Documentation URL:** 19 | 20 | **Contribution URL:** 21 | 22 | **Project Homepage URL (if different):** 23 | 24 | **Please provide a brief statement about your project in terms that are understandable to the target consumer of the library or project, i.e. an elevator pitch for the project:** 25 | 26 | **Please list 5 top non-maintainer contributors to your project** 27 | 28 | **Month you would prefer to be featured** 29 | 30 | **Timeline when to conduct a short interview** 31 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/project-support-request.yml: -------------------------------------------------------------------------------- 1 | name: Project Support Request 2 | description: Request support for an existing .NET Foundation project 3 | title: "[Project Support]: " 4 | labels: ["project support", "triage"] 5 | assignees: 6 | - ChrisSfanos 7 | body: 8 | - type: markdown 9 | attributes: 10 | value: | 11 | Please fill in the information below to request support for your existing .NET Foundation project. 12 | 13 | If your request includes confidential information, you can e-mail 14 | contact@dotnetfoundation.org with the information below. 15 | 16 | You can ping on discord for status, but the GitHub issue is the primary way 17 | to request support to allow for tracking and involving the project support team. 18 | - type: input 19 | id: project 20 | attributes: 21 | label: Project 22 | description: Project Name 23 | placeholder: DotNet Foundation 24 | validations: 25 | required: true 26 | - type: input 27 | id: project-url 28 | attributes: 29 | label: Project Url 30 | description: Project Url 31 | placeholder: https://github.com/dotnet/dotnet-runtime 32 | validations: 33 | required: true 34 | - type: textarea 35 | id: description 36 | attributes: 37 | label: Description 38 | description: Description of the problem 39 | placeholder: The description 40 | validations: 41 | required: true 42 | - type: input 43 | id: due-by 44 | attributes: 45 | label: Due By 46 | description: What date is the item due by? 47 | validations: 48 | required: true 49 | -------------------------------------------------------------------------------- /.github/workflows/add-new-projects-to-board.yml: -------------------------------------------------------------------------------- 1 | name: Add project application to project board 2 | 3 | on: 4 | issues: 5 | types: [labeled] 6 | 7 | jobs: 8 | Add_New_Project_Application_Issue_To_Project_Board: 9 | runs-on: ubuntu-latest 10 | steps: 11 | - uses: konradpabjan/actions-add-new-issue-to-column@7a9ee8bfa125bf97c2fcfbac20ae8f82657f83ba 12 | if: contains(github.event.issue.labels.*.name, 'project application') 13 | with: 14 | action-token: "${{ secrets.ACCESS_TOKEN }}" 15 | project-url: "https://github.com/dotnet-foundation/projects/projects/1" 16 | column-name: "New Project Application" 17 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | ################################################################################ 2 | # This .gitignore file was automatically created by Microsoft(R) Visual Studio. 3 | ################################################################################ 4 | 5 | /.vs 6 | -------------------------------------------------------------------------------- /OnBoardingQuestionaire.docx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dotnet-foundation/projects/994d27d73c55f0adf2776aba23d41cf4fdc1fc3e/OnBoardingQuestionaire.docx -------------------------------------------------------------------------------- /meetings/2020-04-09.md: -------------------------------------------------------------------------------- 1 | Project Committee Meeting - Thursday, April 9, 12:00 PM ET 2 | 3 | Attendees: @sbwaker, @ClaireNovotny, @ChrisSfanos, @ChrisHammond, @snickler, @tannergooding, @eriawan, @mrswoop 4 | 5 | Agenda: 6 | 7 | 1. Review Project Applicants 8 | - Reviewed applications and health metrics for 3 new project submitted in the past month: JHipster.Net, ResXResourceManager, and Trivial 9 | - Action Item: @sbwalker will follow up with project owners via email to collect Eligibility criteria 10 | - Discussions focused on project size, maturity, relevancy. In particular there were questions on whether extensions or plugins to applications/platforms should be included in the Foundation 11 | - Also discussed two projects which were moved to the Seed level after the last Board meeting: Catalyst, Git Extensions 12 | - Seed projects need additional clarification in regards to approved licenses for the .NET Foundation 13 | - Action item: committee should propose the services that the .NET Foundation could offer Seed projects 14 | - Committee agreed upon recommendations to make to the Board of Directors 15 | 16 | 2. Open Source License Recommendations 17 | - Board of Directors requested that the Project Committee submit a proposal related to the licenses which should be supported. 18 | - Discussion ensued with a general suggestion that all OSI approved licenses could be supported 19 | - Members of the committee expressed concern that copyleft licenses are not well understood in the industry 20 | - Some members suggested that the .NET Foundation could offer education in this area 21 | - A website was shared which does a good job of this already: https://choosealicense.com/ 22 | - Opinions were shared that many commercial organizations still avoid copyleft licenses 23 | - It was noted that at one point in time the .NET Foundation had stated that it was focused on "commercial friendly" open source which would seem to indicate permissive licenses 24 | - Committee agreed upon recommendations to make to the Board of Directors 25 | 26 | Meeting adjourned after 1 hour. -------------------------------------------------------------------------------- /meetings/2020-05-14.md: -------------------------------------------------------------------------------- 1 | Project Committee Meeting - Thursday, May 14, 12:00 PM ET 2 | 3 | Attendees: @sbwalker, @ChrisHammond, @snickler, @mrswoop, @ClaireRNovotny, @ChrisSfanos 4 | Absent: @tannergooding, @eriawan 5 | 6 | Agenda: 7 | 8 | 1. Opening Discussion 9 | 10 | - ResXResourceManager- Board of Directors agreed to accept recommendation and approve application last month - Chris Sfanos in process of onboarding 11 | - Trivial - moved to Seed category based on project maturity - will re-evaluate next quarter 12 | - JHipster.Net - Committee discussed request from project owners for marketing exposure opportunities 13 | - Future Board Meetings - Board of Directors requested that Project Committee Chair attend the monthly Board meeting to represent the Project Committee 14 | - New Foundation Website - reviewed new website, discussed opportunity to contribute content for Project area, discussed need for official registry of .NET Foundation projects 15 | 16 | 2. Review Project Applicants 17 | 18 | - Reviewed health metrics for 1 new project submitted in the past month: PInvoke 19 | - @sbwalker has followed up with project owner via email to collect Eligibility criteria 20 | - If no blockers encountered in Eligibility criteria, Project Committee is recommending the Board approve this application 21 | 22 | 23 | 3. Open Source License Discussion 24 | 25 | - Executive Director of .NET Foundation shared background information related to some recent project licensing issues 26 | - Project Committee will be responsible for handling licensing issues on behalf of the .NET Foundation going forward 27 | - Action Item: Project Committee Chair to share internal communications with other Project Committee members related to licensing issues 28 | - Project Committee will have a follow up meeting next week to discuss plan of action 29 | - Project Committee also needs to construct proposal for clear Licensing guidelines for .NET Foundation 30 | - 31 | 32 | Meeting adjourned after 1 hour. -------------------------------------------------------------------------------- /meetings/2020-06-11.md: -------------------------------------------------------------------------------- 1 | Project Committee Meeting - Thursday, June 11, 12:00 PM ET 2 | 3 | Attendees: @sbwalker, @ChrisHammond, @snickler, @tannergooding, @mrswoop, @clairernovotny, @ChrisSfanos 4 | Absent: @eriawan 5 | 6 | Agenda: 7 | 8 | 1. Opening Discussion 9 | 10 | - PInvoke - Board of Directors agreed to accept recommendation and approve application last month 11 | - Chris Sfanos in process of onboarding 12 | - Licensing - discussed latest status of .NET Foundation project which had changed its open source license 13 | - project has rolled back to the previous license 14 | - @sbwalker action item to write a blog promoting the successful collaboration between the project and .NET Foundation 15 | - Board Elections 16 | - Executive Director shared info with the group about the approach for the upcoming Board elections 17 | 18 | 2. Review Project Applicants 19 | 20 | - MahApps.Metro - reviewed health metrics and eligibility criteria 21 | - Project Committee recommends the Board approve this application 22 | - Catalyst - project application had been reviewed previously by Project Committee (March) 23 | - Executive Director indicated one of the earlier blocking issues had been addressed 24 | - reviewed most recent health metrics and eligibility criteria 25 | - Project Committee not able to make recommendation to approve - will contact project owner with feedback 26 | - General Project Discussion 27 | - .NET Foundation needs a master list of projects which includes links to all associated assets, including CLAs 28 | - Chris Sfanos volunteered to reconcile the project master list 29 | 30 | 3. .NET Ecosystem Discussion 31 | 32 | - reviewed recent events, articles related to Microsoft and the Open Source ecosystem 33 | - items were not directly related to the .NET Foundation - they were shared with the Project Committee for general awareness 34 | - discussed general guidelines for public communication on behalf of .NET Foundation 35 | 36 | 4. Open Source Licensing Discussion 37 | 38 | - Project Committee in agreement that approved licenses should only include permissive licenses 39 | - Project Charter should have another iteration of amendments to address any of the specific items which have raised since it was originally published 40 | 41 | 5. Q&A 42 | 43 | - Executive Director requested summary of Project Committee items to include in monthly newsletter 44 | 45 | Meeting adjourned after 1 hour. -------------------------------------------------------------------------------- /meetings/2020-07-09.md: -------------------------------------------------------------------------------- 1 | Project Committee Meeting - July 9, 2020, 12:00 PM ET 2 | 3 | Attendees: Eriawan Kusumawardhono (@eriawan), Jeremy Sinclair (@snickler), Juan Elosegui (@jmelosegui), Tanner Gooding (@tannergooding), Chris Sfanos (@ChrisSfanos), Claire Novotny (@clairernovotny) 4 | Absent: Scott Willhite (@mrswoop), Chris Hammond (@ChrisHammond) 5 | 6 | Agenda: 7 | 8 | 1. Opening Discussion 9 | 10 | - MahApps.Metro - Board of Directors agreed to accept recommendation and approve application last month 11 | - Chris Sfanos in process of onboarding 12 | - Catalyst - feedback sent to project maintainer regarding license and health metric maturity 13 | - ImageSharp - communication with maintainer related to publishing a collaboration blog 14 | - @sbwalker action item to complete draft blog this week 15 | - Board Elections - updated Project Committee members on .NET Foundation election process 16 | - Board candidates announced 17 | - discussion about setting up a meeting with new Board members to explain mandate/progress of Project Committee 18 | 19 | 2. Review Project Applications 20 | 21 | - Verify - reviewed health metrics and eligibility criteria 22 | - health metrics indicate this project is mature 23 | - background check indicated this project was forked from another project 24 | - Project Committee recommends following up with maintainer to obtain additional background/context 25 | - Polyjuice - reviewed health metrics and eligibility criteria 26 | - Project Committee noted that health metrics are not yet at a level which indicate a mature open source project/community 27 | - recommendation is to promote to Seed level and revisit in 3 months 28 | - Project Committee will follow up with maintainer 29 | - Texnomic SecureDNS - reviewed health metrics and eligibility criteria 30 | - Project Committee noted that health metrics are not yet at a level which indicate a mature open source project/community 31 | - in particular this project only has a single contributor 32 | - recommendation is to promote to Seed level and revisit in 3 months 33 | - Project Committee will follow up with maintainer 34 | - Seed Level Definition - it was noted that the .NET Foundation needs a better definition of the benefits which Seed Level projects receive 35 | - @tannergooding volunteered to create proposal on seed project benefits 36 | - Project Reconciliation - ensuring all .NET Foundation projects are in good standing and have required legal paperwork 37 | - @ChrisSfanos provided update on project reconciliation process 38 | - Health Metric Tracking - Project Committee needs an automated system for harvesting daily health metrics for projects 39 | - @sbalker provided demo of application for tracking daily health metrics 40 | - application will be deployed publicly 41 | 42 | 3. Open Source Project Licensing 43 | 44 | - @eriawan led discussion on open source project licensing 45 | - proposal that .NET Foundation projects must be licensed under an approved permissive license and not licensed under multiple open source licenses 46 | - @sbwalker suggestion to use OSI as the trusted source of licenses and focus on the permissive licenses 47 | - @tannergooding suggestion to define our own set of approved licenses and also indicate that licenses which are not part of the list will be reviewed on a case by case basis 48 | - @eriawan volunteered to create list of approved licenses 49 | 50 | 4. Q&A 51 | 52 | - @clairernovotny indicated that she does not expect any changes to the Project Committee post election, but would ensure @sbwalker is able to introduce the work of the Project Committee to the new Board 53 | 54 | Meeting adjourned after 1 hour. -------------------------------------------------------------------------------- /meetings/2020-08-13.md: -------------------------------------------------------------------------------- 1 | Project Committee Meeting - August 13, 2020, 12:00 PM ET 2 | 3 | ATTENDEES: Eriawan Kusumawardhono (@eriawan), Jeremy Sinclair (@snickler), Tanner Gooding (@tannergooding), Chris Sfanos (@ChrisSfanos), Claire Novotny (@clairernovotny), Chris Hammond (@ChrisHammond) 4 | 5 | ABSENT: Scott Willhite (@mrswoop), Juan Elosegui (@jmelosegui) 6 | 7 | STAFF OBSERVERS: Terracia King (@terraciaking) 8 | 9 | AGENDA 10 | 11 | 1. MONTHLY PROGRESS UPDATE 12 | 13 | - Verify - Board of Directors agreed to accept the Projects Committee’s recommendation and approve Verify application 14 | - Polyjuice & SecureDNS - feedback sent to project maintainers regarding license and health metric maturity. Both projects were promoted to the Seed Level. 15 | - ImageSharp - @sbwalker created a draft for the ImageSharp collaboration blog. 16 | - ImageSharp’s owner decided not to move forward with the blog post at this time. 17 | - @sbwalker will follow up. 18 | - Board Elections - updated Project Committee members on .NET Foundation election results. 19 | - New Board members announced. 20 | - Six new Board members and one returning Board member. 21 | - @sbwalker action item to present a Projects Committee overview at the next Board meeting. 22 | 23 | 2. REVIEW NEW PROJECT APPLICATIONS 24 | 25 | - Nanoframework - reviewed health metrics and eligibility criteria. 26 | - Health metrics indicate this project is mature. 27 | - Further research indicated this project includes a very expansive set of subprojects. 28 | - License check indicated that they use different permissive licenses across their projects. 29 | - Project Committee agreed to recommend Nanoframework to the Board for membership. 30 | - nopCommerce - reviewed health metrics and eligibility criteria. 31 | - Health metrics indicate this project is very mature. 32 | - Licensing check indicated that they are licensed under a custom copyleft license that does not fit the criteria. 33 | - Project Committee will present the project to the Board but will not recommend the project for membership. 34 | 35 | 3. PROJECT 36 | 37 | - Project/Seed Benefits Proposal Discussion 38 | - Claire mentioned .NET Foundation now has GitHub Enterprise subscription that projects owners will be asked to join as a benefit. 39 | - @tannergooding provided an update on the list of project benefits started in GitHub. 40 | - suggested that the Foundation could provide "best practices" documentation for early stage projects on how to create a new project. 41 | - The documentation could be a GitHub template that project owners can refer too. 42 | - @tannergooding action item to upload the project benefits to the PR discussion board to allow members to review and add suggestions. 43 | - @tannergooding action item to partner with @clairenovotny to crosslink the discussion post to the Announcement repository. 44 | - DNF Projects Site 45 | - @sbwalker provided an update on the application for daily tracking of health metrics 46 | - https://dnfprojects.azurewebsites.net/net-foundation-projects 47 | - The application can provide metrics such as the compare the projects with the highest growth, monitor a project’s activity, and which projects have the most pull request. 48 | - @sbwalker action item to sync with @clairenovotny to review the Azure credits available for hosting the application within the Foundation. 49 | - Project Reconciliation 50 | - @snickler action item to send any old projects or unusual instances to @clairenovotny and @ChrisSfanos to clean up. 51 | - @clairenovotny is currently working with a lawyer to formally define what it means to be a .NET Foundation project from a legal perspective. 52 | - Open Source Licensing Discussion Continuation 53 | - @eriawan led the open source project licensing discussion. 54 | - @eriawan posted a write up on licenses that should be accepted by the Foundation. 55 | - @eriawan action item will upload the licensing write up as a PR on the Projects’ site to solicit feedback. 56 | - Discussion held about the current licensing criteria and whether there is value in accepting projects outside of that criteria. 57 | 58 | 4. Q&A 59 | 60 | The meeting adjourned at 1:00 pm ET -------------------------------------------------------------------------------- /meetings/2020-09-10.md: -------------------------------------------------------------------------------- 1 | Project Committee Meeting - September 10, 2020, 12:00 PM ET 2 | 3 | ATTENDEES: Eriawan Kusumawardhono (@eriawan), Tanner Gooding (@tannergooding), Chris Sfanos (@ChrisSfanos), Juan Elosegui (@jmelosegui), Shaun Walker (@sbwalker), Chris Hammond (@ChrisHammond), 4 | 5 | BOARD MEMBER: Jeff Strauss (@jstrauss) 6 | 7 | ABSENT: Scott Willhite (@mrswoop),), Jeremy Sinclair (@snickler), Claire Novotny (@clairernovotny), 8 | 9 | STAFF OBSERVERS: Terracia King (@terraciaking) 10 | 11 | AGENDA 12 | 13 | 1. MONTHLY PROGRESS UPDATE 14 | 15 | - Nanoframework 16 | - The Board of Directors agreed to accept the Project Committee’s recommendation and approve Nanoframework’ s application last month. 17 | - nopCommerence 18 | - @sbwalker sent feedback to the project’s maintainer to explain that due to non-permissive licensing, the Foundation will currently not be able to approve the project’s application. The application has been closed. 19 | 20 | 2. REVIEW NEW PROJECT APPLICATIONS 21 | 22 | - Esquio 23 | - reviewed activity metrics and eligibility criteria 24 | - activity metrics indicate this project is fairly mature ( active, multiple contributors ) 25 | - licensing check indicated that they are licensed under Apache 2 which is permissive. 26 | - recommendation: Project Committee agreed to recommend Esquio to the Board for membership. 27 | - Xamarian Community Toolkit 28 | - reviewed activity metrics and eligibility criteria 29 | - activity metrics indicate this project is mature ( started in 2016, active, commit count is low compared to other projects ) 30 | - licensing check indicated that they are licensed under MIT which is permissive. 31 | - recommendation: Project Committee agreed to recommend Xamarian Community Toolkit to the Board for membership 32 | - DataGrid Extensions 33 | - reviewed activity metrics and eligibility criteria 34 | - activity metrics indicate this project is mature however 1 contributor has done 99% of the commits 35 | - licensing check indicated that they are licensed under MIT which is permissive. 36 | - @sbwalker stated that the Project Committee can recommend the project for approcal but also reach out to the maintainer and encourage them to try to solicit more contributors 37 | - recommendation: Project Committee agreed to recommend Datagrid Extensions to the Board for membership 38 | - C# standardization: ECMA TC49 – TG2 39 | - not an Open Source project currently 40 | - is work being done as a Standards Committee as part of ECMA and is primarily comprised of documentation 41 | - the Standards Committee would like the project to become an official member then go through the motions of making it an Open Source project. 42 | - the standard is already public, but they would like to make the communication and work to made public in the next phase. 43 | - @tannergooding recommended that the Project Committee reach out to the C# Standardization project maintainer to ask how they plan on coordinating with C# Language prior to sending them for Board approval. 44 | - recommendation: The Projects Committee will defer the decision for recommendation to next month to gather more information. 45 | - action item: Projects Committee to ask C# Standardization’s project maintainer how they plan to coordinate with C# Language Team. 46 | - action item: @sbwalker to present the Projects Committee’s recommendations and the deferred project to the Board at the September 17th, 2020 Board Meeting. 47 | 48 | 3. PROJECT 49 | 50 | - SixLabors/ImageSharp 51 | - @sbwalker followed up with the project maintainer of ImageSharp to determine next steps and has not received a response. This item remains open. 52 | - DNF Projects Site – Projects Trends 53 | - URL: https://dnfprojects.azurewebsites.net/net-foundation-projects 54 | - @sbwalker provided an update on the application for daily tracking of activity metrics. 55 | - @sbwalker outlined the feedback received on Twitter and adjustments made to the application 56 | - Projects Committee Charter 57 | - the Projects Committee adjusted the charter to replace the word "health" with "activity" ( the Committee has never evaluated project "health" - only public metrics on Github ) 58 | - Nuget Package Ranking Discussion 59 | - Project Committee met previously with Jon Douglas from Nuget about a new proposed package ranking system 60 | - Nuget wants to create an algorithm to consider the popularity, recent activity, and quality of packages 61 | - Projects Committee was asked to provide feedback and continue collaboration on this topic 62 | - Project Benefits 63 | - @tannergooding provided an update on the list of project benefits started in GitHub. 64 | - action item: @tannergooding to meet with @clairenovotny to understand how to open this discussion to the broader community 65 | - Open Source Licensing 66 | - @Eriawan led the discussion on Open Source licensing. 67 | - @Eriawan had created a proposal for suggested permissive licensing to present to the Board. 68 | - @jstrauss suggested that the Projects Committee create a list of licenses that are not accepted. 69 | 70 | 4. Q&A 71 | 72 | The meeting adjourned at 1:03 pm ET -------------------------------------------------------------------------------- /meetings/2020-10-08.md: -------------------------------------------------------------------------------- 1 | Project Committee Meeting - October 8, 2020, 12:00 PM ET 2 | 3 | ATTENDEES: Eriawan Kusumawardhono (@eriawan), Chris Sfanos (@ChrisSfanos), Juan Elosegui (@jmelosegui), Shaun Walker (@sbwalker), Chris Hammond (@ChrisHammond), Scott Willhite (@mrswoop), Jeremy Sinclair (@snickler) 4 | 5 | ABSENT: Claire Novotny (@clairernovotny), Tanner Gooding (@tannergooding), Jeff Strauss (@jstrauss) 6 | 7 | STAFF OBSERVERS: Terracia King (@terraciaking) 8 | 9 | AGENDA 10 | 11 | 1. MONTHLY PROGRESS UPDATE 12 | 13 | - Esquio, Xamarin Community Toolkit, DataGrid 14 | - The Board of Directors agreed to accept the Project Committee’s recommendation and approve these applications from last month. 15 | - C# standardization: ECMA TC49-TG2 16 | - @sbwalker led a discussion regarding the Committee’s meeting with Bill Wagner to gain more insight on the C# Standardization project. 17 | 18 | 2. REVIEW NEW PROJECT APPLICATIONS 19 | 20 | - C# standardization: ECMA TC49 – TG2 21 | - based on results of meeting with Bill Wager Project Committee agreed to recommend C# standardization: ECMA TC49 – TG2 to the Board for membership. 22 | - Stride 23 | - reviewed activity metrics and eligibility criteria 24 | - activity metrics indicate this project is mature and has an active community 25 | - licensing check indicates that they are licensed under MIT. 26 | - @jmelosegui raised a question regarding Stride’s previous ownership and how much research is required to ensure code provenance 27 | - @sbwalker action item to discuss with @clairernovotny the verification steps required for Project Contribution Agreements. 28 | - recommendation: Project Committee agreed to recommend Stride to the Board for membership 29 | - CAP 30 | - it was noted that this project is using the "dotnetcore" organization on Github which may be a trademark violation issue 31 | - recommendation: defer application review until Project Committee can meet with @clairernovotny for further discussion 32 | 33 | 3. PROJECT 34 | 35 | - IdentityServer 36 | - @sbwalker led a discussion regarding the IdentityServer project and their recent decision to commercialize the open source project. 37 | - @mrswoop stated that the Foundation should identify the ideal outcome for projects such as IdentityServer. 38 | - @snickler led a discussion regarding the content on IdentityServer’s product webpage. 39 | - @Eriawan suggested the .NET Foundation needs to create guidelines to explain a standard process for these types of scenarios in the future. 40 | - @sbwalker action to schedule a follow up meeting for the Project Committee with @clairernovotny to gain more insight. 41 | - @sbwalker and @clairernovotny to meet with maintainers of IdentityServer 42 | 43 | 4. Q&A 44 | 45 | - @snickler led a discussion around the recent updates to the Projects webpage on the .NET Foundation site. 46 | 47 | The meeting adjourned at 1:00 pm ET -------------------------------------------------------------------------------- /meetings/2020-11-12.md: -------------------------------------------------------------------------------- 1 | Project Committee Meeting - November 12, 2020, 12:00 PM ET 2 | 3 | ATTENDEES: Chris Sfanos (@ChrisSfanos), Juan Elosegui (@jmelosegui), Shaun Walker (@sbwalker), Chris Hammond (@ChrisHammond), Jeremy Sinclair (@snickler), Tanner Gooding (@tannergooding), Ken Cutt (@kencutt), John Callaway (@ovation22) 4 | 5 | ABSENT: Claire Novotny (@clairernovotny), Eriawan Kusumawardhono (@eriawan), Scott Willhite (@mrswoop) 6 | 7 | STAFF OBSERVERS: Terracia King (@terraciaking) 8 | 9 | AGENDA 10 | 11 | 1. MONTHLY PROGRESS UPDATE 12 | 13 | - C# Standardization, Stride 14 | - The Board of Directors agreed to accept the Project Committee’s recommendation and approve these applications from last month. 15 | 16 | 2. REVIEW NEW PROJECT APPLICATIONS 17 | 18 | - HttpReports 19 | - it was noted that this project is using the "dotnetcore" organization on Github which may be a trademark violation issue ( similar to the earlier CAP applications ) 20 | - active community - mostly in China, documentation is mostly in Chinese, contributions primarily from 1 person 21 | - need clarification from Board of Directors on how to proceed 22 | - Our World & The Oasis 23 | - licensed under GNU license which is not compatible with .NET Foundation charter 24 | - community is not large or active - however application is very substantial effort 25 | - Silk.NET 26 | - activity metrics indicate maturity, license is permissive 27 | - recommendation: Project Committee agreed to recommend Stride to the Board for membership 28 | - Ant Design Blazor 29 | - activity metrics indicate maturity, license is permissive 30 | - recommendation: Project Committee agreed to recommend Stride to the Board for membership 31 | - Finbuckle.MultiTenant 32 | - activity metrics indicate maturity, license is permissive 33 | - recommendation: Project Committee agreed to recommend Stride to the Board for membership 34 | 35 | 3. PROJECT 36 | - Project Recommendations 37 | - @jmelosegui held a discussion around how the Projects Committee could provide feedback to project contributors to indicate areas where they could improve the maturity of their projects 38 | - @jmelosegui action item to create a template for the Project Committee to use when providing feedback with project maintainers on the status of their projects. 39 | - IdentityServer 40 | - @sbwalker and @clairernovotny met with the maintainers of IdentityServer and @sbwalker has exchanged emails sharing his experience in commercializing an open source project 41 | - IdentityServer has committed to supporting the current version of the project for 2 more years 42 | - a new company has been formed named Duende which will offer a commercial version 43 | - .NET 6 Ecosystem Collaboration 44 | - Immo Landwerth from Microsoft reached out to the Project Committee to collaborate on an initiative to Grow the .NET ecosystem through increased Quality, Confidence, and Support. 45 | - the Project Committee had an initial kickoff meeting to understand the context of the request and plan the logistics 46 | - DNN 47 | - @sbwalker and Mitchel Sellers received clarification on trademark matters related to the .NET Foundation contribution agreement 48 | - HaveIBeenPwned (HIBP) 49 | - @kencutt and @ovation22 will facilitate an in-depth discussion with Troy Hunt to come up with a proposal for contributing HIBP to the .NET Foundation 50 | 51 | The meeting adjourned at 1:00 pm ET -------------------------------------------------------------------------------- /meetings/2020-12-10.md: -------------------------------------------------------------------------------- 1 | Project Committee Meeting - December 10, 2020, 12:00 PM ET 2 | 3 | ATTENDEES: Chris Sfanos (@ChrisSfanos), Juan Elosegui (@jmelosegui), Shaun Walker (@sbwalker), Chris Hammond (@ChrisHammond), Jeremy Sinclair (@snickler), Tanner Gooding (@tannergooding), Ken Cutt (@kencutt), Claire Novotny (@clairernovotny), Eriawan Kusumawardhono (@eriawan) 4 | 5 | ABSENT: Jeff Strauss (@jstrauss), Scott Willhite (@mrswoop), John Callaway (@ovation22) 6 | 7 | STAFF OBSERVERS: Terracia King (@terraciaking) 8 | 9 | AGENDA 10 | 11 | 1. MONTHLY PROGRESS UPDATE 12 | 13 | Board of Directors agreed to accept the Projects Committee’s recommendation and approve the following applications last month: 14 | 15 | - Silk.NET 16 | - Ant Design Blazor 17 | - Finbuckle.MultiTenant 18 | 19 | 2. REVIEW NEW PROJECT APPLICATIONS 20 | 21 | - Case Management - https://github.com/simpleidserver/CaseManagement 22 | - relatively new project without a lot of activity 23 | - licensing is permissive 24 | - recommendation: do not recommend for approval, evaluate if suitable for Seed level 25 | - FastTunnel - https://github.com/SpringHgui/FastTunnel 26 | - relatively new project without a lot of activity 27 | - licensing is permissive 28 | - recommendation: do not recommend for approval, evaluate if suitable for Seed level 29 | - Tom’s Toolbox - https://github.com/tom-englert/TomsToolbox 30 | - relatively new project without a lot of activity 31 | - licensing is permissive 32 | - recommendation: do not recommend for approval, evaluate if suitable for Seed level 33 | - NanUI for WinForms - https://github.com/NetDimension/NanUI 34 | - project is mature however does not have much recent activity 35 | - license is permissive but was recently changed from a non-permissive license 36 | - recommendation: do not recommend for approval, evaluate if suitable for Seed level and inquire about license change 37 | 38 | 3. PROJECT 39 | - Project Activity Tracker 40 | - Url: https://dnfprojects.azurewebsites.net/net-foundation-projects 41 | - Committee reviewed activity trends for .NET Foundation projects for the past 6 months 42 | - it was noted that there a large number of .NET Foundation which are inactive 43 | - @clairenovotny asked the Committee if there should be requirements for ongoing activity to stay in the Foundation? 44 | - Press Release Plan 45 | - @sbwalker noted that the New Project Application form asks for submitters to provide a PR Plan and asked if this information is used anywhere 46 | - @clairenovotny indicated that it is not being used currently 47 | - @sbwalker asked if it should be shared with the Marketing Committee 48 | - @tannergooding suggested that the information could be optional 49 | - @snickler suggested that the Committee create a form that would allow the project maintainers to check the types of press that would like for their project (ex. Twitter) 50 | - Trademark Usage 51 | - there is an organization from China on GitHub using "dotnetcore" as its name 52 | - @clairenovotny has reached out to them to determine if they may be able to change their name 53 | - communication is challenging due to language barriers 54 | - some project applications are on hold until this is resolved 55 | - HIBP 56 | - @kencutt provided a status update for the HaveIBeenPwned opportunity. 57 | - @kencutt and @ovation22 have held multiple meetings with Troy Hunt. 58 | - Troy Hunt shared his code with @kencutt and @ovation22 a few days ago. 59 | - They are putting together a game plan to help Troy. 60 | - .NET6 Ecosystem Growth Working Group Next Steps 61 | - @sbwalker held a discussion around the .NET6 Ecosystem Growth working group. 62 | - There will be a meeting held every Thursday from 4:00pm – 6:00pm Eastern time. 63 | - The working group will meet over the next three months. 64 | - @snickler and @eriawan action items to send @sbwalker contacts that would like to join the working group. 65 | - Q&A 66 | - @sbwalker asked @clairenovotny if the Board has any expectations or goals for the Projects Committee in 2021. 67 | - @clairenovotny suggested @sbwalker to ask the question to the Board at the December Board meeting. 68 | - There was a brief discussion held on the new GitHub Sponsor capabilities. 69 | 70 | The meeting adjourned at 1:00 pm ET -------------------------------------------------------------------------------- /meetings/2021-01-14.md: -------------------------------------------------------------------------------- 1 | Project Committee Meeting - January 14, 2021, 12:00 PM ET 2 | 3 | ATTENDEES: Chris Sfanos (@ChrisSfanos), Juan Elosegui (@jmelosegui), Shaun Walker (@sbwalker), Jeremy Sinclair (@snickler), Ken Cutt (@kencutt), Claire Novotny (@clairernovotny), John Callaway (@ovation22), Scott Willhite (@mrswoop), 4 | 5 | ABSENT: Jeff Strauss (@jstrauss), Chris Hammond (@ChrisHammond), Tanner Gooding (@tannergooding), Eriawan Kusumawardhono (@eriawan), 6 | 7 | STAFF OBSERVERS: Terracia King (@terraciaking) 8 | 9 | AGENDA 10 | 11 | 1. MONTHLY PROGRESS UPDATE 12 | 13 | - .NET6 Ecosystem Growth working group 14 | - @sbwalker provided context 15 | - The group had its first meeting last week. 16 | - There will be a meeting held every Thursday from 4-6 PM ET for the next 3 months 17 | 18 | 2. REVIEW NEW PROJECT APPLICATIONS 19 | 20 | - There were no new project applications to review this month. 21 | 22 | 3. PROJECT COMMITTEE DISCUSSION 23 | 24 | - Haveibeenpwned (HIBP) 25 | - @kencutt provided a status update for the Haveibeenpwned opportunity 26 | - @kencutt action item to follow up with the Troy Hunt to continue discussing the HIBP project. 27 | 28 | - Press Release Plan Discussion (from project applications) 29 | - @sbwalker led a brief discussion on the Press Release Plan mentioned on the Project Application form. 30 | 31 | - Q&A 32 | - @clairenovotny shared that the Executive Committee will be asking for the Projects Committee’s goals in 2021 33 | - @jmelosegui suggested that the Project Committee create a method to review project activity and determine criteria that the projects must maintain to be a part of the .NET Foundation. 34 | - @sbwalker suggested that the Project Committee focuses on policy and procedures 35 | - @snickler suggested that the Committee pull items from the .NET Ecosystem Growth meetings to focus on, such as documentation. 36 | - The Committee agreed to work asynchronously to determine the three goals they would like to pursue in 2021. 37 | 38 | The meeting adjourned at 12:26 PM ET 39 | -------------------------------------------------------------------------------- /meetings/2021-02-11.md: -------------------------------------------------------------------------------- 1 | Project Committee Meeting - February 11, 2021, 12:00 PM ET 2 | 3 | ATTENDEES: Chris Sfanos (@ChrisSfanos), Shaun Walker (@sbwalker), Jeremy Sinclair (@snickler), Ken Cutt (@kencutt), John Callaway (@ovation22), Tanner Gooding (@tannergooding), Eriawan Kusumawardhono (@eriawan), 4 | 5 | ABSENT: Jeff Strauss (@jstrauss), Chris Hammond (@ChrisHammond), Scott Willhite (@mrswoop), Claire Novotny (@clairernovotny), Juan Elosegui (@jmelosegui), 6 | 7 | STAFF OBSERVERS: Terracia King (@terraciaking) 8 | 9 | AGENDA 10 | 11 | 1. MONTHLY PROGRESS UPDATE 12 | 13 | - There were no new projects approved last month. Therefore, there was no need to seek any approvals from the Board. 14 | - Project Contribution Model 15 | - A meeting occurred with the .NET Foundation’s lawyer to obtain clarification on the Project Contribution model 16 | - the discussion was focused on the .NET Foundation's legal limitations in terms of being able to provide full support for projects which are not contributed via assigment 17 | - @sbwalker argued that the .NET Foundation has traditionally been an inclusive organization and needs to retain its current “open” policy in regards to project contribution models. This open policy allows the .NET Foundation to accommodate the vast diversity in open source projects in the .NET ecosystem including those which want to pursue commercial models as well as projects which have grown organically and do not have full code provenance of their contributions. 18 | - it was decided that the .NET Foundation should continue to support multiple types of project contributions - both in the form of assignments and licenses 19 | - a new Project Contribution agreement will be created by the lawyer which better defines the details of each approach 20 | - Project onboarding will remain on hold until the new agreement is available 21 | - @tannergooding asked if there will be any impact on projects that entered the .NET Foundation using the current contribution agreement 22 | - @ChrisSfanos indicated this is an open question which needs to be clarified by the lawyer 23 | - @tannergooding suggested that it would be optimal if we could provide project leaders with all of the relevant information they need to know from day one to meet the .NET Foundation’s requirements 24 | - @ChrisSfanos will schedule another meeting with the .NET Foundation lawyer 25 | - .NET6 Ecosystem Growth Working group meetings. 26 | - Continue to occur on a weekly basis 27 | 28 | 2. REVIEW NEW PROJECT APPLICATIONS 29 | 30 | - Venflow 31 | - Activity metrics indicate this project is relatively new. 32 | - licensing is permissive 33 | - recommendation: do not recommend for approval, evaluate if suitable for Seed 34 | - OpenSleigh 35 | - Activity metrics indicate this project is relatively new. 36 | - licensing is permissive 37 | - recommendation: do not recommend for approval, evaluate if suitable for Seed 38 | - OpenMod 39 | - activity metrics indicate this project is fairly well established 40 | - license is permissive, but not standard and has a non-standard jurisdiction issue 41 | - recommendation: do not recommend for approval, follow up with contributor about licensing 42 | - HIBP 43 | - @ovation22 provided a status update for the HIBP project 44 | - open source project is not yet released to the public 45 | - project is well known and respected within the industry. 46 | - good project for the .NET Foundation to be affiliated with. 47 | - maintainer is looking for guidance as it is his first time venturing into open source 48 | - Project Committee will recommend the HIBP project to the Board for approval 49 | 50 | 3. PROJECT 51 | 52 | - Project Committee Discussion 53 | - @sbwalker held a discussion on the Projects Committee 2021 goals. 54 | - @tannergooding suggested that the Projects Committee strive to provide clear and public guidance as to what we are looking for in a project ie. how to setup a project in the right way. 55 | - @sbwalker suggested that the Projects Committee revise the Charter to reflect the latest understanding and criteria 56 | - @snickler suggested that the Committee should review the activities of existing projects regularly. 57 | - @sbwalker mentioned providing the project maintainers guidance as to how to remain a member. 58 | - @snickler suggested the Committe should provide guidelines for how projects can exit the .NET Foundation. 59 | - @snickler asked if there was a threshold or a maximum number of members for the Projects Committee. @sbwalker said there is no limit - it can add as many as necessary as long as appropriate leadership and guidance is being provided and members are contributing value 60 | - @tannergooding suggestd setting up a communication tool that is dedicated to the Project Committee to chat adhoc 61 | - .NET6 Ecosystem Growth working group meetings. 62 | - @sbwalker provided status on the .NET6 Ecosystem Growth working group meetings. 63 | - progress has been limited as the goals are not clear 64 | - @tannergooding suggested that another communication tool may be helpful for collaborating in a less formal fashion. 65 | - .Q&A 66 | - @ChrisSfanos action item to send the projects that have been on hold an email to inform them of what is going on. 67 | - @snickler held a discussion on monetizing open source and its concerns. 68 | 69 | The meeting adjourned at 1:02 PM ET. 70 | -------------------------------------------------------------------------------- /meetings/2021-03-11.md: -------------------------------------------------------------------------------- 1 | Project Committee Meeting - March 11, 2021, 12:00 PM ET 2 | 3 | ATTENDEES: Chris Sfanos (@ChrisSfanos), Shaun Walker (@sbwalker), Jeremy Sinclair (@snickler), John Callaway (@ovation22), Eriawan Kusumawardhono (@eriawan), Scott Willhite (@mrswoop) 4 | 5 | ABSENT: Jeff Strauss (@jstrauss), Chris Hammond (@ChrisHammond), Claire Novotny (@clairernovotny), Juan Elosegui (@jmelosegui), Tanner Gooding (@tannergooding), Ken Cutt (@kencutt) 6 | 7 | STAFF OBSERVERS: Terracia King (@terraciaking) 8 | 9 | AGENDA 10 | 11 | 1. MONTHLY PROGRESS UPDATE 12 | 13 | - HIBP was recommended to the Board for approval prior to public release 14 | - Board did not endorse the recommendation at this time 15 | - Board requested to review HIBP’s private repository to review the state of the code 16 | - Troy Hunt will open HIBP’s private repository for the Board to review. 17 | - @sbwalker and @ovation22 met with Beth Massi to discuss Marketing and PR opportunities to promote the HIBP project. 18 | - Beth Massi suggested possible announcing the HIBP project in May 19 | - Project Contribution Models 20 | - @ChrisSfanos commented that the Project Contribution models are still unresolved 21 | - project onboarding resumed using legacy agreements and approach for the time being 22 | - .NET6 Ecosystem Growth working group meetings are cancelled until April 1st whe survey results will be ready 23 | 24 | 2. REVIEW NEW PROJECT APPLICATIONS 25 | 26 | - .NEXT (https://github.com/sakno/dotNext) 27 | - activity metrics indicate this project is very mature and robust 28 | - @eriawan mentioned project is very popular in Indonesia 29 | - project has extensive documentation 30 | - licensing check indicates that the project meets the required criteria 31 | - Project Committee will recommend the .NEXT project to the Board for approval 32 | - ReactJS Template (https://github.com/Rubix982/ASP.NET-ReactJS-Template/) 33 | - activity metrics indicate this project is very new and not very active 34 | - very few contributors 35 | - licensing check indicates that the project meets the required criteria 36 | - Project Committee will not recommend project to the Board for approval at this time 37 | - project may qualifyas a Seed project at this time 38 | - @sbwalker action item to provide feedback to the project maintainer regarding the Committee's decision 39 | 40 | 3. PROJECT 41 | 42 | - .NET6 Ecosystem Growth working group meetings 43 | - @sbwalker provided an update on the .NET6 Ecosystem Growth working group meetings 44 | - @sbwalker shared a presentation on Open Sustainability 45 | - https://github.com/dotnet-foundation/ecosystem-growth/blob/main/docs/oss-sustainability.pptx​ 46 | - @eriawan created a presentation on how to make contributions more meaningful and fair 47 | - https://github.com/dotnet-foundation/ecosystem-growth/blob/main/docs/proposed-how-to-reward-contributors.pptx​ 48 | - @tannergooding and @snickler working on presentation for Best Practices For Starting An Open Source Project​ 49 | - General 50 | - Information has been shared with James Randall to clarify his recent blog about the .NET Foundation 51 | - https://twitter.com/sbwalker/status/1370451712859893760 ​ 52 | 53 | The meeting adjourned at 12:53 PM ET. 54 | -------------------------------------------------------------------------------- /meetings/2021-04-08.md: -------------------------------------------------------------------------------- 1 | Project Committee Meeting - April 8, 2021, 11:30 AM ET 2 | 3 | ATTENDEES: Chris Sfanos (@ChrisSfanos), Juan Elosegui (@jmelosegui), Shaun Walker (@sbwalker), Chris Hammond (@ChrisHammond), Jeremy Sinclair (@snickler), Tanner Gooding (@tannergooding), Ken Cutt (@kencutt), John Callaway (@ovation22) 4 | 5 | ABSENT: Jeff Strauss (@jstrauss), Scott Willhite (@mrswoop), Claire Novotny (@clairernovotny), Eriawan Kusumawardhono (@eriawan) 6 | 7 | STAFF OBSERVERS: Terracia King (@terraciaking) 8 | 9 | AGENDA 10 | 11 | 1. MONTHLY PROGRESS UPDATE 12 | 13 | - HIBP Progress 14 | - @sbwalker held a discussion regarding the Board’s feedback on the HIBP 15 | - Board has not yet confirmed that they have viewed the private repository 16 | - Ongoing discussions with Beth Massi and Troy Hunt about creating a press release 17 | - .NET6 Ecosystem Growth 18 | - working group meeting resumed Apr 1 19 | - @sbwalker provided a .NET6 Ecosystem Growth working group update 20 | - meeting last week to discuss survey results related to how people were using the opensource within the .NET ecosystems. 21 | - John Douglas shared a presentation about Nuget package scoring benefits 22 | - goal is to collaborate with the community to discuss scoring methods 23 | 24 | 2. REVIEW NEW PROJECT APPLICATIONS 25 | 26 | - fido2-net-lib (https://github.com/abergs/fido2-net-lib) 27 | - activity metrics indicate this project is well established 28 | - four contributors are sponsoring the project. 29 | - decent amount of documentation. 30 | - licensing check indicates that the project meets the required criteria 31 | - Project Committee will recommend the project to the Board for approval 32 | 33 | 3. PROJECT 34 | 35 | - HIBP 36 | - @ovation22 gave an HIBP status update 37 | - @ovation22 action item to contact Troy Hunt to request access to the HIBP private repository for additional Projects Committee members 38 | - discussion around HIBP's new features 39 | - @snickler, @tannergooding, and @ovation22 action item to schedule a meeting to review HIBP 40 | - @snickler and @ovation22 action item to schedule a meeting with Troy Hunt to make recommendations on next steps for HIBP 41 | - @sbwalker action item to recommend the HIBP to the Board for approval 42 | 43 | The meeting adjourned at 12:15 PM ET. 44 | -------------------------------------------------------------------------------- /meetings/2021-05-13.md: -------------------------------------------------------------------------------- 1 | Project Committee Meeting - May 13, 2021, 12:00 PM ET 2 | 3 | ATTENDEES: Shaun Walker (@sbwalker), Jeremy Sinclair (@snickler), John Callaway (@ovation22), Tanner Gooding (@tannergooding), Eriawan Kusumawardhono (@eriawan), Jeff Strauss (@jstrauss), Claire Novotny (@clairernovotny), Juan Elosegui (@jmelosegui) 4 | 5 | ABSENT: Chris Hammond (@ChrisHammond), Scott Willhite (@mrswoop), Chris Sfanos (@ChrisSfanos), Ken Cutt (@kencutt) 6 | 7 | STAFF OBSERVERS: Terracia King (@terraciaking) 8 | 9 | AGENDA 10 | 11 | 1. MONTHLY PROGRESS UPDATE 12 | 13 | - nothing to report 14 | 15 | 2. REVIEW NEW PROJECT APPLICATIONS 16 | 17 | - bUnit (https://github.com/bUnit-dev/bUnit) 18 | - activity metrics indicate this project is mature 19 | - has a lot of momentum 20 | - licensing check indicates that the project meets the required criteria 21 | - Project Committee will recommend the bUnit project to the Board for approval 22 | - Ooki Dialogs (https://github.com/ookii-dialogs) 23 | - activity metrics indicate this project is mature 24 | - not very active project 25 | - has only two active maintainers 26 | - has multiple sub-repositories with multiple versions 27 | - licensing check indicates that the project meets the required criteria 28 | - qualifies as Seed project at this time 29 | - Project Committee will not recommend the Ooki Dialogs project to the Board for approval 30 | - Npgsql (https://github.com/npgsql/npgsql ) 31 | - activity metrics indicate this project is relatively mature 32 | - Project Committee will not recommend the Npgsql project to the Board for approval 33 | - @sbwalker action item to provide feedback to the project maintainer regarding their licensing issue. 34 | - @sbwalker action item to solicit feedback from .NET Foundation legal counsel on status of Npgsql license 35 | - AspNet Boilerplate (https://github.com/aspnetboilerplate/aspnetboilerplate ) 36 | - activity metrics indicate this project is mature 37 | - has permissive license 38 | - here are other commetcial versions of this project 39 | - the project is very active 40 | - licensing check indicates that the project meets the required criteria 41 | - Project Committee will recommend the AspNet Boilerplate project to the Board for approval 42 | - ASP.NET API Versioning (https://github.com/microsoft/aspnet-api-versioning) 43 | - activity metrics indicate this project is mature 44 | - licensing check indicates that the project meets the required criteria 45 | - the project is popular 46 | - specifically for rest APIs 47 | - the Project Committee suggested moving the project out of the Microsoft Github organization 48 | - @sbwalker action item to ask project maintainer if their intent is to move the project out of the Microsoft organization. 49 | - Project Committee will recommend the ASP.NET API Versioning project to the Board for approval 50 | 51 | - Reviewed Seed Projects 52 | - Texnomic SecureDNS Project, Polyjuice, Trivial, NUKE, Case Management, FastTunnel, Tom's Toolbox, NanUI 53 | - based on current activity, Project Committee does not believe any projects are candidates to become Members at this time 54 | 55 | 3. PROJECT 56 | 57 | - HIBP 58 | - @ovation22 gave an HIBP status update 59 | - @ovation22 action item to contact Troy Hunt to request access to the HIBP private repository for additional Projects Committee members 60 | - discussion around HIBP's new features 61 | - @snickler, @tannergooding, and @ovation22 action item to schedule a meeting to review HIBP 62 | - @snickler and @ovation22 action item to schedule a meeting with Troy Hunt to make recommendations on next steps for HIBP 63 | - @sbwalker action item to recommend the HIBP to the Board for approval 64 | 65 | - HIBP Next Steps 66 | - @sbwalker shared an update that the Board of Directors voted to approve the HIBP project as a Member 67 | - @ovation22 gave an update on the HIBP project and discussions with its owner 68 | - @sbwalker to inform Troy Hunt of the project’s approval into the Foundation 69 | - @sbwalker action item to follow up with Claire Novotny on HIBP next steps 70 | - Project Contribution Agreement update 71 | - @sbwalker gave a brief update on the status of the Project Contribution Agreement 72 | - .NET6 Ecosystem Growth working group meetings 73 | - @sbwalker held a discussion on the .NET6 Ecosystem Growth working group meetings 74 | - There is a final meeting scheduled today 75 | 76 | The meeting adjourned at 12:56 PM ET. 77 | -------------------------------------------------------------------------------- /meetings/2021-06-10.md: -------------------------------------------------------------------------------- 1 | Project Committee Meeting - June 10, 2021, 12:00 PM ET 2 | 3 | ATTENDEES: Shaun Walker (@sbwalker), Jeremy Sinclair (@snickler), John Callaway (@ovation22), Eriawan Kusumawardhono (@eriawan), Juan Elosegui (@jmelosegui), Scott Willhite (@mrswoop), Ken Cutt (@kencutt) 4 | 5 | ABSENT: Chris Hammond (@ChrisHammond), Chris Sfanos (@ChrisSfanos), Jeff Strauss (@jstrauss), Claire Novotny (@clairernovotny), Tanner Gooding (@tannergooding) 6 | 7 | STAFF OBSERVERS: Terracia King (@terraciaking) 8 | 9 | AGENDA 10 | 11 | 1. MONTHLY PROGRESS UPDATE 12 | 13 | - HIBP project launched and created a big impact. 14 | - @ovation22 action item to contact the project maintainer to confirm that he would still like to transfer the servicing of the HIBP project to the Foundation. 15 | - the Board approved bUnit, AspNet oilerplate, and ASP.NET API Versioning projects 16 | - the Board requested that the Project Committee review the NUKE project again 17 | - activity metrics indicate this project is mature. 18 | - project has a lot of activity 19 | - similar to the CAKE project ( which is already a Foundation member ) 20 | - Licensing check indicated that the project met the required criteria. 21 | - the project maintainer from OpenMod inquired about the status of their project application 22 | - licensing check revealed that their license is not permissive. 23 | - the project maintainer stated that they would be willing to change the license to a permissive license. 24 | - @sbwalker will stay in touch with the project maintainer for updates. 25 | 26 | 2. REVIEW NEW PROJECT APPLICATIONS 27 | - Arad SMS Gateway 28 | - activity metrics indicate this project is very new. 29 | - very little activity 30 | - does not have many contributors. 31 | - licensing check indicated that the project does not meet the Foundation criteria. 32 | - Project Committee will not recommend the Arad SMS Gateway project to the Board for approval. 33 | - NUKE 34 | - The Project Committee reiterated their previous concerns that promoting alternative build systems can create challenges for .NET developers 35 | - The Board feedback was that we should encourage a variety of solutions within the Foundation and .NET ecosystem which solve similar problems. 36 | - @snickler stated that if NUKE is similar to the CAKE project, then there is nothing that should disqualify it as a member. 37 | - Project Committee will recommend the NUKE project to the Board for approval. 38 | 39 | 3. PROJECT 40 | 41 | - Project Committee Budget 42 | - @sbwalker held a discussion on the Projects Committee’s budget wish list. 43 | - The following budget wish list items were identified: 44 | - Provide Committee members with a @dotnetfoundation.org email address. 45 | - Offer site hosting to project maintainers 46 | - Offer Azure credits to Foundation projects. 47 | - Develop automatic processes around project onboarding and tracking. 48 | - Hold in-person events. 49 | - Host Hack-a-thons to help gain more exposure to the Foundation’s projects. 50 | - Offer prizes or giveaways for volunteers. 51 | - Have a booth at 1-2 conferences throughout the year. 52 | - Provide .NET Foundation’s swag as a welcome package for new project members 53 | 54 | The meeting adjourned at 12:56 PM ET. 55 | -------------------------------------------------------------------------------- /meetings/2021-07-08.md: -------------------------------------------------------------------------------- 1 | Project Committee Meeting - July 8, 2021, 12:00 PM ET 2 | 3 | ATTENDEES: Shaun Walker (@sbwalker), Jeremy Sinclair (@snickler), Eriawan Kusumawardhono (@eriawan), Juan Elosegui (@jmelosegui), Scott Willhite (@mrswoop), Ken Cutt (@kencutt), Tanner Gooding (@tannergooding), Shawn Vause (@napalm684) 4 | 5 | ABSENT: CChris Hammond (@ChrisHammond), Chris Sfanos (@ChrisSfanos), Jeff Strauss (@jstrauss), Claire Novotny (@clairernovotny) 6 | 7 | STAFF OBSERVERS: Terracia King (@terraciaking) 8 | 9 | AGENDA 10 | 11 | 1. MONTHLY PROGRESS UPDATE 12 | 13 | - Quiet momth 14 | - The Board approved the NUKE project 15 | 16 | 2. REVIEW NEW PROJECT APPLICATIONS 17 | - ObjectStore 18 | - activity metrics indicate this project is not mature 19 | - limited activity 20 | - licensing check indicated that the project does not have a permissive license. 21 | - Project Committee will not recommend ObjectStore to the Board for approval at this time. 22 | - Project Committee will follow up with project maintainer 23 | - BrightChain 24 | - activity metrics indicate the project is not mature 25 | - limited activity 26 | - licensing check revealed the license is not permissive. 27 | - project maintainer stated that they would be willing to change the license to a permissive license. 28 | - possible Seed Project if the license is changed. 29 | - Project Committee will not recommend BrightChain to the Board for approval at this time. 30 | - Project Committee will follow up with project maintainer 31 | - MQTTnet 32 | - activity metrics indicate this project is mature. 33 | - a lot of activity and adoption 34 | - Licensing check indicates the project meets the required criteria. 35 | - Project Committee will recommend the MQTTnet project to the Board for approval. 36 | - Arad Xmpp 37 | - activity metrics indicate the project is not mature 38 | - limited activity 39 | - Only one contributor 40 | - Licensing check indicates the project meets the required criteria. 41 | - Does not have a release. 42 | - Project Committee will not recommend the Arad Xmpp project to the Board for approval at this time. 43 | - OpenMod 44 | - Reviewed the OpenMod project last year and did not approve due to non-permissive licensing. 45 | - The project maintainers recently changed the license to MIT. 46 | - activity metrics indicate the project is mature 47 | - lots of activity 48 | - need to obtain legal guidance to determine risk factors of relicensing from EUPL to MIT 49 | 50 | 3. PROJECT 51 | 52 | - Code of Code Enforcement Plan 53 | - @sbwalker held a discussion on the .NET Foundation Code of Conduct Enforcement document. 54 | - @mrswoop action item to provide feedback to Claire Novotny on the Code of Conduct Enforcement document. 55 | 56 | The meeting adjourned at 12:52 PM ET. 57 | -------------------------------------------------------------------------------- /new-projects.md: -------------------------------------------------------------------------------- 1 | # New Project Onboarding 2 | Hello! We are excited you are interested in bringing your project over to the .NET Foundation family! To ensure the process is transparent and runs smoothly, we have put together a walk-through of the onboarding process to guide you. Once you start the application process, we will work with you throughout to complete the work. 3 | ## Your Project and the .NET Foundation 4 | Participation in the .NET Foundation exposes your project to the wider world of .NET developers and helps you to build a better community. The following details the three main steps you and your project will complete to join the .NET Foundation. 5 | 6 | The .NET Foundation has established a set of [eligibility criteria](https://github.com/dotnet-foundation/projects#eligibility-criteria) that your project must meet. Please review these and ensure your project meets all the specified criteria. 7 | 8 | When you are ready to apply to join, [fill out a new project application](https://github.com/dotnet-foundation/projects/issues/new?assignees=&labels=project+application&template=application.md&title=) 9 | 10 | ## Joining the .NET Foundation 11 | Joining the .NET Foundation involves submitting an application, review of the project by the .NET Foundation board, signing the Contribution License Agreement (CLA) once it’s been accepted and completing a set of post on-boarding steps. We will walk through them all in detail below so it’s an easy and straightforward process. 12 | 13 | **Step 1:** Project application and review by the .NET Foundation Board 14 | 15 | **Step 2:** Signing the CLA 16 | 17 | **Step 3:** Project Onboarding 18 | 19 | ## Project Application and Review by the .NET Foundation Board 20 | 21 | When you are ready to apply to join, [fill out a new project application](https://github.com/dotnet-foundation/projects/issues/new?assignees=&labels=project+application&template=application.md&title=) 22 | 23 | You can complete the application in GitHub directly, email us a copy of the document, or attach a copy of the document to the GitHub issue. To help with some of the common questions in the application or to provide clarification on certain items, we’ve included extra details to help you along. 24 | 25 | **Assignment Model.** Under the .NET Foundation assignment model, project ownership and other intellectual property is assigned to the .NET Foundation and the .NET Foundation agrees to grantback a license to the contributor(s). 26 | 27 | **Contribution Model.** Under the .NET Foundation contribution model, a project retains ownership of the copyright, but grants .NET Foundation a broad license to the project’s code and other intellectual property. The project also confirms that the project’s submissions to .NET Foundation are its own original work (there are also instructions for any third party materials that might be included). 28 | 29 | **Review Process.** Once you’ve submitted the issue, it will be reviewed by the Project Review committee and they will follow up with any questions on your application. After the review is complete and it’s ready to move forward, the .NET Foundation Board will review it. The Board meets monthly and reviews new projects sent over from the Project Review committee. After the board votes to approve a new project, signing the CLA is up next. 30 | 31 | ## Signing the CLA 32 | After the .NET Foundation board approves the project, it’s time to sign the CLA and move the project to the .NET Foundation. To setup and distribute the CLA, we will need a few pieces of information from you: 33 | 34 | * **Project Transfer Signatories:** This should be the top contributors, typically the top 2-5 developers who have contributed more than a few hundred lines of code. 35 | * We will need their email addresses, so we can send the CLA for signing (we currently use DocuSign). 36 | * **Project Trademarks - Licensed vs Disclaimed.** When signing the CLA you are asked to describe and choose how you want to handle any trademarks for the project. These include the project name, at a minimum, and potentially any logos or other recognizable, non-descriptive titles used within the project – these do not need to be formally registered trademarks. 37 | 38 | By default, the .NET Foundation selects **Licensed** in the CLA 39 | 40 | |Type|What it Means|Why you'd select it | 41 | -----|-------------|------------------- 42 | |Licensed|Project retains ownership of any trademarks and licenses the .NET Foundation to use them.|This follows the same ownership/license structure as the copyright in the project. The project keeps ownership in the trademarks and .NET Foundation only has the rights that are specifically granted in the license. The project still retains the rights to enforce its rights in the trademarks. | 43 | |Disclaimed|Project agrees not to enforce the trademark against the .NET Foundation or anyone else.|The project doesn’t claim any ownership rights to the trademarks and does not plan to control how .NET Foundation decides to use the trademarks. | 44 | 45 | Once we have the signatories identified, we will send out the CLA via DocuSign for everyone to complete. Once all parties have signed it and we’ve filed it away, we move forward with onboarding the project itself. 46 | 47 | ## Project Onboarding 48 | The last stage of joining the .NET Foundation involves a set of activities to bring your project in line with all .NET Foundation projects and help you join the broader .NET Foundation community. These items will all be tracked via the GitHub issue (that was created when you filled out your project application) and additional details are included in a detailed email you will receive. 49 | 50 | |Tasks|Background| 51 | |-----|----------| 52 | |Configure CLA bot| detailed description needed| 53 | |Mailing List|Join the project leader mailing list| 54 | |Slack channel|Joing the project leader slack channel| 55 | |License updates + copyright|Move your license to MIT (or continue to use Apache)| 56 | |Code of Conduct|Review and add to your README| 57 | |Project list|Get your project included on the project list on the .NET Foundation website| 58 | |Project layout|Adjust your project layout to conform to .NET Foundation guidelines| 59 | |README updates|Updates to your README for the .NET Foundation| 60 | |Website updates|Updates to your project website (if you have one outside of GitHub)| 61 | 62 | ## That's it! You are done! 63 | Once we’ve completed all the above, your project will be full on-boarded to the .NET Foundation! We are definitely excited to have your project join! 64 | -------------------------------------------------------------------------------- /readme.md: -------------------------------------------------------------------------------- 1 | 2 | # .NET Foundation Project Committee Charter 3 | 4 | ## Background 5 | 6 | The .NET Foundation, an independent 501(C)(6) corporation, is chartered to foster open development and collaboration around the growing collection of open source technologies for .NET. It serves as a forum for commercial and community developers alike to strengthen the future of the .NET ecosystem by promoting openness, community participation and rapid innovation. 7 | 8 | The mission of the .NET Foundation is to foster a community of .NET developers focused on collaborating on commercially friendly open source software projects that enhance the .NET platform and create value within the .NET ecosystem. 9 | 10 | ## Rationale 11 | 12 | An important aspect of the .NET Foundation's vision is to attract and foster vibrant communities of open source projects and contributors. However, in order to preserve the relevancy and credibility of the .NET Foundation's brand and reputation, it must ensure that all member projects fully embrace its mission and values and are willing to function as first class ambassadors and representatives of the .NET Foundation. It is the role of the Project Committee to assist the Board of Directors in ensuring this alignment. 13 | 14 | ## Responsibilities 15 | 16 | The Project Committee manages the day to day requirements of Projects. This includes but is not limited to the following: 17 | 18 | - Review and evaluate new Project applications 19 | - Monitor activity of existing Projects 20 | - Provide support to Projects 21 | - Manage the retirement of Projects 22 | 23 | ## Organizational Structure 24 | 25 | The Project Committee is comprised of volunteer .NET Foundation members and does not have any authority to make decisions pertaining to the .NET Foundation. A designated Chairperson will be appointed by the Project Committee and will ensure that the Project Committee meets monthly to discuss and review items pertaining to Projects. The Chairperson will communicate any relevant information, proposals, or recommendations to the Executive Director so that they can be presented to the Board of Directors for review. 26 | 27 | ## Joining the Committee 28 | 29 | The Project Committee meets for one hour on the 2nd Thursday of every month at 5:00 PM ET via Microsoft Teams. If you are interested in becoming a member of our team, please submit a [request to join the project team](https://github.com/dotnet-foundation/projects/issues/new?assignees=sbwalker&labels=membership&template=membership.md) and express your interest in being added to the meeting invite. We welcome individuals from all backgrounds and experience levels who share our passion for .NET, the open source model, and collaborative software development. 30 | 31 | ## Criteria 32 | 33 | Transparency is a key open source characteristic, and as a result the criteria for evaluating .NET Foundation projects is designed to be as measurable and objective as possible. The criteria are not only important for evaluating new project applications but for measuring the ongoing activity of existing projects. There are two types of criteria which have been defined: 34 | 35 | **Eligibility** - this criterion is binary in nature and is used to determine if a project is fully aligned with the mission and values of the .NET Foundation. 36 | 37 | **Activity** - this criterion is quantitative in nature and is based on publicly accessible metrics which can be used to evaluate the activity of a project. 38 | 39 | ## Project Levels 40 | 41 | Projects are categorized according to the following levels: 42 | 43 | **Applicant** - a project which has applied to the .NET Foundation to become a member. The Project Committee will review the application within one month of the submission to determine whether or not the project has satisfied the Eligibility and/or Activity requirements. 44 | 45 | **Seed** - a project which has been reviewed by the Project Committee and meets the basic Eligibility requirements but does not yet meet the Activity requirements. Projects at this level are eligible for some .NET Foundation project services and will be re-evaluated automatically each quarter by the Project Committee to determine if they are ready to graduate to the Member level. 46 | 47 | **Member** - a project which satisfies the Eligibility and Activity requirements and has been on-boarded as an official .NET Foundation project. Projects at this level can identify themselves publicly as Member Projects and are eligible to obtain access to all .NET Foundation project services. The Project Committee will continue to review their activities on a regular basis. 48 | 49 | **Retired** - a project which was once a Member Project but no longer satisfies either the Eligibility or Activity requirements, or has submitted a formal request to withdraw from the .NET Foundation. 50 | 51 | ## Eligibility Criteria 52 | 53 | Broken into a variety of functional areas, the eligibility criteria is a checklist which defines if a project is fully aligned with the mission and values of the .NET Foundation. 54 | 55 | **Suitability** 56 | 57 | - The project operates within the moral and ethical standards of the .NET Foundation. 58 | - The project is aligned with the philosophy and guidelines for collaborative development. 59 | - The project is built on the .NET platform and/or creates value within the .NET ecosystem. 60 | 61 | **Code** 62 | 63 | - The project produces source code for distribution to the public at no charge. 64 | - The project's code is easily discoverable and publicly accessible (preferably on GitHub). 65 | - The project contains a build script that can produce deployable artifacts that are identical to the official deployable artifacts, with the exception of code signing (Exception may be granted for strong name keys, though strongly encouraged to be committed. Exception relies on OSS signing being in the build script for public builds). 66 | - When applicable, project must use reproducible build settings in its toolchain. 67 | - The project uses [Source Link](https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/sourcelink). 68 | - The project uses either embedded PDBs or publish symbol packages to NuGet (if applicable). 69 | - The project code signs their artifacts as appropriate. 70 | 71 | **Licenses and Copyright** 72 | 73 | - The code is offered under a standard, permissive open source license which has been approved by the .NET Foundation. 74 | - Libraries that are mandatory dependencies of the project are also offered under a standard, permissive open source license which has been approved by the .NET Foundation (exceptions include a dependency that is required by the target platform where no alternative open source dependency is available such as the .NET Framework or a hardware specific library). 75 | - Committers are bound by a Contributor License Agreement (CLA) and/or are willing to embrace the .NET Foundation's CLA when the project becomes a Member. 76 | - The copyright ownership of everything that the project produces is clearly defined and documented. 77 | 78 | **Quality** 79 | 80 | - The project is open and honest about the quality of its code. 81 | - The project has a public issue tracker where the status of any defect can be easily obtained. 82 | - The project puts a very high priority on producing secure software. 83 | - The project has a published Security Policy. 84 | 85 | **Community** 86 | 87 | - The project has a home page which provides high level information about its status and purpose. 88 | - The project welcomes contributions from anyone and embraces diversity. 89 | - The project strives to grant more rights and responsibilities to contributors who add value to the project. 90 | - The project has a public communication channel where community members can engage with maintainers. 91 | - The project adheres to, and enforces, the .NET Foundation Code of Conduct. 92 | - The project has a publicly available location where members can review and contribute to documentation. 93 | 94 | It is expected that a project satisfies the majority of the criteria outlined above; however, it is also possible for a project to obtain a waiver for specific criteria. It is the responsibility of the Project Committee to collate the project information, perform an evaluation, and make recommendations on a project's eligibility to the Board of Directors. The Board of Directors has the right to approve or deny a project's eligibility. Projects will also be re-evaluated periodically to ensure they continue to satisfy the eligibility requirements. 95 | 96 | ## Activity Criteria 97 | 98 | Activity criteria are designed to be measurable and are based on publicly accessible metrics which can be used to evaluate the activity of a project on an ongoing basis. For convenience reasons, standard metrics are based on values which can be readily obtained by anyone from GitHub; however, metrics from other open source hosting platforms will also be considered. 99 | 100 | - Age (based on the date on the LICENSE file in the repository or a date provided by the maintainer) 101 | - Stars 102 | - Watchers 103 | - Forks 104 | - Commits 105 | - Issues Open 106 | - Issues Closed 107 | - Pull Requests Open 108 | - Pull Requests Closed 109 | - Branches 110 | - Packages 111 | - Releases 112 | - Contributors 113 | 114 | There are no specific metrics levels, analysis, or calculations which have been defined to judge the activity of a project. Rather, the Project Committee utilizes the various metrics to make a relative determination of whether a project is active and makes this information available to the Board of Directors. Metrics are gathered on an ongoing basis by the Project Committee using the [.NET Foundation Project Trends Site](https://dnfprojects.org). 115 | --------------------------------------------------------------------------------