On 2/22/19 4:49 PM, 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?
Yes, jdd is offering up some good comments.
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.
Yep.
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
My idea, exactly.
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.)
Actually, there are currently only 446 openSUSE Members. That is a number that could easily be split up between Ish, Edwin, Carlos and me -- or more if we can find more -- and that would be less than 112 each. That would make it possible to convert with manual input, even some cut & paste?
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.
Problem is, I know nothing about setting up or working with the current databases. Last time I did any database work was in Borland dBase III/IV. This new stuff is completely foreign to me: Not that I am a database racist or anything, I just do not understand anything about it. ;-) -- -Gerry Makaro openSUSE Member openSUSE Global Moderator openSUSE Contributor YaST Contributor aka Fraser_Bell on the Forums, OBS, IRC, and mail at openSUSE.org Fraser-Bell on Github -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org