Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Dear GitHub

github.com

Post reply on HN
Print view View original

341–350 of 491 posts

Re: Dear GitHub

#341

Post by smarx007 »

int_handler wrote: post #316
avinassh wrote: post #302

Earlier quoted context omitted.

They also removed [0] C Plus Equality [1] project twice. Even Bitbucket [2] and Google [3] also removed it. [0] - https://github.com/FeministSoftwareFoundation/C-plus-Equalit... [1] - https://github.com/ErisBlastar/cplusequality [2] - https://bitbucket.org/FeministSoftwareFoundation/c-plus-equa... [3] - https://code.google.com/p/c-plus-equality/

What was the story behind this anyway? I am having a hard time determining whether this was actually serious or were trying to parody feminist activism.

And what if it really was a parody? Just censor it?

Re: Dear GitHub

#342

Post by Too »

Permit wrote: post #142

This first request is the anti-thesis of GitHub's simple approach: >Issues are often filed missing crucial information like reproduction steps or version tested. We’d like issues to gain custom fields, along with a mechanism (such as a mandatory issue template, perhaps powered by a newissue.md in root as a likely-simple solution) for ensuring they are filled out in every issue. Every checkbox, text-field and dropdown…

This is why your application should always have a "dump version string"-button, conveniently embedded together with your "report bug" button which doesn't have to be more advanced than simply opening your email-client or forward you to a webpage. This form should be free text but pre-filled with the version string pasted at the top and contain headers that invite the user to fill in the rest, such as Reproducing: . 100 different drop-downs makes nobody happy.

Re: Dear GitHub

#343

Post by KuhlMensch »

jonobacon wrote: post #116

Hi Adam, Addy, Andreas, Ariya, Forbes, James, Henry, John-David, Juriy , Ken, Nicholas, Pascal, Sam, Sindre, My name is Jono and I started as Director of Community back in November at GitHub. Obviously I am pretty new at GitHub, but I thought I would weigh in. Firstly, thanks for your feedback. I think it is essential that GitHub always has a good sense of not just what works well for our users, but also where the pa…

I've been personally paying for a couple of years, and the SAAS company I work for (~50 engineers) has committed to moving away from Github for some of these (and other) reasons.

Here are some of my fave :+1:-a-thons that help demonstrate when the issue system starts to be less useful, and the Github acknowledgement seems sparse:

* https://github.com/isaacs/github/issues/18

* https://github.com/isaacs/github/issues/215

Also, you might consider empowering your social media team. I see Github as a pretty cool company. And when I sent this tweet, I was expecting to have a bit of a shared chortle with this tweet as I know I would of had with @SlackHq:

https://twitter.com/Ash_Coolman/status/670595632659206146

