You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by Bertrand Delacretaz <bd...@apache.org> on 2013/05/07 15:19:53 UTC

tech@apache.org ?

Hi,

We don't seem to have a place for cross-cutting technical discussions
at the ASF - language and system issues, standards implementations,
etc.

To fix this, I suggest creating a public tech@apache.org list, owned
by comdev, with the following rules:

-Technical discussions on cross-cutting topics that are directly
related to Apache projects

-Each new thread MUST have one or several [markers] in the subject
line to identify the topics. For example, [java], [osgi], [linux] etc.

I volunteer to get the list started, as an experiment.

WDYT?
-Bertrand

Re: tech@apache.org ?

Posted by Shashi Shailaj <sh...@gmail.com>.
Appears to be a great idea.


On Tue, May 7, 2013 at 6:49 PM, Bertrand Delacretaz
<bd...@apache.org>wrote:

> Hi,
>
> We don't seem to have a place for cross-cutting technical discussions
> at the ASF - language and system issues, standards implementations,
> etc.
>
> To fix this, I suggest creating a public tech@apache.org list, owned
> by comdev, with the following rules:
>
> -Technical discussions on cross-cutting topics that are directly
> related to Apache projects
>
> -Each new thread MUST have one or several [markers] in the subject
> line to identify the topics. For example, [java], [osgi], [linux] etc.
>
> I volunteer to get the list started, as an experiment.
>
> WDYT?
> -Bertrand
>

Re: tech@apache.org ?

Posted by Ulrich Stärk <ul...@spielviel.de>.
+0

I'm not against it but I don't actively support it either. Do you know release-discuss@? That was
meant as a cross-project list for discussing release issues and has seen seven threads within the
last three years with the last one from march last year (excluding cross-list announcements). I fear
that any cross-project technical list will face the same fate. But go ahead and try ;)

Uli

On 07.05.2013 15:19, Bertrand Delacretaz wrote:
> Hi,
> 
> We don't seem to have a place for cross-cutting technical discussions
> at the ASF - language and system issues, standards implementations,
> etc.
> 
> To fix this, I suggest creating a public tech@apache.org list, owned
> by comdev, with the following rules:
> 
> -Technical discussions on cross-cutting topics that are directly
> related to Apache projects
> 
> -Each new thread MUST have one or several [markers] in the subject
> line to identify the topics. For example, [java], [osgi], [linux] etc.
> 
> I volunteer to get the list started, as an experiment.
> 
> WDYT?
> -Bertrand
> 

Re: tech@apache.org ?

Posted by Noah Slater <ns...@apache.org>.
It would be a shame to scrap the idea because we are presuming the worst in
everyone. That seems very anti-ASF to me. A better approach might be to
appoint "social" moderators (i.e. gate keepers of the civility) that reign
the conversation back in if and when things go off-track.

Also, we do have a code of conduct, ala Ubuntu:

https://svn.apache.org/repos/private/committers/voluntary-code-of-conduct.txt


On 7 May 2013 17:34, Marvin Humphrey <ma...@rectangular.com> wrote:

> On Tue, May 7, 2013 at 6:19 AM, Bertrand Delacretaz
> <bd...@apache.org> wrote:
> > WDYT?
>
> I'm skeptical that it will work out well.  I'd expect the list to descend
> into
> shouting matches between warring tribes and to end up as an echo chamber
> dominated by the faction which can generate the greatest volume of email.
>
> On our dev lists, people have a tangible product to keep discussions
> grounded.
> Contributors are invested in what gets committed to the repository, and
> conversations are directed towards achieving a negotiated end.
>  Participants
> in the proposed general "tech" list won't be united by any such common
> goal.
>
> In addition, Apache has only weak traditions encouraging civility -- by
> design, in order to protect gadflies and encourage innovation through
> conflict
> -- and many abrasive people, from the bottom of the organization to the top
> and going back to the foundation's earliest days.  There's no "code of
> conduct" a la Ubuntu, and even if a core group of tech@ subscribers starts
> off by trying to establish a civil norm, they will be swimming against the
> current.
>
> On the other hand, if you're looking to create a list which might make
> members@ look pleasant by comparison, this could do the trick.
>
> Marvin Humphrey
>



