I would recommend against this. Even PHP is switching to using GitHub because of issues
with securing their private Git server that was recently hacked. It is much smarter to
use GitHub and let them deal with the securing of the repository so the developers can
remain focused on the development and security of the code, rather than having to take on
the additional issues of securing authentication access to whom can edit/manage the code.
73,
Jeff Parrish - KB9GXK
-----Original Message-----
From: 44Net <44net-bounces+jeff=kb9gxk.net(a)mailman.ampr.org> On Behalf Of Marius
Petrescu via 44Net
Sent: Friday, April 2, 2021 04:47
To: 44Net general discussion <44net(a)mailman.ampr.org>
Cc: Marius Petrescu <marius(a)yo2loj.ro>
Subject: [44net] Git repository for AMPR stuff
Hi everyone,
Since a lot of people do all kind of development work directed towards the ampr and the 44
network, wouldn't it make sense to have some kind of repository/version tracking for
this work?
Of course, there is Github, as a public place to do this, but wouldn't it be nice to
have our own Git repository, which should be under ARDC control, where we could track our
stuff, from code development and scripts, up to all the host and service lists?
This could even be a topic for the grants committee...
Costs are minimal, with only some effort towards the initial setup (Git is essentially
free, with maybe a small payed support in setup from Atlassian if needed). Afterwards it
is self-sustaining.
73s,
Marius, YO2LOJ
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.a…