Requests to join the organization

[eliandoran]

Everyone is free to join the organization if you would like to contribute to the future of Trilium Notes.

Simply leave a comment here and we'll come back to you.

Also, please join our conversation on 💬Matrix

[meichthys]

@eliandoran count me in! I won't be able to contribute much to the code since I'll be occupied with family things in the near future, but I will do my best as I have in the original project to triage issues and keep the documentation up to date.

[eliandoran]

@meichthys , really glad to hear that. :)

You should already be invited. Please check your email. If not you might be able to access it here: https://github.com/orgs/TriliumNext/people/pending_invitations (not sure of the exact link).

[Nriver]

Count me in :)

[eliandoran]

@Nriver , that is really great news.

I was already looking at your repo regarding translations: https://github.com/Nriver/trilium-translation .

Pragmatically speaking, I think you'll be a great asset if we could introduce translation support without having the same restrictions as you had on your repo (having proper translation files instead of having to find & replace all strings in the project).

[justyns]

Count me in as well

edit: I should mention I can't promise a lot of time between work and personal stuff, but I'll try to!

[eliandoran]

@justyns , invitation sent. We all have time constraints, so no worries about that.
Feel free to pitch in any ideas you might have, brainstorming is also useful.

[McSido]

I would also be interested in joining. I've been using Trilium daily for a couple of years, but didn't go deeper into the code besides writing scripts for my own usage or to debug if something went wrong.

This move towards being more community owned and the direction proposed (e.g. regarding TypeScript) sound really appealing to me and something I'd like to be involved in. Depending on my available time either by code or other things that can bring the project forward

[eliandoran]

@McSido , sounds good. Invitation sent.
Looking forward to your ideas and contributions.

[rodrigoalexandrecosta]

Hi, I also would like to join.

I'm a backend developer but have little-to-none experience with frontend and javascript in general yet. I've been using Trilium for some time and actually been redirecting my learning and studying to be able to contribute with code in the near future.

Nevertheless, I love Trilium and will be extremely happy to join the community and see where this next phase will take us.

[eliandoran]

@rodrigoalexandrecosta , sounds great. Invite sent.
Maybe you could have a look at the backend when you have the time and think about some improvements or bugfixes we can do.
Also it would be really nice if we could look a bit into improving the test coverage of the backend, if you have experience with that.

[rodrigoalexandrecosta]

Thanks @eliandoran. I'll most certainly do that. I work primarily with Python/Django and worked previously with Java/Kotlin/Springboot, like I said, no experience with Javascript/Node, but that'll come in the near future.

[perfectra1n]

Count me in as well! I'm a contributor on trilium-chat, wrote pytrilium, and bothered Nriver with my PRs on awesome-trilium every so often :)

I've also sponsored zadam in the past, so I'm excited to see where this goes.

[eliandoran]

@perfectra1n , sounds great. Welcome on-board! :)

[j-tirelli]

I'd like a seat at this table too, please. I'm a recent convert to Trillium and haven't contributed to this community, but I am a Front-end developer (Typescript, React), with Node experience as well.

[eliandoran]

@j-tirelli , really nice. I would really appreciate it if you could help us port the client or server to TypeScript. Invite sent.

[vlasy]

Hi, I'm interested in joining too. I am a backend (mainly Node.js) developer and using Trillium for a few years. I have a lot of other obligations now, but would like to contribute, once there is a time.

Thanks

[eliandoran]

@vlasy , perfect. Invitation sent.
Looking forward to working with you.

[sigaloid]

I'm interested - I run trilium.cc, and have contributed in the past (and am generally very interested in its development as a daily user). Looking forward to what we can do to improve Trilium!

[eliandoran]

@sigaloid , really glad to have you. Welcome on board! :)

[WPum]

Hi, I would like to join.

I have been using Trilium for more than three years and have developed dozens of plugins for it. It would be exciting for me to contribute to Trilium in the future 😄

[eliandoran]

@WPum , welcome!

[WantToLearnJapanese]

I want to join.

[eliandoran]

Done.

[Asm-Def]

Hi, I'm interested in joining too.
I'm a PhD student in intelligent graphics, initiated a jupyterlab plug-in project that now has 8.9k stars, and currently working on a plug-in to implement the spaced repetition algorithm in trilium

[eliandoran]

@Asm-Def , sounds great. This would greatly benefit from implementing a proper plugin system as mentioned in #6 . Let me know if you have any particular needs in terms of API.

[natalyjazzviolin]

Hello! I'm a new user and would absolutely love to contribute!

[eliandoran]

Invitation sent. :)

[mondayrobot]

Hey, I would like to join as well. I don't code, so my contribution would be limited. I could help with things like testing, documentation or how-to guides (I'm an instructional designer "by day"). I'm a longtime Trilium user and I made a theme a while back.
Thanks!

[eliandoran]

Nice to have you. Invitation sent.

[meichthys]

https://github.com/readme/featured/open-source-non-code-contributions

