I think it's a great idea to open up this decision to the NuPIC Community. I am in favor of whatever most community devs prefer, so long as Numenta engineers will use it publicly and on an even footing with the Community. I would not be in favor of a switch if it created a "two-class system" in any way. It looks from Matt's second message in this thread that switching would depend on some work to automate the flow of information from Numenta's internal JIRA instance to NuPIC's GitHub tracker as appropriate. I'm glad to see that acknowledgement of integration work to be done.
Matt, is that work you'd expect to see Numenta doing, or are you hoping to organize the Community to pick it up? Danese On Oct 16, 2013, at 4:21 PM, Tim Boudreau <[email protected]> wrote: > +1 to ditching JIRA - Github has done a very nice job of making their issue > tracker as simple as it needs to be (kind of an object lesson in how removing > features can make software more powerful). Whereas JIRA's UI is click-heavy, > clunky and goshawful - classic software you sell to management which makes > developers miserable. > > -Tim > > _______________________________________________ > nupic mailing list > [email protected] > http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org _______________________________________________ nupic mailing list [email protected] http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org
