4 ms·

I'm the author of the article, and throwing away the tickets was suggested many times by different people. We had a pretty big discussion in #parrot about the

I'm the author of the article, and throwing away the tickets was suggested many times by different people. We had a pretty big discussion in #parrot about the value of this ticket set. People on the project plowed through the Trac database and closed tickets, and even with that we still hundreds that tracked all sorts of development. Many were bug reports, and many were effectively to-do items, and many were bug reports that had been resolved but still couldn't be closed for various reasons, such as needing an automated test to verify it. It's nice to start over clean, but sometimes there's too much baby with the bathwater.

lucian303 14y ago
Sounds like you guys did your due diligence. In that case, of course, writing the app to move them over is the right choice. Thank you for the article, BTW. It may be obvious to some but not to most. Especially contributing to documentation. I'd say that most open source projects can benefit more from that than from new features ... and maybe even most bug-fixes, depending on severity.
- petdance 14y ago
  I'm glad you liked the article, and it seems to have struck a chord. One of the things I've found very handy is that I now have a place to point people on, say, StackOverflow when someone asks "How do I get started in open source?" I started 89starts.com as an offshoot of the article, but I haven't yet gotten it ready for prime time. Agreed about documentation, and at the top of my to-do list for today is making final edits to another article for them on open source documentation. Should be out in a week or two I think.