Hi Nick, As a very new member of this community, I found it extremely useful to browse the list of "issues" in this centralized github location. I started to comb through the email list archives, but that was rather tedious and getting the full context of any particular topic was, well, difficult (and maybe I missed it, but it was also not searchable).
One of the great things about the github "issues" is that you can annotate them with labels and then filter by those labels. Perhaps a "bug" label could be used to differentiate between an "enhancement" or a "discussion". This would allow the core developers to focus on critical problems with released code as well as engage a [somewhat peripheral] group of stakeholders in the discussion and planning. It would also allow people like me and Duane get a sense for what is coming in future releases and whether the kinds of features we might want are forthcoming and beneficial for the broader community. My inbox is already quite cluttered, and it's is a tranquil relief to come here to participate in open discussions with like minded developers like you. Thanks and I hope that wasn't too preachy for a new person! -ben Originally entered as a comment for #394: https://github.com/openannotation/annotator/issues/394#issuecomment-56309894 --------- On Sep 21, 2014, at 11:22 AM, Nick Stenning <[email protected]> wrote: > Dear all, > > You may notice that I've just engaged in a pretty substantial issue > purge on the Annotator repository. > > My intentions are good (trying to reduce the cognitive overhead of > dealing with open issues on Annotator, while opening up the mailing list > to a wider range of discussions) but my implementation may be imperfect. > > If you feel I've closed an issue incorrectly, please do feel free to > reopen the issue with an explanation of how my decision was hasty. But > do please note that if your issue is a feature request, and not a report > of an extant bug in code or documentation, the correct place for that > discussion is now the mailing list, and not the issue tracker. The > contributing guidelines will be updated to reflect this in due course. > > Best, > N > _______________________________________________ > annotator-dev mailing list > [email protected] > https://lists.okfn.org/mailman/listinfo/annotator-dev > Unsubscribe: https://lists.okfn.org/mailman/options/annotator-dev _______________________________________________ annotator-dev mailing list [email protected] https://lists.okfn.org/mailman/listinfo/annotator-dev Unsubscribe: https://lists.okfn.org/mailman/options/annotator-dev
