On 1/27/19 12:27 PM, Gregg Reynolds wrote: > On Mon, Dec 10, 2018, 4:48 AM Wouter van der Beek (wovander) < > wovan...@cisco.com > > ... > >> Hence filing tickets is THE thing to make the deficiencies known. >> > ... > > >> It would be good to have ticket each time someone encounter something that >> is: >> >> - Not clear >> - Clearly wrong >> - outdated >> >> so that we (that includes everyone on this email thread) can do something >> about it. >> > Recently sent a few messages to mailing list regarding minor issues. > Because I'm a little reluctant to spam the jira with stuff that may turn > out to be silly. (Spamming the list feels less transgressive, for some > reason.) Just to confirm: should I be submitting such stuff on jira? > > Thanks, > > G
Gregg, it's a good question to ask. I admit I don't know what iotivity thinks their policy is (especially these days when the people involved and the level of involvement has changed from the earlier days). Personally, I happen to sit in the camp of "just get the ticket filed, it can easily be closed/rejected if not appropriate". But different projects do things differently - I work on one where the maintainer gets grumpy if you file any ticket unless it's been first discussed on the mailing list and "the community" agrees it's a real issue, and that it doesn't duplicate something existing. In other words, my personal stance is to file it all, and quickly deal with it in bug triage; wheres this maintainer prefers to have the bugs pre-triaged before the go into the tracker. Neither way is wrong... just different approaches to the same problem. Do we have a current stance on that topic? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10148): https://lists.iotivity.org/g/iotivity-dev/message/10148 Mute This Topic: https://lists.iotivity.org/mt/28653513/21656 Group Owner: iotivity-dev+ow...@lists.iotivity.org Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
