Project moved to https://github.com/AlexanderWillner/kingraph

[janisz]

It looks like this project is dead but it's continued by @AlexanderWillner https://github.com/AlexanderWillner/kingraph

[vorburger]

https://github.com/elenawinters/kingraph has something more recent; see also discussion in https://github.com/elenawinters/kingraph/pull/2, and my https://github.com/vorburger/kingraph.

[vorburger]

@rstacruz perhaps we can use this issue here on your original repo instead of the closed https://github.com/elenawinters/kingraph/pull/2 in @elenawinters, to continue further discussion about what was started there?

Re. kingraph name on NPM, I personally don't have any particular interest in or use for that, at least for now. Full Disclosure: I just want this for personal use, but am very happy to share what I am doing. And not looking for additional project to spend too much time to maintain. 😈

Re. happy to make an edit on the readme for my repo to point to the most active fork, that fork currently appears to be my own. I had a brief look over the Network Graph, and started with @elenawinters HEAD, which also includes work by @marekkalnik @raisedadead @vabene1111 @AlexanderWillner @constantinmaes.

I was wondering if @AlexanderWillner re. "Might make sense to have a GitHub Kingraph Organization - but at the end, doesn't matter which repo to improve step by step." might be something you would consider doing? Concretely, create an org, and move this rstacruz/kingraph repo under that org? https://github.com/kingraph seems to be already taken, is that yours, or a squatter? 🤣

@rstacruz if you are concerned about any additional workload this could generate, rest assured that I'm not "expecting" anything 🍭 of you... it's up to you if you then want to invite an additional contributors to an Org. I would be honoured, if you so chose. It's also totally "fair", at least to me, to then let such additional new contributors decide what they want to merge, what pull requests they would like to review (or not), which issues they want to engage on (or not) - we're all busy, everyone's time is limited. But we're more together than the sum of each of us. I have used a model like this on https://github.com/lastnpe, where I basically pretty quickly invited anyone who sent 2-3 PRs to become an additional commiter, and at least for that community, that worked out well, for me; I launched it, found other people interested - and am currently not involved in it anymore myself!

So to be even more explicit: If you did create an org and invite me as a co-owner/admin, I personally would probably push my changes there instead of my fork, and review anyone else's PRs as long as they build and don't break existing tests [I've set an Action on my fork], and invite such contributors as new committers. I myself likely would not have the time to offer much "support" on issues. Other additional committers might though. You wouldn't really have to do anything additional, after creating the org and moving the repo - unless new activity motivates you to, obviously.

@momack2 FYI (given your at least past interest on some of the open issues)

[AlexanderWillner]

I was wondering if @AlexanderWillner re. "Might make sense to have a GitHub Kingraph Organization - but at the end, doesn't matter which repo to improve step by step." might be something you would consider doing? Concretely, create an org, and move this rstacruz/kingraph repo under that org? https://github.com/kingraph seems to be already taken, is that yours, or a squatter? 🤣

No. Also no (public) activity since it was registered in 2014...

[rstacruz]

Good points - moving to an org definitely makes sense! Given @kingraph is taken, @kingraph-diagram might be a good alternative. Any thoughts on the name?

[marekkalnik]

It may be possible to get kingraph if you want it ?

https://dev.to/lucis/how-i-got-the-github-username-of-my-dreams-5db5#:~:text=TL%3BDR%3A%20If%20the%20user,you'll%20probably%20receive%20feedback.

[AlexanderWillner]

Got feedback:

Thank you for your request. It appears that you are asking about releasing a dormant or inactive username. We no longer review requests to release dormant or inactive usernames.

[rstacruz]

I'll move the repo to kingraph-diagram/kingraph, and publish the npm package as @kingraph/kingraph. The kingraph npm package name has been taken by another fork. @AlexanderWillner if you have an npm username, let me know and I can add you.

[AlexanderWillner]

Now I have: alexander.willner

[giganteous]

any progress on this?

[AlexanderWillner]

I think @rstacruz wanted to setup an NPM package (not done I think) and a organisation kingraph-diagram seems to exist...but no repo yet

[hasangokdag]

leaving a comment to see where this goes

[AlexanderWillner]

Might make sense to create another organization. Depends a bit whether there are volunteers interested in joining.

[giganteous]

Heya,Im not particular interested in contributing: i rewrote most of the code in python as I generally have no nodejs installed. I did find a bug (really an unused code path), if you're interested I could writethat down. Nice to see others picking this up: it is very lean.regardskaiSent from my iPhoneOn 4 Jun 2024, at 14:12, Alex @.***> wrote: Might make sense to create another organization. Depends a bit whether there are volunteers interested in joining.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

[AlexanderWillner]

A rewrite in Python sounds appealing...

[giganteous]

I've uploaded my python "fork" to https://gitlab.com/giganteous/famstam. It took some effort to get roughly the same output with my large family, but I managed.

I don't consider myself a programmer: there's probably an even easier way to template this using jinja or something.