[jira] [Updated] (COMDEV-319) Use Whimsy JSON data instead of ldapsearch

[Shane Curcuru (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shane Curcuru updated COMDEV-319:
-
Attachment: (was: ADCLK854.pdf)

> Use Whimsy JSON data instead of ldapsearch
> --
>
> Key: COMDEV-319
> URL: https://issues.apache.org/jira/browse/COMDEV-319
> Project: Community Development
>  Issue Type: Task
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Minor
>
> Most of reporter.a.o uses the Whimsy JSON data files rather than ldapsearch.
> Should fix addrelease.py and jiraversions.py to do likewise.
> (This would have avoided COMDEV-318)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Updated] (COMDEV-319) Use Whimsy JSON data instead of ldapsearch

[Shane Curcuru (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shane Curcuru updated COMDEV-319:
-
Attachment: (was: -Bose Connect-.htm)

> Use Whimsy JSON data instead of ldapsearch
> --
>
> Key: COMDEV-319
> URL: https://issues.apache.org/jira/browse/COMDEV-319
> Project: Community Development
>  Issue Type: Task
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Minor
>
> Most of reporter.a.o uses the Whimsy JSON data files rather than ldapsearch.
> Should fix addrelease.py and jiraversions.py to do likewise.
> (This would have avoided COMDEV-318)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Issue Comment Deleted] (COMDEV-319) Use Whimsy JSON data instead of ldapsearch

[Shane Curcuru (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shane Curcuru updated COMDEV-319:
-
Comment: was deleted

(was: This is fine.but some little bit confused )

> Use Whimsy JSON data instead of ldapsearch
> --
>
> Key: COMDEV-319
> URL: https://issues.apache.org/jira/browse/COMDEV-319
> Project: Community Development
>  Issue Type: Task
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Minor
>
> Most of reporter.a.o uses the Whimsy JSON data files rather than ldapsearch.
> Should fix addrelease.py and jiraversions.py to do likewise.
> (This would have avoided COMDEV-318)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [VOTE] Create a mailinglist for intra-project communication

[Lars Francke]

+1 on c)

On Fri, Jun 7, 2019 at 3:51 PM Christofer Dutz 
wrote:

> Hi all,
>
> I would like to propose to introduce a new mailing-list for intra-project
> communication.
> As it is my primary goal to help communication in the IoT field at Apache
> I would like your votes on this.
>
> As we have the option to create a general purpose list (tech@) or a
> topic-dependent one (iot@) you don’t have the usual +1, 0 and -1, but a),
> b) and c)
>
> a) no new list
> b) create a tech@a.o list that's expected to be used with
> [subject][line][tags] only
> c) create an iot@a.o list
>
> The vote will stay open for the normal 72 hours.
>
> Chris
>

AW: [VOTE] Create a mailinglist for intra-project communication

[Julian Feinauer]

C) and I also. Volunteer for moderation as this concern was raised.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: [VOTE] Create a mailinglist for intra-project communication
Von: Naomi S
An: ComDev
Cc:

my mistake, Christofer. I didn't spot that it had been re-started with a
new discussion

> b) create a tech@a.o list that's expected to be used
with [subject][line][tags] only

-1 without a moderation team including multiple ComDev PMC members

> c) create an iot@a.o list

-1 for now because we only have one volunteer to moderate this list

additionally, if this is under ComDev's purview, I would like at least one
moderator from the PMC

naturally, I will change this to a +1 if we get volunteers :)


On Fri, 7 Jun 2019 at 16:57, Andrew Garza  wrote:

> C)
>
> On Fri, Jun 7, 2019, 10:50 AM Christofer Dutz 
> wrote:
>
> > Then please just read the other lengthy thread on this list. We have had
> > multiple iterations of discussions about this and there was a general
> > consensus on establishing A list, this vote should settle the discussion
> > about which option to take.
> >
> > Chris
> >
> > Outlook für Android herunterladen
> >
> > 
> > From: Naomi S 
> > Sent: Friday, June 7, 2019 4:45:14 PM
> > To: ComDev
> > Subject: Re: [VOTE] Create a mailinglist for intra-project communication
> >
> > On Fri, 7 Jun 2019 at 16:41, Naomi S  wrote:
> >
> > >
> > > consensus building should be used before any options are tabled for
> > voting
> > >
> >
> >  "tabled" in the British English sense! (i.e., put forward)
> >
> > (thanks Joan...)
> >
>

