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

PSA: I've made a fork, and I do intend to maintain it. #137

Open
johnalanwoods opened this issue Jan 23, 2024 · 20 comments
Open

PSA: I've made a fork, and I do intend to maintain it. #137

johnalanwoods opened this issue Jan 23, 2024 · 20 comments

Comments

@johnalanwoods
Copy link

johnalanwoods commented Jan 23, 2024

Hello,

I'm John, someone who cares deeply about the Unix philosophy and software engineering generally.
I loved this repo and recommended it many times, but I am frustrated with the lack of ownership .

In the spirit of open src, I've forked it (I appreciate there are 700 forks), but I DO intend to maintain it, and I WILL merge sane PRs.

I want to create a canonical src of modern Unix tooling.

I'm someone who daily drives Linux and macOS, and put it this way, my .vimrc is 1500 lines.

Please feel free to contribute, I'd appreciate it.

@johnalanwoods
Copy link
Author

I've updated Exa to Eza, Dog to Doggo, and also made sure the screenshots work.

@chapmanjacobd
Copy link

canonical src of modern Unix tooling

This is a noble goal. It would be helpful to have better ranking of alternatives. For example, what is the difference between httpie, curlie, and xh ? They all seem to be doing many of the same things;

Likewise "with a focus on improved performance" is not very objective. It would be more useful to have actual performance comparisons. To be a true canonical source I would think some improvements like that would be required

just some thoughts

@johnalanwoods
Copy link
Author

johnalanwoods commented Jan 23, 2024

For example, what is the difference between httpie, curlie, and xh ? They all seem to be doing many of the same things;

Completely agree. We should aim to curate a list of the essential modern unix tools, where overlap is minimised and relevance is essential.

My personal day to day is so dependent on these tools that I felt the need to drive the catalog.

Likewise "with a focus on improved performance" is not very objective. It would be more useful to have actual performance comparisons. To be a true canonical source I would think some improvements like that would be required

Also love this, many tools I use like dd are just great, it's not just "performance" that is relevant, but relative delta in UX. I'd love this expansion.

@ibraheemdev
Copy link
Owner

ibraheemdev commented Jan 23, 2024

Hey, just happened to see this despite not really looking at this repository. I created this llist ist a while ago but don't have time or the interest to maintain it anymore. Would you open to becoming a maintainer on this repository @johnalanwoods? That should be better than a less accessible fork. You can feel free to make any reasonable changes (whether layout or content) without my explicit approval, your comments here already resonate with my opinions about this list :) My only request would be for this list to not turn into another awesome-terminal, staying focused on the current theme, alternatives to existing tools.

@ccoVeille
Copy link

Hi @johnalanwoods

There is currently a doubt about what would you plan to do with
https://github.com/johnalanwoods/maintained-modern-unix

@ibraheemdev replied to you here by suggesting that he could grant you as a maintainer of existing https://github.com/ibraheemdev/modern-unix project

Could you please share your thoughts and reply to @ibraheemdev in this issue?

I might be wrong but I think that I'm not the only one interested in knowing what you plan.

Here is an issue raised by @nielsbom on your project johnalanwoods#3

Thanks

Also thank you @ibraheemdev , you helped to discover great tools years ago.

@johnalanwoods
Copy link
Author

I’d rather not become a maintainer of someone else’s repo.

Going to take this in my own direction.

@ccoVeille
Copy link

I’d rather not become a maintainer of someone else’s repo.

Going to take this in my own direction.

Thanks for replying me.

@khaister
Copy link

Hey, just happened to see this despite not really looking at this repository. I created this llist ist a while ago but don't have time or the interest to maintain it anymore. Would you open to becoming a maintainer on this repository @johnalanwoods? That should be better than a less accessible fork. You can feel free to make any reasonable changes (whether layout or content) without my explicit approval, your comments here already resonate with my opinions about this list :) My only request would be for this list to not turn into another awesome-terminal, staying focused on the current theme, alternatives to existing tools.

Hi @ccoVeille I'm interested in becoming a maintainer of this repo. Please LMK.

@ccoVeille
Copy link

