TriliumNext/Trilium
1
0
Fork 0
mirror of https://github.com/TriliumNext/Trilium.git synced 2025-12-10 21:07:05 -06:00
Code Issues 1.1k Packages Projects Releases 10 Wiki Activity

Regarding inactive members of the organization #316

New Issue
Closed
opened 2025-10-01 15:51:04 -05:00 by giteasync · 10 comments
giteasync commented 2025-10-01 15:51:04 -05:00
Owner
Copy Link

Originally created by @eliandoran on GitHub.

Describe Task

@TriliumNext/everyone ,

When @zadam mentioned that the Trilium project would enter a maintenance phase, we created the TriliumNext organization in order to advance the development of the project. At first, we allowed a large number of members into the organization simply via invite.

Now that the project has grown, it has become clear that we need to do a bit of a "spring cleaning" within our organization, especially since we have members that have not been active for a long time now.

As such, the criteria to being part of the organization is defined is one (or more) of the following:

By the end of June, we'll go through all the active and inactive members of the organization and check if they match this criteria (considering the last three months). If not, we will remove them from the organization. Of course, this is not a permanent decision and it can be reconsidered on a case-by-case basis.

If you see this notification and would like to voluntarily quit the organization, just let us know.

Originally created by @eliandoran on GitHub. ### Describe Task @TriliumNext/everyone , When @zadam mentioned that the Trilium project would enter a maintenance phase, we created the TriliumNext organization in order to advance the development of the project. At first, we allowed a large number of members into the organization simply via invite. Now that the project has grown, it has become clear that we need to do a bit of a "spring cleaning" within our organization, especially since we have members that have not been active for a long time now. As such, the criteria to being part of the organization is defined is one (or more) of the following: - Contribute code to the repository consistently (https://github.com/TriliumNext/Notes/graphs/contributors should help distinguish easily this aspect). - Contribute translations to the project. - Help organize the [project issues](https://github.com/TriliumNext/Notes/issues) and contribute to [discussions](https://github.com/orgs/TriliumNext/discussions). - Help advertise the application on various online channels. - Report issues on development and beta versions. By the end of June, we'll go through all the active and inactive members of the organization and check if they match this criteria (considering the last three months). If not, we will remove them from the organization. Of course, this is not a permanent decision and it can be reconsidered on a case-by-case basis. If you see this notification and would like to voluntarily quit the organization, just let us know.
giteasync commented 2025-10-01 15:51:05 -05:00
Author
Owner
Copy Link

@Alumniminium commented on GitHub:

I'm not active but actively following whats happening here.

I got quite burned out on the documentation task, and then my life got busy due to work/job related things

But its not all bad, because it gave me the opportunity to learn typescript for the past months (and getting paaid for it) and I'm feeling pretty comfortable with it now. I'm looking forward to contributing code!

Sadly our workload is so high right now, that I'm just falling over from my chair right into bed every evening.

If you kick me out I'll kick the door in whenever things calm down

o/

@Alumniminium commented on GitHub: I'm not active but actively following whats happening here. I got quite burned out on the documentation task, and then my life got busy due to work/job related things But its not all bad, because it gave me the opportunity to learn typescript for the past months (and getting paaid for it) and I'm feeling pretty comfortable with it now. I'm looking forward to contributing code! Sadly our workload is so high right now, that I'm just falling over from my chair right into bed every evening. If you kick me out I'll kick the door in whenever things calm down o/
giteasync commented 2025-10-01 15:51:05 -05:00
Author
Owner
Copy Link

@TriangularCube commented on GitHub:

sigh likewise here, life has a way of throwing curveballs. Please remove me as well.

@TriangularCube commented on GitHub: _sigh_ likewise here, life has a way of throwing curveballs. Please remove me as well.
giteasync commented 2025-10-01 15:51:05 -05:00
Author
Owner
Copy Link

@eliandoran commented on GitHub:

@Alumniminium , yeah, documentation was indeed quite a difficult task, and we still have a lot to do, but your help was much appreciated!

