Issue 122803

Summary:	Make sure that developers read Bug reports related to their field of activity
Product:	Infrastructure	Reporter:	Rainer Bielefeld <rainerbielefeld_ooo_qa>
Component:	Bugzilla	Assignee:	AOO issues mailing list <issues>
Status:	UNCONFIRMED ---	QA Contact:
Severity:	Normal
Priority:	P3	CC:	andrefischerfeb, issues, robweir, vsfoote
Version:	current
Target Milestone:	---
Hardware:	All
OS:	All
See Also:	https://issues.apache.org/ooo/show_bug.cgi?id=123092
Issue Type:	TASK	Latest Confirmation in:	---
Developer Difficulty:	---

Description Rainer Bielefeld 2013-07-23 06:14:00 UTC

From time to time I get advice "Post your needs on dev@openoffice.apache.org", here nobody will find it.

I think that's the wrong way. I will not split information to various places.

It is easy to create a Bugzilla account for that list (if not already done) and to arrange the mailing settings for that account so that the list will only get 1 single Mail for a new Bug where that posting for the list is required.

Comment 1 V Stuart Foote 2013-07-23 13:56:50 UTC

@Rainer,

Yes, I'd also rather open and then track "issues" within a fully described Bugzilla record. A record is then all concisely present in one location regardless of external discussion.

But, you'll note that as Andre F. pointed out, that the issues@openoffice.apache.org address IS subscribed by default to a new Bugzilla reported issue.  I believe key developers and members of the PMC already receive Bugzilla generated issues to that mail list. So our preference to raise a properly described issue using just the Bugzilla framework is already routed for mail list distribution. What you've asked for is already accomplished.

Mail list based discussions are not going away, but what might be helpful would be better linkage from within a Bugzilla issue back to substantive discussions occurring on mail lists.  Along the lines of the "see also" to tie one's choice of archival Mark mail or Nabble listing linking any discussion back to the BZ issue.

=-=-=
Links for this issue

Nabble for example
http://openoffice.2283327.n4.nabble.com/Bug-122803-Make-sure-that-developers-read-Bug-reports-related-to-their-field-of-activity-tp4648340.html

Mark's mail
http://markmail.org/search/?q=openoffice+date%3A201307+%22developers+read+Bug+reports+related%22

Comment 2 Rainer Bielefeld 2013-08-05 15:16:53 UTC

The intention of this report is to avoid such
<https://issues.apache.org/ooo/show_bug.cgi?id=122233#c2>
friction loss