Except, this isn't for users of WIAB, it is for general discussion about Wave, so user@ doesn't really fit. There are other general@ lists, so there's precedence there.
The other issue though, is that mailing lists work when there's a shared project to discuss. I'm not yet clear what the shared project is that would be discussed on the general@ list - what the shared goal would be. I'd say let's continue the conversations for a while longer, and when the time comes, I can create the list (I have the necessary karma). Upayavira On Wed, Jun 5, 2013, at 08:51 PM, Ed - 0x1b, Inc. wrote: > On Wed, Jun 5, 2013 at 12:09 PM, Christian Grobmeier > <grobme...@gmail.com> wrote: > > On Wed, Jun 5, 2013 at 8:41 PM, Ali Lown <a...@lown.me.uk> wrote: > >> Following on from the talk, if we intend to develop Apache Wave as an > >> end-product focused project, we should probably migrate talks of > >> 'visions' and 'community' to a separate mailing list from to allow > >> wave-dev to be kept as a developer list related to work on the > >> code-base and documentation. > >> > >> How about would people feel about a wave-general list for the non-dev > >> focused discussions? > > > > Sure, we can give it a try. > > Other apache projects usually have wave-user@ (later to be renamed to > > u...@wave.apache.org) > > > > +1 > > > General would be ok too. But I think user would be better, as it > > follows old patterns. If there is a need to for example discuss the > > protocol later and the users list is getting to much traffic it could > > be separated once more. > > > > > > > > > >> Ali > > > > > > > > -- > > http://www.grobmeier.de > > https://www.timeandbill.de
