8 Apr
2016
8 Apr
'16
11:43 a.m.
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 devs(a)xwiki.org
(because they are a lot) but I would be particularly interested of not
missing the ones about contrib extensions. However, today, I don't know how
to differentiate them, I would need to read all devs(a)xwiki.org 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
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
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?
Anca
8 Apr
8 Apr
noon
Hi,
On 08 Apr 2016, at 11:43, Anca Luca
<lucaa(a)xwiki.com> 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 devs(a)xwiki.org
(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 devs(a)xwiki.org 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 contrib(a)xwiki.org 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:
"users(a)xwiki.org : For questions about using XWiki, using the XWiki API, suggestions
for improvements, ideas, etc.”
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.
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
12:06 p.m.
New subject: [xwiki-devs] [Proposal] Add mechanism to allow following only contrib related mails
On Fri, Apr 8, 2016 at 12:00 PM, Vincent Massol <vincent(a)massol.net> wrote:
For this one I think I would prefer [<Project>] instead of a general [Contrib].
But I doubt this rule would be followed.
--
Thomas Mortagne
Hi,
I'm fine with contrib(a)xwiki.org being for contrib devs and don't
change users(a)xwiki.org and notifications(a)xwiki.org.
On 08 Apr 2016, at 11:43, Anca Luca
<lucaa(a)xwiki.com> 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 devs(a)xwiki.org
(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 devs(a)xwiki.org 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 contrib(a)xwiki.org 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:
"users(a)xwiki.org : For questions about using XWiki, using the XWiki API, suggestions
for improvements, ideas, etc.”
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. 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
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs 
25 Apr
25 Apr
12:27 p.m.
New subject: [xwiki-devs] [Proposal] Add mechanism to allow following only contrib related mails
On Fri, Apr 8, 2016 at 1:00 PM, Vincent Massol <vincent(a)massol.net> wrote:
Hi,
IMO contrib devs should be up to date with the changes in the platform and
we should keep the communication tight with the platform. As we can see,
many topics on contrib apps trace down to the platform and vice-versa.
It would also not be very helpful for the project/community to do such a
segregation, so I agree with Vincent.
Since we are talking about contrib (which are devs and which have a guide
to follow), as Thomas suggested, it would be a helpful idea to mention the
app in the subject so that we can apply filters in the mail client, should
we need them.
Thanks,
Eduard
On 08 Apr 2016, at 11:43, Anca Luca
<lucaa(a)xwiki.com> 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
devs(a)xwiki.org
(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 devs(a)xwiki.org 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 contrib(a)xwiki.org
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: "users(a)xwiki.org : For questions about using XWiki,
using the XWiki API, suggestions for improvements, ideas, etc.”
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.
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
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
27 Apr
27 Apr
1:59 p.m.
New subject: [xwiki-devs] [Proposal] Add mechanism to allow following only contrib related mails
Actually I don't like the idea of having the name of the application itself
and not a unique keyword because it's not easy to have filters in the mail
client for all the names of the applications on contrib (I cannot imagine
how I would create these filters). With a single keyword filters are easier
to do.
Let's please decide quickly on this, because I see there is already contrib
related activity that I am missing...
Thanks,
Anca
On Mon, Apr 25, 2016 at 12:27 PM, Eduard Moraru <enygma2002(a)gmail.com>
wrote:
On Fri, Apr 8, 2016 at 1:00 PM, Vincent Massol
<vincent(a)massol.net> wrote:
any
Hi,
"[VOTE]”?
On 08 Apr 2016, at 11:43, Anca Luca
<lucaa(a)xwiki.com> 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
devs(a)xwiki.org
(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 However, today, I don't know how
to differentiate them, I would need to read all devs(a)xwiki.org 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 contrib(a)xwiki.org
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: "users(a)xwiki.org : For questions about using XWiki,
using the XWiki API, suggestions for improvements, ideas, etc.”
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 fragmentation between Contrib and Core, which is
probably a good thing.
IMO contrib devs should be up to date with the changes in the platform and
we should keep the communication tight with the platform. As we can see,
many topics on contrib apps trace down to the platform and vice-versa.
It would also not be very helpful for the project/community to do such a
segregation, so I agree with Vincent.
Since we are talking about contrib (which are devs and which have a guide
to follow), as Thomas suggested, it would be a helpful idea to mention the
app in the subject so that we can apply filters in the mail client, should
we need them.
Thanks,
Eduard
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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Anca
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
2:42 p.m.
New subject: [xwiki-devs] [Proposal] Add mechanism to allow following only contrib related mails
Then [Contrib][<Project>] I guess.
On Wed, Apr 27, 2016 at 1:59 PM, Anca Luca <lucaa(a)xwiki.com> wrote:
Actually I don't like the idea of having the name
of the application itself
and not a unique keyword because it's not easy to have filters in the mail
client for all the names of the applications on contrib (I cannot imagine
how I would create these filters). With a single keyword filters are easier
to do.
Let's please decide quickly on this, because I see there is already contrib
related activity that I am missing...
Thanks,
Anca
On Mon, Apr 25, 2016 at 12:27 PM, Eduard Moraru <enygma2002(a)gmail.com>
wrote:
--
Thomas Mortagne
On Fri, Apr 8, 2016 at 1:00 PM, Vincent Massol
<vincent(a)massol.net> wrote:
any
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs Hi,
"[VOTE]”?
On 08 Apr 2016, at 11:43, Anca Luca
<lucaa(a)xwiki.com> 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
devs(a)xwiki.org
(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 However, today, I don't know how
to differentiate them, I would need to read all devs(a)xwiki.org 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 contrib(a)xwiki.org
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: "users(a)xwiki.org : For questions about using XWiki,
using the XWiki API, suggestions for improvements, ideas, etc.”
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 fragmentation between Contrib and Core, which is
probably a good thing.
IMO contrib devs should be up to date with the changes in the platform and
we should keep the communication tight with the platform. As we can see,
many topics on contrib apps trace down to the platform and vice-versa.
It would also not be very helpful for the project/community to do such a
segregation, so I agree with Vincent.
Since we are talking about contrib (which are devs and which have a guide
to follow), as Thomas suggested, it would be a helpful idea to mention the
app in the subject so that we can apply filters in the mail client, should
we need them.
Thanks,
Eduard
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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Anca
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
4:41 p.m.
New subject: [xwiki-devs] [Proposal] Add mechanism to allow following only contrib related mails
+1 for [Contrib][<Project>]
On Wed, Apr 27, 2016 at 2:42 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com>
wrote:
Then [Contrib][<Project>] I guess.
On Wed, Apr 27, 2016 at 1:59 PM, Anca Luca <lucaa(a)xwiki.com> wrote:
--
Thomas Mortagne
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Actually I don't like the idea of having the
name of the application
itself
and not a unique keyword because it's not
easy to have filters in the
mail
client for all the names of the applications on
contrib (I cannot imagine
how I would create these filters). With a single keyword filters are
easier
to do.
Let's please decide quickly on this, because I see there is already
contrib
related activity that I am missing...
Thanks,
Anca
On Mon, Apr 25, 2016 at 12:27 PM, Eduard Moraru <enygma2002(a)gmail.com>
wrote:
> On Fri, Apr 8, 2016 at 1:00 PM, Vincent Massol <vincent(a)massol.net>
wrote:
>
> > Hi,
> >
> > > On 08 Apr 2016, at 11:43, Anca Luca <lucaa(a)xwiki.com> 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
> > devs(a)xwiki.org
> > > (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 devs(a)xwiki.org 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 contrib(a)xwiki.org
> > 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: "users(a)xwiki.org
: For questions about using
XWiki,
> > using the XWiki API, suggestions for
improvements, ideas, etc.”
> >
> >
> > > 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.
> >
> > > 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.
> >
>
> IMO contrib devs should be up to date with the changes in the platform
and
> we should keep the communication tight with
the platform. As we can see,
> many topics on contrib apps trace down to the platform and vice-versa.
>
> It would also not be very helpful for the project/community to do such a
> segregation, so I agree with Vincent.
>
> Since we are talking about contrib (which are devs and which have a
guide
> to follow), as Thomas suggested, it would be
a helpful idea to mention
the
> app in the subject so that we can apply
filters in the mail client,
should
we need
them.
Thanks,
Eduard
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Thanks
-Vincent
> Anca
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
4 May
4 May
2:32 p.m.
New subject: [xwiki-devs] [Proposal] Add mechanism to allow following only contrib related mails
On Wed, Apr 27, 2016 at 5:41 PM, Anca Luca <lucaa(a)xwiki.com> wrote:
+1 for [Contrib][<Project>]
+1
On Wed, Apr 27, 2016 at 2:42 PM, Thomas Mortagne <
thomas.mortagne(a)xwiki.com>
wrote:
differentiate
[Contrib]
would
see,
--
Thomas Mortagne
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Then [Contrib][<Project>] I guess.
On Wed, Apr 27, 2016 at 1:59 PM, Anca Luca <lucaa(a)xwiki.com> wrote:
imagine
Actually I don't like the idea of having the
name of the application
itself
and not a unique keyword because it's not
easy to have filters in the
mail
> client for all the names of the applications on contrib (I cannot how I
would create these filters). With a single keyword filters are
easier
to do.
Let's please decide quickly on this, because I see there is already
contrib
related activity that I am missing...
Thanks,
Anca
On Mon, Apr 25, 2016 at 12:27 PM, Eduard Moraru <enygma2002(a)gmail.com>
wrote:
> On Fri, Apr 8, 2016 at 1:00 PM, Vincent Massol <vincent(a)massol.net>
wrote:
>
> > Hi,
> >
> > > On 08 Apr 2016, at 11:43, Anca Luca <lucaa(a)xwiki.com> 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
> > devs(a)xwiki.org
> > > (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 > >
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 devs(a)xwiki.org 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 contrib(a)xwiki.org
> > 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: "users(a)xwiki.org
: For questions about using
XWiki,
> > using the XWiki API, suggestions for
improvements, ideas, etc.”
> >
> >
> > > 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. 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.
>> >
>> > > 4/ any other technical solution that I didn't think about that
>> > 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.
> >
>
> IMO contrib devs should be up to date with the changes in the platform
and
>> we should keep the communication tight with the platform. As we can >> many topics on contrib apps trace down
to the platform and vice-versa.
>>
>> It would also not be very helpful for the project/community to do
such a
>
segregation, so I agree with Vincent.
>
> Since we are talking about contrib (which are devs and which have a
guide
> to follow), as Thomas suggested, it would be
a helpful idea to mention
the
> app in the subject so that we can apply
filters in the mail client,
should
we need
them.
Thanks,
Eduard
>
> Thanks
> -Vincent
>
> > Anca
>
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
9:23 p.m.
New subject: [xwiki-devs] [Proposal] Add mechanism to allow following only contrib related mails
-0 (leaning more towards -1) since the focus should be on the extension and
not on the fact that it`s a contrib project. I really see no constructive
point generally in following "contrib-only" discussions and it`s something
that I`d personally prefer not to encourage. If you are interested in a
particular extension or a particular list of extensions, then it should be
easy to make a filter only for those keywords.
I do not support creating a community-wise segregation in any way between
the development of the XWiki core and its extensions, either explicit
(through a separate discussion list) or implicit (by differentiating core
discussions from extensions or the other way around). I find it already
hard enough to build a community, as it is.
Thanks,
Eduard
On Wed, May 4, 2016 at 3:32 PM, Marius Dumitru Florea <
mariusdumitru.florea(a)xwiki.com> wrote:
On Wed, Apr 27, 2016 at 5:41 PM, Anca Luca
<lucaa(a)xwiki.com> wrote:
to
would
> >> > allow
> >> > > to automatically decide if a mail is about contrib or not,
without
think
vice-versa.
mention
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
+1 for [Contrib][<Project>]
+1
On Wed, Apr 27, 2016 at 2:42 PM, Thomas Mortagne <
thomas.mortagne(a)xwiki.com>
wrote:
enygma2002(a)gmail.com>
Then [Contrib][<Project>] I guess.
On Wed, Apr 27, 2016 at 1:59 PM, Anca Luca <lucaa(a)xwiki.com> wrote:
imagine
> > how I would create these filters). With a single keyword filters are
> easier
> > to do.
> >
> > Let's please decide quickly on this, because I see there is already
> contrib
> > related activity that I am missing...
> >
> > Thanks,
> > Anca
> >
> > On Mon, Apr 25, 2016 at 12:27 PM, Eduard Moraru < Actually I don't like the idea of having the
name of the application
itself
and not a unique keyword because it's not
easy to have filters in the
mail
> client for all the names of the applications on contrib (I cannot > > wrote:
> >
> >> On Fri, Apr 8, 2016 at 1:00 PM, Vincent Massol <vincent(a)massol.net>
> wrote:
> >>
> >> > Hi,
> >> >
> >> > > On 08 Apr 2016, at 11:43, Anca Luca <lucaa(a)xwiki.com>
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
> >> > devs(a)xwiki.org
> >> > > (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 devs(a)xwiki.org
> 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
contrib(a)xwiki.org
> >> > 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: "users(a)xwiki.org : For questions about using
> XWiki,
> >> > using the XWiki API, suggestions for improvements, ideas, etc.”
> >> >
> >> >
> >> > > 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.
>> >
>> > > 4/ any other technical solution that I didn't think about that
>>
> 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 > 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.
> >> >
> >>
> >> IMO contrib devs should be up to date with the changes in the
platform
and
>> we should keep the communication tight with the platform. As we can
see,
> >> many topics on contrib apps trace down to the platform and >>
>> It would also not be very helpful for the project/community to do
such a
> >> segregation, so I agree with Vincent.
> >>
> >> Since we are talking about contrib (which are devs and which have a
> guide
> >> to follow), as Thomas suggested, it would be a helpful idea to the
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
> app in the subject so that we can apply
filters in the mail client,
should
> we need them.
>
> Thanks,
> Eduard
>
>
> >
> > Thanks
> > -Vincent
> >
> > > Anca
> >
> > _______________________________________________
> > devs mailing list
> > devs(a)xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/devs
> >
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
3057
days inactive
3083
days old
8 comments
5 participants
participants (5)
-
Anca Luca -
Eduard Moraru -
Marius Dumitru Florea -
Thomas Mortagne -
Vincent Massol