[mondayrobot]

Very useful. Thanks!

[alexpietsch]

Hello! I use Trilium for some time now and I would love to support it's future

[eliandoran]

Welcome!

[Nmohamud]

Hi,
I would like to join.
Thx!

[meichthys]

Done. Welcome, and we look forward to your contributions!

[thfrei]

Hey
I implemented the trilium excalidraw integration (zadam/trilium#2798) and would love to be part of the new community and also implement some features / stability issues.
Thanks and best wishes
Thomas

[meichthys]

Done. Welcome, and we look forward to your contributions!

[CobriMediaJulien]

Thomas, did u join any of the communication channel the org is using e.g. Discord or Element? I have 1 question regarding the Excalidraw integration.

[doobes]

Wow!

I just literally an hour ago installed Trilium on my laptop. I'm gobsmacked.

Last month I spent a goodly amount of time standing up a Joplin server instance on a RPi and installing Joplin on all my devices with the goal being eliminating MS products from my life (OneNote, OneDrive, yadda, yadda, yasa) That was an interesting experience.

Truth be told Joplin is really not what I am looking for. It's a force fit with it's unholy reliance on MarkDown.

Frankly, after a quick dip in the water, Trilium is more my cup 'o tea. An absolutely beautiful user experieince.

Would love to be part of the team, but have little/no applicable code experience.

I am a retired Electro-Mechanical engineer. Fluent in VBA (thanks SolidWorks), conversant in Python, and somewhat knowledgeable of C, C++, Fortran, etc.

I can provide document review, documentation development, testing, the odd cup of Joe :).

Cheers,

chris

[meichthys]

Done. Welcome, and we look forward to your contributions! I've invited you to our documentation and testing teams.

[kaanyalova]

I would like to join

[meichthys]

Invite sent!

[penguinsam]

@eliandoran Please count me in. Discovered Trilium a month ago and been very impressed with it. I can contribute to some programming and translations, I've been doing some enhancements to the Telegram integration.

[meichthys]

I just sent you a member invite. We look forward to your contributions!

[mpstein]

I am interested in keeping an eye on the conversation and adding my $0.02 when appropriate. Thank you!

[meichthys]

Welcome Aboard! I Just sent you a member invite.

[royalmoose]

Happy to support and participate where I can!

[meichthys]

@royalmoose Welcome. I've invited you to be a member. We look forward to your contributions!

[paulternate]

I would love to be involved in any way I can. Love the project. Thanks!

[meichthys]

Welcome! I've approved your membership. Please plug yourself into one of our existing teams (https://github.com/orgs/TriliumNext/teams) and feel free to start contributing.

Also be sure to join our conversations on Matrix: https://matrix.to/#/#triliumnext:matrix.org

[newmedicine]

Everyone is free to join the organization if you would like to contribute to the future of Trilium Notes.

Simply leave a comment here and we'll come back to you.

Yes please!
Nick

[meichthys]

Invite sent 👍
Welcome!

