Closed egil closed 3 years ago
Hello! I will be assisting in the on-boarding process for bUnit. We will follow the checklist below - thanks!
CLA is out for signing
@ChrisSfanos signed the project agreement via DocuSign.
I have not received anything about signing a CLA. Is it because I signed a CLA on GitHub when I contributed AngleSharp.Diffing to AngleSharp?
Project agreement is signed - I'll send out the email on the CLA steps here in a few minutes
CLA on-boarding complete - the remaining steps for onboarding will be sent out in a bit
newsletter entry created and will go out with the next edition
Great. Thank you @ChrisSfanos.
all items are wrapped up - onboarding is complete
1. General Information
Project Name: bUnit
License: MIT
Contributor (Company, Organization or individual name(s)): @egil
Existing OSS Project? (Yes/No): Yes
Source Code URL: https://github.com/bUnit-dev/bUnit
Project Homepage URL (if different): https://bunit.dev/
Project Transfer Signatories: Full legal name and email address required of the individual(s) with the 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).
2. Description
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:
bUnit is a testing library for Blazor Components. Its goal is to make it easy to write comprehensive, stable unit tests. With bUnit, you can:
bUnit builds on top of existing unit testing frameworks such as xUnit, NUnit, and MSTest, which run the Blazor component tests in just the same way as any normal unit test. bUnit runs a test in milliseconds, compared to browser-based UI tests which usually take seconds to run.
Please provide a 1 sentence (<140 character) summary of your project to help users when searching the .NET Foundation projects
bUnit is a testing library for Blazor Components. Its goal is to make it easy to write comprehensive, stable unit tests.
3. Project Governance
Please complete this section about who will be maintaining the open source project and how it will run. Project Lead: (Who is the primary contact point for the community and the .NET Foundation when discussing governance of the project.)
Name: Egil Hansen Email: egil@assimilated.dk GitHub Profile URL: @egil
Committers:
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)
Governance Model:
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.
The ideal process is as follows:
As for appointing new committers, this is something I do not have much experience with. Non have reached out and asked to join as a maintainer/committer yet, and there have only been a handful of significant code contributions until now from others except me. I do expect that the precursor to becoming an maintainer on the project is at least one major implementation of a feature, which shows the committers ability to understand the coding and architecture style of the project.
CLA
If already an OSS project, was a Contribution License Agreement in place for contributions accepted? How does the project check who has signed one?
No. But contributors have to check a checkbox in the PR template indicating they have read the CONTRIBUTING.md document, which states that all contributions will fall under the projects license.
CLA Notification Alias Provide an email address that will receive CLA related notifications from the .NET Foundation CLA automation.
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).
Contribution Model. Under the .NET Foundation contribution model, a project retains ownership of the project, 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).
4. Repository Layout
The .NET Foundation host guidance for new projects and details on recommended structure here: https://github.com/dotnet/home/tree/master/guidance
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.
Please define below any changes you would want to make to your repositories as part of the process of joining the .NET Foundation
5. Eligibility Criteria
Please complete the following for your project
6. PR Plan
Please summarize the public relations plan for the announcement when joining the foundation (and releasing as open source if appropriate). What is the main story we wish to promote, through what channels, what issues should we be aware of? For significant news events then please also work with your .NET Foundation contact to ensure a full PR plan is developed.
No particular PR plan. A tweet or two perhaps.
7. Infrastructure Requirements
Please describe any infrastructure requirements for the project. For example, how will build servers be operated? Any web hosting or service hosting requirements? Do we need to set up SSL certificates or provide Authenticode Code Signing arrangement for releases?
A dotnet cli to build and test locally. GitHub Actions is used to manage CI and releases on GitHub.
8. Additional Notes
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.