Ah, fair point!

On Thu, Mar 12, 2020 at 10:25 AM Jan Lehnardt <j...@apache.org> wrote:
>
>
>
> > On 12. Mar 2020, at 16:21, Paul Davis <paul.joseph.da...@gmail.com> wrote:
> >
> > I'm not against anything of that nature, but if memory serves the
> > email lists are dictated by ASF policy.
>
> If you remember when we did the GitHub transition, as long as we can make
> sure messages end up on a mailing list, we should be fine wrt the 
> requirements.
>
> Best
> Jan
> —
> >
> > On Thu, Mar 12, 2020 at 9:32 AM Garren Smith <gar...@apache.org> wrote:
> >>
> >> Hi All,
> >>
> >> The CouchDB slack channel has been a real success with lots of people
> >> asking for help and getting involved. The main issue is that it is not
> >> searchable so we often get people asking the same questions over and over.
> >> The user mailing list is great in that sense that if you have subscribed to
> >> it you have a searchable list of questions and answers. However, it's
> >> really not user-friendly and judging by the fact that it has very low user
> >> participation I'm guessing most people prefer to use slack to ask 
> >> questions.
> >>
> >> I've been really impressed with how the FoundationDB forum[1] and the rust
> >> internal forum work [2]. I find them easy to use and really encourage
> >> participation. I would like to propose that we move our user and dev
> >> discussion to Discourse or a forum that works as well as Discourse. I think
> >> that would make it really easy for users of CouchDB to look up answers to
> >> questions and get involved in the development discussion.
> >>
> >> I haven't checked yet, but I'm sure we could get all discourse threads to
> >> automatically email back to the user and dev mailing list so that we still
> >> fulfill our Apache requirements.
> >>
> >> I know its a big step away from what we're used to with our mailing lists,
> >> but I think it would definitely open up our community.
> >>
> >> Cheers
> >> Garren
> >>
> >>
> >> [1] https://forums.foundationdb.org/
> >> [2] https://internals.rust-lang.org/
>

Reply via email to