[jira] [Updated] (COMDEV-319) Use Whimsy JSON data instead of ldapsearch

[Qhoriyah yusri (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Qhoriyah yusri updated COMDEV-319:
--
Attachment: ADCLK854.pdf

> Use Whimsy JSON data instead of ldapsearch
> --
>
> Key: COMDEV-319
> URL: https://issues.apache.org/jira/browse/COMDEV-319
> Project: Community Development
>  Issue Type: Task
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Minor
> Attachments: -Bose Connect-.htm, ADCLK854.pdf
>
>
> Most of reporter.a.o uses the Whimsy JSON data files rather than ldapsearch.
> Should fix addrelease.py and jiraversions.py to do likewise.
> (This would have avoided COMDEV-318)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Updated] (COMDEV-319) Use Whimsy JSON data instead of ldapsearch

[Qhoriyah yusri (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Qhoriyah yusri updated COMDEV-319:
--
Attachment: -Bose Connect-.htm

> Use Whimsy JSON data instead of ldapsearch
> --
>
> Key: COMDEV-319
> URL: https://issues.apache.org/jira/browse/COMDEV-319
> Project: Community Development
>  Issue Type: Task
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Minor
> Attachments: -Bose Connect-.htm
>
>
> Most of reporter.a.o uses the Whimsy JSON data files rather than ldapsearch.
> Should fix addrelease.py and jiraversions.py to do likewise.
> (This would have avoided COMDEV-318)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Commented] (COMDEV-319) Use Whimsy JSON data instead of ldapsearch

[Qhoriyah yusri (JIRA)]

[ 
https://issues.apache.org/jira/browse/COMDEV-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858786#comment-16858786
 ] 

Qhoriyah yusri commented on COMDEV-319:
---

This is fine.but some little bit confused 

> Use Whimsy JSON data instead of ldapsearch
> --
>
> Key: COMDEV-319
> URL: https://issues.apache.org/jira/browse/COMDEV-319
> Project: Community Development
>  Issue Type: Task
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Minor
>
> Most of reporter.a.o uses the Whimsy JSON data files rather than ldapsearch.
> Should fix addrelease.py and jiraversions.py to do likewise.
> (This would have avoided COMDEV-318)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [VOTE] Create a mailinglist for intra-project communication

[sebb]

On Fri, 7 Jun 2019 at 16:29, Naomi S  wrote:
>
> my mistake, Christofer. I didn't spot that it had been re-started with a
> new discussion
>
> > b) create a tech@a.o list that's expected to be used
> with [subject][line][tags] only
>
> -1 without a moderation team including multiple ComDev PMC members
>
> > c) create an iot@a.o list
>
> -1 for now because we only have one volunteer to moderate this list
>
> additionally, if this is under ComDev's purview, I would like at least one
> moderator from the PMC
>
> naturally, I will change this to a +1 if we get volunteers :)
>

Note that moderators are normally only needed for posts from people
who have not yet subscribed.
If the moderator accepts and allows the post, then future posts from
the same email won't need moderation.

If the lists are subscriber post only (as suggested earlier), then
moderators are only needed to deal with bad posters.

However if you want total control over subject matter and body content
then the list can be set up like announce@, i.e. all posts have to be
moderated.
That would be a lot of work.

> On Fri, 7 Jun 2019 at 16:57, Andrew Garza  wrote:
>
> > C)
> >
> > On Fri, Jun 7, 2019, 10:50 AM Christofer Dutz 
> > wrote:
> >
> > > Then please just read the other lengthy thread on this list. We have had
> > > multiple iterations of discussions about this and there was a general
> > > consensus on establishing A list, this vote should settle the discussion
> > > about which option to take.
> > >
> > > Chris
> > >
> > > Outlook für Android herunterladen
> > >
> > > 
> > > From: Naomi S 
> > > Sent: Friday, June 7, 2019 4:45:14 PM
> > > To: ComDev
> > > Subject: Re: [VOTE] Create a mailinglist for intra-project communication
> > >
> > > On Fri, 7 Jun 2019 at 16:41, Naomi S  wrote:
> > >
> > > >
> > > > consensus building should be used before any options are tabled for
> > > voting
> > > >
> > >
> > >  "tabled" in the British English sense! (i.e., put forward)
> > >
> > > (thanks Joan...)
> > >
> >

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Introducing lists based on the overall project categories?

[Bertrand Delacretaz]

Hi Alex,

On Fri, Jun 7, 2019 at 6:03 PM Alex Harui  wrote:
> ...Does the ASF have an example of a cross-project list that failed?...

I cannot remember that - I pointed to Stefano's Law of Busy Lists as a
reason to create a single tech@ list as opposed to multiple ones for
smaller audiences.

-Bertrand

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Introducing lists based on the overall project categories?

[Alex Harui]

Hi Bertrand,

Your link took me to a post about splitting lists because some list is busy, 
but AIUI, this proposal for iot@ is to communicate between related projects.  
Does the ASF have an example of a cross-project list that failed?

Thanks,
-Alex

On 6/7/19, 4:34 AM, "Bertrand Delacretaz"  wrote:

On Fri, Jun 7, 2019 at 12:48 PM Christofer Dutz
 wrote:
> ...For me it looks as if tech@ would be one huge list ...

It *might* eventually become large, then big, then huge...but like
everything it will start small.

If it does indeed grow, it *might* be fine to farm out specific busy
topics to their own lists.

Until then, a single list is the best way to create momentum around a
place to have cross-cutting technical discussions at the ASF.

I think I've exposed my position, multiple times so I'll stop now and
as mentioned whoever does the work decides.

Please just keep the Wisdom Of The
Elders in mind, as reported at

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgrep.codeconsult.ch%2F2011%2F12%2F06%2Fstefanos-mazzocchis-busy-list-pattern%2Fdata=02%7C01%7Caharui%40adobe.com%7Cd4a971a7b8914177060c08d6eb3c0d32%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636955040515183248sdata=dHSIBSpDbUNxaXn2mFx1DfznQfYvEgLpMWXMq8OsrOQ%3Dreserved=0
(blog post of mine based on content provided by Stefano Mazzocchi’s,
Apache Cocoon's original author)

-Bertrand

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [VOTE] Create a mailinglist for intra-project communication

[Bertrand Delacretaz]

On Fri, Jun 7, 2019 at 3:51 PM Christofer Dutz
 wrote:
...
> b) create a tech@a.o list that's expected to be used with
> [subject][line][tags] only ...

+1 and I volunteer as a moderator.

-Bertrand

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [VOTE] Create a mailinglist for intra-project communication

[Bertrand Delacretaz]

Hi,

On Fri, Jun 7, 2019 at 4:50 PM Christofer Dutz
 wrote:
> A list, this vote should settle the discussion about which option to 
> take...

FWIW as I have said, whoever does the work decide - so if you and a
few others from the comdev PMC (I'd say 2-3 moderators are needed) are
willing to oversee a list I'm fine with it being created. With the
risk that the comdev PMC would shut it down if moderators stop being
active.

I do volunteer to moderate a list if it's based on option b)

I'm not competent for an iot list so cannot help with option c)

-Bertrand

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [VOTE] Create a mailinglist for intra-project communication

[Naomi S]

my mistake, Christofer. I didn't spot that it had been re-started with a
new discussion

> b) create a tech@a.o list that's expected to be used
with [subject][line][tags] only

-1 without a moderation team including multiple ComDev PMC members

> c) create an iot@a.o list

-1 for now because we only have one volunteer to moderate this list

additionally, if this is under ComDev's purview, I would like at least one
moderator from the PMC

naturally, I will change this to a +1 if we get volunteers :)


On Fri, 7 Jun 2019 at 16:57, Andrew Garza  wrote:

