Given the discussions, I'd like to propose now that we close in on a
"two lists - dev and user" - answer to this one. I realize there are
tradeoffs, but because we do have some users already who are decidedly
non-developer types - and more coming - I'd like to have a list "for
them" that encourages them to be on it (by its topics and volume). Is
there a way we can/should bring this to a vote/decision by those that
get to decide? (This will be our first case-study in a
post-joining-incubation decision. :-))
Cheers,
Mike
On 4/24/15 5:46 AM, Jochen Wiedmann wrote:
On Wed, Apr 22, 2015 at 9:49 AM, Till Westmann <[email protected]> wrote:
I’m not completely sure that I want one. We currently have one and it has some
reasonable traffic and the discussions are at a user-level.
Also all developers are subscribed to the user-list, so developers are aware of
user problems but not necessarily the other way around.
I think that works pretty well, but maybe a single list would work better.
Thoughts from the other AsterixDB developers?
What about automatically generated notifications, like Jira issues,
commit messages, etc.?
I wouldn't recommend to push those to a user list?
Jochen