-- 
NS

Re: tech@apache.org ?

Posted by Marvin Humphrey <ma...@rectangular.com>.
On Tue, May 7, 2013 at 6:19 AM, Bertrand Delacretaz
<bd...@apache.org> wrote:
> WDYT?

I'm skeptical that it will work out well.  I'd expect the list to descend into
shouting matches between warring tribes and to end up as an echo chamber
dominated by the faction which can generate the greatest volume of email.

On our dev lists, people have a tangible product to keep discussions grounded.
Contributors are invested in what gets committed to the repository, and
conversations are directed towards achieving a negotiated end.  Participants
in the proposed general "tech" list won't be united by any such common goal.

In addition, Apache has only weak traditions encouraging civility -- by
design, in order to protect gadflies and encourage innovation through conflict
-- and many abrasive people, from the bottom of the organization to the top
and going back to the foundation's earliest days.  There's no "code of
conduct" a la Ubuntu, and even if a core group of tech@ subscribers starts
off by trying to establish a civil norm, they will be swimming against the
current.

On the other hand, if you're looking to create a list which might make
members@ look pleasant by comparison, this could do the trick.

Marvin Humphrey

Re: tech@apache.org ?

Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, May 7, 2013 at 3:19 PM, Bertrand Delacretaz
<bd...@apache.org> wrote:
> ...I suggest creating a public tech@apache.org list, owned
> by comdev...

We seem to have at least a decent consensus on creating that list, and
as I said I volunteer to lead the experiment so you guys can blame me
if needed ("Bertrand's list failed" T-shirts or whatever works).

On Marvin's "making members@ look like a nice place" note, we do have
ways to prevent that, the first one being ignoring the trolls and
aggressively banning people if needed, once/if there's a documented
code of conduct. Also, I'm optimistic by nature. Humans Are Nice.
Sometimes.

Unless anyone from the comdev PMC opposes, I'll request creation of
that list later this week.

-Bertrand

Re: tech@apache.org ?

Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, May 7, 2013 at 4:09 PM, Ross Gardler <rg...@opendirective.com> wrote:
> Why not use dev@community (with subject tags?)...

IMO community is about community building, tech@ would be for the
hardcore tech stuff.

It's a different audience IMO (with overlap of course), which warrants
a different list.

-Bertrand

Re: tech@apache.org ?

Posted by Ross Gardler <rg...@opendirective.com>.
Why not use dev@community (with subject tags?)

I don't object to a new list, just adding another option.

Sent from a mobile device, please excuse mistakes and brevity
On 7 May 2013 06:20, "Bertrand Delacretaz" <bd...@apache.org> wrote:

> Hi,
>
> We don't seem to have a place for cross-cutting technical discussions
> at the ASF - language and system issues, standards implementations,
> etc.
>
> To fix this, I suggest creating a public tech@apache.org list, owned
> by comdev, with the following rules:
>
> -Technical discussions on cross-cutting topics that are directly
> related to Apache projects
>
> -Each new thread MUST have one or several [markers] in the subject
> line to identify the topics. For example, [java], [osgi], [linux] etc.
>
> I volunteer to get the list started, as an experiment.
>
> WDYT?
> -Bertrand
>

Re: tech@apache.org ?

Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,

On Sun, May 12, 2013 at 4:58 PM, Rob Weir <ro...@apache.org> wrote:
> ...Farmers know that large hay stacks are susceptible to spontaneous
> combustion....

But in general we love busy lists [1] (shameless plug but the original
is not from me)

> ...I wonder whether multiple smaller lists, maybe including
> reviving some existing but little known lists, might work better?  For
> example, tech-java, tech-cpp, tech-standards, etc.  That also makes
> the discussion more cohesive and potentially more relevant to the
> subscribers....

That would defeat the purpose of a list that brings together all
bright Apache community folks who have cross-cutting questions about
our projects, and with a well defined (organically well-defined that
is) set of [subject tags] people can filter at will.

-Bertrand

[1] http://grep.codeconsult.ch/2011/12/06/stefanos-mazzocchis-busy-list-pattern/

Re: tech@apache.org ?