> C)
>
> On Fri, Jun 7, 2019, 10:50 AM Christofer Dutz 
> wrote:
>
> > Then please just read the other lengthy thread on this list. We have had
> > multiple iterations of discussions about this and there was a general
> > consensus on establishing A list, this vote should settle the discussion
> > about which option to take.
> >
> > Chris
> >
> > Outlook für Android herunterladen
> >
> > 
> > From: Naomi S 
> > Sent: Friday, June 7, 2019 4:45:14 PM
> > To: ComDev
> > Subject: Re: [VOTE] Create a mailinglist for intra-project communication
> >
> > On Fri, 7 Jun 2019 at 16:41, Naomi S  wrote:
> >
> > >
> > > consensus building should be used before any options are tabled for
> > voting
> > >
> >
> >  "tabled" in the British English sense! (i.e., put forward)
> >
> > (thanks Joan...)
> >
>

Re: [VOTE] Create a mailinglist for intra-project communication

[Andrew Garza]

C)

On Fri, Jun 7, 2019, 10:50 AM Christofer Dutz 
wrote:

> Then please just read the other lengthy thread on this list. We have had
> multiple iterations of discussions about this and there was a general
> consensus on establishing A list, this vote should settle the discussion
> about which option to take.
>
> Chris
>
> Outlook für Android herunterladen
>
> 
> From: Naomi S 
> Sent: Friday, June 7, 2019 4:45:14 PM
> To: ComDev
> Subject: Re: [VOTE] Create a mailinglist for intra-project communication
>
> On Fri, 7 Jun 2019 at 16:41, Naomi S  wrote:
>
> >
> > consensus building should be used before any options are tabled for
> voting
> >
>
>  "tabled" in the British English sense! (i.e., put forward)
>
> (thanks Joan...)
>

Re: [VOTE] Create a mailinglist for intra-project communication

[Christofer Dutz]

Then please just read the other lengthy thread on this list. We have had 
multiple iterations of discussions about this and there was a general consensus 
on establishing A list, this vote should settle the discussion about which 
option to take.

Chris

Outlook für Android herunterladen


From: Naomi S 
Sent: Friday, June 7, 2019 4:45:14 PM
To: ComDev
Subject: Re: [VOTE] Create a mailinglist for intra-project communication

On Fri, 7 Jun 2019 at 16:41, Naomi S  wrote:

>
> consensus building should be used before any options are tabled for voting
>

 "tabled" in the British English sense! (i.e., put forward)

(thanks Joan...)

Re: [VOTE] Create a mailinglist for intra-project communication

[Naomi S]

On Fri, 7 Jun 2019 at 16:41, Naomi S  wrote:

>
> consensus building should be used before any options are tabled for voting
>

 "tabled" in the British English sense! (i.e., put forward)

(thanks Joan...)

Re: [VOTE] Create a mailinglist for intra-project communication

[Naomi S]

On Fri, 7 Jun 2019 at 15:52, Christofer Dutz 
wrote:

> Hi all,
>
> I would like to propose to introduce a new mailing-list for intra-project
> communication.
>

I think we should be cautious about creating new foundation-wide lists.
unless there's an existing group or activity that the list serves, I expect
that it's hard to get critical mass to make the list useful

the recent creation of diversity@ made sense, for example, because a
specific group of people (rather miraculously) emerged who would use the
list. I think it would have not worked to create the diversity@ list first
and then invite people to join it. if that makes sense?

horse before the cart, etc, etc

for intra-project communication, is there a reason why copying multiple
project-specific lists is not a viable option?


> As it is my primary goal to help communication in the IoT field at Apache
> I would like your votes on this.
>

I absolutely do not want to contribute stop energy to your efforts here.
having said that, I lack the context behind this proposal. has there been a
discussion somewhere else about this? i.e., are multiple IoT related
projects requesting one?


> b) create a tech@a.o list that's expected to be used with
> [subject][line][tags] only
>

I can't weigh in on (a) or (c) without more information. but (b) seems to
be unrelated to this proposal. is there a feeling that enough people would
subscribe to a gene...@apache.org type list to make it useful?

