Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated fork - with some PRs #60

Open
eyJhb opened this issue Mar 19, 2019 · 9 comments
Open

Updated fork - with some PRs #60

eyJhb opened this issue Mar 19, 2019 · 9 comments

Comments

@eyJhb
Copy link

eyJhb commented Mar 19, 2019

I have forked this repo and merged some of the PRs I found the most interesting and relevant.
If you feel like anything else should be included or changed, please do make an issue with the fork and or do a new PR!

here

Thanks!

@ddugovic
Copy link

Thanks! (I know there's no CLA, but I happily consent to this.)

@eyJhb
Copy link
Author

eyJhb commented Mar 20, 2019

@ddugovic yeah, didn't really think of that! But I am hoping that the PRs I merged are okay ;)
But no clue if people will adapt to it! I need to make some changes to it too..

@PartialVolume
Copy link

When the maintainer prefers to leave the code as is, there's certainly no harm in forking, in fact I'd recommend it.

As for CLAs https://ben.balter.com/2018/01/02/why-you-probably-shouldnt-add-a-cla-to-your-open-source-project/

That article suggests projects are better if without them.

@buhtz
Copy link

buhtz commented Mar 7, 2024

It seems there is no reaction anymore from Toyoda-san.
I would suggest you to treat your repo eyJhb/sl as the "official one" and go on with developing and fixing. The GNU Linux distros will follow then.

@eyJhb
Copy link
Author

eyJhb commented Mar 9, 2024

Given the amount of issues/PRs that are open for sl (on my fork), I'm not sure it's a good idea that I maintain the fork anymore. Most likely someone with more time, that still uses sl would be better.

@buhtz
Copy link

buhtz commented Mar 9, 2024

In the end it doesn't matter if it is your fork, this repo (you take over) or another fork. Important is that something is rolling. 😄
But OK, thanks for your feedback.

IMHO in the first place it is important that the maintainer of this repo state in the README the current situation. The repo is dead (and this is OK).

@gresm
Copy link

gresm commented May 14, 2024

Seems like someone picked up your fork.

@eyJhb
Copy link
Author

eyJhb commented May 14, 2024

Oh nice! Hopefully they are better at it than me :D

@eyJhb
Copy link
Author

eyJhb commented Jun 8, 2024

Seems like someone picked up your fork.

It's a shame that the repo does not allow issues, unsure why however.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants