On 3 Apr 2021, at 10:21, Paul Sladen
<44net(a)paul.sladen.org> wrote:
On Sat, 3 Apr 2021, G1FEF wrote:
..Chris:
Are there any blockers (eg. next ~7 days) to making the
existing Gitlab instance and its existing hosted repos openly
available?
Yes there are: The current GitLab repo is mostly used for ...
So to clarify, the Portal and other 44net *infrastructure* code is now
mixed up in the same git tree/repo as stuff from the *grant-making*
side of the business?
No, that’s not what I said: The GitLab repo we currently have is used mostly for grant
applications. It also has other “internal” ARDC documents relating to the board, GAC and
TAC, there is currently no “code” on it at all.
I am setting
up a new, separate repo where members can deposit
code snippets and other useful information. Watch this space, it
won’t be long…
Okay.
Jeff Parrish and Pierre Martel both made a good points though, ...
that the path of least resistance/effort would be to revert back, to
using an already extant Github account:
https://github.com/amprnet
and to restore the deleted AMPR projects there and actually *use* it.
Chris: Would have be a simpler solution?
Sorry if I did make myself clear before: That account was setup a while ago to redevelop
the Portal code, the hope was that we would get a few people collaborating, but it never
happened, I uploaded the initial commit with the outline of a Laravel framework but in
spite of a few interested comments at the start, nothing happened. I eventually deleted it
as it was serving no purpose. I have now removed the account as well to avoid any
confusion.
The ARDC board prefers open source, self hosted solutions. So using GitHub, which is now
owned by Microsoft, is not really an option.
73,
Chris