honestly, my initial concern is community management. who is going to
moderate that list? (specifically, and at a minimum, making sure people
abide by our Code of Conduct). project communities, and their associated
lists, small as they are, can be exhausting to manage. how much more
challenging would that be for a foundation-wide list. and who would do it?


> The vote will stay open for the normal 72 hours.
>

I think it was premature to start a vote. voting is the failure mode of
discussion :)

if you are sure that what you want to do is okay, you can just inform the
list and wait for lazy consensus (i.e., no objections). if a discussion is
started, then consensus building should be used before any options are
tabled for voting

Re: [VOTE] Create a mailinglist for intra-project communication

[Christofer Dutz]

c)

Chris

Outlook für Android herunterladen


From: Qhoriyah Yusri 
Sent: Friday, June 7, 2019 4:20:55 PM
To: dev@community.apache.org
Subject: Re: [VOTE] Create a mailinglist for intra-project communication

Pada Jum, 7 Jun 2019 9:51 PM Christofer Dutz 
menulis:

> Hi all,
>
> I would like to propose to introduce a new mailing-list for intra-project
> communication.
> As it is my primary goal to help communication in the IoT field at Apache
> I would like your votes on this.
>
> As we have the option to create a general purpose list (tech@) or a
> topic-dependent one (iot@) you don’t have the usual +1, 0 and -1, but a),
> b) and c)
>
> a) no new list
> b) create a tech@a.o list that's expected to be used with
> [subject][line][tags] only
> c) create an iot@a.o list
>
> The vote will stay open for the normal 72 hours.
>
> Chris
>

Re: [VOTE] Create a mailinglist for intra-project communication

[Qhoriyah Yusri]

Pada Jum, 7 Jun 2019 9:51 PM Christofer Dutz 
menulis:

> Hi all,
>
> I would like to propose to introduce a new mailing-list for intra-project
> communication.
> As it is my primary goal to help communication in the IoT field at Apache
> I would like your votes on this.
>
> As we have the option to create a general purpose list (tech@) or a
> topic-dependent one (iot@) you don’t have the usual +1, 0 and -1, but a),
> b) and c)
>
> a) no new list
> b) create a tech@a.o list that's expected to be used with
> [subject][line][tags] only
> c) create an iot@a.o list
>
> The vote will stay open for the normal 72 hours.
>
> Chris
>

[VOTE] Create a mailinglist for intra-project communication

[Christofer Dutz]

Hi all,

I would like to propose to introduce a new mailing-list for intra-project 
communication.
As it is my primary goal to help communication in the IoT field at Apache I 
would like your votes on this.

As we have the option to create a general purpose list (tech@) or a 
topic-dependent one (iot@) you don’t have the usual +1, 0 and -1, but a), b) 
and c)

a) no new list
b) create a tech@a.o list that's expected to be used with
[subject][line][tags] only
c) create an iot@a.o list

The vote will stay open for the normal 72 hours.

Chris

Re: Introducing lists based on the overall project categories?

[sebb]

On Fri, 7 Jun 2019 at 12:58, Christofer Dutz  wrote:
>
> Hi Bertrand,
>
> There was a discussion about subscription only lists ... is that possible?

Yes, that can be requested.

A bit more work for contributors up front, but less work for moderators.

To forestall questions, I recommend explaining the choice (and why it
was made) on the page that advertises the list.

> But I think if I sign up as moderator for c) I would probably start writing a 
> moderation-bot
> as soon as I get more than 2 moderation emails with the same title in the 
> payload:
>
> -> decline all of them __
>
> Chris
>
> Am 07.06.19, 13:52 schrieb "Bertrand Delacretaz" :
>
> Hi Chris,
>
> On Fri, Jun 7, 2019 at 1:44 PM Christofer Dutz
>  wrote:
> > ...So I guess we'll just vote on it ... do we have 2-way votes?..
>
> You can setup any poll or vote that works, I'd say
>
> a) no new list
> b) create a tech@a.o list that's expected to be used with
> [subject][line][tags] only
> c) create an iot@a.o list
>
> Keep in mind that the comdev PMC will own any new list, so you'll need
> volunteers to moderate them. I would volunteer but for b) only ;-)
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Introducing lists based on the overall project categories?

