Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update FaqFoundation.component.js #2645

Closed
wants to merge 1 commit into from
Closed

Update FaqFoundation.component.js #2645

wants to merge 1 commit into from

Conversation

robokow
Copy link
Contributor

@robokow robokow commented Jul 14, 2023

It's been a year since we found out that the Trustroots foundation was dissolved, and it's about time that we update the FAQ to reflect this change.

I'd like to suggest keeping the update short and straight to the point. Previous proposals didn't quite hit the mark in terms of clear communication. They seemed more like what some of us volunteers thought the problem was, but not everyone.

Furthermore, I believe it's crucial to focus on working towards the minimum outcome that we can all agree upon, rather than engaging in discussions about everyone's individual opinions on the matter.

So, here's my suggestion: let's make some minor adjustments to effectively convey the main message that, I think, would be good to communicate, which is that it's important to emphasize that, for the community, things remain unchanged. However, behind the scenes, discussions take place among different volunteer groups to explore possible future paths.

Fixes #2585

@mrkvon mrkvon requested a review from chagai95 July 15, 2023 10:25
Copy link
Contributor

@mrkvon mrkvon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to invite @mariha @TMC89 @JohnvdWaeter @chagai95 @MrSalami @hlibbabii and other volunteers to review this PR. I can't request a review from most of you. Probably you're not added to the GitHub teams.


FYI, we've also had an extensive discussion about this with @robokow privately

Let's start this review by re-stating the issue this PR tries to solve:

Information about Trustroots Foundation is not accurate any more

That's the problem at hand, would you agree @robokow ?

It's great that this PR attempts to progress in that direction. Unfortunately it goes only half-way, and re-introduces some outdated information, which @mariha fixed before.

It reads as if nothing changed for the members. After all that was one of the objectives @robokow, as you wrote. However, legally, things have changed for the members. And members are entitled to have the correct information on the website.

For this reason, this is unfortunately not the minimum outcome that i could agree on. It reintroduces outdated information, although it also contains steps in the right direction.


Summary:

  • The new information is great to have included, let's keep it!
  • My main concern is with Trustroots Foundation owns and operates Trustroots and listing the Board. That's incorrect and outdated. I provided details in review comments.
  • also suggested a few minor improvements (typos etc)

