Announcement: status of the project -- maintenance paused until second half of the year

[joshuakto]

Thank you all for your interest in the project! There are a good number of issues filed and some PR! My bandwidth recently unfortunately does not allow me to put in additional maintenance effort for the moment but I will aim to reserve some time later this year to merge suitable PRs and address issues that need attention.

Time permitting, I will try to review the activities sooner if possible.

[lrlunin]

Should I reopen my pull request if it was stale closed by the github bot or it isn't necessary?

[savdeem]

When you add files to note (for example *.tar.gz) and synchronization git, and when you delete file from a note, after synchronization with git, this file still staing in git.

[joshuakto]

@lrlunin Should I reopen my pull request if it was stale closed by the github bot or it isn't necessary? Not necessary, I will keep a mental note, also thanks for contributing!

[progzone122]

@joshuakto Can you update the plugin version in the obsidian plugin store itself? The last time the release was updated was 8 months ago and because of that it doesn't have an important fix (https://github.com/joshuakto/fit/pull/21) that makes me unable to use the plugin. On iOS it's problematic to clone the repository. Thanks

[Demigoddd]

@joshuakto Thank you for the plugin and for your effort. I wonder if the ability to auto-sync at startup will be added? A necessary thing in the Git plugin, such functionality is present.

[andyjphu]

@joshuakto Are you open to more maintainers?

[github-actions[bot]]

Stale issue message

[ihtiandr9]

What help are you needed?

[dbarnett]

It is now "second half of the year", but considering this issue was autoclosed and isn't getting replies I'm guessing it's still paused?

After wrestling with both this and the https://github.com/silvanocerza/github-gitless-sync plugin, I'm very interested to fork an actively maintained version and start fixing up some major issues:

• Poor error messaging (improved in https://github.com/beachvisitor/obsidian-fit)
• Sync failure cases (#23) that look like trivial fixes (just guard changes in .obsidian when syncing)
• Some high-severity vulnerabilities in dependencies (braces, cross-spawn)

I'd also like to add some tests for the core sync logic, see if it's possible to allow syncing some settings data too, and pull in some other stale PRs and changes in forks.

My question: If instead of just forking I send PRs here for all that, will anyone actually review them? If not, anyone have preferences on how to manage a fork (naming, contribution guidelines, etc)? Obviously it's simpler if we can just contribute here without all the hassle of a hard fork, so LMK if you'd be interested to just add maintainers here and if buying some coffees would make it worth your while, but in any case I'd hope the project maintenance could be set up to be a little more pause-proof... 😆

[jc-nana]

Thanks again for everyone's interest! I am open to adding maintainers for reviewing PR and merging them; and sponsors will definitely make this project more sustainable financially. My bandwidth is unfortunately still limited now but I can set up a new branch where collaborators can contribute to. If anyone is willing to become a maintainer and dedicate effort to reviewing PR and testing those changes before publishing as a new obsidian package, please comment below so we can set that up.

Prior obsidian packaging maintenance / general software engineering experience would be preferred to keep the code quality decent.

I am pretty new to setting up a community-based open source project, so if anyone has experience on how to set that up, feel free to chime in and make suggestions along the way.