Files
2012-02-21 01:15:00 -05:00

1 line
3.6 KiB
JSON

[{"user_id": 5006, "stars": [], "topic_id": 40343, "date_created": 1308943327.4633441, "message": "@kennethreitz I tried that one time and was lost ... :). Maybe I should retrieve all forks and do a lot of diff and inspect diffs by hand but there should be a better more automated way. Do you know if there is a place to make suggestions to github team ?", "group_id": 591, "id": 1479206}, {"user_id": 8391, "stars": [], "topic_id": 40343, "date_created": 1308943078.5162671, "message": "Clicking on the 'Network' graph should give you the best idea: https://github.com/pieter/gitx/network", "group_id": 591, "id": 1479153}, {"user_id": 5006, "stars": [], "topic_id": 40343, "date_created": 1308942803.5240071, "message": "Sometime I come accross a project that has been forked many times but the original project has not been updated since ages. Is there a way to find the branch or the fork that has accepted the most patches and that is the most healthy / active ? Is there an automated way to determine this ?", "group_id": 591, "id": 1479110}, {"user_id": 8391, "stars": [], "topic_id": 40343, "date_created": 1308943142.2320571, "message": "( and moving all the way over to the right edge of the graph )", "group_id": 591, "id": 1479165}, {"user_id": 28370, "stars": [{"date_created": 1309037924.398958, "user_id": 36456}], "topic_id": 40343, "date_created": 1308955333.209178, "message": "How do you automate figuring out which changes are the \"best\"?", "group_id": 591, "id": 1481213}, {"user_id": 8391, "stars": [], "topic_id": 40343, "date_created": 1308956180.4003241, "message": "I'd sort by ('most recent commits', 'most watchers')", "group_id": 591, "id": 1481294}, {"user_id": 2320, "stars": [], "topic_id": 40343, "date_created": 1308959031.7907121, "message": "@kennethreitz That sounds like a terrible way to measure \"best\"", "group_id": 591, "id": 1481513}, {"user_id": 1126, "stars": [], "topic_id": 40343, "date_created": 1308960937.903692, "message": "in that case, just use the network graph, and hover over the \"dots\" in the graph to quickly browse commit messages", "group_id": 591, "id": 1481666}, {"user_id": 1126, "stars": [], "topic_id": 40343, "date_created": 1308960891.2742381, "message": "if the core project is what you're looking for, the only reason to use a fork would be if it includes a feature that the original doesn't have, or fixes a bug / security issue that's critical to what you need from it", "group_id": 591, "id": 1481660}, {"user_id": 1126, "stars": [], "topic_id": 40343, "date_created": 1308960832.1041169, "message": "I think you're approaching the problem incorrectly", "group_id": 591, "id": 1481653}, {"user_id": 1126, "stars": [], "topic_id": 40343, "date_created": 1308961021.556916, "message": "if you're looking for something that requires a bit less work, I just look for the fork that solves the problem with the original project with the most watchers", "group_id": 591, "id": 1481670}, {"user_id": 8391, "stars": [{"date_created": 1309031146.754267, "user_id": 28370}], "topic_id": 40343, "date_created": 1308978797.9251039, "message": "@catsby well i wouldn't automate it period, but the question was asked", "group_id": 591, "id": 1482857}, {"user_id": 2343, "stars": [], "topic_id": 40343, "date_created": 1309200053.1406569, "message": "@pewpewarrows I don't think searching the graph is a good solution when the amount of forks and commits are enormous. Good luck trying to search that whole graph and check all commits in a reasonable time frame.", "group_id": 591, "id": 1498275}, {"user_id": 8391, "stars": [], "topic_id": 40343, "date_created": 1309200571.5490401, "message": "google: `projectname site:github.com`", "group_id": 591, "id": 1498322}]