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

Move manpage content back to README.md #134

Closed
wants to merge 1 commit into from

Conversation

darthwalsh
Copy link

Homebrew/brew#16822 Removed autoupdate from the official manpage.

Add that documentation back into README.md so the link isn't misleading. It seems to render fine on github.com

Homebrew/brew#16822 Removed autoupdate from the official manpage.

Add that documentation back into README.md so the link isn't misleading.
It seems to render fine on github.com
@swissbuechi
Copy link
Contributor

swissbuechi commented Mar 28, 2024

I once created a github action for this project which auto generated the manpage for the readme.

I'll reopen this PR 🚀

#114

@darthwalsh
Copy link
Author

@DomT4 What's your preference this PR or #135? Either way, it would be great to restore the help content in the README.

@swissbuechi
Copy link
Contributor

swissbuechi commented Jun 3, 2024

@DomT4 What's your preference this PR or #135? Either way, it would be great to restore the help content in the README.

Sadly @DomT4 is not quite responsive.
Forst priority should be PR #136 to fix the integration tests. Another month passed without any activity... Not a lot of fun contributing to a project you like, just to get left on "read".

Take a look at PR #119, this would address a very serious scheduling issue. It's beeing left without any feedback for nearly half a year...

Seems like a dead project to me, maybe time for a new fork to take over...

@DomT4
Copy link
Owner

DomT4 commented Oct 1, 2024

Sadly @DomT4 is not quite responsive. Forst priority should be PR #136 to fix the integration tests. Another month passed without any activity... Not a lot of fun contributing to a project you like, just to get left on "read".

Take a look at PR #119, this would address a very serious scheduling issue. It's beeing left without any feedback for nearly half a year...

Seems like a dead project to me, maybe time for a new fork to take over...

I do apologise. I don't have the time I used to - I work 42-50 hours a week + travel 2 hours a day to do so, and then have the rest of life to contend with after that. I'd love for this to be something that I'd be able to afford to take time away from that for and find that passion again but understandably enough it's not like a tap to update Homebrew in the background generates much income.

I think I've said it elsewhere before but I do largely see this project as feature complete albeit with some cleaning up/tweaking to existing features/etc needed. I don't generally plan to go much further with it than I have.

Obviously if someone wants to fork the project and drive it forwards in a different direction that's the beauty of open source and they have my blessing to do that. Otherwise I'll continue to code review when I can, and update/tweak things periodically, but it's just a case that when I'm getting up at 7am and not getting home until 7pm or later most days by the time I eat/clean/etc there's minimal time/energy left in me. It's not a lack of appreciation for people caring or being interested in the project, or your own significant work @swissbuechi.

@darthwalsh - I have merged @swissbuechi's PR to update documentation automatically and consequently will close this. Thank you though.

@DomT4 DomT4 closed this Oct 1, 2024
@swissbuechi
Copy link
Contributor

Sadly @DomT4 is not quite responsive. Forst priority should be PR #136 to fix the integration tests. Another month passed without any activity... Not a lot of fun contributing to a project you like, just to get left on "read".

Take a look at PR #119, this would address a very serious scheduling issue. It's beeing left without any feedback for nearly half a year...

Seems like a dead project to me, maybe time for a new fork to take over...

I do apologise. I don't have the time I used to - I work 42-50 hours a week + travel 2 hours a day to do so, and then have the rest of life to contend with after that. I'd love for this to be something that I'd be able to afford to take time away from that for and find that passion again but understandably enough it's not like a tap to update Homebrew in the background generates much income.

I think I've said it elsewhere before but I do largely see this project as feature complete albeit with some cleaning up/tweaking to existing features/etc needed. I don't generally plan to go much further with it than I have.

Obviously if someone wants to fork the project and drive it forwards in a different direction that's the beauty of open source and they have my blessing to do that. Otherwise I'll continue to code review when I can, and update/tweak things periodically, but it's just a case that when I'm getting up at 7am and not getting home until 7pm or later most days by the time I eat/clean/etc there's minimal time/energy left in me. It's not a lack of appreciation for people caring or being interested in the project, or your own significant work @swissbuechi.

@darthwalsh - I have merged @swissbuechi's PR to update documentation automatically and consequently will close this. Thank you though.

Now I feel kind of bad for pointing this out as a "dead project". I totally understand your point about work/life balance and after all you always should put yourself first!

I would love continuing with my contributions and don't really feel like the project should be transferred/forked at the moment.

As long as you review my PRs once every few months, I'm completely okay with that.

Keep it up and enjoy yourself.

@darthwalsh darthwalsh deleted the patch-1 branch October 1, 2024 20:47
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

Successfully merging this pull request may close these issues.

3 participants