Skip to content
This repository has been archived by the owner on Feb 14, 2023. It is now read-only.

Project benefits content #1085

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

JamesNK
Copy link
Member

@JamesNK JamesNK commented Feb 10, 2022

I think the current project benefits page - https://dotnetfoundation.org/projects/why-join - can be improved.

This PR:

  • Adds a couple of sentences that summarize the goal of benefits (improve governance, maturity, stability) and non-goals (replacing maintainers and contributors)
  • Changes list of benefits to a flat list. The current page groups benefits into administrative and technical. This seems unnecessary and distracts from the benefits themselves
  • Clarifies why a couple of benefits are useful. e.g. why a CLA is good, why code signing is beneficial. Probably more could be done here

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.

Copy link
Member

@Perksey Perksey left a 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

input/projects/why-join-wip.md Outdated Show resolved Hide resolved
input/projects/why-join-wip.md Outdated Show resolved Hide resolved
Copy link

@robmen robmen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some quibbles.

input/projects/why-join-wip.md Show resolved Hide resolved

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
Copy link

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).

Copy link
Member

@Perksey Perksey Feb 10, 2022

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

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


## 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.

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.

Copy link

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.

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.

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?

Copy link
Member Author

@JamesNK JamesNK Feb 11, 2022

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.

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.

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

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?

Copy link
Member Author

@JamesNK JamesNK Feb 11, 2022

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.
Copy link

@oskardudycz oskardudycz Feb 11, 2022

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.

Copy link

@glennawatson glennawatson Feb 11, 2022

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.

Copy link
Member Author

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.

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.

@abergs
Copy link
Contributor

abergs commented Feb 11, 2022

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:

  • You are signing away the IP of what you've built. -- What does that mean for a developer?
  • Your workflow should conform to the rules/ preferred method of development, as per the Onboarding-guide.
  • There is some initial work that needs to be done by you (Prep-work etc)

@Perksey
Copy link
Member

Perksey commented Feb 11, 2022

I think that's more a topic for after they've considered onboarding. i.e. the flow I think would be appropriate:

  1. here's a page with the benefits and cool writing
  2. click a link saying you're interested
  3. links to a page with more verbose information on both the benefits and the drawbacks
  4. if you're still interested, click another link to fill out an application

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.

@abergs
Copy link
Contributor

abergs commented Feb 11, 2022

I think that's more a topic for after they've considered onboarding

I agree that it should come after "Here's why you should consider us".
I do however think it's necessary information to give quite early, since it helps the reader evaluate if they are indeed interested.

@nicoleabuhakmeh
Copy link
Contributor

Adding Board Members to this thread as we work on benefits to projects, maintainers and members for the Foundation.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.