On 23/02/2019 11:19, Christian Boltz wrote:
Hello,
[ I have about 50 unread mails in this discussion, so I might not have seen all relevant comment yet. One thing I noticed is that we have several volunteers. I'm really happy about that :-) Please forgive me for answering only to one of you ;-) ]
Am Freitag, 22. Februar 2019, 08:47:36 CET schrieb Ish Sookun:
On 2/22/19 1:22 AM, Vinzenz Vietzke wrote:
Came up twice already: take a Nextcloud, drop an LibreOffice Calc document there. It's not the shiny knight on a white horse solution but it should be enough to a) keep the membership committee working b) store the member's data safe c) get rid of this ugly spam dump called connect.o.o
Agreed. We start simple.
In a mail nearby, jdd asked the right question:
and why is a *cloud* storage needed to manage membership?
Using nextcloud with a LibreOffice Calc document in it would be a bad idea IMHO. Not because my personal preference is ownCloud ;-) but because it makes things more complicated than necessary. For example, extracting the mail aliases out of a LibreOffice table would be a PITA, or in general, automating anything would be a PITA.
Depends on how you define PITA and simple but i'm not doing the work so I only care that its maintainable, for example you could export the spreadsheet to a CSV then it'd just take some basic commandline tools to split out the email address's
So let's start even more simple and less cloudy, please ;-)
If we go for "a table that can only be edited by the membership committee", then I'd propose to use a MySQL database + phpMyAdmin
The interface would look a bit more "technical", but not too different/ difficult, and it would have several advantages: - extracting the mail aliases out of a database is boring and easy (much easier than extracting them from a binary[1] LibreOffice file) - setting up the server is easy - we could easily track changes, for example with a daily CSV export that gets auto-commited to a git repo (not a requirement for the initial implementation, just an idea for the future) - if we setup a "request membership" form, writing to a database is much easier than writing to a LibreOffice document
The hard part is to convert the data from connect.o.o to the new database scheme. (I never looked at the database scheme used by connect.o.o, therefore I have no idea how hard this will be.)
Writing/updating the export scripts (for example for the mail aliases) is also some work, but not really hard.
I volunteer for this. Will check Heroes where I can set this up.
I'm happy to hear that :-)
Getting a VM (IMHO: for phpMyAdmin and an empty database) shouldn't be too hard ;-) Please write a mail to the heroes mailinglist to request it, and while on it, please also request access to the VPN and the connect.o.o database.
Until that setup is done, you can already start on the drawing board with stuff like "which columns will we need?" I know it sounds boring, but I'm also sure nobody will get this right on the first attemp ;-) On the positive side, adding a column later is easy, so don't worry too much.
On the other hand expecting all the membership officials to learn how to do direct database entry could be considered more of a PITA so please make sure there willing to learn if we go down this route. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org