[Pattern Draft] Maintainer Apprentice about innersourcepatterns

[spier]

Hi Jason.

I noticed you closed this pattern draft due to inactivity.

Had two reactions to it:

1. kind of cool - in terms of cleaning up things in GitHub (I don't always do myself when opening issues/PRs)
2. kind of sad - as you got no reaction from anybody, other than me in discussions that happened before opening the PR

Activity in our patterns community varies quite a bit at different times.
Also it seems like some people only engage via Slack, others only via GitHub.
Lastly, some conversions need to be started and restarted multiple times until something interesting happens :)

Therefore I will try to post this topic one more time in Slack, to see if anybody engages.

[michael-basil]

Within Dojo from SAP we leverage the concept of Senpai. This person effectively becomes a Sensei apprentice (our Sensei are project admins). They gain write access to the repository and take on some responsibilities within GitHub and the social community at large.

We have our Sensei and Senapi in GitHub teams.

The high level approach is described in the blog article below:

• From Learner to Leader: The Power of Senpai

Before they could become a Senpai they have to have made their green level demonstration through a belt claim (captured as a GitHub pull request). This is not so easy to do and acts as a filter.

I believe this qualifies as a known instance for SAP. @dellagustin, would you know of other known instances at SAP?

[jmeridth]

Closing due to no interaction

[spier]

Some more thoughts on this:

1. In our patterns repo we used the "maintainer apprentice" idea only for people that were contributing to the translations of our patterns. You could argue that this is almost a "side project" i.e. there is (a) the creating of new patterns in English, and (b) the translation of the existing patterns to other languages.
2. We don't really have proof that the path of leveling up those "maintainer apprentices" into full "maintainers" through this process.
3. While our patterns repo is open source (not InnerSource), we believe that mostly the same effects apply in this area. If at all, we hope it might be easier in a corporate context to level up people to truster committer / maintainer more quickly then in open source, as you have more established relationships with them already