[Rich Bowen]

On 6/7/19 3:26 AM, Bertrand Delacretaz wrote:

Hi Chris,

On Thu, Jun 6, 2019 at 4:02 PM Christofer Dutz
  wrote:

...I would really like to create an...@apache.org  mailinglist...

Allow me to insist;-)

What's wrong with an [iot] subject line tag on at...@apache.org  mailing list?


I've heard of this tech@ list, but never subscribed. I just went looking 
for it, to see what traffic was like, and it is not listed on 
lists.apache.org . Is this a theoretical list, or an actual one?


--
Rich Bowen - rbo...@rcbowen.com
http://rcbowen.com/
@rbowen

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Introducing lists based on the overall project categories?

[Christofer Dutz]

Hi Bertrand,

There was a discussion about subscription only lists ... is that possible?

But I think if I sign up as moderator for c) I would probably start writing a 
moderation-bot 
as soon as I get more than 2 moderation emails with the same title in the 
payload: 

-> decline all of them __

Chris

Am 07.06.19, 13:52 schrieb "Bertrand Delacretaz" :

Hi Chris,

On Fri, Jun 7, 2019 at 1:44 PM Christofer Dutz
 wrote:
> ...So I guess we'll just vote on it ... do we have 2-way votes?..

You can setup any poll or vote that works, I'd say

a) no new list
b) create a tech@a.o list that's expected to be used with
[subject][line][tags] only
c) create an iot@a.o list

Keep in mind that the comdev PMC will own any new list, so you'll need
volunteers to moderate them. I would volunteer but for b) only ;-)

-Bertrand

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Introducing lists based on the overall project categories?

[Bertrand Delacretaz]

Hi Chris,

On Fri, Jun 7, 2019 at 1:44 PM Christofer Dutz
 wrote:
> ...So I guess we'll just vote on it ... do we have 2-way votes?..

You can setup any poll or vote that works, I'd say

a) no new list
b) create a tech@a.o list that's expected to be used with
[subject][line][tags] only
c) create an iot@a.o list

Keep in mind that the comdev PMC will own any new list, so you'll need
volunteers to moderate them. I would volunteer but for b) only ;-)

-Bertrand

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Introducing lists based on the overall project categories?

[Christofer Dutz]

I Bertrand,

Well I still think that I personally would rather sign up to an
i...@apache.org mailinglist than to a t...@apache.org one.
So I guess we'll just vote on it ... do we have 2-way votes? 

Sort of:

-1: No: don't want any list
+T: Yes, but want a tech-list
+I: Yes, but want an IoT-list

Chris

Am 07.06.19, 13:33 schrieb "Bertrand Delacretaz" :

On Fri, Jun 7, 2019 at 12:48 PM Christofer Dutz
 wrote:
> ...For me it looks as if tech@ would be one huge list ...

It *might* eventually become large, then big, then huge...but like
everything it will start small.

If it does indeed grow, it *might* be fine to farm out specific busy
topics to their own lists.

Until then, a single list is the best way to create momentum around a
place to have cross-cutting technical discussions at the ASF.

I think I've exposed my position, multiple times so I'll stop now and
as mentioned whoever does the work decides.

Please just keep the Wisdom Of The
Elders in mind, as reported at

