> What do you think should be the right behaviour for managing such emails? > Forward this email to user@ (and remove dev@ address from copy) and ask > politely to continue a discussion there? I tried it several times but > sometimes it happened that discussion was "forked” and continued in two > different lists which is even worse, imho. > > I like your proposal but I do share the same concern of forked threads. One > suggestion, instead of forking the thread we can ask users to ask on user@ > list next time and still answer the question in the original thread. > Hopefully that can reinforce good habits over time.
Agree with asking and not to fork, since it usually won’t help. > Anything else? What do you believe should work better in such cases (maybe > some experience for other projects)? > > I wonder if there is a reason for people to ask on dev@ instead of user@? Web > site instructions look pretty clear to me. There is a good amount of activity > and engagement on user@ list as well. I am not sure about why users pick one > list over another. Maybe we need to make it even more clear on web page that dev@ list is _only_ for dev-related questions, that are supposed to have any relationship with project development in any sense (new features/ infrastructure/ bugs/ testing/ documentation/ etc) and provide some examples for both of the lists?
