On Mar 27, 2017 3:56 AM, "Christian Gran" <gran at lynxtechnology.com> wrote:
Hi, I have updated the section about Outdated Tickets on the Wiki. Does this capture the thoughts and the discussion we had on the reflector? https://wiki.iotivity.org/jira_how_to_use?&#outdated_tickets it's a good start but not open-sourcey enuff imho. for example " A ticket should *never* be unassigned." why? this makes zero sense to me. We are not a corporation. "If a ticket is not updated for 6 month there needs to be a final decision if this should be either dealt with short term, or if it should be closed as 'withdrawn." i'll ask again: why? what makes 6 months so magical? why is it a problem to have open tickets? i suggest you spend some quality time studying http://dev.clojure.org/display/community/Contributing. clojure is a very successful open source project that has dozens of open, unassigned jira tix, going back to at least 2014. of course clojure has the luxury of a BDFL, Rich Hickey, who is a certified sw genius. we might have some geniuses but we do not have a BDFL. Which makes it even more important to avoid arbitrary bureaucratic rules. in particular, it is pure folly to insist or even suggest that submitting a jira ticket thereby entails obligations of any kind on the submitter. equally important is figuring out how to prevent the obstreperous from blocking progress (e.g."sure, this patch fixes a critical bug but i don't like the var names you use so i'm going to block it") but i'm not sure how to do that in the absence of a BDFL. gregg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170327/aadd9799/attachment.html>
