couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kyle Snavely <kjsnav...@gmail.com>
Subject Re: [DISCUSSION] Move Fauxton to its own mailing list?
Date Tue, 14 Apr 2015 15:11:11 GMT
+1 to Jan's idea -- I love seeing all the dev discussion but my inbox is
exploding due to our wonderful fauxton work.

On Tue, Apr 14, 2015 at 10:58 AM, Garren Smith <garren@apache.org> wrote:

> +1, I think thats a great idea.
>
> > On 14 Apr 2015, at 4:09 PM, Jan Lehnardt <jan@apache.org> wrote:
> >
> > Thanks for all your feedback!
> >
> > How about this:
> >
> > We create new mailing list code@couchdb.apache.org (or your favourite
> bike shed) that gets all JIRA and GitHub traffic.
> >
> > dev@ then is for discussion and decisions for all code projects
> (including Fauxton).
> >
> > If you want to keep track of tickets and pull requests, sign up for code@
> .
> >
> > There is a bit of a discrepancy between discussions in JIRA and dev@,
> but I’m willing to take that risk, as most people probably bulk-delete all
> JIRA mails anyway :)
> >
> > What do you think?
> >
> > Best
> > Jan
> > --
> >
> >
> >
> >> On 18 Feb 2015, at 15:41, Robert Kowalski <rok@kowalski.gd> wrote:
> >>
> >> I like the cross-pollunation between the dev-topics, e.g. when we
> >> announced / suggested coding style guidelines, I would like to keep
> >> that  at the main dev-list
> >>
> >> I also think the amount of git-commit-mails and Jira stuff is floody.
> >>
> >> Can we just move the Jira and git-commit stuff to an own mailing list?
> >>
> >> On Wed, Feb 18, 2015 at 3:23 PM, Andy Wenk <andywenk@apache.org> wrote:
> >>> On 18 February 2015 at 15:15, Jan Lehnardt <jan@apache.org> wrote:
> >>>
> >>>>
> >>>>> On 18 Feb 2015, at 15:12, Andy Wenk <andy@nms.de> wrote:
> >>>>>
> >>>>> Hi Jan,
> >>>>>
> >>>>> I am +0. Recently, there is not that much traffic at dev@. So I
am
> >>>>> wondering what the intention is to split technical discussions
> further.
> >>>> We
> >>>>> saw in the last year, that the main list is dev@ for developing
on
> >>>> CouchDB.
> >>>>> The only list with much traffic is marketing@ because it is a
> complete
> >>>>> different topic.
> >>>>
> >>>> This is mostly about the git notifications, they are significant :)
> >>>>
> >>>
> >>> ok fair point ... I just have the fear, that the participation will
> >>> decrease because of yet another ML a developer has to subscribe to.
> But we
> >>> can inform every one appropriately ... so let's go for it ...
> >>>
> >>>
> >>>>>
> >>>>> Unless I am missing something essential like to much different
> topics in
> >>>>> one list, I would leave it at dev@.
> >>>>>
> >>>>> Cheers
> >>>>>
> >>>>> Andy
> >>>>>
> >>>>> On 18 February 2015 at 14:38, Garren Smith <garren@apache.org>
> wrote:
> >>>>>
> >>>>>> +1 that is a good idea.
> >>>>>>
> >>>>>>
> >>>>>>> On 18 Feb 2015, at 3:34 PM, Jan Lehnardt <jan@apache.org>
wrote:
> >>>>>>>
> >>>>>>> Hey all,
> >>>>>>>
> >>>>>>> I’m wondering how you would feel to give the Fauxton team
their own
> >>>>>> mailing list for discussions and GitHub notifications?
> >>>>>>>
> >>>>>>> In my view, the Fauxton project is generating enough traffic
to
> warrant
> >>>>>> it’s own space :)
> >>>>>>>
> >>>>>>> I’d propose fauxton-dev@couchdb.apache.org
> >>>>>>>
> >>>>>>> Best
> >>>>>>> Jan
> >>>>>>> --
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Andy Wenk
> >>>>> Hamburg - Germany
> >>>>> RockIt!
> >>>>>
> >>>>> http://www.couchdb-buch.de
> >>>>> http://www.pg-praxisbuch.de
> >>>>>
> >>>>> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588
> >>>>>
> >>>>> https://people.apache.org/keys/committer/andywenk.asc
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Andy Wenk
> >>> Hamburg - Germany
> >>> RockIt!
> >>>
> >>> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588
> >>>
> >>> https://people.apache.org/keys/committer/andywenk.asc
> >
> > --
> > Professional Support for Apache CouchDB:
> > http://www.neighbourhood.ie/couchdb-support/
> >
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message