Yes it's free for public repositories. But it is not free for private repositories and not under our control. On 02/04/2021 13:10, Tom M0LTE wrote:

Ok. No problem with that. This doesn't change the fact that it is an external site that is not under our control. And it is owned by Microsoft which means it could change... It was just an idea. No pressure here. On 02/04/2021 14:41, Alistair Mackenzie via 44Net wrote:

ARDC do have a self hosted GitLab server, the board and the TAC/GAC are using it for document sharing and so on. I have just had a quick chat with Rosy and ARDC would be happy to setup an “official” public GitLab instance if the membership would find it useful? So I guess the question is, what would folk use it for? @Paul - You are right, I did setup a public repo on GitHub a while back as a platform to get the Portal code re-developed, but nothing ever came of it, so I deleted it. There was nothing really of interest there, just a basic Laravel framework that I had started working on. 73, Chris

I wouldn't mind sharing code snippets for things like OpenVPN configurations, IPTables and NF Tables configs, etc.

On Fri, 2 Apr 2021, G1FEF via 44Net wrote: Bit confused here: https://gitlab.ampr.org/ already exists, so nothing needs creating. Just unticking the "keep everything sup3r s3cr3t" checkbox. Sure, for example: 1. I would like to collaboratively maintain the archive of historical ARDC/AMPRNet material so that it's not lost again---things like the 1980s address plan; and the original/ammended MoUs between Brian Kantor/ARDC and UCSD covering CAIDA's allowance to "collect, filter and curate data destined for the AMPRNet(tm)" [until July 2023]. For new employees, technical advertisers, or trustees, (and Hams/users in general) this would help in giving a much better overview and single "go-to" location. Ditto for the board minutes, that were being held back from release until the 2019 accounts had been filed. 2. We observe several support requests arranging at 44net@, mostly then batted off-list. This could be better handled via an issue tracker; and then tied to the resulting commits/updates to the routeing DB resulting from those requests. 3. Nat Morris did a bunch of research and tool development recently to find inconsistencies in the Whois/database/BGP advertisements---would be great to get those tools in the same place; and to fix/document the origin of the inconsistencies. 4. Unforunately ARDC is funding a *tonne* of stuff, all with an open-access requirement: the simplest way for Rosy/the board to enforce open-publication compliance is to require a mirror of the work to be uploaded to the AMPRNet Gitlab instance. Having Github.com/AMPRNet disappear is not a problem, /if/ the Portal code and other tools were now visibly self-hosted on AMPR Gitlab... However, checking just now, (I) can't see them. ..Chris: Are there any blockers (eg. next ~7 days) to making the existing Gitlab instance and its existing hosted repos openly available? -Paul (... ARDC is funding work on 44net/AMPRNet infrastructure, ... and ARDC funding /usually/ comes with an unambigious requirement that the fruits of that ARDC funding must be open-access/openly available).

On Sat, 3 Apr 2021, G1FEF wrote: 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? 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? -Paul

That is why I suggested gitlab, which is open source as an alternative to github. On Sat, Apr 3, 2021, 05:20 G1FEF via 44Net <44net(a)mailman.ampr.org> wrote: -- The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. Please do not print this email unless it is necessary. Every unprinted email helps the environment.

The ARDC Public GitLab is now setup and ready for use: https://git.ampr.org <https://git.ampr.org/> Please feel free to register and share. 73, Chris

Who has experience using this GitLab service? I have a local GIT repository and I try to import it into the server but I am not sure how to do that.  When using "Repo from URL" and giving it the location on my webserver where I have temporarily copied that repository (the location where the .git subdirectory exists), it imports the metadata but not the actual files that exist there. How is that to be done? Rob On 4/4/21 9:02 PM, G1FEF via 44Net wrote:

+1 re: SSH. Here's some documentation from GitLab that may be helpful: https://docs.gitlab.com/ee/ssh/ Also GitLab has a ton of great documentation. Definitely recommend it for anyone using the service. https://docs.gitlab.com/ee/README.html Thank you so much, Chris, for setting this up. All the best, Rosy Rosy Wolfe - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ampr.org On 4/5/21 9:35 AM, Jim Popovitch via 44Net wrote:

