can I create a subteam for netbeans related plugins?

15 views
Skip to first unread message

Milos Kleint

unread,
Nov 8, 2016, 4:38:38 AM11/8/16
to mojohaus-dev
Hello,

I've noticed that we have a subteam for sonar related repositories. Can I add a similar one for netbeans related plugins? nbm-maven-plugin, nb-repository-plugin and nbm-shared repositories. I would like to give a guy access there who contributed a lot of patches. (ebarboni)

From what I could search in the archive, I'm not sure what the decision was with regard to subteams vs org access.


Cheers

Milos Kleint

Olivier Lamy

unread,
Nov 8, 2016, 5:21:14 AM11/8/16
to mojoha...@googlegroups.com
Hi
You can simply add Eric to the dev group
That will ease the life!
Just do it in 24H (give a bit of time to folks to maybe complain :-) )

Olivier

--
You received this message because you are subscribed to the Google Groups "mojohaus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mojohaus-dev+unsubscribe@googlegroups.com.
To post to this group, send email to mojoha...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/153e82dd-56a1-458c-a36e-b4e489e6d180%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Baptiste Mathus

unread,
Nov 8, 2016, 5:47:47 AM11/8/16
to noreply-spamdigest via mojohaus-dev
Why not just follow the original "process"? We "just" changed our infra, not the way we work I guess?

Welcoming someone new is quite normal if they proved active, np with that. So feel free to just start a VOTE thread?

I don't really like the idea of having sub-teams as a standard practice. We don't have that many plugins. IMO, it's just best judgement when working on a plugin: if I want to work on some plugin I know is mostly worked on by another member, I'll sync with him/her to show some "respect", but that's all. IIRC, we always have wanted that any MOJO[Haus] could work and commit on any of our plugins.

IIRC again, we also kind of agreed that in some cases, like Sonar, it might just make more sense to just move the related plugins under the sonarsource/sonar-community GH org. As we said that, if the related org is willing to do, it would make sense that, say, Cassandra-m-p is maintained by the Cassandra team and so on (and also granted the original plugin agrees, goes w/o saying IMO).

WDYT?

Reply all
Reply to author
Forward
0 new messages