News for hackers. Stuff that matters.
Re:The Pull Request Hack by kibwen on Monday March 11, 2013 @01:49PM (#5358395)
I think the bigger problem here is that Github is rather useless at gracefully abandoning a project. The usual solution is for an interested maintainer to fork the project and continue, but with any sufficiently popular project it's impossible to tell which forks, if any, have momentum.

I feel like there's got to be a middle ground between the current "fork in obscurity" model and the OP's "commit bits for everyone" model. But I'm not smart enough to think of what that might entail.

Re:The Pull Request Hack by typicalbender on Monday March 11, 2013 @01:56PM (#5358458)
I like the idea Github providing an easier way to gauge momentum on a repository and then maybe do some sorting based on that. I can't tell you how many times i've been looking for a repository and a large number of them come up with no indication, other than number of starts and forks, about whether that is the main repository that is still maintained or not.
Re:The Pull Request Hack by weaksauce on Monday March 11, 2013 @03:15PM (#5358977)
That could still be gamed by committing a lot if you are a malicious user. I'm sure they could figure out a way that would work but it seems the naive way is Not ideal.
Re:The Pull Request Hack by kzrdude on Monday March 11, 2013 @09:53PM (#5359520)
Also remember that you can trivially fake author name, email and date in git and thus github. Only the github-side push log will tell which user pushed what, the commit log can lie all it wants.

Most notably, you can backdate a commit and github won't even show it in the commit log (because it uses strict commit date order).

Re:The Pull Request Hack by snprbob86 on Monday March 11, 2013 @11:47PM (#5360005)
Yes, but also remember that you'll get loud warnings about non-fast-forwards thanks to the cryptographically secure SHA1 hashes. This means that the repo admins and downstream clones can trivially detect history rewrites for branches they have fetched. Unfortunately, there isn't a good way for code-consumers to tell if and when a non-rewrite commit or branch has been "blessed" by an admin rather than some random committer. I guess this means that the README should make some mention of the collaboration policy and the admins should preserve release power to whatever the relevant package manager is.
Re:The Pull Request Hack by kzrdude on Monday March 11, 2013 @11:52PM (#5360025)
You don't need to rewrite history. You just add new commits with fake author & date.
Re:The Pull Request Hack by moe on Tuesday March 12, 2013 @11:52AM (#5362587)
but with any sufficiently popular project it's impossible to tell which forks, if any, have momentum.

Seconded. This is one of the pain-points I wish github would address. The constantly broken "network graph" and complete lack of (meaningful) tools to compare forks or branches is a royal pain in the ass.

Many of the missing operations ("In which branches does commit X exist", "Show delta between A,B") shouldn't even be hard to implement.

I don't understand why github spends their resources on useless gimmicks ("streaks", "pop repos") rather than pushing their core product.

Re:The Pull Request Hack by markburns on Wednesday March 13, 2013 @03:09PM (#5370440)