-
Notifications
You must be signed in to change notification settings - Fork 563
Project benefits content #1085
base: main
Are you sure you want to change the base?
Project benefits content #1085
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(maintainers committee) Generally looks awesome :D here's some nits I couldn't resist though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some quibbles.
|
||
The more people who know about .NET, the better for the ecosystem. We work with Amazon, JetBrains, Microsoft, Progress, and other industry leaders to improve your project's exposure within the community at large. Your success is our success-we'd love to see you achieve the accolades you deserve! | ||
|
||
## CLA management |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The CLA is just a bot you add. .NET Foundation doesn't provide anything (except a ready made document you must use).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Arguably having the legalese covered is a benefit, and the thing I like most about the .NET Foundation CLA is that it applies to all DNF projects so you sign it once and it's gone away forever, which I think is alluded to in this section.
EDIT: alluded to in the "IP and Legal" section
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah doesn't hurt to be concise I guess
Co-authored-by: Dylan Perks <[email protected]>
|
||
## Tools | ||
|
||
If your maintainers need access to certain software to enable them to work more effectively on their open source projects, contact us and we can talk with vendors on your behalf. Microsoft has sponsored a number of MSDN subscriptions for .NET Foundation project contributors over the past 12 months. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This used to be very common in the early days to get a msdn subscription and hasn't in later years. It's requires someone to nominate the project. Might be worth not mentioning this one since it's not a direct benefit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@glennawatson is right. The MSDN subscription is near impossible to come by any longer, even for renewals. I would not highlight this as a benefit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was also unaware of such an option.
|
||
## Continuous integration | ||
|
||
The .NET Foundation has a dedicated Azure DevOps instance, which allows projects to use as many agents in Pipelines as they need and provide storage for CI feeds with Artifacts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
QUESTION: How is it different from the regular Azure DevOps free tier for OSS projects?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess the dedicated Azure DevOps instance has higher limits on CI minutes and Artifacts storage. Getting a little more detail here from people who know for sure would be good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Azure DevOps has higher limits on CI minutes/artifacts, but it's shared between multiple projects so when other projects have high usage there can be delays to projects running.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, so too me that doesn't sound like an exclusive benefit.
|
||
## Secret management | ||
|
||
Get a secure vault to store secrets related to your project (social media credentials, website logins, etc.). Share credentials securely between trusted maintainers on your project, and enjoy the peace of mind that they're safely saved |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
QUESTION: Could you expand on what technology is and how it's different from GH repository/organisation secrets?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm guessing it is Azure Key Vault? IDK. More detail here from a person who knows the details would be good.
|
||
## Project guidance and mentoring | ||
|
||
New projects joining us will get mentorship on how to best run an open source community along with access to developers currently seeking .NET projects. We work with project leads to help ensure the project grows into a vibrant and welcoming community. And, of course, we love to share best practices for managing a friendly, collaborative, and innovative open source workplace, wherever you may be. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
QUESTION: Could you give examples of mentoring and a vibrant community? I think that it's important to be more precise on what project can get from the .NET community. Personally, I haven't noticed a lot of collaboration or mentoring initiatives. I might have missed them. That's why I'm curious. It'd be more convincing to put here a list of example initiatives.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The mentoring has come up during the maintainer's committee meetings as something they'd like to adopt in the near future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't give examples, I'm just playing around with content.
I think some more detail from people who know more about this area would be useful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@JamesNK it's being discussed as something we'd like to start adopting in the maintainer's committee but not something currently that's provided beyond the initial onboarding help with the infrastructure.
Would it perhaps be of value to the readers of that page to also highlight the consequences (trade offs) of joining? I think it's in the foundations ultimate interest to be as transparent and clear as possible so that members understand the consequences of joining. Consequences:
|
I think that's more a topic for after they've considered onboarding. i.e. the flow I think would be appropriate:
If we progress beyond step 2, we know the reader sees merit in our benefits and is actively interested in what the drawbacks are as well. I don't think we'd want to risk losing the reader early. Just my opinion though. |
I agree that it should come after "Here's why you should consider us". |
Adding Board Members to this thread as we work on benefits to projects, maintainers and members for the Foundation. |
I think the current project benefits page - https://dotnetfoundation.org/projects/why-join - can be improved.
This PR:
Something else to do now could be to remove benefits that aren't valid anymore (is offering Azure Dev Ops for CI useful now that GitHub has actions?) and add new ones.
The PR is currently markdown to focus on the content. If the content is eventually approved then it can be adapted to cshtml.