org-roam
Maintenance Status?
I see the org-roam organisation has multiple users, yet development has been stagnant for months with serious bugs popping up. What can we do about that?
Honestly I'd be up for a small sponsorship sum if I could then rest assured that roam will work consistently, as I base many of my daily workflows on it...
I'm concerned too. It might be as much a time issue as a sponsorship/money issue. How can we help? @jethrokuan @zaeph @progfolio what support do you need?
I stopped using org-roam quite some time ago because it became much more than what I needed/wanted out of such a system. I currently use a private package I've authored which is much simpler, but suits my needs. I'm also busy maintaining Elpaca and straight.el. I appreciate the gesture, but I wouldn't be the right person for the job.
It's most certainly just a time issue, and has nothing to do with sponsorship and money. I also no longer have a personal laptop, making any bugfixes near impossible. I want to address this, but i'll be preoccupied until at least mid September. There are 2 alternate options here:
- A successor for the project is found, who would do a better job at maintaining the project. If this option is chosen, I would like to find someone who shares my vision for Org-roam and keep it lean.
- Org-roam is forked and maintained by a separate maintainer.
@jethrokuan I have time, interest and (most of the) technical skills to help out with org-roam. Clearing issues, verifying bug reports, clearing PRs, etc. I agree with your focus on keeping org-roam lean.
But I'd rather not take over as sole maintainer - for a project like this there should be multiple brains involved. Please consider if you're willing to allow extra people to merge PRs and how to do so safely.
@jethrokuan:
i'll be preoccupied until at least mid September.
@jmay:
But I'd rather not take over as sole maintainer
Would it be acceptable for both of you to get @jmay now to help out, with the perspective of @jethrokuan joining forces again later this year? @jmay could begin with a focus on fixing bugs, which would help him get a good start feeling and finding into the role without the need to make fundamental design decisions on day one.
Would it be acceptable for both of you to get @jmay now to help out, with the perspective of @jethrokuan joining forces again later this year?
@jethrokuan Friendly ping. :) It would be great to hear your thoughts on this.
Hi,
Sorry for the lack of news until now. I’m settling in a new job, and I could pick up the flame again in early October. I’d need to familiarize myself with the design changes @jethrokuan introduced in v2, but I’m confident I could pick things up quickly.
I don’t think the current state of the repo is so dire as to require immediate action, but I appreciate your volunteering, @jmay.
I’ll update here once I’m ready.
@jethrokuan:
I also no longer have a personal laptop, making any bugfixes near impossible. I want to address this, but i'll be preoccupied until at least mid September.
Are you still in need of a new laptop? Would it be cool if org-roam community members got you one? I don't mean to presume anything about your life, but this could be a straightforward way for us to offer support to the project.
How about merging Org Roam into Org, now that version 2 is lean and Emacs ships with SQLite out of the box? The project might get more love on the mailing list and get better integrated with Org. For example, the tests can run together with Org tests, and so on.
How about merging Org Roam into Org, now that version 2 is lean and Emacs ships with SQLite out of the box? The project might get more love on the mailing list and get better integrated with Org. For example, the tests can run together with Org tests, and so on.
Org should aim to become leaner, not take on the maintenance burden of its many extensions. An effort in this direction has been moving many of the repositories that were in "org-contrib" into their own separately maintained repositories.
@progfolio
I see where you are coming from, but I also think that Org Roam, stripped to its core, is fundamental to note taking.
Nicholas Vollmer @.***> writes:
Org should aim to become leaner, not take on the maintenance burden of its many extensions. An effort in this direction has been moving many of the repositories that were in "org-contrib" into their own separately maintained repositories.
Yes and no.
There are likely parts of org-roam that could be useful for Org in general. For example, roam capture templates that allow creating notes in individual files - this would be a natural addition to the existing org-capture functionality.
On the other hand, the whole org-roam is not something that should be added because it will increase the existing maintenance burden - Org already has many non-trivial parts and a limited number of maintainers.
-- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Reading this thread, it looks like (1) Jason (@jmay) is willing to become a maintainer provided he is not the sole maintainer, (2) Leo (@zaeph) is willing to resume work as a maintainer once he familiarizes himself with v2, and (3) Jethro (@jethrokuan) is willing to walk Leo through the relevant v2 changes. So maybe a way forward is for Jason, Leo and Jethro to start a conversation to coordinate things?
Unfortunately, I lack the technical skills to be of any use, but if money (rather than time or motivation) is an impediment, I’d be more than happy to contribute.
My current main concern is the looming incompatibility of Org-roam with Org Mode 9.7. As I don't know much about Org-Roam, Org Mode, and Elisp in general, I neither can help directly nor do I know how big of a task the change for the API update is.
RecentlyRezzed @.***> writes:
My current main concern is the looming incompatibility of Org-roam with Org Mode 9.7. As I don't know much about Org-Roam, Org Mode, and Elisp in general, I neither can help directly nor do I know how big of a task the change for the API update is.
Mind sharing the relevant bug report that details the incompatibility?
-- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Mind sharing the relevant bug report that details the incompatibility?
I was wrong. I thought the problem described in https://github.com/org-roam/org-roam/issues/2361 , https://github.com/org-roam/org-roam/issues/2381 and https://github.com/org-roam/org-roam/issues/2384 was due to some changes that also broke org-ql and therefore the solution was to pin Org Mode to a previous version as it is mentioned in some of the comments. But the solution is to use a more current version of straight.
I am sorry for the inconvenience.
I see @jethrokuan is still merging PR's as of Jan, 2024 but there's a bit of a vacuum on this thread for clear maintainership direction.
Can we get a status update from @jethrokuan or Jethro's nominated successor on the successor status?
You don’t need to worry about maintenance because we still have 1) plenty of expertise to go around, and 2) access to the repo. I understand that a dip in availability is a barrier to adoption, but we haven’t abandoned the project.
Re: my availability, I can’t commit the time towards active maintenance just yet, but I’m still available here to answer questions and review critical issues. Anything more involved will have to wait.
Would you like some help managing the issues or PR backlog? At the very least I'm sure some of us are willing to go through old issues and point out which may already be fixed, or offer general support where we can, recommend which ones should be closed, etc. Couldn't hurt to clear out some issues?
i'm happy to add people to the organization, please let me know if you would be willing to take on general maintenance.
@jethrokuan , please add me to the organization so that I may help with maintenance, etc.
@jethrokuan , please add me to the organization so that I may help with maintenance, etc.
Yeah me too if you’re still looking for volunteers.
I think it is a good idea to add a few people who will merge fixes as maintainers.
While this project seems functionally stable, lots of fixes will be needed.
Yes, for example there have been a lot of good discussions around performance of huge notes collection (caching, memoization etc…) in recent months and it would be great to finally settle on a built-in solution.
@jethrokuan I would also enjoy to be a maintainer, starting to help with simple tasks such as:
- merging non critical PRs, like https://github.com/org-roam/org-roam/pull/2430
- triaging existing issues by applying common tags such as "bug", "feature request" etc…
Thanks a lot for the invitation jethrokuan. I was able to join the org-roam organization. :+1:
Unfortunately it appears that the permissions assigned to the base membership does not allow any meaningful operations on the repo. As I described in the previous post I attempted to do non-critical tasks to begin with, such as adding tags to issues and merge the PR about the typos mentioned above, but nothing is available yet. I'm no expert about GitHub RBAC system, but I believe there may remain something to do in the repo settings to unlock this. I believe other people who joined recently like lewisbrown and dustinfarris may be stuck in a similar limbo.
Thanks a lot.