https://grep.codeconsult.ch/2011/12/06/stefanos-mazzocchis-busy-list-pattern/
(blog post of mine based on content provided by Stefano Mazzocchi’s,
Apache Cocoon's original author)

-Bertrand

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Introducing lists based on the overall project categories?

[Bertrand Delacretaz]

On Fri, Jun 7, 2019 at 12:48 PM Christofer Dutz
 wrote:
> ...For me it looks as if tech@ would be one huge list ...

It *might* eventually become large, then big, then huge...but like
everything it will start small.

If it does indeed grow, it *might* be fine to farm out specific busy
topics to their own lists.

Until then, a single list is the best way to create momentum around a
place to have cross-cutting technical discussions at the ASF.

I think I've exposed my position, multiple times so I'll stop now and
as mentioned whoever does the work decides.

Please just keep the Wisdom Of The
Elders in mind, as reported at
https://grep.codeconsult.ch/2011/12/06/stefanos-mazzocchis-busy-list-pattern/
(blog post of mine based on content provided by Stefano Mazzocchi’s,
Apache Cocoon's original author)

-Bertrand

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Introducing lists based on the overall project categories?

[Christofer Dutz]

Hi Bertrand,

For me it looks as if tech@ would be one huge list ... 
and the amount of emails of interest to me would be only a fraction.
Having named topic lists would help focus. 
It would allow to skim the topics and react on the ones of interest.

Guess a tech-list would just feel like being on one of those project lists,
Here they do most discussions in guthub pull-requests and who's mailinglists 
have almost no emails of interest anymore or I just can't find them in 
between 1000 of bot emails.

Chris



Am 07.06.19, 09:26 schrieb "Bertrand Delacretaz" :

Hi Chris,

On Thu, Jun 6, 2019 at 4:02 PM Christofer Dutz
 wrote:
> ...I would really like to create an i...@apache.org mailinglist...

Allow me to insist ;-)

What's wrong with an [iot] subject line tag on a t...@apache.org mailing 
list?

The problem with single-topic lists is that discussions are rarely
single-topic: if you have a question about memory leaks in Java in a
Docker image that runs in an iot context, and we have multiple
java|docker|memorymanagement|iot lists, where are you going to post?

Cross-posting is ugly...writing to t...@apache.org with
[java][memory][docker][iot] subject line tags will work, and having a
single list will help get critical mass about "the place where Apache
community members discuss cross-cutting technical issues".

But whoever does the work decides...

-Bertrand

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Introducing lists based on the overall project categories?

[Lars Francke]

We can have both. And if we can have only one thing I'm in favor of the
project category list that Chris suggested.

If we have one huge list it'll just mean more mails etc., people having to
set up filters or skip over stuff they are not interested in.

I can imagine a single bigdata@ list to be super useful for coordination
between all those scattered projects: <
https://projects.apache.org/projects.html?category> (hadoop has its own
category there, a bit confusing)



On Fri, Jun 7, 2019 at 9:26 AM Bertrand Delacretaz 
wrote:

> Hi Chris,
>
> On Thu, Jun 6, 2019 at 4:02 PM Christofer Dutz
>  wrote:
> > ...I would really like to create an i...@apache.org mailinglist...
>
> Allow me to insist ;-)
>
> What's wrong with an [iot] subject line tag on a t...@apache.org mailing
> list?
>
> The problem with single-topic lists is that discussions are rarely
> single-topic: if you have a question about memory leaks in Java in a
> Docker image that runs in an iot context, and we have multiple
> java|docker|memorymanagement|iot lists, where are you going to post?
>
> Cross-posting is ugly...writing to t...@apache.org with
> [java][memory][docker][iot] subject line tags will work, and having a
> single list will help get critical mass about "the place where Apache
> community members discuss cross-cutting technical issues".
>
> But whoever does the work decides...
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Introducing lists based on the overall project categories?

[Bertrand Delacretaz]

Hi Chris,

On Thu, Jun 6, 2019 at 4:02 PM Christofer Dutz
 wrote:
> ...I would really like to create an i...@apache.org mailinglist...

Allow me to insist ;-)

What's wrong with an [iot] subject line tag on a t...@apache.org mailing list?

The problem with single-topic lists is that discussions are rarely
single-topic: if you have a question about memory leaks in Java in a
Docker image that runs in an iot context, and we have multiple
java|docker|memorymanagement|iot lists, where are you going to post?

Cross-posting is ugly...writing to t...@apache.org with
[java][memory][docker][iot] subject line tags will work, and having a
single list will help get critical mass about "the place where Apache
community members discuss cross-cutting technical issues".

But whoever does the work decides...

-Bertrand

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org