For example, I once found and patched a bug in paperclip, explained why it happened and sent a PR. It was ignored for 5 years and then they abandoned the project.
Or I once fixed Heroku issues by upgrading the ImageMagick version with a custom build pack. They featured it somewhere and suddenly I was getting entitled emails every day by random strangers who strongly felt that I should fix their Heroku deployment.
Then there's the issue of dependencies. My cool tool for analysing satellite photos won't be of much use to anyone who doesn't have API access to a satellite ground station. I.e. there's no benefit in making it open source.
And lastly, I've had the unpleasant experience of a company taking my open source project, adding copy protection and then selling it as theirs while simultaneously refusing to adhere to my license of either following GPL or paying for closed source use.
Nowadays, I only share source code for hobby projects with friends, but not publicly. Otherwise it's more work and less pleasant for me.
You mentioned the full extent of your attempt at contributing to open source consisted of a grand total of two meager pull requests.
I'm sorry to say but if throughout all those years you only managed to put together two patches then quite obviously you did close to zero contributions, both in absolute and in relative terms.
In fact, it seems you complain more about floss than actually contribute stuff.
I find that I general it's terribly easy to get your pull requests accepted to random FLOSS projects. Whether your PR is janitorial work, fixing bugs or adding features, you don't need much work to get your contribution in. So, quite frankly it sounds like you are grossly exaggerating and overstating not only the extents of your work but also the challenges you supposedly face.
> Then there's the issue of dependencies. My cool tool for analysing satellite photos won't be of much use to anyone who doesn't have API access to a satellite ground station.
In that case your so called cool tool to analyse satellite photos sounds very poorly designed. I mean, the whole FLOSS earth observation stack is designed literally from the ground up with extensive separation of concerns in mind (see GDAL and proj4 and orpheo toolbox for example) and apparently somehow you failed to learn the lesson that everyone doing professional, academic, and even amateur work knows by heart.
Similarly, I've had unpleasant experiences with entitled users more than once, I just picked the Heroku buildpack randomly.
As for the satellite tool, open tools will only take you so far. I do use GDAL, for example. But when you need to take photos on demand, you need very precise real-time trajectory and weather data, for which there is no free equivalent. Plus you actually need to send your photo request somewhere. And that's when you become dependent on an NDA-ed proprietary API.
There's good open source tools if you want to do offline analysis of static archive images. But not everyone has such relaxed requirements for refresh period and processing latency.
Consider using satellite photos to analyze traffic. You schedule photos with a proprietary API, use proprietary modules to download them, followed by proprietary file format converters. And then there's a block of image processing that I could open source, but that won't be helpful without the data acquisition and conversion pipeline. But actually it's a TensorFlow AI trained on proprietary data, so even releasing that is a legal nightmare. The whole project is commercially tainted from start to finish.
Also, I’m glad your PRs are accepted. I see a lot of projects with lots of old, open PRs. Maybe others don’t have the same experience as you do.
Opensource is enormous at this point. One data point(or even 30!) is no longer particularly relevant. Instead think of it like any endeavor in life. You are taking a leap of faith. Sometimes you'll have a great experience that may even blossom into greater things you never expected. Sometimes you'll be let down despite your best efforts and intentions.
niche projects that can only be used by a small group of people still benefit from open collaboration that FOSS enables.
also, i might patch your code to work without that ground station on publicly available satellite image data.
that last example is clearly a copyright violation. you should have legal means to go after them. i realize that is not trivial and may cost you a lot of effort, and while i would love to say there is help available i can't right now point you to one.
is there an organization that helps any FOSS project (not just their own) with license violations?
And yes, I did eventually succeed in resolving the copyright violation. But it was still a lot of work for me which I could have avoided entirely by keeping my source code secret.
Submitting a PR allows others in the community to apply your patch (or incorporate into a forked version of the project) if the PR doesn't get merged or deleted. From a project maintainer's point of view, significant patches can be difficult to test & review, and merging a PR implies accepting the long term maintenance of those changes. I've left some promising PRs for much longer than I'd prefer to because of factors like time to review and the risk of merging code which may not have adequate tests. If an open PR attracts some community interest or discussion, that can give project contributors a helpful signal for prioritising.
If a PR is featured somewhere, this can be an opportunity to raise your profile and perhaps introduce those inquiring users to something you can benefit from more directly. If I get direct emails about a PR or project I contribute to, I try to politely point those users to the right channel (eg raise a GitHub issue) and ideally a contributor guide so they can be empowered to contribute directly. This may not be a straightforward reflex to develop, but I think responding with "This is a volunteer effort -- here's how you can help with docs, testing, or code" is a better viewpoint than "Ugh, more entitled users". I've been pleasantly surprised to see this approach turn some agitators into useful contributors.
If a project has very niche dependencies (like requiring API access to a satellite ground station), there can still be an audience and they may be even more motivated to collaborate on your open source project. I feel like this may have the best upside in terms of potential ratio of users to collaborators.
I think your last example is the most challenging. If you are concerned about someone else benefiting by stealing or repackaging a project you have openly shared, it would be best to keep that effort private. Compliance with open source licenses (or the spirit of open collaboration) requires ethics that are not universal across developers, companies, and countries. This problem isn't unique to open source (commercial licenses also don't prevent piracy), but is a harder blow when you are personally affected.
Notably the first. You fixed a bug, you contributed, you did your part but it was ignored. Did you learn anything from that? Beyond "Open Source is a waste of time" I guess?
It's easy to look at things negatively, but there's often positives to be found if you simply look for them. Not to say you're wrong, just, trying to offer some perspective.
What many fail to understand is that disinterest in Github absolutely does not tell you anything meaningful about that programmer.
Too many hiring managers/recruiters/HR people focus only on the first point, as some sort of religion.
I just self-host Gogs, GitLab, Trac, cgit, etc. They are independent of each other, of course. :) Different teams, different needs. As far as my personal projects go, I just self-host cgit, and I accept "pull requests" through e-mail. It works.
It is an opinion I share but disagreeing with the inclusion of politics into tech makes people believe you have taken the opposite stance.
There is little nuance permitted in US politics and US politics is the only politics permitted in technology.
I blogged about it. It has cost me job opportunities.
I tend to not share my political views anywhere, especially not on Twitter. I do not even own a Twitter account! If I express my beliefs, it is under a pseudonym. Sometimes I even argue in favor of something with what I disagree only to learn more.
could you elaborate?
a place that forces me to get involved in political arguments or where partisan politics influences business decisions or the company openly favors a particular party such that all employees are assumed to support that choice, is not a place where i want to work.
The parent explicitly said they disagree with GitHub's political views. I take this to mean they in fact have taken the opposite stance.
By all means, they can care about politics- but they cant force me to care about their politics and they should not be as reactionary as they are when I take my business elsewhere.
I am just a dude who likes computers. I don’t need to shoulder problems from half a world away on behalf of billion-dollar corporations.
Don't know what they though that my involvement in open-source projects would correlate well to e-commerce CMS work (I've worked in e-commerce dev well before opening a Github account). But it's probably some weird "tie breaker" decision given that I am not local to LA.
Well, it does. It says he doesn't have a portfolio for some reason. Is it because he is incompetent and has nothing to show for? Perhaps not, but if the candidate makes it difficult for recruiters and interviewers to get an objective way to corroborate his claims regarding his level of expertise then just for the sake of avoiding wasting your time with yet another paper tiger... It would be better to cut him out of the shortlist for further interviews.
No, you do not have to have a "reason" for not having a public portfolio. Not having a public portfolio doesn't say anything at all about someone's competence.
>> if the candidate makes it difficult for recruiters and interviewers to get an objective way to corroborate his claims regarding his level of expertise
Public code is not the only way to assess skills, indeed as I mentioned elsewhere in this thread its actually a pretty bad way to assess skills. If the best tools you have for assessing competence is github then your recruiting process is lacking.
>> It would be better to cut him out of the shortlist for further interviews.
I can imagine employers with this attitude lamenting how hard it is to find good people.
Some companies I've interviewed with claim that I'm just not enthusiastic about programming, or that I'm not motivated enough, simply because I don't do any programming at home. They also questioned how I could learn new things. And my answer is usually the same; if they expect someone that wants to program 24/7, then I'm definitely not the right person. I have other hobbies I'm interested in, and I have no desire to burn out. I also expect to be given the time to keep up with new tech on the job.
$10/mo isn't bad for a 'professional' service. Basic manicures are ~$20 and last 7-10 days; they are common with in-person sales and marketing jobs.
Yes those things I did took a lot of time but I typically do it out of boredom . To be honest my GitHub projects are demos and I just like giving presentations .
If you compare yourself or anyone on any given metric you will feel bad. What is even worse is when people tell you all the time about a metric that you should do but once you do it you find that it wasn’t necessary at all and it’s some kind of mental gatekeeping.
The point isn't that the hypothetical banker can't have an active github profile, it's that there are reasons they might not.
Take me for instance, I haven't really done anything significant in the public for over a decade now. The vast majority of my code has been for one private company or another.
And that's the case because either my job has me working the hours or after putting in 8 to 10 hours of code in private, there's exercising, practicing guitar, socializing with friends and family, building Lego sets, reading, playing video games, and other activities that don't involve me writing more code.
That's not to say I don't, it's just I don't have that much time to do it outside of work.
I've been coding since 1995 and my open source contributions tailed off around 2002 or so. Wasn't how I wanted to invest my spare time.
I just spent the past 4 years getting an MBA, my github repos are all horribly out of date because I had more important things to do. It doesn't mean I'm any less passionate about the technology.
Based on the people I've worked with (both great and mediocre programmers), I think that is highly uncommon.
https://www.joelonsoftware.com/2016/12/09/developers-side-pr...
- get approval from VP to spend time on that
- get approval from legal (they checked the license and if the company has any liability from that code not working, this alone took a couple months)
- get approval for release of code from a so called open-source committee (basically checked if your contribution doesn't damage company's reputation)
It was easier to set up a fake account and get things fixed this way. But no way I could do that on company hardware or time.
> I will still think odd that’s someone who is a professional hasn’t found one bug in an open source lib that is worth a PR or even an issue in a decade of work.
It seems like the person is surprised how nobody has any contributions from just their professional work. Naturally unless I had no life outside of programming I would spend the vast majority of my time doing my 9-5 stuff.
I have no idea about enforcement, and most coworkers I've had have ignored those clauses.
Free Github private repos has been a blessing for just storing modifications to existing projects.
I'm going to guess you're in USA, is it legal to stop phone workers using the phone outside work. Seems like not allowing people to work on things directly related to their actual work (due to IPR claims by the employer) would be a thing, but no OSS at all?
My last company did have a policy that you are prohibited from participating in OSS, unless getting a bunch of approvals per project or per patch. I'm risking my job sending a PR.
It's work related, it should be fixed at work. (I certainly don't want to patch things in my spare time because the company forbids me to work at work).
P.S. I am in London. USA would be worse.
It's almost always yes for the former and no for the latter.
Maybe they work 8 hours a day on a bank or government project that is all private and then they spend the rest of the day acting as a care giver to a relative, studying, or volunteering in a women's refuge. All noble activities that I would consider positives for a candidate, but I'd never know if I just checked "Do you go home and cut code out of hours?".
I mistook my own privilege of free time as a universal truth and I'm glad I was called out on it early on and able to change my (interviewing/screening) ways. I wonder what else I need someone to call me out on...