skysight-inc/HackerNews huggingface dataset:
The obvious solution for owners of such projects is to grant more people commit access so more people can handle outstanding PR's. A single person being responsible for all pull requests doesn't scale.

But the issue is that owners don't like giving up that much control, because it can lead to the project being taken in a direction they didn't originally intend.

This is an issue for any open-source project, which is why the biggest projects tend to have a structure where there is a dictator, a hierarchy of core contributors, and everyone else should stick to mailing lists or pull requests to contribute code.

But for small projects it's difficult because it's tough to make that kind of hierarchy work on GitHub.

I'm starting to think there needs to be a boilerplate "Contribution Guidelines for Small Open Source Projects" meta-guideline that small Open Source projects (on the size of things like gems or small utilities) can adopt, similar to how projects can adopt SemVer or a particular OSS license.

Some simple tenants of such a guideline system (or basically, an example thereof:)

1) Contributions to this Open Source project shall adhere to this projects MANIFESTO.md, which shall define the goals of the project, its scope, what it aspires to be, etc.

2) The owner of this open source project shall grant commit access (promoting them to "Core Contributors") to developers who show a consistent drive to make enhancements and fixes that fall within this well-defined manifesto.

3) Only the owner shall make changes to the manifesto. Changes to a project's manifesto should require a fork of the project. Manifestos can be designed by consensus but it should ultimately be up to the owner to commit the change.

4) Core contributors should be able to merge other developer's pull requests, and even grant commit access accordingly. If any commits get merged which fall outside of the manifesto's guidelines, the commits can be rolled back by the owner, or the core contributor can make the case for changing the manifesto, or they should fork the project to keep the commit.

I don't really have the clout to be able to develop such a meta-guideline (I'm not active in any OSS projects), but I think it would be really cool if someone would.
> It's not that Computer Science schools could not teach that stuff. It's that they don't.

Yes, this is the classic Academics v. Industry gap you see everywhere.

Teachers in an accredited program that leads to certification spend most of their time studying theory on psychology, child development, learning, and (now more than often) special education. When they get to the point where they actually have to go student teach, they have lots of knowledge but lack practical experience. As someone who has tried teaching and knows lots of teachers, classroom management is the foundation for everything that happens in a classroom.

In the whole 'teaching more people to code' momentum, the problem is usually that there is some perverse incentive to give the impression that coding is 'easy'. Coding, as most of us know, is by far, 'not easy'. In fact, for many of us, that fractal difficulty is the draw.

The whole movement of teaching CS in high schools baffles me because, again, CS does not teach one how to code. I would much rather see AP CS go away and be replaced by something that teaches Scratch and other tools as a stepping stone to teaching youth to think computationally.
Oh, and I didn't worry about wifi, as my travel was done before that was invented.
You misunderstood the sentence. In the sentence you quoted, "you" is referring to the project maintainer and "people" is referring to the contributors. So in essence, the suggestion is for the maintainer to charge the contributors for looking at their pull requests.
would you mind explaining why that might be better?
That's a different issue. Pattern-matching a sum-type value, though safer, would be "noise" too.
You can do a lot with Funscript, but for professional/enterprise level F# interop with Javascript checkout WebSharper, which is finally under a permissive OSS license http://websharper.com/blog-entry/4124. It has been developed and supported by Intellifactory as their flagship platform for many years, and has a rock-solid reputation. Intellifactory just completed migration of the codebase to Github yesterday, http://websharper.com/blog-entry/4125, and is looking forward to PRs.
> I may have missed something but where in the original article did he say he was _inviting issues and pull requests_?

It's right there on the Github project page. I don't know if Github has an option of disabling those things; it would perhaps be best if it did, but at the moment it - at the very least - implicitly invites participation.

As for other situations: is my suggestion of adding a note to the README.md problematic?
Standard high speed trains in the UK run at 125mph, but that’s pretty slow compared to countries with shinkansen type trains (e.g. Japan, Germany’s ICE, France’s TGV etc) that regularly hit 200+mph.
If you only ever look at the fraction of the universe for which we have a plausible explanation that is passing scientific criteria, you're missing out on a lot of what is part of human existence all around the globe.

Science is a good tool for positive filtering (as in "hey, because of these observations I think how this works, and I think that by doing the following tests I can get some further confirmation of that") but as soon as you use it as a negative filter (as in "hey, there's no proof of it so for all practical purposes it doesn't exist, sorry"), you're just rejecting things based on a technicality.
Updating Intel CPU Microcode Series
> But when I looked at the mailing list for the project, I saw a wasteland of good patches that were completely ignored, where the submitter would ping the list a couple times and then give up. Did it seem worth spending a week to disentangle our IP from the project in order to submit a set of patches that would, in all likelihood, get ignored? No.

