Hi Amareshwari
fair and good points. The purpose of an user mailing list is to address
end user question, and avoid noise created "internally" by the dev
discussion.
I agree with your "should go/should not go".
Regards
JB
On 01/14/2015 07:46 AM, amareshwarisr . wrote:
Some thoughts on user mailing list :
Trying to put what should go in user mailing list and what not (started
doing this nowdays)
What should go
- A question from user - regarding usage?
- Announcements to users - new feature/new release and etc.
- Not sure people will only subscribe to user list and not dev list. If
there are people, I'm thinking they will mostly interested in
announcements
on what is happening.
- The main use of user mailing list would to separate out user
discussions and development discussions, assuming jira related updates are
put in proper filters.
What should not go
- Jenkins updates
- Jira updates
- Reviw board updates
One challenge we always see is to find where should a post from user should
go - whether to user list or dev list and redirect them accordingly.
Overall, +1 for user mailing list - useful when project becomes big and
there are many users.
Thanks
Amareshwari
On Wed, Jan 14, 2015 at 11:56 AM, Jean-Baptiste Onofré <[email protected]>
wrote:
Hi all,
After a couple of crazy months (due to a bunch of customer engagements),
I'm now back in the business and happy to be back on Falcon contribution \o/
By the way, now that Falcon is TLP, what do you think:
1/ create an user mailing list ?
2/ "normally", we use to promote all PPMC/Mentor/IPMC involved during the
incubation to be PMC on the project (at least we ask if they want to be).
WDYT ?
Regards
JB
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
