Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
82 lines (68 sloc) 5.07 KB

New Project Checklist

Participation in the .NET Foundation exposes your project to the wider world of .NET developers and helps you to build a better community. If you would like to learn a bit more about what joining the .NET Foundation involves then please see the guidance below. To start the conversation about your project joining the .NET Foundation then fill out this simple survey to start the process.

When projects join the foundation, there are two ways that they can come in.

  • License - The first is for the maintainers of the project to sign a contribution agreement licensing the code to the .NET Foundation under the terms of the open source license and confirming that they have the rights to do that. This type of agreement is most common when projects have had a long history of being open source, with lots of contribution from many different individuals and the project community now wish to now be supported by the .NET Foundation.

  • Assignment - The other is to assign the copyright of the project to the .NET Foundation and confirm that they have the rights to do this. This type of agreement is usually used when releasing something as open source for the first time or by a project that has had a high degree of control over contributions to the existing project in the past.

When you contact the .NET Foundation, they will help you decide which type of agreement is most likely to suit you based on your needs.

When on-boarding a project into the .NET Foundation, we typically go through the following steps to make sure everything is set up properly. Feel free to copy the checklist below into a new issue in your project to make sure we remember to do everything or create individual issues for the items that are currently missing.

Title: On-Board project to the .NET Foundation

We're getting ready to bring the project into the .NET Foundation, but before we
do we need to do the following:

## Getting into the .NET Foundation
- [ ] Make sure the project has a good name that is easy to remember and 
 spell. Check that it doesn't [conflict with another existing project](
- [ ] Make sure the people involved in the project want to join the .NET Foundation
- [ ] Make sure the project has a clear understanding about how it accepts contributions and the process
     it follows when selecting new committers to the project.
- [ ] [Register an interest]( in joining the .NET Foundation
- [ ] Work with the .NET Foundation to fill out an On-Boarding Questionaire
- [ ] .NET Foundation sends out completed questionaire to .NET Foundation Advisory Council for comments
- [ ] .NET Foundation Executive Director submits new project proposal to the .NET Foundation Board
- [ ] Configure a CI build for the project and ensure build status badges are available from the README

## Once accepted into the .NET Foundation
- [ ] Sign the contribution / assignment agreement
- [ ] Agree a date to move into the .NET Foundation
- [ ] Prepare a guest blog post announcing the move on the .NET Foundation Blog
- [ ] Read the [code of conduct](, 
      [link to it in your code]( and 
      understand what to do if you are concerned about any behaviour or have
      concerns reported to you.
- [ ] Tell the world we have joined!
- [ ] Get CLA Automation enabled to ensure contributors can easily sign the 
      [Contribution License Agreement](
- [ ] Send a PR to add the Project into the .NET Foundation 
- [ ] Ensure the repo contents are up to date with [.NET Foundation guidance](
- [ ] Review the [README guidance]( and update if necessary
- [ ] If applicable [update the LICENSE file]( to show Copyright has been assigned to the .NET Foundation
      and look to update any file headers.
- [ ] If applicable, update any copyright statements in websites owned by the project to reflect 
      assignment to the .NET Foundation
- [ ] If applicable, update any websites associated with the project to include
      "Supported by the <a href="">.NET Foundation</a>" or
      similar link back to the .NET Foundation in the footer. If applicable, please
      include image links from [our swag repo]( (We think a link in the footer using the horizontal logo looks very nice.)
- [ ] [Sign up for Project Leader news](
- [ ] Configure any resources requested from the .NET Foundation (SSL Certs, Code Signing,
      Secret Management, Build Servers etc)