Is this still under active development?

[seagoj]

I am intrigued by the idea, but it seems like there haven't been any recent commits.

[philoserf]

Ping @tmrts

The project has collected a few more stars. Good job. Might be time to recruit a few collaborators to help triage, test, and merge.

[Ilyes512]

I would like to help out... Got some (easy to implement) idea's and it looks like I just found a bug that I will try to fix.

ping @tmrts So what do you say? I would rather prefer to work in this repo then perform a hard fork...

[schmunk42]

Would be great if someone could maintain an updated fork.

[Ilyes512]

I am sort of doing that here https://github.com/Ilyes512/boilr

edit: fixed link

[jackwilsdon]

@Ilyes512 would that not be better as just a fork with issues enabled? I'm not a fan of all of the existing commits being attributed to you. (oops I'm wrong about that!)

[Ilyes512]

@jackwilsdon what? I did not change any of the original commits? I also added a disclaimer here https://github.com/Ilyes512/boilr#note So not sure what you mean with "commits being attributed to you". So please explain what you mean.

Maybe I should't have chosen to "hard" fork it, but I got a little "scared" after reading this https://www.niels-ole.com/ownership/2018/03/16/github-forks.html Did not wanted to deal with that chance.

[jackwilsdon]

It looks like your hard-fork has re-attributed all of the commits to you (I'm sure that was not your intent), although I'm not sure that there's all that much that can be done in this case (due to how GitHub manages who commits belong to).

I can understand your concern with GitHub's forks, but the issues listed in that article seem to relate to repositories which are already private. Those don't seem to apply here thankfully;

• If the repository is deleted then one of the forks becomes the new base
• If the repository is made private then one of the forks becomes the new base

[jackwilsdon]

Ah my apologies @Ilyes512, I see you've been adding additional commits! Please ignore everything I've said regarding that. From the first page of commits it looked like existing ones had been re-attributed to you (I didn't notice they were new ones 😖).

[Ilyes512]

Okey, glad we solved that misunderstanding :)

I actually needed to read the article (I did now, but before I actually only skimmed it and missed the preivate repo part). I will try and fix the repository (by having it linked again to the original), but I believe that wont be as easy (would need to delete current repo, refork it and re-release whatever I released). Might not be worth the trouble, but it would be nice.