Oleg, I agree that having projects that jenkins depends deeply on sitting in personal repo's is not great. Offering or asking the owners of those projects the option to bring their project into the project umbrella makes sense.
I see in your doc that part of the intent of having a separate org is to let maintainers of those project retain some control, even having a process for a project to leave the jenkins-contrib org. Is that is even an interesting scenario to the owners of project you are thinking of? We might be addressing a non-issue. Maybe there's a more general discussion to be had around whether the github org structure is the place to express overall project structure and if so what that structure should be. I could see how it would make sense to have an org that would hold jenkins adjacent projects such as "stapler", to maintain the clarity around which project could be used separately from jenkins. I added a couple suggestions to the doc as placeholders for further discussion. On Wednesday, October 10, 2018 at 7:22:41 AM UTC-7, Jesse Glick wrote: > > On Wed, Oct 10, 2018 at 7:13 AM Oleg Nenashev <o.v.ne...@gmail.com > <javascript:>> wrote: > > The governance model and hosting processes are slightly different from > lugins. > > Sure, but that is also true of 200+ repos in `jenkinsci` today, and we > manage somehow. > > > it may be tricky for external contributors to distinguish what is > Jenkins-only and what is available to be used outside > > A big notice in `README.md`? Availability on Maven Central? > > > We already have hundreds of repos in the Jenkins org, and it's not good > for visibility of "contrib" projects > > Why is it more important for, say, `file-leak-detector` to have high > visibility than, say, `job-dsl-plugin`? And what makes you think a new > small GH org provides additional visibility, as opposed to the obvious > things like blog posts and tweets and search-engine-friendly links > from prominent documents? > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2b86a321-6787-472f-9e94-585cd95788ce%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