Posted by Rob Weir <ro...@apache.org>.
On Tue, May 7, 2013 at 9:19 AM, Bertrand Delacretaz
<bd...@apache.org> wrote:
> Hi,
>
> We don't seem to have a place for cross-cutting technical discussions
> at the ASF - language and system issues, standards implementations,
> etc.
>
> To fix this, I suggest creating a public tech@apache.org list, owned
> by comdev, with the following rules:
>
> -Technical discussions on cross-cutting topics that are directly
> related to Apache projects
>
> -Each new thread MUST have one or several [markers] in the subject
> line to identify the topics. For example, [java], [osgi], [linux] etc.
>
> I volunteer to get the list started, as an experiment.
>
> WDYT?

I certainly could see the value of facilitating cross-project
discussion on areas of common interest.  Presumably the list would be
open to the public, not limited to committers, so the opportunity for
bad behavior increases.  (The potential number of people to flame on
an Apache Pig technical topic is far smaller than the number
able/willing to do the same on a general topic like "Python versus
Ruby").

Farmers know that large hay stacks are susceptible to spontaneous
combustion.  I wonder whether multiple smaller lists, maybe including
reviving some existing but little known lists, might work better?  For
example, tech-java, tech-cpp, tech-standards, etc.  That also makes
the discussion more cohesive and potentially more relevant to the
subscribers.

Regards,

-Rob

> -Bertrand

Re: tech@apache.org ?

Posted by janI <ja...@apache.org>.
On 7 May 2013 20:03, Ulrich Stärk <ul...@spielviel.de> wrote:

> We already have a listing at [1]. It's hidden behind 2 clicks from the
> main site. We could use that
> as a starting point.
>
> Uli
>
> [1] http://mail-archives.apache.org/mod_mbox/
>
> On 07.05.2013 18:22, Noah Slater wrote:
> > A note to committers@ might be a good first start. But, in general, I
> > really think we need to do a better job of communicating the existing
> > mailing lists we have. Perhaps a page on the main site, or on the
> community
> > site, would be a good start.
> >
> >
> > On 7 May 2013 16:58, Bertrand Delacretaz <bd...@apache.org> wrote:
> >
> >> On Tue, May 7, 2013 at 5:53 PM, Rich Bowen <rb...@rcbowen.com> wrote:
> >>> ...the problem with Yet Another Mailing List, which is that we don't
> >> know about the ones that we
> >>> already have, and so how will people know about this one. Hmm.
> Dunno....
> >>
> >> We'll tweet about it! Tell the world! Write fantastic things on it so
> >> that people link to it! Marketing!
> >>
> >> Seriously...that's a problem, but it's easier to be aware of one
> >> general list than tons of specialized ones.
> >>
> >> -Bertrand
> >>
> >
> >
> >
>

+1 I might see the list a bit different, but never the less, I see it as an
opportunity to have committers get aquinted across projects.

I f.x. am a C++ programmer (main focus protocols, low layer stuff), heavy
project leader experience, and today PMC in openoffice...I  look for a
project that could use my experience. Such a list would be a general place
to talk about that.

rgds
Jan I.

Re: tech@apache.org ?

Posted by janI <ja...@apache.org>.
On 7 May 2013 20:44, Ulrich Stärk <ul...@spielviel.de> wrote:

> Join infra. You will get to know all the dark corners of the ASF ;).
>

you might have heard of the bad, the good the ugly on the infra list called
janIV.

at least we have said "hi" on different ocasions.

And about the dark corners, I think I got my share of that already, but no
C++ project.

rgds
jan I.


>
> No really. You will hear about lists, projects, web pages, etc. you would
> never have heard of
> otherwise or only if you spent a lot of time looking.
>



