On Fri, Apr 8, 2016 at 12:00 PM, Vincent Massol <[email protected]> wrote: > Hi, > >> On 08 Apr 2016, at 11:43, Anca Luca <[email protected]> wrote: >> >> Hello all, >> >> Since http://xwiki.markmail.org/thread/jrug6cbbqpia5bx4 (but not only) the >> rule says that we should discuss contrib related stuff with the community. >> In my case, I cannot manage to follow all the mails on the [email protected] >> (because they are a lot) but I would be particularly interested of not >> missing the ones about contrib extensions. > > Since the dev rules for xwiki contrib are now the same as for xwiki core > (i.e. dev.xwiki.org), I’m not sure if it makes sense to differentiate > proposals. Maybe you could just filter mails with "[Proposal]" and "[VOTE]”? > >> However, today, I don't know how >> to differentiate them, I would need to read all [email protected] to not miss >> one. >> >> There are multiple solutions that I can propose for this, please let me >> know what you think: >> 1/ have a contrib mailing list > > I feel that xwiki-contrib might be large enough now to warrant a mailing list > but maybe not 2 (users and devs). > > However there are issues: > > * Notifications from jira. We could have a single [email protected] mailing > for everything related to contrib (users, devs, notifications). > > * Users don’t know if what they’re using from e.x.o is from Core or from > Contrib so they’d have a hard time choosing the right list from > http://dev.xwiki.org/xwiki/bin/view/Community/MailingLists. For example right > now we have: "[email protected] : For questions about using XWiki, using the > XWiki API, suggestions for improvements, ideas, etc.” >
I'm fine with [email protected] being for contrib devs and don't change [email protected] and [email protected]. > >> 2/ have an alias for the contrib that would send on the same list, this way >> we could filter by the "to" field >> 3/ have a convention about mails related to contrib (e.g. [Contrib] in the >> subject) that would allow to filter > > This is probably the simplest ATM. The pros is that it wouldn’t create any > fragmentation between Contrib and Core, which is probably a good thing. For this one I think I would prefer [<Project>] instead of a general [Contrib]. But I doubt this rule would be followed. > >> 4/ any other technical solution that I didn't think about that would allow >> to automatically decide if a mail is about contrib or not, without reading >> it :D >> >> >> 1, 2 and even 4 are perfectly fine with me, 3 is a bit risky because people >> might not follow conventions. >> >> What do you think? > > If we follow the direction that we’re trying to take, which is to have a > single large community (ie bring contrib and core together), I think the best > is to keep using the same lists as now but do a best effort of using > "[Contrib]” for mails related only to contrib stuff. > > Thanks > -Vincent > >> Anca > > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs -- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