Hey, just happened to see this despite not really looking at this repository. I created this llist ist a while ago but don't have time or the interest to maintain it anymore. Would you open to becoming a maintainer on this repository @johnalanwoods? That should be better than a less accessible fork. You can feel free to make any reasonable changes (whether layout or content) without my explicit approval, your comments here already resonate with my opinions about this list :) My only request would be for this list to not turn into another awesome-terminal, staying focused on the current theme, alternatives to existing tools.

Hi @ccoVeille I'm interested in becoming a maintainer of this repo. Please LMK.

I talked but I'm only a random guy who appreciate @ibraheemdev work. He is the owner and creator. He might reply you.

@khaister
Copy link

Hey, just happened to see this despite not really looking at this repository. I created this llist ist a while ago but don't have time or the interest to maintain it anymore. Would you open to becoming a maintainer on this repository @johnalanwoods? That should be better than a less accessible fork. You can feel free to make any reasonable changes (whether layout or content) without my explicit approval, your comments here already resonate with my opinions about this list :) My only request would be for this list to not turn into another awesome-terminal, staying focused on the current theme, alternatives to existing tools.

Hi @ibraheemdev I'm interested in becoming a maintainer of this repo. Please LMK.

@ccoVeille
Copy link

Hey, just happened to see this despite not really looking at this repository. I created this llist ist a while ago but don't have time or the interest to maintain it anymore. Would you open to becoming a maintainer on this repository @johnalanwoods? That should be better than a less accessible fork. You can feel free to make any reasonable changes (whether layout or content) without my explicit approval, your comments here already resonate with my opinions about this list :) My only request would be for this list to not turn into another awesome-terminal, staying focused on the current theme, alternatives to existing tools.

Hi @ibraheemdev I'm interested in becoming a maintainer of this repo. Please LMK.

I'm not sure but I would suggest to create a github.com/modern-unix organization or simply a user and fork historical project in it. So it would keep the stars things. And archive the original one after updating it to mention the main project is now on github.com/modern-unix/modern-unix

Another pattern could be to move the current project into modern-unix org and then fork again it in @ibraheemdev, update the readme, then archive it.

I remember the point raised by @johnalanwoods that maintaining someone else repository is a bit strange.

These are the patterns of migration I'm thinking about. I could be wrong and something else would be better.

I know it's somehow also about mitigate with everyone else ego. 😅😁

@johnalanwoods
Copy link
Author

I'm open to these suggestions!

@nielsbom
Copy link

+1 on making it an organisation, my guess is that that's the best for the long term.

If it becomes an org I'm also interested in helping out.

@ccoVeille
Copy link

So everyone is now waiting your reply @ibraheemdev

What are your thoughts about all these ideas?

I'm also curious to know if everyone would agree to maintain a project to be github.com/modern-unix/modern-unix

This question are for you guys: @khaister @johnalanwoods @nielsbom

Thanks

@nielsbom
Copy link

Wrt the name of the org: modern-unix is "unavailable" as an org-name on GitHub.

I do think "unix" is the right term (instead of "linux"), but maybe we can make it more broad by naming the org modern-cli.

So then we'd get https://github.com/modern-cli/modern-unix

Please 👍 or 👎 for that suggestion or comment alternatives.

@ja0nz
Copy link

ja0nz commented Mar 26, 2024

Glad for the momentum here️✌️ modern-cli has my +1
I also would like to throw in modern-tools as an org for a even more broader context. The repo can be more specific anyway. I found it also a bit catchier😁

@aduzsardi
Copy link

or maybe any of these modern-cli-utils or modern-cli-tools

@nielsbom
Copy link

nielsbom commented Mar 27, 2024

I've done some things

If anybody else wants to be added to that organization: let me know.

Update 2024-04-01, haven't heard from @ibraheemdev yet.

@ccoVeille
Copy link

Based on this https://github.com/orgs/community/discussions/22669#discussioncomment-3237667

I would say that if @ibraheemdev moves it to https://github.com/modern-cli/modern-unix nothing else will be needed

GitHub will automagically redirects users

@nielsbom
Copy link

nielsbom commented Apr 9, 2024

FYI: it's been 13 days and I haven't heard back from @ibraheemdev yet. I hope he's alright.

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

8 participants