| readme.mdView |
|---|
| 1 … | +This is a project called Tracking Issues. It's for people that want to track their issues in public and other people can say what issues they have with them, the tracker of issues, and thus perhaps get issues resolved. Why? Because we live in an open source world and tracking issues is what people who work in open source do. |
| 2 … | + |
| 3 … | +### Project Genesis |
| 4 … | + |
| 5 … | +The project started on 19 July 2016 when I mentioned to Everett (to whom I'm micro-married and with whom I share space) that I could use git issues to track the issues that come up between the two of us. He was all: no. Just track your own issues. So, that's what this is. An individual issue tracker; an issue tracker for the individual writing this readme right now. |
| 6 … | + |
| 7 … | +Everett was stupid with happiness about the whole thing. Making me think I must have major issues and he must have some major beef with me he wants to bring up. 72 hours later he was still pushing for it. Then he said, 'if you don't start the _tracking issues_ repo, I will.' |
| 8 … | + |
| 9 … | +### Project Reasoning |
| 10 … | + |
| 11 … | +Last night at dinner (23 July) he brought up tracking issues _again_. So it's July 24th, he's still sleeping. I'm drinking coffee, inhaling the copal that's blowing in my face, and preparing to push this live. Yo, yes, it makes me nervous to be tracking issues on a public, append only log. Are you kidding me? I think one of the biggest pushbacks I'm going to get is 'by focusing on problems/issues, you attract more of them.' But that's just some esoteric idealist gobbledygook. I know, having been in the coding world learning to be a developer and even now being a minor league tater tot developer, that tracking issues leads to awareness of the problem, the bug, the compile error, the thing that needs fixing. When the developer knows what needs fixing, the developer can get on the road to fixing said issue. |
| 12 … | + |
| 13 … | +Also, yeah, if the developer doesn't think something's an issue, the developer has the right to close it without changing anything about the project. |
| 14 … | + |
| 15 … | +### Project Inspiration |
| 16 … | + |
| 17 … | +As usual, I want to give credit to Linus Torvalds for inspiring this repo. I appreciate that when someone within the kernel community has major beef with him, he brings it up and addresses it in his own way. He doesn't expect everyone to agree with him (or does he?) and I believe he does a good job of airing issues in a decidedly developerish way. The biggest issues I've ever had (both in person and on the web) have been in my slamming doors instead of letting light in; tracking issues aims to forever fix that. |
| 18 … | + |
| 19 … | +### Project Author |
| 20 … | + |
| 21 … | +My name is Gwen Bell, gb on sbot. You might want to start your own Tracking Issues project after reading this. If so, fork and run with your own name. Not that anyone has issues with you, but wouldn't it be great if they could express them if they do. |
|
| 22 … | + |
| 23 … | +### Project License |
| 24 … | + |
| 25 … | +This is an open source project, as well as fodder for a future for profit book and speaking tour. |