IRC logs for #farmOS, 2024-02-15 (GMT)

2024-02-14
2024-02-16
TimeNickMessage
[20:43:56]* abdberkana has joined #farmos
[05:44:06]<Spixmaster[m]>I have read the [documentation](https://farmos.org/guide/people/) but do not find the appropriate information.
[05:44:06]<Spixmaster[m]>Does the first user with ID 1 have administrative privileges? In my example, the first user is able to do everything although he is not assigned to a role.
[05:45:01]<Spixmaster[m]> * I have read the [documentation](https://farmos.org/guide/people/) but do not find the appropriate information.
[05:45:01]<Spixmaster[m]>Does the first user with ID 1 have administrative privileges? In my example, the first user is able to do everything although he is not assigned to a role.
[05:45:01]<Spixmaster[m]>Is it therefore advised not to actually use the user with ID 1 and keep it as a backup if needed?
[05:45:15]<mstenta[m]>Spixmaster: That's correct. Drupal user 1 is comparable to "root" in Linux.
[05:45:16]<mstenta[m]>https://www.drupal.org/docs/user_guide/en/user-admin-account.html
[05:46:23]<mstenta[m]>(It might be worth adding a note about this to the "People" page you linked to in our farmOS.org guide.
[05:47:56]<mstenta[m]>> For those interested, farmOS can now be easily installed for Arch Linux as a package.
[05:47:56]<mstenta[m]>Spixmaster question: when new versions of farmOS are released, do you need to manually update the Arch package to provide the new version?
[05:48:33]<mstenta[m]>I originally asked about this in https://github.com/farmOS/farmOS/issues/790#issuecomment-1926901096
[05:49:31]<mstenta[m]>I'm still interested in discussing this with you and others in the community. So I'll copy and paste my comment from that issue:... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/UjZiTfRBFXmxbHTx...)
[05:50:29]<mstenta[m]>I want to reiterate that I'm thrilled you are using farmOS and want to help make it easier for others to install it as well!
[05:52:50]<mstenta[m]>But I'm sure you can understand that it also introduces a risk to the project's reputation, longer term. If we are not officially maintaining a packaged release, we need to make sure that users are not misled into thinking they can trust it, or that it has our official approval.
[05:53:38]<mstenta[m]>I'm sure you are trustworthy, but imagine a case where a malicious actor packages their own release of farmOS and includes malware, for instance.
[05:55:53]<mstenta[m]>We can't always prevent this, of course, since it is an open source project. The only power we have, legally speaking, is our trademark on the name "farmOS". We have official community guidelines for it's use here: http://farmos.org/community/trademark
[06:00:15]<mstenta[m]>As long as the Arch package is the original "unmodified source code", then using the farmOS name is allowed. But I think it would still be good to add a note to the package description to make it clear that it is not officially maintained by the farmOS organization/maintainers, and include a link to https://farmOS.org.
[06:01:13]<mstenta[m]>It's also very important that anyone installing farmOS is familiar with the process for updating farmOS. Simply updating the code is not enough. See https://farmos.org/hosting/update/
[06:12:09]<Spixmaster[m]>I have an appointment now. I will have to answer later.
[06:13:35]<mstenta[m]>Thanks Spixmaster! Talk soon. :-)
[12:01:09]<paul121[m]>FarmOS dev call starting now! https://meet.jit.si/farmos-dev
[12:58:07]<mstenta[m]>FYI the conventions/schema discussion will follow the farmOS dev call at 1pm Eastern
[17:38:17]* farmBOT has joined #farmos