>
> Uli
>
> On 07.05.2013 20:39, Noah Slater wrote:
> > Sure, but it's not very prominent, and things get lost in the noise. I
> was
> > thinking something more like a page for foundation-wide lists that people
> > might want to subscribe to. I really had to go hunting around for things
> > when I decided to up my involvement and a lot of it was a surprise for
> me.
> >
> >
> > On 7 May 2013 19:03, Ulrich Stärk <ul...@spielviel.de> wrote:
> >
> >> We already have a listing at [1]. It's hidden behind 2 clicks from the
> >> main site. We could use that
> >> as a starting point.
> >>
> >> Uli
> >>
> >> [1] http://mail-archives.apache.org/mod_mbox/
> >>
> >> On 07.05.2013 18:22, Noah Slater wrote:
> >>> A note to committers@ might be a good first start. But, in general, I
> >>> really think we need to do a better job of communicating the existing
> >>> mailing lists we have. Perhaps a page on the main site, or on the
> >> community
> >>> site, would be a good start.
> >>>
> >>>
> >>> On 7 May 2013 16:58, Bertrand Delacretaz <bd...@apache.org>
> wrote:
> >>>
> >>>> On Tue, May 7, 2013 at 5:53 PM, Rich Bowen <rb...@rcbowen.com>
> wrote:
> >>>>> ...the problem with Yet Another Mailing List, which is that we don't
> >>>> know about the ones that we
> >>>>> already have, and so how will people know about this one. Hmm.
> >> Dunno....
> >>>>
> >>>> We'll tweet about it! Tell the world! Write fantastic things on it so
> >>>> that people link to it! Marketing!
> >>>>
> >>>> Seriously...that's a problem, but it's easier to be aware of one
> >>>> general list than tons of specialized ones.
> >>>>
> >>>> -Bertrand
> >>>>
> >>>
> >>>
> >>>
> >>
> >
> >
> >
>

Re: tech@apache.org ?

Posted by Ulrich Stärk <ul...@spielviel.de>.
Join infra. You will get to know all the dark corners of the ASF ;).

No really. You will hear about lists, projects, web pages, etc. you would never have heard of
otherwise or only if you spent a lot of time looking.

Uli

On 07.05.2013 20:39, Noah Slater wrote:
> Sure, but it's not very prominent, and things get lost in the noise. I was
> thinking something more like a page for foundation-wide lists that people
> might want to subscribe to. I really had to go hunting around for things
> when I decided to up my involvement and a lot of it was a surprise for me.
> 
> 
> On 7 May 2013 19:03, Ulrich Stärk <ul...@spielviel.de> wrote:
> 
>> We already have a listing at [1]. It's hidden behind 2 clicks from the
>> main site. We could use that
>> as a starting point.
>>
>> Uli
>>
>> [1] http://mail-archives.apache.org/mod_mbox/
>>
>> On 07.05.2013 18:22, Noah Slater wrote:
>>> A note to committers@ might be a good first start. But, in general, I
>>> really think we need to do a better job of communicating the existing
>>> mailing lists we have. Perhaps a page on the main site, or on the
>> community
>>> site, would be a good start.
>>>
>>>
>>> On 7 May 2013 16:58, Bertrand Delacretaz <bd...@apache.org> wrote:
>>>
>>>> On Tue, May 7, 2013 at 5:53 PM, Rich Bowen <rb...@rcbowen.com> wrote:
>>>>> ...the problem with Yet Another Mailing List, which is that we don't
>>>> know about the ones that we
>>>>> already have, and so how will people know about this one. Hmm.
>> Dunno....
>>>>
>>>> We'll tweet about it! Tell the world! Write fantastic things on it so
>>>> that people link to it! Marketing!
>>>>
>>>> Seriously...that's a problem, but it's easier to be aware of one
>>>> general list than tons of specialized ones.
>>>>
>>>> -Bertrand
>>>>
>>>
>>>
>>>
>>
> 
> 
> 

Re: tech@apache.org ?

Posted by Noah Slater <ns...@apache.org>.
Sure, but it's not very prominent, and things get lost in the noise. I was
thinking something more like a page for foundation-wide lists that people
might want to subscribe to. I really had to go hunting around for things
when I decided to up my involvement and a lot of it was a surprise for me.


On 7 May 2013 19:03, Ulrich Stärk <ul...@spielviel.de> wrote:

