JoS IT suggestions - Element, GIT, and more

[AFODO]

I would rather rely on disroot's services instead of element.

 

[Daemontech [NG]]

I would rather rely on disroot's services instead of element.

I am not familiar with it, but in any case I only said Element because that's what is already being used for the Outreach Project.
It could be on any safe-enough app of this type, Hell, we could even make it ourselves but we've gotta start somewhere.

 

[ApolloAbove [SG]]

In general I am in favor of this, however we do not have enough members trained to use git correctly. We also could use more IT minded Zevism in general. If you're reading this and you think you are suited for this, send me an email and we can talk.

 

[Ælberiigor]

It's exactly my concern these days.
Thanks to you to raise the problem. As recent user, I didn't dare to talk about that.

If on servers hosting one git repository per project, each developper/editor managing its own branch (linked to its account), then a responsible can merge the stable branches on the master branch then alert his own responsible and so on.

The problem is that no many people feel to ease with command lines, so it's necessary to write a stuff which click-to-command-line the business.

I've started few years ago an experimental nodejs code to handle the gpg command, the graphic interface being the web browser.
I've just verified how it worked : NodeJs call the bash script which manage the details - simplest to write.

A monolithic NodeJs-only code would be better for portability and to permit to every one to install it easily. But NodeJs is a bit special and not practice for algorithmy.
Bash is slow and not powerfull, I'll restart that with a NodeJs+PHP combination. The end user will only need to install this combination + GIT to start, and I'll try to implement the mechanism to add/load PHP (or else) modules.

I talked about, I must do now.