Howdy, > I agree almost completely with Andy Dougherty here. Suppose we were to > migrate to a Shiny New Bug Tracker (SNBT) or, better yet, a Shiny New Bug
Just to be clear, I am not talking about a wholesale migration. I will just simply not use Trac for new tickets and will suggest that others do the same. Instead, issues in the appropriate repo on Github will be created. If somebody cares enough about a TT, it will get migrated to a Github issue. I don't want to hear strawman arguments about how I don't care about all the hardwork that people have put into our TTs. I have created and cagecleaned many TT's. But the simple fact is that we, Parrot hackers, need to refactor our community infrastructure if we hope to continue. "Do what you have always done, get what you have always gotten". Parrot is losing developers and quickly becoming even more irrelevant, and I refuse to just rearrange furniture on the deck of a sinking ship. Trac actively discourages new developers, since we have to lock it down from Trac spam. Github actively encourages new developers via all the social features. If we want to continue, we need to fully embrace Github. Duke -- Jonathan "Duke" Leto <[email protected]> Leto Labs LLC 209.691.DUKE // http://labs.leto.net NOTE: Personal email is only checked twice a day at 10am/2pm PST, please call/text for time-sensitive matters. _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