> We already have a listing at [1]. It's hidden behind 2 clicks from the
> main site. We could use that
> as a starting point.
>
> Uli
>
> [1] http://mail-archives.apache.org/mod_mbox/
>
> On 07.05.2013 18:22, Noah Slater wrote:
> > A note to committers@ might be a good first start. But, in general, I
> > really think we need to do a better job of communicating the existing
> > mailing lists we have. Perhaps a page on the main site, or on the
> community
> > site, would be a good start.
> >
> >
> > On 7 May 2013 16:58, Bertrand Delacretaz <bd...@apache.org> wrote:
> >
> >> On Tue, May 7, 2013 at 5:53 PM, Rich Bowen <rb...@rcbowen.com> wrote:
> >>> ...the problem with Yet Another Mailing List, which is that we don't
> >> know about the ones that we
> >>> already have, and so how will people know about this one. Hmm.
> Dunno....
> >>
> >> We'll tweet about it! Tell the world! Write fantastic things on it so
> >> that people link to it! Marketing!
> >>
> >> Seriously...that's a problem, but it's easier to be aware of one
> >> general list than tons of specialized ones.
> >>
> >> -Bertrand
> >>
> >
> >
> >
>



-- 
NS

Re: tech@apache.org ?

Posted by Ulrich Stärk <ul...@spielviel.de>.
We already have a listing at [1]. It's hidden behind 2 clicks from the main site. We could use that
as a starting point.

Uli

[1] http://mail-archives.apache.org/mod_mbox/

On 07.05.2013 18:22, Noah Slater wrote:
> A note to committers@ might be a good first start. But, in general, I
> really think we need to do a better job of communicating the existing
> mailing lists we have. Perhaps a page on the main site, or on the community
> site, would be a good start.
> 
> 
> On 7 May 2013 16:58, Bertrand Delacretaz <bd...@apache.org> wrote:
> 
>> On Tue, May 7, 2013 at 5:53 PM, Rich Bowen <rb...@rcbowen.com> wrote:
>>> ...the problem with Yet Another Mailing List, which is that we don't
>> know about the ones that we
>>> already have, and so how will people know about this one. Hmm. Dunno....
>>
>> We'll tweet about it! Tell the world! Write fantastic things on it so
>> that people link to it! Marketing!
>>
>> Seriously...that's a problem, but it's easier to be aware of one
>> general list than tons of specialized ones.
>>
>> -Bertrand
>>
> 
> 
> 

Re: tech@apache.org ?

Posted by Noah Slater <ns...@apache.org>.
A note to committers@ might be a good first start. But, in general, I
really think we need to do a better job of communicating the existing
mailing lists we have. Perhaps a page on the main site, or on the community
site, would be a good start.


On 7 May 2013 16:58, Bertrand Delacretaz <bd...@apache.org> wrote:

> On Tue, May 7, 2013 at 5:53 PM, Rich Bowen <rb...@rcbowen.com> wrote:
> > ...the problem with Yet Another Mailing List, which is that we don't
> know about the ones that we
> > already have, and so how will people know about this one. Hmm. Dunno....
>
> We'll tweet about it! Tell the world! Write fantastic things on it so
> that people link to it! Marketing!
>
> Seriously...that's a problem, but it's easier to be aware of one
> general list than tons of specialized ones.
>
> -Bertrand
>



-- 
NS

Re: tech@apache.org ?

Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, May 7, 2013 at 5:53 PM, Rich Bowen <rb...@rcbowen.com> wrote:
> ...the problem with Yet Another Mailing List, which is that we don't know about the ones that we
> already have, and so how will people know about this one. Hmm. Dunno....

We'll tweet about it! Tell the world! Write fantastic things on it so
that people link to it! Marketing!

Seriously...that's a problem, but it's easier to be aware of one
general list than tons of specialized ones.

-Bertrand

Re: tech@apache.org ?

Posted by Rich Bowen <rb...@rcbowen.com>.
On May 7, 2013, at 11:36 AM, Noah Slater wrote:

> Well, release-discuss[1] was one place suggested for things like "how do we
> version releases?" (The only correct answer being semver! *wink*) But
> unfortunately, discussion sort of dried up there.
> 
> [1] http://mail-archives.apache.org/mod_mbox/www-release-discuss/
> [2] http://semver.org/


Which, of course, highlights the problem with Yet Another Mailing List, which is that we don't know about the ones that we already have, and so how will people know about this one. Hmm. Dunno.

