Hola Scott,
I have been researching a few moments before closing my days to see a way around this.
In MicroProfile though I am a committer, submitting PRs are the way to go while collaborating on documentations. It is easy after forking the repo on my github account.
True that
- to copy/paste changes into a git issue to have others with access merge those contributions is poor at best OSS etique & won't enhance nor welcome others to collaborate.
Current issue is a positive step forward for the Jakarta EE TCK about how it chooses to manage community contributions updates in the wiki while still keeping healthy control of the space.
Early this year, I -- with the help of wonderful Christopher Guindon - Manager, Web Development | Eclipse Foundation and a few others (not only MicroProfilers)~20 individuals in the ticket contributing, we revived a +4 years old github bug that affects positively all the Contributors under the EF: Bug 483563 - Allow assignment of Github issues to contributors Since the middle of December last year, active contributors in any Eclipse project can be added to any Repo. It just need to be executed by the Project itself.
I owe (got sidetracked with the heavy duty work collaborating on the creation of the MP working group + MP is prohibit from releasing MP 4.0 so the blog took a step back as we have no use for it YET] Chris and the EF web team the publishing of that blog still, title: [MP Blog]Adding Contributors to the MP Repository #230
How about we use the draft of the blog to pilot with the Jakarta EE TCK adding me as a contributor to the Repo itself. The steps are simple enough but THIS awesome new contributors feature have yet to be tested. I welcomed you to do some research using the bug tracing -- a few other tickets were opened/closed to fix the issue and still protect the projects. :)
I appreciate you, your follow up shows much care Scott, you are awesome! -- lets try stuff, fail fast, learn/unlearn and re-try, openly!