Looking forward to your contributions.

@eliandoran commented on GitHub: @Alumniminium , yeah, documentation was indeed quite a difficult task, and we still have a lot to do, but your help was much appreciated! Looking forward to your contributions.
giteasync commented 2025-10-01 15:51:05 -05:00
Author
Owner
Copy Link

@cjrutherford commented on GitHub:

same boat, wanted to help, life happened, please remove me.

On Mon, Jun 9, 2025, 3:58 AM Michael Liu @.***> wrote:

TriangularCube left a comment (TriliumNext/trilium#5786)
https://github.com/TriliumNext/trilium/issues/5786

sigh likewise here, life has a way of throwing curveballs. Please
remove me as well.

—
Reply to this email directly, view it on GitHub
https://github.com/TriliumNext/trilium/issues/5786,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACICOR223WIBTXU64UKMRFL3CU5BHAVCNFSM6AAAAAB6ZBHON6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNJUHE4TGMJXHE
.
You are receiving this because you are on a team that was mentioned.Message
ID: @.***>

@cjrutherford commented on GitHub: same boat, wanted to help, life happened, please remove me. On Mon, Jun 9, 2025, 3:58 AM Michael Liu ***@***.***> wrote: > *TriangularCube* left a comment (TriliumNext/trilium#5786) > <https://github.com/TriliumNext/trilium/issues/5786> > > *sigh* likewise here, life has a way of throwing curveballs. Please > remove me as well. > > — > Reply to this email directly, view it on GitHub > <https://github.com/TriliumNext/trilium/issues/5786>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACICOR223WIBTXU64UKMRFL3CU5BHAVCNFSM6AAAAAB6ZBHON6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNJUHE4TGMJXHE> > . > You are receiving this because you are on a team that was mentioned.Message > ID: ***@***.***> >
giteasync commented 2025-10-01 15:51:05 -05:00
Author
Owner
Copy Link

@mondayrobot commented on GitHub:

First of all, apologies. I really wanted to help, but then life happened and I was not able to contribute in any way. Please remove me from the organisation. If I get a little bit of time going forward, I'll help in any way I can, without being a member. Thanks and keep up the great work!

@mondayrobot commented on GitHub: First of all, apologies. I really wanted to help, but then life happened and I was not able to contribute in any way. Please remove me from the organisation. If I get a little bit of time going forward, I'll help in any way I can, without being a member. Thanks and keep up the great work!
giteasync commented 2025-10-01 15:51:05 -05:00
Author
Owner
Copy Link

@AkechiShiro commented on GitHub:

Please remove me as well, thanks

@AkechiShiro commented on GitHub: Please remove me as well, thanks
giteasync commented 2025-10-01 15:51:06 -05:00
Author
Owner
Copy Link

@zerebos commented on GitHub:

TriliumNext is a project I was very excited to be involved in, then due to let's say certain reasons I was unable to be involved in early/live discussions. Combine that with having several life events happen in a row, and this project (and my Trilium-related OSS projects) just fell through the cracks and onto the backburner.

Unfortunately to this day I am still playing catch-up on things both in the real world and in the open source space--just take a look at my GitHub activity and my projects with open issues/prs. So although it's disappointing (at least to me) I don't know when or even if I'll be able to return to this project and take a more active contributing role. Heck, I don't even know when I'll get back to it even as a user, I've been severely lacking on note-taking and organization.

Regardless of my actual involvement, I have been following the development and progress as close as I can. I have to say, I am glad that the project has someone as active and proactive as you Elian to lead it. I don't think this project would have the momentum it does otherwise.

@zerebos commented on GitHub: TriliumNext is a project I was very excited to be involved in, then due to let's say certain reasons I was unable to be involved in early/live discussions. Combine that with having several life events happen in a row, and this project (and my Trilium-related OSS projects) just fell through the cracks and onto the backburner. Unfortunately to this day I am still playing catch-up on things both in the real world and in the open source space--just take a look at my GitHub activity and my projects with open issues/prs. So although it's disappointing (at least to me) I don't know when or even if I'll be able to return to this project and take a more active contributing role. Heck, I don't even know when I'll get back to it even as a user, I've been severely lacking on note-taking and organization. Regardless of my actual involvement, I have been following the development and progress as close as I can. I have to say, I am glad that the project has someone as active and proactive as you Elian to lead it. I don't think this project would have the momentum it does otherwise.
giteasync commented 2025-10-01 15:51:06 -05:00
Author
Owner
Copy Link

@newmedicine commented on GitHub:

Me too sorry!

From: Samy Lahfa @.>
Sent: 09 June 2025 17:17
To: TriliumNext/Notes @.>
Cc: Nick Bell @.>; Team mention @.>
Subject: Re: [TriliumNext/Notes] Regarding inactive members of the organization (Issue TriliumNext/trilium#5786)

[https://avatars.githubusercontent.com/u/14914796?s=20&v=4]AkechiShiro left a comment (TriliumNext/trilium#5786)https://github.com/TriliumNext/trilium/issues/5786

Please remove me as well, thanks

—
Reply to this email directly, view it on GitHubhttps://github.com/TriliumNext/trilium/issues/5786, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFLHNYYL7WS4RWDFQJFQA333CWXRLAVCNFSM6AAAAAB6ZBHON6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNJWGI3DKNBSGQ.
You are receiving this because you are on a team that was mentioned.Message ID: @.***>

@newmedicine commented on GitHub: Me too sorry! ________________________________ From: Samy Lahfa ***@***.***> Sent: 09 June 2025 17:17 To: TriliumNext/Notes ***@***.***> Cc: Nick Bell ***@***.***>; Team mention ***@***.***> Subject: Re: [TriliumNext/Notes] Regarding inactive members of the organization (Issue TriliumNext/trilium#5786) [https://avatars.githubusercontent.com/u/14914796?s=20&v=4]AkechiShiro left a comment (TriliumNext/trilium#5786)<https://github.com/TriliumNext/trilium/issues/5786> Please remove me as well, thanks — Reply to this email directly, view it on GitHub<https://github.com/TriliumNext/trilium/issues/5786>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFLHNYYL7WS4RWDFQJFQA333CWXRLAVCNFSM6AAAAAB6ZBHON6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNJWGI3DKNBSGQ>. You are receiving this because you are on a team that was mentioned.Message ID: ***@***.***>
giteasync commented 2025-10-01 15:51:06 -05:00
Author
Owner
Copy Link

@CobriMediaJulien commented on GitHub:

I would like to stay in the org and get more involved into the documentation as i´m going to use triliumnext now rather than optimizing it all the time :)

@CobriMediaJulien commented on GitHub: I would like to stay in the org and get more involved into the documentation as i´m going to use triliumnext now rather than optimizing it all the time :)
giteasync commented 2025-10-01 15:51:06 -05:00
Author
Owner
Copy Link

@deajan commented on GitHub:

Not quite the most active member I guess (I too have a quite big workload), but still I try to help when it comes to digital signatures and bug reporting (or just fancy feature requests :)), so I'll happily stay in the org.

@deajan commented on GitHub: Not quite the most active member I guess (I too have a quite big workload), but still I try to help when it comes to digital signatures and bug reporting (or just fancy feature requests :)), so I'll happily stay in the org.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
BE
Difficulty: Easy
Difficulty: Hard
Difficulty: Hard
State: Blocked
State: Outdated
State: Triage
State: Triage
State: Under Debate
Type: Documentation
Type: Scripts & Themes
UI
UI
UI
awaiting feedback
ckeditor
container
dependencies
desktop-app
downstream
effort-high
effort-low
effort-medium
geo-map
llm
mermaid diagrams
mobile
ported-issues
pull-request
Mirrored from GitHub Pull Request
question
refactor
regression
scripting
search
search
sync
upstream
web-clipper
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
giteasync
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: TriliumNext/Trilium#316
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?