-- 
Rich Bowen
rbowen@rcbowen.com :: @rbowen
rbowen@apache.org






Re: tech@apache.org ?

Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, May 7, 2013 at 5:36 PM, Noah Slater <ns...@apache.org> wrote:
> Well, release-discuss[1] was one place suggested for things like "how do we
> version releases?" (The only correct answer being semver! *wink*) But
> unfortunately, discussion sort of dried up there....

I wasn't aware of that one - yes that's the kind of stuff that can go
on tech@, and having a wider audience and set of topics should give
more chances for a lively list.

-Bertrand

Re: tech@apache.org ?

Posted by Noah Slater <ns...@apache.org>.
Well, release-discuss[1] was one place suggested for things like "how do we
version releases?" (The only correct answer being semver! *wink*) But
unfortunately, discussion sort of dried up there.

[1] http://mail-archives.apache.org/mod_mbox/www-release-discuss/
[2] http://semver.org/


On 7 May 2013 16:33, Rich Bowen <rb...@rcbowen.com> wrote:

>
> On May 7, 2013, at 11:24 AM, Suresh Marru wrote:
>
> > Hi Bertrand,
> >
> > This is a great idea + 1.
> >
> > Infact a useful exchange of ideas of will be on release versioning and
> audit of stability. To be precise, when should we call a software 1.0, the
> PMC can decide itself, but can it solicit feedback from other projects
> which went this route and have them spend an hour or two providing
> feedback? Other than apache con, there are scant technical venues where
> projects share knowledge, experience and some tricks of the trade. I am not
> saying a new mailing list will address any of these, but could booster some
> discussions.
>
>
> It might be a good place to generally speak about best practices. There's
> nowhere outside of the incubator to have those kinds of discussions.
>
> --
> Rich Bowen
> rbowen@rcbowen.com
> Shosholoza
>
>
>


-- 
NS

Re: tech@apache.org ?

Posted by Rich Bowen <rb...@rcbowen.com>.
On May 7, 2013, at 11:24 AM, Suresh Marru wrote:

> Hi Bertrand,
> 
> This is a great idea + 1.
> 
> Infact a useful exchange of ideas of will be on release versioning and audit of stability. To be precise, when should we call a software 1.0, the PMC can decide itself, but can it solicit feedback from other projects which went this route and have them spend an hour or two providing feedback? Other than apache con, there are scant technical venues where projects share knowledge, experience and some tricks of the trade. I am not saying a new mailing list will address any of these, but could booster some discussions. 


It might be a good place to generally speak about best practices. There's nowhere outside of the incubator to have those kinds of discussions.

-- 
Rich Bowen
rbowen@rcbowen.com
Shosholoza



Re: tech@apache.org ?

Posted by Suresh Marru <sm...@apache.org>.
Hi Bertrand,

This is a great idea + 1.

Infact a useful exchange of ideas of will be on release versioning and audit of stability. To be precise, when should we call a software 1.0, the PMC can decide itself, but can it solicit feedback from other projects which went this route and have them spend an hour or two providing feedback? Other than apache con, there are scant technical venues where projects share knowledge, experience and some tricks of the trade. I am not saying a new mailing list will address any of these, but could booster some discussions. 

Thanks,
Suresh

On May 7, 2013, at 9:19 AM, Bertrand Delacretaz <bd...@apache.org> wrote:

> Hi,
> 
> We don't seem to have a place for cross-cutting technical discussions
> at the ASF - language and system issues, standards implementations,
> etc.
> 
> To fix this, I suggest creating a public tech@apache.org list, owned
> by comdev, with the following rules:
> 
> -Technical discussions on cross-cutting topics that are directly
> related to Apache projects
> 
> -Each new thread MUST have one or several [markers] in the subject
> line to identify the topics. For example, [java], [osgi], [linux] etc.
> 
> I volunteer to get the list started, as an experiment.
> 
> WDYT?
> -Bertrand


Re: tech@apache.org ?

Posted by Javin Paul <sa...@gmail.com>.
Indeed a great idea, +1.


On Tue, May 7, 2013 at 9:32 PM, Charith Madusanka <ch...@gmail.com>wrote:

