Can we PLEASE get a small public roadmap?

Feedback
1

:rotating_light: IMPORTANT. PLEASE READ THIS LOGSEQ TEAM (pretty please)

I know this has been asked for in many instances, but I believe now might be a better time.
Could the team please invest some time in writing a (at least small) public ROADMAP?
As a user, I have absolutely no idea what to expect from this project. The latest major features that were developed came with absolutely 0 warning or input of any kind from us users: the last one is the MCP server I believe, and before that it was the Logseq CLI, and before that the Vector search capability (Im not complaining about these features though, they are awesome!).

By looking at the commit history daily, I can see that the team is currently working on RTC and the latest new feature they are polishing seems to be an audio recording and transcribing tool for mobile. But again, this last feature is appearing out of thin air, at least from the perspective of the users, with absolutely 0 community feedback or, at the very least, announcement of any sort.

To conclude, what am I ACTUALLY asking for?

Not much. Just a small checkbox list, maybe on the README file on the Github repo so that the team doesnt have to bother doing anything OUTSIDE their development environment. This list would simply include:

  1. what the team is working on

  2. what the team is planning to work on

Features on (2) should only include anything planned for the IMMEDIATE future, so anything that the team knows they are going to work on. For example, the 1st commits referencing the audio transcribing feature appear on Sep 4 ( feat(mobile): audio record && transcribe by xyhp915 Ā· Pull Request #12105 Ā· logseq/logseq Ā· GitHub ). I imagine that the team knew they were going to work on this new feature at least some days (or weeks?) BEFORE the first commits showed up on Github out of the blue. All Im asking for is that the team adds a new entry to the checkbox list whenever they have decided to work on a new feature, then they can tick it off whenever they feel its finished.

Thank you for reading, and I hope Logseq continues to improve as it is doing now

2

I agree. There is this trello roadmap though: Trello

But I donā€™t see the point of that roadmap if they still drop features not mentionned in the roadmap.

2 Likes
3

Thanks for the suggestions!

We definitely need a ā€œliveā€œ public roadmap, our plan is to host it directly on Logseq because weā€™re collaborating using Logseq :smiley:

Iā€™m going to post screenshots from our internal team graph until Logseq publishing is ready.

image
image1970Ɨ1712 222 KB

23 Likes
4

Oh my god no way we are getting built-in calendar support, I think Im gonna cry. Awesome, and thank you so much for the response!

6 Likes
5

Youā€™re welcome, thanks for the post!

5 Likes
6

Hope we can get 1.0 version quickly. Thanks for your Logseq

7

Great to see this.

The one feature that I see as a gap for my long-page use cases is proper support for automatic/dynamic Table of Content generation from markdown headers. All KM tools I used before had it and itā€™s a pain not having it. There was only one addon that could handle internal links in the TOC for long pages and it disappeared from GitHub a year ago. The only remaining plugin in the marketplace only works for short pages, links work as long as the page is shorter than the ā€œlazy loading" threshold.

Hopefully the DB re-design will embed this or handle plugins and/or lazy loading differently so the TOC links will allow jumping to anywhere in the page

8

I dont see whiteboards here . Also can you tell us whats under RTC Others?

3 Likes
9

Yea, I was also hoping to see whiteboards somewhere :confused:

4 Likes
10

Thank you for the roadmap!

11

Hi! I am very interested in the calendar integration. What is the rough idea? Capture events created in logseq blocks with properties like start and end or even allow online calendars via calDAV or import via ical?

This is the point I struggle with the most: I want everythin in one place and as of now if there is an event I create it in Logseq as a scheduled task and put it in my calendar bc I need reminders and sync, things I donā€™t get from Logseqā€¦ that really is a hustle!

1 Like
12

is the sync between mobile beta app and desktop db version planned?

1 Like
13

That is part of the RTC, on the roadmap. It is currently in closed alpha testing.

2 Likes
14

Hopefully, it will still be possible to synchronise data between devices using Syncthing. That has been a huge advantage so far.

2 Likes
15

I personally lost hope a while ago to try and find ā€œone software to rule them allā€ā€¦ I hope youā€™ll be more lucky than me :slight_smile:

1 Like
16

Hey @tienson,

A community manager of some kind could add a lot of value in interfacing between how all of you (engineers) convey and update progress, features, etc, in ways that the average user is reading it.

The roadmap image is a nice start but doesnā€™t really tell us much. Itā€™s opaque with very broad topics in some cases that could relate to one of many things. There are inconsistencies between that image, the Trello board, and the actually GitHub tracked development. Itā€™s not clear what to trust. What does a checkmark mean? Is it really complete? What is ā€œcompleteā€ for the ones marked as checked? What does the half filled circle mean? Partial completion, but what? How much remains?

In your roadmap image, are we meant to infer that both the closed DB alpha and closed DB beta are complete?

If so then why does the Trello board indicate the closed DB Alpha as still in progress with no task for a closed db beta?

Sorry to be so nitpicky but this is really just meant to highlight why I think your team needs a ā€˜non-engineerā€™ who can help translate and valorise all the work you guys are doing into human readable terms. We could then get excited about that work.

And pleaseā€¦ please. Tell us your deadlines! Even with the caviat that deadlines can change, but communication about why and indication of what the new goals are would go a long way to build trust.

Itā€™s very clear to me how much you care about this project and everyoneā€™s experience of it. Thank you for that. Itā€™s one of the big reasons Iā€™ve been holding on.

9 Likes
17

I actually made an account here to cross-post a Reddit post (I canā€™t post links?) I had made as some people had mentioned that it should be here on the discourse and not Reddit, but I think RDs really summed it up well there too - the community could really use someone who engages regularly and consistently.

Two incredibly great people come to mind, both on other Discourse communities:

Kirby CMS Discourse - Texnixe - Answers everyone with incredible consistency, relays information back and forth with the team and involves devs/engineers when necessary. (10yo account, 127k posts read, 5mon read time, 32.5k posts created)

Mudita Discourse - Urszula - She answers every single question and the ones she cannot, she relays to/from the devs and gets back to everyone. She is incredibly consistent, warm and builds so much trust. (6 year old account, 35.1k posts read, 19d read time, 6.5k posts created)

The funny thing is, as nice as it would be, Logseq doesnā€™t even need someone this engaged. Even someone who just posted a clear community-focused update and answered questions once a month would already be light years of what we have now. Without question, to the average non-technical user, this project seems completely dead.

TL;DR - @tienson please consider hiring a community ambassador/manager who answers everyoneā€™s questions and keeps an active relay between dev and users.

And quick question - when DB is released, is there an official path to migrating or are we expected to start fresh?

-ā€“

Iā€™ve been a logseq user for 4 years and opencollective subscriber for 3 and have constantly felt like I have no idea what is going on with the development/community.

What concerns me is reading more and more posts about people abandoning logseq not because of the app itself but just the utter lack of transparency and communication.

Itā€™s crazy to see the Obsidian sub with 265k members, 2.8k weekly contributions and 183k weekly visitors and then Logseq with 17k members, 158 weekly contributions and 8.7k weekly visitors.

Thatā€™s basically a 17x in community engagement here alone, let alone the general content stream available on all other channels (youtube etc). Of course, a lot of this can be considered noise and distraction, but itā€™s important to feel like something you plan to sink hours of time into using has an active community around it.

I understand that the appā€™s development is happening behind the scenes but it doesnā€™t help the community if nothing is communicated to existing and potential users.

I am pleading: please invest in some kind of ambassador/community engagement manager who can act as an intermediary between the development team and the rest of us and keep the lines of communication open to help foster a sense of trust in this productā€™s future - currently, everything seems very opaque, it doesnā€™t feel like thereā€™s any sense of active official community engagement at all.

I think this is a big deterrent to newcomers and causes existing users to question if they should really be investing time in something that feels, on the surface, dead.

Itā€™s very sad to see many people asking questions with no response whatsoever from the team and then a community member has to chime in months after the fact with an educated guess.

Itā€™s also sad to see recent posts like because they ring so true:

Migrating away from Logseq after years and Iā€™m feeling weirdly sad about it

Iā€™m moving to Obsidian mainly because I donā€™t trust the future of LogSeq.

I moved away to Obsidian. This is how.

lā€™ve become tired of the lack of releases, the lack of plugin support for the iOS version, and the frigging several times I had to input my vault password on iOS and desktop

Please bring on a dedicated Community Manager. We need a human element to reassure us that the time we are investing in this tool is safe. Seeing posts about people ā€œmigrating away due to lack of trustā€ is heartbreaking for those of us who love logseq and want it to succed.

5 Likes
19

Logseq-DB is no longer closed actually. You can either use it at https://test.logseq.com or download the desktop version at Build-Desktop-Release Ā· logseq/logseq@d867bf6 Ā· GitHub (scroll down to the bottom of the page and choose the version for your system, e.g. darwin-arm64 for MacOS).

1 Like
21

Actually, we got really active contributors who have been helping to communicate updates, etc. Just curious, do you feel that it is still considered inconsistent communication because it does not come directly from the dev team?

22

Sorry for the stupid question, once downloaded, how can one installs it?
Thank you