Me or other devs can help with making linter and tests happy @robokow 😉 (currently they're failing)


I tried to leave out opinions. If you think some of my factual statements are incorrect, or opinions, please point them out and let's discuss them specifically. 🙂 I'll be more than happy to change or withdraw opinions.

Ok, "members are entitled to have the correct information on the website" is an opinion after all... 🙂 But i guess that's fundamental to this issue.

Comment on lines +13 to +14
The website is owned and operated by{' '}
<a href="/foundation">Trustroots Foundation</a>, a non-profit
Copy link
Contributor

@mrkvon mrkvon Jul 15, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sentence is incorrect. The following is correct information:

Comment on lines +117 to +123
<div className="faq-question" id="who-are-the-board">
<h3>{t('Who are the board?')}</h3>
<Trans t={t} ns="pages">
<a href="/foundation#board">We</a>: Mikael and Natalia.
</Trans>
</div>

Copy link
Contributor

@mrkvon mrkvon Jul 15, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should say that it's former board, to be factually correct. There is no board, currently. This is outdated information.

Sure, it still makes sense to give credit to Mikael and Natalia by mentioning them here as former board. In that case maybe also Carlos, Kasper and Callum should be here as former directors?

Additionally, maybe let's also list here the members of the "small core team" who currently operate Trustroots?

Edit: i didn't notice that there is the link https://team.trustroots.org/Server.html which lists the people who operate the server

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would replace the Q&A Who are the board? with Who operates Trustroots servers? or something similar.

As for me, there are two important pieces of information here: (1) who maintains and can troubleshoot the servers in case something happens; (2) who has access to the data, relevant from data privacy/protection perspective.

Former Board Members are listed and presented on the https://www.trustroots.org/foundation page (which needs updating too, BTW).

There could be a Q&A Who founded Trustroots? with an answer giving credits to all founders, possibly with the years when they were board members.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just noticed that there's the link https://team.trustroots.org/Server.html where the folks who operate Trustroots server are listed. That's great to have it there.

The website is owned and operated by{' '}
<a href="/foundation">Trustroots Foundation</a>, a non-profit
Limited by Guarantee (LBG) under section 60 exemption, registered in
the United Kingdom since March 2015. However, the Trustroots Foundation has been inactive since the 24th of May 2022. This is why we are considering to either establish a new foundation, migrating to a p2p decentralized solution or reactivating the existing foundation one to resume its operations. Meanwhile, a small core team, consisting of members who have been involved with Trustroots since its early days, is currently managing the <a href="https://team.trustroots.org/Server.html">server and user database</a>.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏾 This reads like a fair summary of the plans, and current management.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Next to migrating to a p2p decentralized solution you can consider adding also federated decentralization which is what we planned to do in https://openHospitality.network.

The website is owned and operated by{' '}
<a href="/foundation">Trustroots Foundation</a>, a non-profit
Limited by Guarantee (LBG) under section 60 exemption, registered in
the United Kingdom since March 2015. However, the Trustroots Foundation has been inactive since the 24th of May 2022. This is why we are considering to either establish a new foundation, migrating to a p2p decentralized solution or reactivating the existing foundation one to resume its operations. Meanwhile, a small core team, consisting of members who have been involved with Trustroots since its early days, is currently managing the <a href="https://team.trustroots.org/Server.html">server and user database</a>.
Copy link
Contributor

@mrkvon mrkvon Jul 15, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In reactivating the existing foundation one to resume, remove one

Also it would be more accurate to replace existing with former or dissolved

The website is owned and operated by{' '}
<a href="/foundation">Trustroots Foundation</a>, a non-profit
Limited by Guarantee (LBG) under section 60 exemption, registered in
the United Kingdom since March 2015. However, the Trustroots Foundation has been inactive since the 24th of May 2022. This is why we are considering to either establish a new foundation, migrating to a p2p decentralized solution or reactivating the existing foundation one to resume its operations. Meanwhile, a small core team, consisting of members who have been involved with Trustroots since its early days, is currently managing the <a href="https://team.trustroots.org/Server.html">server and user database</a>.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be great to add link to the info about the current Foundation status to inactive since the 24th of May 2022

@@ -134,7 +132,7 @@ export default function FaqFoundation() {
<a href="/contribute">Donations</a> and grants are the most likely
ways. There are many inspiring organisations out there serving as
great examples:{' '}
<a href="http://www.abgefahren-ev.de/">Abgefahren e.V.</a>{' '}
<a href="http://www.abgefahren-ev.de/">Abgefahren e.V.</a>,{' '}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The previous version (without ,) seemed correct.

@mrkvon mrkvon requested a review from hlibbabii July 15, 2023 12:14
@mrkvon
Copy link
Contributor

mrkvon commented Jul 15, 2023

Previous proposals didn't quite hit the mark in terms of clear communication.

Please let's differentiate between what's "emotionally triggering" and "confusing".

I suppose the accurate, up-to-date information can be potentially emotionally triggering. It has already proven so.

But i can't see how accurate information can be confusing, ever.

Let's keep that in mind for further discussion here, please. 🙂

edit: this comment is partially based on private conversation, FYI in case some context is missing

@chagai95
Copy link
Contributor

I agree very much with @mrkvon review, all of the comments make a lot of sense to me. I was not part of any private discussions so I'm pretty much in the dark here and I can only say that I would love to get more information both as a volunteer and as a user and it seems like these changes would do at least a bit of that. I would like to add that even if the case were to be that legally nothing changed (which is not from what I understand), even then, from a volunteers perspective who saw how it was like to work with Mikael I observed a huge change (good and bad) to how things are and I expect full transparency about this with our users and volunteers... For example - we have lost our main developer, maintainer, founder and leader of the project but on the other side, we are going towards a vision of decentralization with a new fresh mindset and have already successfully migrated away from slack.

Copy link
Contributor

@mariha mariha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's great that this page gets finally updated! and as @mrkvon stated, the point is to provide accurate information. I generally agree with Michal's comments.

In addition to the Foundation being dissolved, as for me the answer to the Who decides what gets done? needs to be updated too (possibly in a separate patch). I would consider adding also Who operates the servers? Q&A.

Thanks @robokow for moving this issue forward. I am looking forward to the changes being deployed!

The website is owned and operated by{' '}
<a href="/foundation">Trustroots Foundation</a>, a non-profit
Limited by Guarantee (LBG) under section 60 exemption, registered in
the United Kingdom since March 2015. However, the Trustroots Foundation has been inactive since the 24th of May 2022. This is why we are considering to either establish a new foundation, migrating to a p2p decentralized solution or reactivating the existing foundation one to resume its operations. Meanwhile, a small core team, consisting of members who have been involved with Trustroots since its early days, is currently managing the <a href="https://team.trustroots.org/Server.html">server and user database</a>.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Next to migrating to a p2p decentralized solution you can consider adding also federated decentralization which is what we planned to do in https://openHospitality.network.

Comment on lines +117 to +123
<div className="faq-question" id="who-are-the-board">
<h3>{t('Who are the board?')}</h3>
<Trans t={t} ns="pages">
<a href="/foundation#board">We</a>: Mikael and Natalia.
</Trans>
</div>

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would replace the Q&A Who are the board? with Who operates Trustroots servers? or something similar.

As for me, there are two important pieces of information here: (1) who maintains and can troubleshoot the servers in case something happens; (2) who has access to the data, relevant from data privacy/protection perspective.

Former Board Members are listed and presented on the https://www.trustroots.org/foundation page (which needs updating too, BTW).

There could be a Q&A Who founded Trustroots? with an answer giving credits to all founders, possibly with the years when they were board members.

@chmac chmac closed this Jan 25, 2024
@chmac chmac deleted the FAQ-updates branch January 25, 2024 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Information about Trustroots Foundation is not accurate any more
5 participants