Sure its convenient if you just have a small project and don't want to host an issue tracker yourself and don't care about the usability of the issue tracker.
The "killer feature" of the issue tracker is that you don't need to create yet another login just to report a bug. Chances are you've reported an issue on github before, or if not you just have to create a user once, that you can use to report bugs on any github project.
I consider Github's issue tracker to be a significant step backward/in the wrong direction from Bugzilla for several reasons:
* defaults to markdown instead of plain text [1]
* no easy way to attach binary files[2]
* no easy way to attach files[3]
At least from a project developer's perspective I find bugzilla much easier to use (once you get used to it), and has more features.There are some minor improvements in Github's issue tracker, but none that would want to make me switch.
[1] Whenever I paste some error message / shell output I need to escape it in <pre> or <code> blocks, otherwise it messes up the formatting. I initially created a lot of broken bugreports, that I had to edit once I've seen how bad it looked, of course then I found out you can preview the bug before submitting. IMHO text should be the default for bugreports, not markdown!
[2] they come in handy depending on the project. If the project deals with binary files, it is expected that bugreports may have to contain them as well
[3] Besides creating a gist and pointing to the gist you pretty much have to self-host any file you want to "attach" to a Github issue, unless I'm missing something.
* For markdown I prefer the synatx highlighting and scrollbars that show up on github to the giant blobs plain text gives you.
* I rarely want to attach binary files while I often find myself embedding inline images to illustrate a point
* I use cat test | gist -c -f test.txt -d "Output from failure" (it puts the gist link in my clipboard).
The missing pieces (from my perspective) on GitBucket is that I can't use ssh keys for identification/authorization. I think GitHub, Gitolite, etc do this part right.
EDIT: Fossil always seemed interesting, and now there's Veracity which is missing IDE integration but seems to have all the server-client parts done correctly.
Huh? I haven't read any negative comments about Fossil here.
And yes, Fossil deserves to become more mainstream, it's pretty good (though my use is simple).
In any event, it is nice to meet others using it.
> more recently a la ArchLinux and Music Player Daemon
> (MPD) I have seen Mantis BT.
Arch Linux uses Flyspray, not Mantis.Great post.
UPDATE: Sigh, too late to edit now. The internet preserves my follies for future generations!
I come back to programming again and again to solve problems or deepen understanding. Popularity is nice, but I post to Github because it is a public place, not to gain popularity. You will never see my code there, I am sure. Most Github repos I stumble upon are through other media and social networks mentioning cool stuff, just like HN. I use plenty of self-hosted tools and I respect those people just the same, maybe even more because they got their somehow without recommendations on the side of a page or trending repo notifcations and email updates.
However, what do I wish I saw more of, like a lot now that I read up on Common Lisp, is people mirror aggressively on repo.or.cz, Github, Bitbucket and the like, when their site goes down or they lose interest. Github makes that easy, but we should not throw out the baby with the bath water: Git and tools like it encourage this simple reproduction of effort. I love open source because it is the only human organization I am familiar with that makes this and transparency such an important mantra (I am biased).
In short, I will never get attention, but I hope to get understanding. I understand some people contribute for different reasons, but if you are on Github to get attention, the rest of "normalized" society is laughing at us anyway.
I work in an IT department, and when I mention Github and source code and different languages, people stare at me like an alien. I will never get attention anywhere, but Github is not making that better or worse.
(And to be fair, I know I am vastly oversimplifying your argument and I know I am overemphasizing it. This is not meant to troll, but I see a lot of people these days on Github and places who embody your one comment much more grandiosely, and it pisses me off. Who does open source for attention? Haha.)
Ugh, I hate that the term "circle jerk" is being applied to "a place where people share things they have made."
Github is a self-described "social coding" website. If people did post code simply to show it off to others, do you feel this is better or worse than Facebook-esque low-content narcissism? I feel like you come to this with a feeling of superiority for some reason.
>In short, I will never get attention, but I hope to get understanding. I understand some people contribute for different reasons, but if you are on Github to get attention, the rest of "normalized" society is laughing at us anyway.
So what if people are on Github to get attention? Self-promotion can help you get a better job or help establish a reputation. The programming community is small and there's nothing wrong with wanting to participate.
However, I posit that people push to public-read Github so that their code gets attention. When I post code to my tech blog, the broadcast audience is small. When I post it to Github, anyone can see/critique/benefit/suggest changes/easily discuss it with context. That's pretty cool.
>I work in an IT department, and when I mention Github and source code and different languages, people stare at me like an alien.
If you work in an IT department where Github or code-review is strange, that's a different issue.
>I will never get attention anywhere, but Github is not making that better or worse.
I don't even know how to respond to this.
> Ugh, I hate that the term "circle jerk" is being applied to "a place where people share things they have made."
Well, I did not mean to sound superior. I do not think I can code well enough to look down at other people for coding ability. I just feel that people increasingly, like any social network, will work on projects on Github for attention and the content is questionable or strange. Social is transforming to a place to socialize, and the latter I do not like for Github or anywhere else for enthusiast programming.
Recently, I had an idea because I got sick of TinyTinyRSS, a PHP-based feed reader with some good mobile app integration. I wrote a small README, uploaded a SVG of the MySQL DB structure to get an idea, and had not written any of the Python I described. I received three stars a week later, and not a single line of code yet. How does that even make sense? My point is people go around look for attention without effort. Yes, I know this describes every social network. I dislike them. You can balk at that ironically, because I am here, ostensibly another social network in different orange wrapper. Nonetheless, the kind of voting and sometimes absurd comment threads in nerd wars, like the whole Node.js commit changing gender and the Joyent employee who lost his job over it, were disgusting. I understood both sides of that issue, but people were declaring there sides with superfluous commentary in the pull request comments, and the hundred or so comments supporting various views on women and IT and superfluous garbage showed it was a hot topic. No one wanted to debate the merits of the commit or how to handle the issue as it pertained to the Node community with that specific issue, of course. It was just an angry Facebookesque flameware on Github. I hoped I would not see Github turn into that. I foolishly assumed it would be a long time before I saw that because, like it or not, computer culture, especially open source stuff, is still fringe.
It is this that bothers me. Some people write cutesy meaningless libraries to get attention. I probably write garbage, code far worse than anyone of that ilk. But what I do not like is the stress Github is now turning the celebration of open programming and collaboration into, merely a celebrity contest. I cannot find the talk by one of the Node guys talking about how he started to be really affected by the number of stars he received on projects (and this is a guy that had projects in Node with sometimes three or four digits in his star count! I never broke more than 1, on anything). He said it ruined his focus drive and he had to re-center himself.
My point here, whether you disagree or not, is that a social network for coding does not mean a socializing network where it is playground for different cliques, with random bullies and popular kids looking down at you. Github is not that yet, but my point was that prioritizing attention-getting when working in open source projects seems quite contrary to me.
Ask Richard Hipp.
That's kind of the point of social coding. If I care and think that I can help your project, I'll suggest a solution that I'm capable of implementing (pull request).
>Social is transforming to a place to socialize, and the latter I do not like for Github or anywhere else for enthusiast programming.
No one is forcing you to do anything. You can post your code for others to see without interacting.
>I wrote a small README, uploaded a SVG of the MySQL DB structure to get an idea, and had not written any of the Python I described. I received three stars a week later, and not a single line of code yet. How does that even make sense?
Maybe someone liked your idea or starred it as a reminder to come back later.
>and the hundred or so comments supporting various views on women and IT and superfluous garbage showed it was a hot topic.
Political opinions don't require an understanding of the issue or any ability. To talk about code, the amount of ability and understanding increases with the complexity of the sample. Which is to say, of course the noise political discussion drowns out talk about coding because there's more potential participants.
>Some people write cutesy meaningless libraries to get attention.
So what?
>But what I do not like is the stress Github is now turning the celebration of open programming and collaboration into, merely a celebrity contest.
Do you think that this behavior comes from Github or its users?
>I never broke more than 1, on anything)
Earlier you said that you received multiple stars for a project you hadn't coded.
I'm going to stop responding because you're responding with anecdotes, some of which are fictitious.
So Atlassian might be free for open source projects (they say for Stash at least after Googling), but that can always change with any app or service you use. RMS free should not change, and you should be able to understand the most current copy you have of source to find alternatives or build your own. Fortunately, this rarely happens for the core FOSS items I use. I have been lucky.
Also, Atlassian can be pretty hefty for small weekend projects in my opinion. But I have only used Confluence at work, it seems like it would require much more resources than a server or VPS for weekend projects would require. I could be wrong.
What I do not understand, with all due respect, is the value of Github, and to a lesser extent Bitbucket, is in the features outside of the VCS core and how most people realize there is nothing Git-like to replace the actual project management tools where people find Github value. That is, bug tracking/issue tracking is the killer feature.
To self-host this is problematic. This is not to say there are not good solutions. Traditionally that is Bugzilla, Trac, Redmine, and more recently a la ArchLinux and Music Player Daemon (MPD) I have seen Mantis BT. It looks interesting. The problem is, as others point out, maintenance, and adding the centralized to the decentralized, thus the point of Git, Mercurial, and others. I noticed this guy hosts his own repos (I tried links to bugsplat.rb) and it did not load, but I assume there is not bug tracking, despite the name.
Even this year, I decided to look into the state of DVCS integrated bug tracking. Very few tools exist, or many have problems. BE, bugseverywhere, kind of exists and has seen contributions as of last year. Ticgit was forked to ticgit-ng, but ironically that is a Github project and its bugs are in the Github issue tracker. There was a very cool Perl project, which seems abandoned, called SimpleDefects (SD), which also wanted to do distributed bug tracking. It was going to sync with Github and other issue tracker systems with decentralizaton, so you could git pull for bugs as well. This one has not seen updates for years, as I can tell, but might be the coolest of them.
Unfortunately, keeping you whole project decentralized is difficult. I have begun to look into fossil again, despite what people here say, because it might be ugly, but no VCS has its own bug tracker or wiki integration, all written in C. It is the SCM and bug tracker for Sqlite, Tcl, and even for all of NetBSD packages. The last really surprised me. I think for the little guy, that is ideal. Monotone might be worth revisiting (I had multiple problems 3 or 4 months ago because it was embedding Lua and they had not come up to the 5.1-5.2 API changes and builds failed; everyone is hard to find), even with the only data about it is there page and links to snarky Linus Torvalds jokes about the horror of OO data structures and modern C++ programming for a SCM.
In short, you should know to host your own Git repos (they are designed, with the native package tools in Git or others) to host simply on a website. It is best for even the lowest footprint web servers, shared hosting or not.
What git does not have, is the beautiful features that keep people on Github all day. I really wish distributed bug tracking advanced, but no one is interested. This topic only comes up when Github is down (or maybe in this case but Github is having publicity problems today). If people made a good tool like SD, that has its own bug tracking that syncs well with Github or (insert hosted SCM here), that would be fantastic. I could be more relaxed, principally, by relying on such tools.
Back to read the Fossil manual.