Sounds like the OP should have checked activity levels first ...then decided not to spend the extra time.

When I look at using open source for something I often use the following to determine if I should use it:

a) does it have the functionality I need today

b) is it active and being maintained ( through frequency of updates, active mailing list, sometime a financial sponsor (bigco who uses it))
Illinois is upgrading that route to 110mph, and is supposed to be making some signal and bypass improvements that will increase on-time performance as well. Will be interesting to see if it does. http://www.idothsr.org/
Ask HN: How to get listed on producthunt.com?
I've tried submitting my startup but didn't manage to appear anywhere. Are there special rules to follow? I cannot manage to find useful information regarding submitting to Product Hunt.
To that end, the author also suggested that it may serve the project (and subsequent forks) well if the project owner disabled PRs.
Yes, the fact that a vocal chunk of opensource users expose an attitude that could be summed up as "you wrote this tool I'm using, you're obliged to fix all my issues with it" is a constant strain on open source contributors. It's certainly not as bad as death threats, but it's still a problem and it's one that needs to be called out.

People need to be aware that something was given to them and that they need to give back in return if they want to preserve what was given. I, personally, think that a humbly written bug report is sufficient in terms of giving, but courtesy towards the author/maintainer should always be included in a bug report. I try to add PRs when I can, but I obviously can't in all cases.
That's what "Discovery" and "Deposition" are for.

In the United States - specifically the US, I don't know about other countries - the Constitutional right to not incriminate oneself only applies to criminal procedures, not to civil ones.

So all I would have to do is put Zuckerberg - or whoever I think may have made the decision not to hire me - under oath in a deposition, then ask them directly whether the didn't hire me as a result of my age. If they perjure themselves, they would do hard time in prison.

Now there are people who will lie in depositions, or on the witness stand before a jury, so we have discovery. I would just say "Give me all of your email" and they would have to - or again, they would go to prison.

I myself have Amazon cold for violating the Americans with Disabilities Act. I have two very prominent links at the top of every single page on my website, to essays about my mental illness. Amazon's HR was all over me like a cheap suit until I asked them to have a look at my site. Within the hour I received an email that informed me I would not be getting an interview.

I myself am reluctant to file an ADA complaint, what I would rather do is to address the problem by writing more essays. However, were my writing to have any effect, that would only happen very slowly.

I might file that complaint, as it would help other mentally ill people get work.

The reason I work as a coder, and not a physicist, is for the specific reason that computer programming "accomodates" my mental illness in a way that academia does not.

That is, I can be floridly paranoid, even hallucinating - and I do hallucinate from time to time - yet I can still write really good software.
We did the Martinez to Denver route about 10 years ago. I really really want to love the train and for it to be successful but we were 22 hours late arriving. Some of it was weather but we had a train car lose it's suspension near Truckee, then due to that delay the crew went "dead" due to their hours and we literally had to stop for a couple of hours in the middle of Nevada while the next crew came to us. After that we got moving and made some decent time but then a freight train had issues ahead of us so we sat somewhere in Colorado for a few hours waiting. To top it all off, the woman in the sleeper next to us ran out of extra oxygen because she wasn't expecting to be at higher elevation that long and without access to more oxygen supplies and so we had to wait for an ambulance to come.

We flew back.

Some of this was Amtrak's fault, some of this was not. If the food were better and the trains a little more modern we wouldn't have minded as much but even then spending 22 hours extra on that route is just not going to work for much of anyone. But with all the moving parts it takes to get right for a train to come in on some semblance of a schedule I just don't see how it will ever be anything but a niche product for long haul routes.
It also depends on who is saying it. A person you know online and your manager carry different weight.
One more called cdiff: https://github.com/ymattw/cdiff

(works with repositories; not a general diff replacement.)
just throwing myself in here: Starve [1] also runs on FreeBSD.

[1] https://www.starve.io
Lampsort:  Leslie Lamport's Non-recursive Quicksort
It prioritizes them overall. People wouldn't have to pay, but paid ones take priority. Maybe even crowdfund each request, would put the priority in the hands of the community, while the owners retain final say.
Very slick! Reminds me of a slimmed-down version of the Where's It Up API (https://api.wheresitup.com/), but with monitoring.

(Full disclosure: I've done some work for the Where's It Up folks.)
I disagree with this assessment.

The distance from Chicago to Houston is roughly 1100 miles. Non-stop flights from O'Hare to Houston Hobby are listed on Kayak.com at 2 hours and 45 minutes. Add approx. 1 hour for pre-flight check-in, security and an average delay factor (it's O'Hare after all). That's a 3 hour and 45 minute trip time. We could add post-flight transportation from the airport to where you actually want to be and probably add another hour, but let's ignore that detail.

In 2007, the French TGV set a speed record on conventional track of 357 mph. The unconventional track (maglev) record belongs to the Japanese SCMaglev and is 368 mph [0]. These were set under very experimental conditions, but if it were possible to realize equivalent speeds in a practical setting (perhaps via underground tunnels), the train trip from Chicago to Houston would require only 3 hours(!).

But let's assume the above is impossible in real operating conditions. French TGV passenger routes regularly attain speeds of 200mph. This makes our Houston trip a little under 5 1/2 hours. That strikes me as quite efficient.

I'm not an expert, but given the deplorable state of American infrastructure, especially rail, implementation of a system like this would most likely require starting from scratch. As such, equivalence of the French TGV seems very attainable.

More likely, new innovation would lead to performance improvements over their system, which was conceived in the 1970s. Is 300mph attainable? I don't know, but it seems like a reasonable goal. That brings our Houston trip to roughly the equivalent of a flight, when including pre-flight check-in procedures. Of course, trains are safer, less energy and infrastructure intensive and a lot more pleasant.

All of this without mentioning the fact that SCNF, the operator of the French TGV, achieved a $1.75 billion operating profit in 2007.

[0] http://en.wikipedia.org/wiki/Land_speed_record_for_rail_vehi...
Much of the route map outside of the Northeast has been designed as much for congressional favor as for actual ridership.
The reason many PRs get submitted is that many of them just aren't good. Over time, having to deal with formatting issues, way too many commits in a PR that change random files, solutions to things that are really important but not done in a foward thinking way. Great PRs when done right are a wonderful thing, but the reality is that the majority of them are not great and this takes a tax on the developer.

What us OSS devs can do to help fix this is be very clear about PR protocol: ONE commit, change ONE thing. Code changes should have a unit test. And then make sure we are either merging or closing PRs for active projects.
Show HN: View twitter trends worldwide at single glance
I've used that a lot over the years ..and wished the same thing. hell, less can even do color with -R
Show HN: A Markdown-based task manager for hackers and people who build stuff
But as long as the attacker can detect when the user opens devtools all your efforts are futile.

This sounds even scarier - the user should be in control and able to inspect the page without the page knowing, since as he mentions, the attacker could otherwise deploy countermeasures to evade.
Correct me if I'm wrong, but I believe with sum types you can chain together multiple calls then pattern match once at the end. In Go you have to check at each call.
"Complaints have 0 global cost."

That theory seems to be the essence of this entire debate.
Show HN: Generate Alliterative Animal Usernames
Funny that this particular complaint then is quite justified, while the generalized one is not. Because, well, github is commercial enterprise which builds it's business on the phenomena of open source itself, by providing the service that uses this particular library as well and users of this service just provide them with fixes for this app (which obviously is maintained, as we are using that service right now and somewhere out there are programmers, paid to work on this particular app).

But author of the blogpost didn't want to reveal what library he's talking about, which makes the whole complaint much harsher than it should be.
This is incorrect on all accounts.

The Acela doesn't run in California and it doesn't run in Texas.

http://texascentral.com/

Trains in Eurpoe are going to 220mph.

http://www.bloomberg.com/video/take-a-look-at-europe-s-faste...

The average speed between NYC and Boston is something like 79mph. Saying you have a top speed 130mph, and doing it only for a small portion of the trip is quite misleading. At any rate, peak has little meaning. I've been on commuter trains that peaked at 90mph for 5 minutes.
>Blithely dismiss

In regards to Greek Mythology (adopted by the Romans), the majority of people I know have learned about this in their public school curriculum (multiple years). So "blithely" is a fallacious argument.

>Considering all the Gods and then considering their existence

Many people do study multiple religions. I happen to be one of them. Everything from modern day Jewish, Mormon, and Scientology beliefs, to more Ancient Hindu, Buddhist, Mayan, Nordic, and Egyptian beliefs, etc., etc. There are a lot of similarities between these belief systems (too many to discuss here -- and probably more than most people who have never studied these belief systems would be comfortable admitting too).

It takes a lot of courage to call other people hypocritical, when dismissing ALL gods without sufficient study of various belief systems, no?
You can easily disable issues and either disable the wiki or make it editable only by project members, but there does not seem to be a way to disable or restrict pull requests.
Just because you have fewer attempted break-ins doesn't mean your system is more secure. In other words, the only relation between the number of successful break-ins and the number of attempted break-ins is "less than or equal to".
Some advices in this post are related to restrictive tooling and some are related to adjusting ones attitude. Whereas I used to rely on the former, nowadays I find the latter brings a completely different (and better) kind of calm.

This article [0] is one of the best ways I've ever seen it put, and I think both the culling and surrender parts it mentions are very important - not just one of them.