Just registered but have a question.. If one of the usage scenarios is to access this resource over amateur RF, then is it wise to have https:// or should it be http:// ? 73, Mark, N2MH On 4/4/21 3:02 PM, G1FEF wrote:

This is the first mention of RF access, but if folks have a genuine desire to access it over RF, I can look into providing a non-encrypted version. I’m not keen on putting unencrypted access over the general internet, I know it’s an open repository of code, but the code providers still have to login with usernames & passwords, which should never go over the wire in plain text. It may be possible to provide access behind a firewall to source IPs within the 44 address ranges... Do many people want this I wonder? 73, Chris

Chris, Would it be worthwhile to check with the involved regulator(s) exactly where the limit goes regarding encryption when using ham frequencies? When we asked our regulator, we got the answer that they do not really care if we use encrypted login credentials as longs as they can find out who is transmitting, since their main concern is that they can find you if your transmission causes unacceptable QRM. /bjorn On 2021-04-09 16:36, G1FEF via 44Net wrote:

Hi; I partially agree with that. As a regulator myself (but in a different area of Federal regulation), asking the regulator can be helpful, but you really are better off doing your homework first. That includes looking at the regulations, asking knowledgeable others (non-regulators) about their interpretations (I am thinking ARRL here), and if questions persist, asking the regulator informed questions of limited scope. Hope this helps, Erik N7FYO -----Original Message----- From: 44Net &lt;44net-bounces+traderbeckola=tahoma.com(a)mailman.ampr.org&gt; On Behalf Of Rob PE1CHL via 44Net Sent: Sunday, April 11, 2021 6:46 AM To: Bjorn Pehrson via 44Net &lt;44net(a)mailman.ampr.org&gt; Cc: Rob PE1CHL &lt;44net(a)pe1chl.nl&gt; Subject: Re: [44net] Git repository for AMPR stuff My experience is that THE WORST thing you can do is "ask the regulator"! You may get the response you got and be happy, but there is more chance that they will just enforce or even extend what can already be read in the regulations, and make explicit statements about that. After which you can no longer say "well, we thought that as long as you could identify our transmissions it wouldn't be that much of a problem". Rob On 4/11/21 11:37 AM, Bjorn Pehrson via 44Net wrote: _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net

My question is "what use case or situation *requires* using ham radio to access a source repository?" ------------------------------ John D. Hays - K7VE Kingston, WA <http://k7ve.org/blog> <http://twitter.com/#!/john_hays> <http://www.facebook.com/john.d.hays>

+1 Bob On 2021-04-14 17:41, Bill Vodall via 44Net wrote: -- When you change the way you look at things, the things you look at change  Max Planck

Prefers self hosted? Something wrong with Microsoft?

I would recommend the use of gitea over gitlab. Upgrading gitlab to stay current addressing security concerns is a significant admin effort in comparison. On Sat, Apr 3, 2021 at 7:33 AM pete M via 44Net &lt;44net(a)mailman.ampr.org&gt; wrote:

On Fri, 2 Apr 2021, Tom M0LTE via 44Net wrote: Chris/G1FEF already has a Github account for this: https://github.com/AMPRNet which used to have useful stuff on it: https://github.com/AMPRNet/Portal/ http://web.archive.org/web/20201231161431/https://github.com/AMPRNet/Portal (until recently removed). Since then ARDC has now tightened its open access requirement: https://www.ampr.org/grantmaking-categories-requirements-goals/#open-access "we require it to be able to freely spread without limit, to everyone who can benefit and to everyone who can contribute. Thus all technology, documentation, and other materials produced using ARDC funds must be made freely available to the public." Perhaps as a first step in fulfilling this requirement, the *existing* AMPRNet repos could be restored on Github. Chris: is there anything blocking getting this done ASAP? -Paul

I see it pretty straight forward.. Anyone has read access to public repositories, people can request an account and set up their projects which should be public by default, and maintain them. Exactly the same way like github works now, just under full ARDC control. Marius, YO2LOJ On 02/04/2021 18:56, pete M via 44Net wrote: