There's a lot of projects I want to remember but don't necessarily care about the daily activity.
And no, browser bookmarks aren't good enough. A nice faved/starred page would show stats and maybe last commit/activity. That's it.
There's a lot of projects I want to remember but don't necessarily care about the daily activity.
And no, browser bookmarks aren't good enough. A nice faved/starred page would show stats and maybe last commit/activity. That's it.
In theory I could just bookmark them using my normal system with a tag of "github" or something but the "Watched Repositories" widget is too useful to miss.
It's not up for public use yet, as i've yet to replicate the watched repos widget inline with bookmarks but next weekend I'll have a crack at it.
https://plus.google.com/u/0/b/110983919160550210204/11098391...
A new button will not fix Github's news feed problem. Making the news feed more relevant to users will.
But could you apply it to GitHub where all you care about in Project X is Feature Y or Issue Z?
I guess the easiest way is if you could somehow figure out that the pages the User was looking and commenting on all related to one thing, such as CSS issues or problems with C pointers and only display those issues. I'm not sure if that is doable but the people at GitHub probably don't have the necessary resources to devote to implementing this (at least in the near future), whereas Facebook has more engineers, resources, data, and time to throw at the problem.
Maybe for you, but my experience is exactly the opposite. I find the Facebook news feed to be just about as useful as the Github news feed... which is to say, totally useless.
The problem, as I see it, is that G+, Twitter, Github, etc. all make the same fundamental mistake... assuming that "connecting" to an "entity" means "I want to see every update from/about this entity." So, I "friend" somebody on G+ or "watch" a project on Github, now I'm on the hook to see all their updates. But there's NO particular reason to think that the above assertion holds. At best, "friending" a person or "watching" a project says you're more interested in it/them than a random project/person.
These "event stream" implementations really need one or both of two things: The ability to specify more about what it is you're interested in, and smarter ML algorithms to figure out what to show you, based on both declared (or, for that matter, inferred) interests, and social connections, OR the ability to specify filters to exclude "stuff you don't want."
If I had to choose, I'd ask for the latter. Better filters would go a long way towards giving us control of our streams / news-feeds. I'd like, for example to be able to say "I don't want any pictures of cats with funny hats, regardless of who posted them, in my stream." Or, in the Github example "I don't want any commits from project $FOO in my stream."
If I'd seen much (or any) evidence to suggest that the machine learning stuff was smart enough to give me a truly meaningful feed without manual tweaking, I would care less about filters, but so far I'm just not seeing it. Facebook appear to try, but my feed there is still full of crap because they assume too much based on who I follow, not what I'm interested in.
<rant-over />
Facebook and GitHub live in different problem spaces and may need different solutions. You probably don't have one friend that literally posts 200 times more posts than your average friend, but GitHub commits can very easily have this sort of pathological distribution. They're going to need to deal with that in a way that Facebook does not.
Pathological distributions can really be a pain in general. This sort of spiky, long-tail distribution can wreck up a lot of good plans.
For that matter, contra some suggestions about "machine learning" solving the problem I'd lay a few bucks that "commits I'm interested in" is so pathologically distributed that it is effectively unlearnable itself.
> A new button will not fix Github's news feed problem
But it will fix a problem a lot of people have: "I want to remember this project, but I don't care about news from it".On GitHub, watched projects could show up in your feed by default, but you can hide them if they turn out to be too verbose.
(edit: put the wrong gitmarks project in here, updated to the one I meant)
>Codeshelver lets you clean up your GitHub watchlist by storing repositories you would like to remember on your shelf. You can tag any repository and search for it later on - until then it won't spam your dashboard timeline.
Codeshelver helps you find that one project that you had seen ages ago, which you did not want to follow (watch), but perhaps use somewhere.
This is the thing i always click watch in the first place, but i never get to the dashboard in reality.