But instead I got nothing, except a vague sense of having offended someone (sorry BTW, it was only a joke! :'()

Re: Dear GitHub

#344

Post by seivan »

jonobacon wrote: post #116

Hi Adam, Addy, Andreas, Ariya, Forbes, James, Henry, John-David, Juriy , Ken, Nicholas, Pascal, Sam, Sindre, My name is Jono and I started as Director of Community back in November at GitHub. Obviously I am pretty new at GitHub, but I thought I would weigh in. Firstly, thanks for your feedback. I think it is essential that GitHub always has a good sense of not just what works well for our users, but also where the pa…

Not sure you'll read this but I'd love a tagging feature for starring. Sorting on code isn't good enough.

Re: Dear GitHub

#345

Post by kbart »

clinta wrote: post #266
simoncion wrote: post #248

Earlier quoted context omitted.

> I normally put a big "[DEPRECATED]" notice at the beginning of the README. Aye. Some folks in the discussion linked to by krschultz complain that "People sometimes don't read the README and -thus- don't notice deprecation warnings.". To them I ask: "What makes you think that those sorts of people will notice anything less than an overlay that prevents them from interacting with the Github UI for that particular rep…

One concern would be around tools that fetch from github automatically. go get for example would need some sort of structured metadata if it wanted to surface an error to a user that a library is deprecated.

Agree. I've had literary thousands of libs/tools/apps dependencies in one of my projects that was built using automatic tools (Bitbake + Yocto). It's simply impractical to go through all these README's manually, so a tool to detect depreciated projects is a must in such situations. Of course, one could implement some tool to scan all README files for keywords ('DEPRECIATED', 'UNMAINTAINABLE' etc.), but that's just a workaround and I'd like a proper, reliable way to do that.

Re: Dear GitHub

#346

Post by slavik81 »

kbart wrote: post #345
clinta wrote: post #266

Earlier quoted context omitted.

One concern would be around tools that fetch from github automatically. go get for example would need some sort of structured metadata if it wanted to surface an error to a user that a library is deprecated.

Agree. I've had literary thousands of libs/tools/apps dependencies in one of my projects that was built using automatic tools (Bitbake + Yocto). It's simply impractical to go through all these README's manually, so a tool to detect depreciated projects is a must in such situations. Of course, one could implement some tool to scan all README files for keywords ('DEPRECIATED', 'UNMAINTAINABLE' etc.), but that's just a…

What if the maintainer never marks the library as deprecated? What if they're just hit by a bus?

I feel like if you have so many direct dependencies that you can't keep tabs on them, you simply have too many. Whoever decided it was OK to depend on that library should be able to follow it closely enough to say when it cannot be depended on.

Re: Dear GitHub

#348

Post by gabriele »

joelhooks wrote: post #246
jessaustin wrote: post #231

Earlier quoted context omitted.

If they're using it, they're doing so in completely different fashion than everyone else. That is, it's not public for viewing, submitting, commenting, etc. Indeed TFA indicates exactly the sorts of pain points that would be missed by those using the tool in such a radically different way than everyone else. If someone at GH had to wade through all the damn +1's then something would have been done about them years ag…

95% of all my github activity is in private repositories.

GitHub pretty please, give us an option to hide our profile from search engines just like Facebook do.

Re: Dear GitHub

#349

Post by Sir_Substance »

beshrkayali wrote: post #166
Sir_Substance wrote: post #123

Earlier quoted context omitted.

>but what I'd genuinely like to know is why don't big projects just move to their own thing? Github is a great advertising and marketing platform for large OSS projects. Quite the opposite, large projects should be moving towards github, because it's a great stage for them to perform on. On top of that, it's rather become the defacto replacement for sourceforge (sorry FOSShub, it was a bold try), with all that implie…

The reason why I thought bigger projects would be more capable of handling this is because team size = more manpower obviously. > Quite the opposite, large projects should be moving towards github, because it's a great stage for them to perform on. On top of that, it's rather become the defacto replacement for sourceforge. Not exactly sure what they're supposed to perform better/easier on a shared-hosting locked-in p…

>Not exactly sure what they're supposed to perform better/easier on a shared-hosting locked-in platform.

To be clear, I meant perform as in "tap dance routine" and was being metaphorical.

A large project on github gets more exposure than a large project not on github, because it regularly shows up in the "explore" section of the site. A small project on github gets no more exposure than a small project not on github, because it does not.

(I have no citation for this, it's based on my observations only)

Re: Dear GitHub

#350

Post by shurcooL »

fphilipe wrote: post #340

My biggest gripe with GitHub has been the notification system. Personally I can't use the web UI for notifications because they bundle multiple notifications per issue. This leads to potentially missed notifications since it is up to me to scan the issue/PR for new comments. My workaround has been to use email notifications exclusively. I have a Gmail filter that applies a label to all notifications and skips the inb…

> Personally I can't use the web UI for notifications because they bundle multiple notifications per issue. This leads to potentially missed notifications since it is up to me to scan the issue/PR for new comments.

I think the bundling aspect is an awesome feature! I can read multiple new comments all at once, with context in mind and less total context switches.

About being able to miss new comments - doesn't the link in the notifications UI take you directly to the first unread comment?

Post reply on HN