What's the general etiquette if you find something open source (Apache 2.0) that doesn't really work has had no commits for a while and you "fix it" but also change how it works somewhat. Do you go back and propose your changes (even if it's quite a lot)? Do you put it out there separately? Don't want to step on any toes 🤔
@parcifal While opening a feature request as an issue might by a slippery-slope, submitting a PR is often seen as more forthcoming because it reduces the effort the maintainer has with it, given you don't know how much time they currently can and want to spend with the project. It's worth a try but if they have little time and can't quickly take stock of the outcome, they might decline it and a fork might be more suitable.
@parcifal people getting mad about forks is honestly ridiculous. If they don’t like that, they shouldn’t use an open source license. With that said, I think it’s always best to try and reach out before. Not to ask for permission but to see if there is an opportunity for collaboration, or upstreaming the code.
@anderseknert this was kind of my line of thought, I will reach out and see if what I've done makes sense for them and if not, there is no problem co-existing I suppose 🤔
Add comment