Many of us have proposed their services to the Asgardia community. We have been told to send an email to X address, or apply there or there, send a C.V, etc.

But so far, and after more than a month I still haven't got any feedback about all of this. Some of it was done by email, FB PM, forum, etc.

It would be nice to have a place to follow our applications and I'm pretty sure you thought (meaning, the Staff) of it already.

I understand there may be thousands of such applications due to the huge amount of Asgardians, but what I've seen so far is a lot of unused people who wish to participate more and be helpful.

So, what do you plan for handling that many applications? How are you planning to give us feedback? More basically, how would you improve this?

How I'd improve this, is deploy git on our server(s).

This would give an environment where all are able to create and contribute and or edit existing code/policy/design, without any requirement for applications. Let the quality of each individual submission/edit speak for itself.

I guess you mean some kind of internal Git client, like https://about.gitlab.com/products/ ?

We can't really ask people to use git CLI to apply, we're talking about a wide range of people and most of them won't ever touch a CLI. So I guess you meant the Git client.

I believe we already have a Github at https://github.com/asgardia but there doesn't seem to be any public repo. Maybe use that one for starter?

As for the idea of using a git-based client for applications, it may work but I wonder if we can't find something better. I mean, Github hasn't been built for this purpose in the first place, although it would be interesting to use it for applications using the traditional "issues".

No I don't mean a client. I mean git itself(https://git-scm.com/book/en/v2/Git-on-the-Server-Setting-Up-the-Server).

The CLI can be lent a GUI frontend interface thanks to the magic of CGI. Really, the first things to get up should be the digital services that would allow any further task to be completed with ease. And the people capable of doing this are really unlikely to be fearful of the command line interface. Else they can be educated. There's also standalone GUI clients that can be executed locally.

The problem with the link you've offered is the lack of control. Sure, it's better in terms of data rights than say, google docs, but doesn't come close to retaining control yourself. If nothing else, how can you assure that will be there tomorrow? or five years time? ten years time? etc.

Github hasn't been developed for such uses indeed, but we can (re)build the frontend as we please - and for things like an application we can repress applications from visibility to others - only visible to the applicant and the people processing the applications. Can also have the frontend display "applications" instead of "issues".

Interesting!

Well, Gitlab CE (Community Edition) is open source (unlike github) and would provide a good starting base. https://github.com/gitlabhq/gitlabhq

We can fork & modify it as we please. And stay up-to-date with the official repo as well. We can also host it on our own servers.

I used it two years ago for a banking application, no way we would have put such sensitive source code on something hosted on American soil ;)

Granted, I'm not entirely conversant on the differences, but I was to understand gitlab-CE was a "cutdown" version missing "features" ?

Unless I've grabbed the wrong thing in my haste, I was thinking that link I'd provided is the "full on git"

Either way, they both open source and we can modify to suit. Republishing our source shouldn't be a problem as we have founding principles of freedom of knowledge. I'm not entirely fussed what's used, as long as it can do the job.

Indeed, you're right. The CE doesn't allow all the things the Enterprise Edition do. See https://about.gitlab.com/products/#compare-options

But AFAIK the link your provided only allows to setup Git itself, not any GUI like Gitlab or Github, meaning nothing like pull request and such. (I may be wrong about that, but to me the Git client is simply the CLI we got on our computer to talk to the CLI on the server, without the handful of features Github provides)

https://git-scm.com/book/en/v2/Git-on-the-Server-GitLab