Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

On-Board project to the .NET Foundation #2026

Closed
22 tasks done
jbogard opened this issue Mar 23, 2017 · 34 comments
Closed
22 tasks done

On-Board project to the .NET Foundation #2026

jbogard opened this issue Mar 23, 2017 · 34 comments

Comments

@jbogard
Copy link
Member

jbogard commented Mar 23, 2017 •
edited

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
    list
  • 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 .NET Foundation" 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)
@jbogard
Copy link
Member Author

jbogard commented Mar 27, 2017

@TylerCarlson1 @lbargaoanu any questions/comments/concerns? I had a call w/ MS on what it meant and really the biggest thing would be a CLA if we decide to go that route.

@lbargaoanu
Copy link
Member

I'm good :)

@TylerCarlson1
Copy link
Member

My main concern, other than the CLA and possibly standardizing it, is what about the other projects that are based off AutoMapper. Do those have to follow these rules or do they remain outside the scope?

@jbogard
Copy link
Member Author

jbogard commented Mar 27, 2017

Good question, @jongalloway I forgot to ask you this one. This is just for the main project, right? Not the ancillary ones under the AutoMapper org?

@lbargaoanu
Copy link
Member

I guess the CLA thing would add an extra hurdle for first time contributors.

@jongalloway
Copy link

@jbogard You'd be welcome to move the other project, but you don't have to.

@lbargaoanu The CLA isn't required. Most projects do end up using it, because with the CLA bot it's pretty low impact and you can have more confidence in the source of contributions, but you don't have to if you think it's a blocker.

@jbogard
Copy link
Member Author

jbogard commented Mar 28, 2017

@lbargaoanu having gone through the process it's pretty easy. When you submit a PR the CLA bot will send you a link to a docusign thingy that you e-sign. I thought it would be a huge pain but tbqh it was kinda impressive how it all is automated.

@jbogard
Copy link
Member Author

jbogard commented Mar 28, 2017

@TylerCarlson1 since the Collection project is yours, it's your choice, I'm leaving the others out for now. They're so small anyway (EF6 and Data etc)

@TylerCarlson1
Copy link
Member

@jbogard Ok that's fine with me. I guess we'll see how AM goes and I'll decide from there. Not necessarily opposed to it just wanted to know how all that would work.

@jbogard
Copy link
Member Author

jbogard commented Jul 7, 2017

@jongalloway ping

@jongalloway
Copy link

Project was accepted by .NET Foundation directors. Next step is for significant contributors (I believe that's @jbogard @ChrisMissal @lbargaoanu @TylerCarlson1 correct?) to sign the contribution agreement. I'll need e-mail addresses so I can send via docusign. Can you send via e-mail / DM and I'll get the contribution agreement out to you?

@lbargaoanu
Copy link
Member

My email domain is hotmail.com and my user name is the same as on github.

@TylerCarlson1
Copy link
Member

Email is on github account page

@lbargaoanu
Copy link
Member

@jongalloway I'm not sure where you draw the line, but @BlaiseD belongs on the list and @ChrisMissal doesn't. I think :) https://github.com/AutoMapper/AutoMapper/graphs/contributors

@ChrisMissal
Copy link
Member

Seems fine. I think he was just looking at the organization's members: https://github.com/orgs/AutoMapper/people

@jbogard
Copy link
Member Author

jbogard commented Jul 18, 2017

@BlaiseD can you update with email?

@BlaiseD
Copy link
Member

BlaiseD commented Jul 18, 2017 •
edited

@jbogard Yep - done - now on my profile page. Thanks.

@jbogard
Copy link
Member Author

jbogard commented Jul 18, 2017

@jongalloway that looks like everyone here!

@jongalloway
Copy link

Great, I'll get the agreement out to you today then.

@jbogard
Copy link
Member Author

jbogard commented Jul 24, 2017

@jongalloway ping :)

@jongalloway
Copy link

Sent

@BlaiseD
Copy link
Member

BlaiseD commented Jul 26, 2017

Signed. @lbargaoanu - appreciate the plug (#2026 (comment)) BTW. Thanks.

@jbogard
Copy link
Member Author

jbogard commented Jul 26, 2017

Signed!

@jongalloway
Copy link

Thanks everyone for the quick review and signature. There are a few more things that can be checked off the list above. The next step is to agree on a date to announce and if you've got any specific announcement requirements. Generally we've just been posting a quick announcement on http://dotnetfoundation.org/blog and publicizing via twitter (@dotnetfdn).

If you add the @dnfadmin account as a contributor on the project I can help keep the checklist up to date.

Congrats on making it through the grueling onboarding process. :) Sincerely, welcome!

@jbogard
Copy link
Member Author

jbogard commented Jul 26, 2017

@jongalloway added @dnfadmin !

@jbogard
Copy link
Member Author

jbogard commented Jul 26, 2017

@jongalloway as far as announcement requirements, I really don't have anything specific. I'll blog about it too on whatever date we agree. What's the lead time there? It won't take long for me to write a post up.

@jongalloway
Copy link

One day lead time is fine - you can see the recent announcement posts on https://dotnetfoundation.org/blog, they're just quick announcements. How about Wednesday Aug 2 at 12 PM Pacific time?

Also, to get the project listed on the our project list, can you submit a pull request to github.com/dotnet/home similar to this one: https://github.com/dotnet/home/pull/57/files

@jbogard
Copy link
Member Author

jbogard commented Aug 2, 2017 via email

@jbogard
Copy link
Member Author

jbogard commented Aug 2, 2017

OK I've got a blog post ready on my side and created that PR. Ready when you are!

@jbogard
Copy link
Member Author

jbogard commented Aug 2, 2017

Oh one other thing @jongalloway - what do I need to do to get CLA automation going?

@jongalloway
Copy link

@jbogard I'm working on getting CLA automation set up. It is arduous but still, I will persist.

@jbogard
Copy link
Member Author

jbogard commented Sep 26, 2017

@jongalloway ping :)

@jbogard jbogard closed this as completed Jan 23, 2018
@jbogard
Copy link
Member Author

jbogard commented Jan 23, 2018

All complete!

@lock
Copy link

lock bot commented May 6, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators May 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@ChrisMissal @jongalloway @jbogard @lbargaoanu @TylerCarlson1 @BlaiseD