Live data from Hacker News

PR spam today looks like email spam in the early 2000s

greptile.com

161–167 of 167 posts

Re: PR spam today looks like email spam in the early 2000s

#161

I remember that on the not so early days of the internet around 1993, I managed to exchange emails with pretty much important people, known professionals and even got responses to my questions. It looked like a very very small world. Then, came the spam. I really hate the marketing people mindset. It fucks everything that is nice.

[dead]

Re: PR spam today looks like email spam in the early 2000s

#162
post #125

Earlier quoted context omitted.

as an open source project maintainer, we dont want tokens bro, we want $.

I don't even want $ really unless its enough to replace my dayjob rather than adding a second one.

I'd just like a lil bit of side money. For example, an extra $1000/m goes a long way imo.

I dont need 6 figures, just a lil bit.

Re: PR spam today looks like email spam in the early 2000s

#163
post #131

I value Open Source very highly, and enjoy contributing. Fix a bug here, add a small feature there, most OSS projects have low hanging opportunities. And these days, to "switch off" from my at-work code, try to do more OSS contribution as well. What I see instead, really, is that most projects no longer, or very rarely look at any contribution, and e.g. any issue + PR/MR combo I make, has a much higher chance of neve…

I wish we had a license like "this project merely extends the project it's based on to add features and fix bugs". So that we could justify immediately switching to the fork that solves our immediate problem. When OSS first got big in the 90s, I thought that it was a free-for-all where anyone could contribute (no maintainers/PRs/MRs) and people would use the most popular branch. That way it would evolve freely at lig…

That license IS any copy left license, but nobody will trust a random fork is my understanding.

I can agree though that the network effect of "everyone else uses X" is pretty unfortunate and has led to a lot of other issues too, so yes very disappointing

Re: PR spam today looks like email spam in the early 2000s

#165

Earlier quoted context omitted.

Huh? Proprietary code sometimes leaks on GitHub, but open source code hosted on GitHub is the opposite of proprietary. What bad spot are you going to get into?

Often times, candidates are currently employed, likely at a competitor. Any code they write can potentially be claimed as a work product and I want no part of that possibility.

Fascinating. Seems really really remote so as to cause actionable trouble to me, but to each their own.

Re: PR spam today looks like email spam in the early 2000s

#166
post #131

I value Open Source very highly, and enjoy contributing. Fix a bug here, add a small feature there, most OSS projects have low hanging opportunities. And these days, to "switch off" from my at-work code, try to do more OSS contribution as well. What I see instead, really, is that most projects no longer, or very rarely look at any contribution, and e.g. any issue + PR/MR combo I make, has a much higher chance of neve…

I wish we had a license like "this project merely extends the project it's based on to add features and fix bugs". So that we could justify immediately switching to the fork that solves our immediate problem. When OSS first got big in the 90s, I thought that it was a free-for-all where anyone could contribute (no maintainers/PRs/MRs) and people would use the most popular branch. That way it would evolve freely at lig…

"I can go use whatever fork already exists that solves my problem" is great right up until you have two problems.

Re: PR spam today looks like email spam in the early 2000s

#167

Earlier quoted context omitted.

I wish we had a license like "this project merely extends the project it's based on to add features and fix bugs". So that we could justify immediately switching to the fork that solves our immediate problem. When OSS first got big in the 90s, I thought that it was a free-for-all where anyone could contribute (no maintainers/PRs/MRs) and people would use the most popular branch. That way it would evolve freely at lig…

"I can go use whatever fork already exists that solves my problem" is great right up until you have two problems.

Make your own fork and cherrypick/merge the fixes you need
Post reply on HN