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.

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

New InnerSource Project Assessment #73

Open
rrrutledge opened this issue Oct 23, 2023 · 11 comments
Open

New InnerSource Project Assessment #73

rrrutledge opened this issue Oct 23, 2023 · 11 comments
Assignees

Comments

@rrrutledge
Copy link
Contributor

rrrutledge commented Oct 23, 2023

How to assess if a candidate InnerSource project is ready to invite additional contributors and consumers.

@rrrutledge
Copy link
Contributor Author

Could be a pattern.

@dellagustin
Copy link
Contributor

Related patterns:

@azinshahidi2019
Copy link

What we have created is indeed based on the documents that Guilherme @dellagustin has shared. Please have a look and see if this type of checklist can be helpful for this purpose?

https://drive.google.com/file/d/15p0LIzwO1SnTyEhC0FXf5eWaMBFrdqra/view?usp=drive_link

@dellagustin-sap
Copy link
Contributor

@rrrutledge could you please check the questionnaire shared by @azinshahidi2019 and check if we could use as base?
Are you thinking about the assessment as a self-assessment for teams or as a kind of centrally checked maturity model?

@rrrutledge
Copy link
Contributor Author

Yes I think it could be used. Yes am thinking as self-assessment. We can't have manual central assessments or it won't scale. So we need self-assessment or automated central assessment.

@dellagustin-sap
Copy link
Contributor

dellagustin-sap commented Dec 4, 2023

Somewhat related to #79 .
@azinshahidi2019 , are you planning to work on a pattern for this, or should we move back to "Challenge".
P.S.: if you move this one forward, please check #61, seems to be a duplicate, we should consider merging both issues. That one has already some discussion and a lot of refererences.

@azinshahidi2019
Copy link

I believe this can be merged with #61 . Let's mark it as duplicate and continue on 61.

@rrrutledge
Copy link
Contributor Author

Whoops! We accidently closed #61 instead. I guess we'll keep this one :)

@rrrutledge
Copy link
Contributor Author

@azinshahidi2019 did you want this one closed because it's not something you're actively working on now?

@azinshahidi2019
Copy link

I think with the new rules that we have created for health checking our projects, we are taking a new approach by giving the option of opening any project to contribution but grading their projects based on their documentation completeness. That way, the motivated teams would be eager to elevate their project grading to attract contributors.
The rules are as follows: ( this is customised for our organisation but you get the concept):

Bronze:
Has REDME.md file
and
Has CONTRIBUTING.md file
or
Has a Contributing Section

Silver:
Has Project Name
and
Has Project Description
and
Has Usage (or Getting Started) Section
and
Has a Installation (or Environments) Section

Gold:
Has Communication Link
and
Has Issues Link
and
Has Members Roles
And
Has Governance.md file
or
Has a Governance Section

@azinshahidi2019
Copy link

@azinshahidi2019 did you want this one closed because it's not something you're actively working on now?

We can close this if everyone agrees.

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

No branches or pull requests

4 participants