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

Contributor Journey Optimization #157

Open
dellagustin-sap opened this issue Dec 17, 2024 · 8 comments
Open

Contributor Journey Optimization #157

dellagustin-sap opened this issue Dec 17, 2024 · 8 comments
Assignees

Comments

@dellagustin-sap
Copy link
Contributor

dellagustin-sap commented Dec 17, 2024

Description

Contributor Journey Optimization (CJO) is a method, currently under ideation and development, that describes how a project can be evaluated for the creation of concrete tasks for the adoption of InnerSource, specifically aiming to facilitate the journey of project stakeholders in becoming contributors, trusted committers and/or maintainers.

Results

Related Meetings

@spier
Copy link
Member

spier commented Jan 2, 2025

@dellagustin-sap the idea looks interesting. I understand it as reducing the barrier to entry i.e. making contributions as easy as possible.

I have access to the miro board linked above, and left some comments there.

Have you already checked if there open source community has already created documentation related to this problem space?

Further I am wondering if in InnerSource additional methods can be used that would be harder to implement in open source.

@rrrutledge
Copy link
Contributor

@dellagustin-sap let us know how this is going (or if it is still something being worked on?

@dellagustin-sap
Copy link
Contributor Author

@rrrutledge , I have not done much since I presented it in Dec 16, but I'm still working on it.
I will present it on the InnerSource Gathering in Berlin.

@spier
Copy link
Member

spier commented Jan 14, 2025

@dellagustin-sap that Gathering is March 12th I believe.

I would love to help with this.

My experience is that people will contribute more easily to an existing pattern, rather than starting from zero.

Therefore my aim here would be to have a version of this pattern merged to the repo ahead of the Gathering.

Then we can give people something that they can disagree with, if you know what I mean :)

@dellagustin-sap
Copy link
Contributor Author

@spier , that's also my goal, I want to have a v1 of my idea board completed and at least a merged initial pattern before the gathering.

@spier
Copy link
Member

spier commented Jan 14, 2025

@dellagustin-sap I did little experiment with ChatGPT about this:
https://gist.github.com/spier/724794bb1e18060c5b9fdce77a18a5dd

I do like the stage names that it made up. unaware/aware and supporter sound useful.

Also note the amazing examples of hallucination related to the existing patterns.
ChatGPT really invented pattern names (and even URLs) that should existing but don't :)

@rrrutledge
Copy link
Contributor

That’s crazy - is ChatGPT just glorified pattern matching?

@spier
Copy link
Member

spier commented Jan 19, 2025

That’s crazy - is ChatGPT just glorified pattern matching?

Hehe, I would argue it does a little bit more interesting stuff than this :) In this example I found ChatGPT to be a great brainstorming-buddy.

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

No branches or pull requests

3 participants