> +1, nice idea.
>
>
> On Tue, May 7, 2013 at 6:59 PM, Rich Bowen <rb...@rcbowen.com> wrote:
>
> >
> > On May 7, 2013, at 9:19 AM, Bertrand Delacretaz wrote:
> >
> > > Hi,
> > >
> > > We don't seem to have a place for cross-cutting technical discussions
> > > at the ASF - language and system issues, standards implementations,
> > > etc.
> > >
> > > To fix this, I suggest creating a public tech@apache.org list, owned
> > > by comdev, with the following rules:
> > >
> > > -Technical discussions on cross-cutting topics that are directly
> > > related to Apache projects
> > >
> > > -Each new thread MUST have one or several [markers] in the subject
> > > line to identify the topics. For example, [java], [osgi], [linux] etc.
> > >
> > > I volunteer to get the list started, as an experiment.
> > >
> > > WDYT?
> >
> >
> > In the past we have had lengthy discussions about creating new lists, and
> > the merits thereof. My position has always been TIAS (Try It And See). If
> > the list is valuable, it will be valuable. If it isn't, it will be
> > abandoned.
> >
> > So, yeah, +1
> >
> > --
> > Rich Bowen
> > rbowen@rcbowen.com :: @rbowen
> > rbowen@apache.org
> >
> >
> >
> >
> >
> >
>
>
> --
> Charitha Madusanka
> Linkdin : http://www.linkedin.com/pub/charith-madusanka/1a/508/42a
> Twitter  : http://twitter.com/#!/charithccmc
>



-- 
Thanks
Javin
http://javarevisited.blogspot.com/

Re: tech@apache.org ?

Posted by Charith Madusanka <ch...@gmail.com>.
+1, nice idea.


On Tue, May 7, 2013 at 6:59 PM, Rich Bowen <rb...@rcbowen.com> wrote:

>
> On May 7, 2013, at 9:19 AM, Bertrand Delacretaz wrote:
>
> > Hi,
> >
> > We don't seem to have a place for cross-cutting technical discussions
> > at the ASF - language and system issues, standards implementations,
> > etc.
> >
> > To fix this, I suggest creating a public tech@apache.org list, owned
> > by comdev, with the following rules:
> >
> > -Technical discussions on cross-cutting topics that are directly
> > related to Apache projects
> >
> > -Each new thread MUST have one or several [markers] in the subject
> > line to identify the topics. For example, [java], [osgi], [linux] etc.
> >
> > I volunteer to get the list started, as an experiment.
> >
> > WDYT?
>
>
> In the past we have had lengthy discussions about creating new lists, and
> the merits thereof. My position has always been TIAS (Try It And See). If
> the list is valuable, it will be valuable. If it isn't, it will be
> abandoned.
>
> So, yeah, +1
>
> --
> Rich Bowen
> rbowen@rcbowen.com :: @rbowen
> rbowen@apache.org
>
>
>
>
>
>


-- 
Charitha Madusanka
Linkdin : http://www.linkedin.com/pub/charith-madusanka/1a/508/42a
Twitter  : http://twitter.com/#!/charithccmc

Re: tech@apache.org ?

Posted by Rich Bowen <rb...@rcbowen.com>.
On May 7, 2013, at 9:19 AM, Bertrand Delacretaz wrote:

> Hi,
> 
> We don't seem to have a place for cross-cutting technical discussions
> at the ASF - language and system issues, standards implementations,
> etc.
> 
> To fix this, I suggest creating a public tech@apache.org list, owned
> by comdev, with the following rules:
> 
> -Technical discussions on cross-cutting topics that are directly
> related to Apache projects
> 
> -Each new thread MUST have one or several [markers] in the subject
> line to identify the topics. For example, [java], [osgi], [linux] etc.
> 
> I volunteer to get the list started, as an experiment.
> 
> WDYT?


In the past we have had lengthy discussions about creating new lists, and the merits thereof. My position has always been TIAS (Try It And See). If the list is valuable, it will be valuable. If it isn't, it will be abandoned.

So, yeah, +1

-- 
Rich Bowen
rbowen@rcbowen.com :: @rbowen
rbowen@apache.org