Inner calm is so important. Like countless others in this post have said: Try meditation, and give it time. It can be an important piece of the puzzle of silencing those voices.

Good luck.

[0] The Sad, Beautiful Fact That We're All Going To Miss Almost Everything: http://www.npr.org/blogs/monkeysee/2011/04/21/135508305/the-...
For C++ std::string, I might well code up an iterator adapter. :-D

A while back I mentioned this on Kuro5hin. "K5" members are reknowned for being total jackasses. Some kuron told me that the correct solution was to call the C standard library function that reverses strings - "strrev()" or some such. His point was that one should never implement code from scratch, if one could use a library call.

I pointed out that I was required to implement strrev() myself. My interviewer wasn't asking me to call a library function.

This set off a flame war that lasted for hours. This compleat gentleman flatly refused to accept that there was any other correct solution than to call a library routine, despite that it was quite clear to me, when I interviewed, that I was not permited to.
Wow I just did the math and at this rate it would take New Horizons roughly 20,000 years to travel 1 lightyear. Slingshotting around Jupiter takes longer to play out than a straight shot obviously, but it puts things in perspective.
I would like to see some evidence that's really the core problem. 52% of America owns stocks (down from 69% at its peak). Versus how many individuals who perform this kind of financial manipulation, 10,000? 1,000? Counting ringleaders only, maybe 100?

If you're going to make $100m from a scam, you can afford to make it look pretty convincing. Way more convincing than the average amateur investor will be able to ferret out. There's an inbuilt information asymmetry.

The theory of public stock markets is that they are well-regulated enough for individuals to invest safely. Either we make that true or we should close the markets to unlicensed amateurs. Blaming victims is always popular, but it never leads to change. (Which is a big part of why it's popular.)
If it doesn't DoS my firewall, a port scan like that will be easily detected and blocked. A stealthy port scan takes a good amount of time.
OP here. This video was just a one-off that was essentially a one-off warm-up for Nathan's class, but I absolutely recommend going through the rest if you're interested in programming languages or want to learn how to write an interpreter or compiler. It was really useful for me and it's totally free at http://nathansuniversity.com
Prior to today I had seen this anecdotally on the Keystone Corridor. I live outside Harrisburg, PA and have seen traffic increase dramatically once they upgraded the track to Philadelphia to dedicated "high speed" rail (110mph max) with free WiFi. Looking at the map both Harrisburg and Lancaster have seen half a million new riders in the past decade, all bound in the direction of Philadelphia. Unfortunately the Pittsburgh leg is shared with freight traffic and turns a 3.5 hour journey by car into an impractical and relatively expensive 6 hour train ride. There's a plaque in Pittsburgh commemorating the first rail line from Philly in the 1860s which shaved travel time from 7 days to 8 hours and all I thought upon seeing it was what a shame it was that so little has changed since then.
That's a leap that's far from guaranteed by the cases summarized in your link. A court or the copyright office could just as easily say "just as the latest digital outline fonts have elements that can be protected as software, emoji have elements that can be protected as visual art."
Well, the readme _does_ expose the lack of functionality in the first line. It links to the underlying library which explicitly states that it's an incomplete set.

Also, because somebody behaved like an asshole in a different situation does not grant me the permission to behave like an ass in a different situation.
You're using anecdotal evidence to argue against the general case.

Consider the book "Laughter is the Best Medicine". Some guy's cancer went into remission when he watched a whole bunch of really funny movies.

Given that, would you suggest that we should do away with chemotherapy, radiation and oncology surgeons?
Not really, because you well might be open to contributions and merge them sometimes and maybe even fix some bug reports yourself, but you don't have to and if I'm contributing a pull-request for your project it doesn't mean that you are obligated (in any sense of the word) to merge it or take any actions on it whatsoever. If I'm making a pull request I must be prepared for it, because nobody promised me it would be otherwise.
Or even just a regular link to site.com/get-url-for-paypal-then-redirect.
you mean "in a totally different way", do you?

you are comparing a gem replacing, in a string with html content, a text fragment with an '<img />' tag, with a way to load and apply custom font from a remote location to a web page text region.

While, closing one eye, the effect of the two solution are similar, the solutions are totally different from the technological point of view, from the abstraction layer when they are applied to the practical implications (try to do a simple cut-n-paste from the browser to a text editor, for example)
From time to time I'll see a job posted on Craigslist or the like that says "We only want applicants with Computer Science degrees from Berkeley, MIT or Stanford".

I myself have a Physics degree from the University of California Santa Cruz - "Uncle Charlie's Summer Camp".

Despite that, I quite commonly find that I'm a better, or more productive coder than colleagues with CS degrees from those schools.

Just because you have a degree, it doesn't mean that you have a clue.

And just because your degree is from a school that no one has ever heard of, it doesn't mean that you're ignorant.