71–80 of 364 posts
Like not fixing it when you can or know better is not good, but in the meantime the code isn't going to be poetic and just write it already...
But when potential employers come looking at your work they'll say "hey this code is shitty! It's not a work of art with 100% code coverage tests and perfect in every way. We can't possibly give you a job. Every line of code in our corporate repo is Mona Lisa quality, we can't let rubbishy developers like you in."
The first thing you learn when you're proud of your Github profile is that nobody is actually clicking into your projects and reading code, with few exceptions. Sure, at small companies where developers interview you, or maybe if you link to a specific relevant project in your cover letter, you might get a pair of eyeballs. But I think people vastly overestimate the readership of their repos when looking for jobs.
It's uncommon (and my anecdote is part of the "exceptions" for sure), but it's very very motivating when it happens.
I just picked up maintainership of django-address. It is a set of models and methods for dealing with postal addresses in Django. The product is dominant in seo and many django beginners and intermediate install it without looking at it. But it has also languished for years and failed to get an important model rearchitecture after the author had to stop work on it. Still, I see it as a great turnaround opportunity an…
Earlier quoted context omitted.
I think that's understandable. You closed issues for bugs you didn't resolve.
Maybe you know the OP, but in my experience a lot of issues are not bug reports but very low quality, uninformed or unreasonable requests or questions. Like questions made about basic functionality that is answered in the documentation/faq, or requests for features that are completely outside the scope of the project. Another popular category is requests for basic education e.g. “how does DQN work?”. That’s fine if i…
Earlier quoted context omitted.
I have a pretty simple project with 2.4k stars, and have met nothing but good people eager to help, and bending over backwards to help me help them. My project's "niche" may have something to do with it.
What is it / what niche?
Earlier quoted context omitted.
Problem is there's no auto detection that a repo is no longer maintained. Easy to do but github does not do it.
The first thing I do is just check commit history for recent commits. Usually a good indicator a thing is abandoned
I agree: it is OK for your open source library to be a bit shitty. However, it also can simultaneously be not OK for you to publish it in a package directory with a generic name and a description talking about how awesome it is as a trap for other people to run into, and that is really the core problem: it isn't that you didn't spend an unreasonable amount of time and money to make a good product that no one paid for…
I need to publish it publicly to install it via pip, npm, cargo, etc. for public use.
Install packages from:
- PyPI (and other indexes) using requirement specifiers.
- VCS project urls.
- Local project directories.
- Local or remote source archives.
Although I’m not quite sure how you’re using “for public use” in that sentence.
[0] https://pip.pypa.io/en/stable/reference/pip_install/#id19
I had a GitHub project that got a few hundred stars. The amount of mean, crazy, and entitled people is crazy. I have no idea how the bigger projects can deal with it.
I agree: it is OK for your open source library to be a bit shitty. However, it also can simultaneously be not OK for you to publish it in a package directory with a generic name and a description talking about how awesome it is as a trap for other people to run into, and that is really the core problem: it isn't that you didn't spend an unreasonable amount of time and money to make a good product that no one paid for…
I need to publish it publicly to install it via pip, npm, cargo, etc. for public use.
Earlier quoted context omitted.
I have few projects on 1k+ stars; the ones that are more beginner-friendly are normally where I get most unrelated requests. I used to help people where possible, but now I just don't have the time (or TBH, motivation). So I closed the issues on those two projects that got most low-quality issues. People started to open PR to tell me I was wrong and I should open the issues. This cemented my decision, oh the entitlem…
Did you tell them why you were closing the issues as #WONTFIX? I maintain a few projects in the "hundreds of stars" range, and I also send PRs to numerous projects with regularity (I make a point to fix typos and such in documentation when I find them). Of course some people are low effort issuers, but some people put time and effort into opening an issue on a project. When the maintainer closes it without even takin…