Please plug yourself into one of our existing teams (https://github.com/orgs/TriliumNext/teams) and feel free to start contributing.

Also be sure to join our conversations on Matrix: https://matrix.to/#/#triliumnext:matrix.org

[qwertyyb]

I’ve used trilium half a year, I’d like to join it

[meichthys]

Invite sent 👍
Welcome!

Please plug yourself into one of our existing teams (https://github.com/orgs/TriliumNext/teams) and feel free to start contributing.

Also be sure to join our conversations on Matrix: https://matrix.to/#/#triliumnext:matrix.org

[fabyx]

My life is written in Trilium, would be happy to join & help if I can.

[meichthys]

Invite sent 👍
Welcome! Let's keep Trilium for Life! 😆 TFL!

Please plug yourself into one of our existing teams (https://github.com/orgs/TriliumNext/teams) and feel free to start contributing.

Also be sure to join our conversations on Matrix: https://matrix.to/#/#triliumnext:matrix.org

[raaaaayn]

I'd love to help wherever I can 😄

[meichthys]

hey @raaaaayn Welcome! I'll add you to the 'everyone' team for now. Check out our other teams (https://github.com/orgs/TriliumNext/teams) and let me know if you'd like to join one of them once you feel comfortable with contributing.

Also join our conversations on Matrix if you wast the be in the know on the latest happenings: https://matrix.to/#/#triliumnext:matrix.org

[kryoqa]

Can I also join ? I've been a user of Trilium for more than 2 years and would really like to help out TriliumNext

[eliandoran]

Hi, @kryoqa .

Just discussed during today's steering that we will gradually stop accepting new members for the organization, but I will make an exception for you.

Looking forward to see contributions from you. Which team would you like to join (dev, testing, translation, documentation)?

[kryoqa]

Testing

[eliandoran]

@kherry , it is done.

[kherry]

Thank you for the update, I will review access and begin contributing upon return to the office!

[eliandoran]

@kherry , sounds wonderful.
I meant to tag @kryoqa instead.

[eliandoran]

Discussed a bit during the steering meeting of today and I would like to pause for now inviting people to the organization. The initial goal of adding members to the organization was to group together the people who would like to contribute to the application in various ways (code, testing, documentation, translations), but currently a handful of people are actively contributing to the project. Thus, I would prefer not to artificially boost the number of members.

We will still be inviting people to the organization, but only after we notice active involvement in the project.

Thank you for understanding.

cc. @meichthys

[eliandoran]

@mpstein, it's a good point. How should we proceed to make ways to contribute clearer?

[mpstein]

Take me for example. My professional life is devops / aws automation, and I rarely (if ever) do feature work anymore. I decided after reading this thread that I wanted to get involved by supporting a low-code area, documentation. After going to the landing page, I followed the link to the documentation team. I joined the Matrix channel to see what's going on. I had no idea that's where the development conversations were happening as I expected it to be done more in GitHub.

And now that I've joined the documentation room, I have no idea where to go next. What are we documenting? What are we cleaning up? What files should I start with or what features should I focus on? There isn't even a pinned message saying what the goals are. Please know this isn't any sort of dig against the project or the team lead, just showing how easy it is to get overwhelmed when starting.

You asked how to make ways to contribute clearer? Here are my suggestions. Not saying all of them need to be implemented, just something. I'm happy to take a shot of it and submit a PR for the readme later today.

1. A section on the GitHub page saying "Start Here" that outlines how to join the Matrix server and what the rooms are used for.
2. A breakdown of the teams and their goals.
3. A list of possible topics to introduce someone to the code bank (e.g. simple documentation tasks or local changes)
4. An overview of the testing process or a basic guide on "how to find MRs that require code review or functional testing"
5. Ways to provide feedback or feature requests

These are just a few things that came to mind.

[eliandoran]

@meichthys , maybe you could have a look at this?

A document on how to allow people to contribute would be a good starting point, I was thinking of it was well.
Regarding testing, we can go for simply testing beta releases.

[eliandoran]

And now that I've joined the documentation room, I have no idea where to go next. What are we documenting? What are we cleaning up? What files should I start with or what features should I focus on? There isn't even a pinned message saying what the goals are

@mpstein , as far as I am aware, the tasks for documentation are documented as issues in a separate repo: https://github.com/TriliumNext/Docs/issues

In my opinion, documentation has always been free-flow, if you identify a gap in the documentation or some outdated article, it can be addressed. The documentation environment is not very well defined since I think it's stored as MarkDown but it can be edited in TriliumNext as well (by importing it). The documentation for these steps is available here: https://github.com/TriliumNext/Docs/blob/main/Wiki/import-docs.md

[meichthys]

Yes, we need to tie up some loose ends here. I'll take a look. I'm just getting back into the groove after being away for a few weeks.

[Br0kenSilos]

Let me add my two cents from my perspective only. I can only assume a lot of other people are in the same/similar boat as I am. When I found Trilium, I fell in love with it. It was the perfect software for me to start keeping track of all the random things in my head, in my life, in my work. What a great project and wonderful gift from @zadam. It was also one of my first ventures into FOSS beyond just using some software(s). It kick-started me into realizing that hey, people build these things with contributions from all kinds of people. Since that time I have been paying more attention and trying to be more involved in one way or another into a few projects.

By trade I am a Systems Engineer / Administrator. I have no development skills (to speak of) and I am pretty new to github on the whole as well. I have no experience with contributing to projects. And with a heavy day job and a side gig, my time can be limited sometimes. That being said, because of my love for this project, I really want to contribute in some way. The big question for me is... Exactly how and when? For the How part, just taking a stab in the dark, but as I have a pretty beefy home lab, perhaps the best way for me to contribute is testing installs and connectivity and such. As I am new to all of this, perhaps I am selling myself short. So I think I kind of just wait around and look for an opportunity to smack me in the head and say "Hey you! This one is right up your ally". :D

I'd like to be helpful wherever I can. But with my inexperience in these things, I'm not sure where to start. That being said, how do you all feel I could best contribute?

[eliandoran]

@Br0kenSilos , since your time might be limited, a good starting point would be testing:

• Testing the beta releases. The feedback for these kind of releases is quite low, unfortunately. There are ready-to-download versions that can be run locally without even requiring a virtual machine or a dedicated environment, since they have a certain level of stability apart from a few bugs here or there (and there's always the possibility of downgrading). For example, I've been personally using the latest beta for a few weeks now, both personally and at work.
• Testing the nightly builds, basically daily builds of the latest development branch. This requires a bit more time, but it's in the same alley as the beta release testing. There's still some work before we can start testing nightlies, though. These are a bit riskier since there can be more bugs as they haven't been tested end-to-end.
• Testing various platforms that we are not covering very well, for example the ARM side (Windows, macOS and Linux).
• Identifying gaps in our documentation.
• Translations, if you are knowledgeable of another language.