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
Might I suggest looking at GitLab. The software is free and they offer free hosting that ARDC could start with and migrate over to self hosted when appropriate.
On Fri, Apr 2, 2021, 04:48 Marius Petrescu via 44Net 44net@mailman.ampr.org wrote:
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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Hi Marius
GitHub is free unlimited public/private repos, unlimited collaborators.
Beauty of git is there is no provider lock-in. Everyone has the full repo and can push it (retaining the full history) wherever they like.
Cheers Tom M0LTE
On Fri, 2 Apr 2021 at 10:48, Marius Petrescu via 44Net < 44net@mailman.ampr.org> wrote:
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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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:
Hi Marius
GitHub is free unlimited public/private repos, unlimited collaborators.
https://github.com/pricing https://github.com/pricing
Beauty of git is there is no provider lock-in. Everyone has the full repo and can push it (retaining the full history) wherever they like.
Cheers Tom M0LTE
On Fri, 2 Apr 2021 at 10:48, Marius Petrescu via 44Net <44net@mailman.ampr.org mailto:44net@mailman.ampr.org> wrote:
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@mailman.ampr.org <mailto:44Net@mailman.ampr.org> https://mailman.ampr.org/mailman/listinfo/44net <https://mailman.ampr.org/mailman/listinfo/44net>
Marius,
I feel like you have not read the pricing information on the GitHub website.
It is clear under the "Compare features" section that an organization can have unlimited private repositories on the free plan.
On Fri, Apr 2, 2021 at 12:12 PM Marius Petrescu via 44Net < 44net@mailman.ampr.org> wrote:
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:
Hi Marius
GitHub is free unlimited public/private repos, unlimited collaborators.
https://github.com/pricing https://github.com/pricing
Beauty of git is there is no provider lock-in. Everyone has the full repo and can push it (retaining the full history) wherever they like.
Cheers Tom M0LTE
On Fri, 2 Apr 2021 at 10:48, Marius Petrescu via 44Net <44net@mailman.ampr.org mailto:44net@mailman.ampr.org> wrote:
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@mailman.ampr.org <mailto:44Net@mailman.ampr.org> https://mailman.ampr.org/mailman/listinfo/44net <https://mailman.ampr.org/mailman/listinfo/44net>
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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:
Marius,
I feel like you have not read the pricing information on the GitHub website.
It is clear under the "Compare features" section that an organization can have unlimited private repositories on the free plan.
On Fri, Apr 2, 2021 at 12:12 PM Marius Petrescu via 44Net < 44net@mailman.ampr.org> wrote:
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:
Hi Marius
GitHub is free unlimited public/private repos, unlimited collaborators.
https://github.com/pricing https://github.com/pricing
Beauty of git is there is no provider lock-in. Everyone has the full repo and can push it (retaining the full history) wherever they like.
Cheers Tom M0LTE
On Fri, 2 Apr 2021 at 10:48, Marius Petrescu via 44Net <44net@mailman.ampr.org mailto:44net@mailman.ampr.org> wrote:
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@mailman.ampr.org <mailto:44Net@mailman.ampr.org> https://mailman.ampr.org/mailman/listinfo/44net <https://mailman.ampr.org/mailman/listinfo/44net>
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
In the case that there was any reduction in service from the GitHub / Microsoft end, the whole repo (including branches) could be pushed from anybody’s local clone to any other git provider (including self-hosted) with no data loss and no need to interact with GitHub, so there should be no issue there.
Opening up the existing GitHub repo sounds like a good idea :)
Cheers Tom M0LTE
On Fri, 2 Apr 2021 at 12:48, Marius Petrescu via 44Net < 44net@mailman.ampr.org> 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:
Marius,
I feel like you have not read the pricing information on the GitHub
website.
It is clear under the "Compare features" section that an organization can have unlimited private repositories on the free plan.
On Fri, Apr 2, 2021 at 12:12 PM Marius Petrescu via 44Net < 44net@mailman.ampr.org> wrote:
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:
Hi Marius
GitHub is free unlimited public/private repos, unlimited collaborators.
https://github.com/pricing https://github.com/pricing
Beauty of git is there is no provider lock-in. Everyone has the full repo and can push it (retaining the full history) wherever they like.
Cheers Tom M0LTE
On Fri, 2 Apr 2021 at 10:48, Marius Petrescu via 44Net <44net@mailman.ampr.org mailto:44net@mailman.ampr.org> wrote:
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 underARDC
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 setupfrom
Atlassian if needed). Afterwards it is self-sustaining. 73s, Marius, YO2LOJ _________________________________________ 44Net mailing list 44Net@mailman.ampr.org <mailto:44Net@mailman.ampr.org> https://mailman.ampr.org/mailman/listinfo/44net <https://mailman.ampr.org/mailman/listinfo/44net>
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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
On 2 Apr 2021, at 12:51, Tom M0LTE via 44Net 44net@mailman.ampr.org wrote:
In the case that there was any reduction in service from the GitHub / Microsoft end, the whole repo (including branches) could be pushed from anybody’s local clone to any other git provider (including self-hosted) with no data loss and no need to interact with GitHub, so there should be no issue there.
Opening up the existing GitHub repo sounds like a good idea :)
Cheers Tom M0LTE
On Fri, 2 Apr 2021 at 12:48, Marius Petrescu via 44Net < 44net@mailman.ampr.org> 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:
Marius,
I feel like you have not read the pricing information on the GitHub
website.
It is clear under the "Compare features" section that an organization can have unlimited private repositories on the free plan.
On Fri, Apr 2, 2021 at 12:12 PM Marius Petrescu via 44Net < 44net@mailman.ampr.org> wrote:
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:
Hi Marius
GitHub is free unlimited public/private repos, unlimited collaborators.
https://github.com/pricing https://github.com/pricing
Beauty of git is there is no provider lock-in. Everyone has the full repo and can push it (retaining the full history) wherever they like.
Cheers Tom M0LTE
On Fri, 2 Apr 2021 at 10:48, Marius Petrescu via 44Net <44net@mailman.ampr.org mailto:44net@mailman.ampr.org> wrote:
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 underARDC
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 setupfrom
Atlassian if needed). Afterwards it is self-sustaining. 73s, Marius, YO2LOJ _________________________________________ 44Net mailing list 44Net@mailman.ampr.org <mailto:44Net@mailman.ampr.org> https://mailman.ampr.org/mailman/listinfo/44net <https://mailman.ampr.org/mailman/listinfo/44net>
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
I would actually like to see all the scripts/code/dcuments that are created/updated by the ppl on this list.
It is much easier to keep track on this part browsing a reposityry than referring to mails sent some time ago :-)
On 02/04/2021 16:15, G1FEF 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
On 2 Apr 2021, at 12:51, Tom M0LTE via 44Net 44net@mailman.ampr.org wrote:
In the case that there was any reduction in service from the GitHub / Microsoft end, the whole repo (including branches) could be pushed from anybody’s local clone to any other git provider (including self-hosted) with no data loss and no need to interact with GitHub, so there should be no issue there.
Opening up the existing GitHub repo sounds like a good idea :)
Cheers Tom M0LTE
On Fri, 2 Apr 2021 at 12:48, Marius Petrescu via 44Net < 44net@mailman.ampr.org> 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:
Marius,
I feel like you have not read the pricing information on the GitHub
website.
It is clear under the "Compare features" section that an organization can have unlimited private repositories on the free plan.
On Fri, Apr 2, 2021 at 12:12 PM Marius Petrescu via 44Net < 44net@mailman.ampr.org> wrote:
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:
Hi Marius
GitHub is free unlimited public/private repos, unlimited collaborators.
https://github.com/pricing https://github.com/pricing
Beauty of git is there is no provider lock-in. Everyone has the full repo and can push it (retaining the full history) wherever they like.
Cheers Tom M0LTE
On Fri, 2 Apr 2021 at 10:48, Marius Petrescu via 44Net <44net@mailman.ampr.org mailto:44net@mailman.ampr.org> wrote:
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 underARDC
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 setupfrom
Atlassian if needed). Afterwards it is self-sustaining. 73s, Marius, YO2LOJ _________________________________________ 44Net mailing list 44Net@mailman.ampr.org <mailto:44Net@mailman.ampr.org> https://mailman.ampr.org/mailman/listinfo/44net <https://mailman.ampr.org/mailman/listinfo/44net>
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
I wouldn't mind sharing code snippets for things like OpenVPN configurations, IPTables and NF Tables configs, etc.
-----Original Message----- From: 44Net 44net-bounces+jason=mfamily.org@mailman.ampr.org On Behalf Of Marius Petrescu via 44Net Sent: Friday, April 2, 2021 9:18 AM To: 44Net general discussion 44net@mailman.ampr.org Cc: Marius Petrescu marius@yo2loj.ro Subject: Re: [44net] Git repository for AMPR stuff
I would actually like to see all the scripts/code/dcuments that are created/updated by the ppl on this list.
It is much easier to keep track on this part browsing a reposityry than referring to mails sent some time ago :-)
On 02/04/2021 16:15, G1FEF 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
On 2 Apr 2021, at 12:51, Tom M0LTE via 44Net
44net@mailman.ampr.org wrote:
In the case that there was any reduction in service from the GitHub / Microsoft end, the whole repo (including branches) could be pushed from anybody’s local clone to any other git provider (including self-hosted) with no data loss and no need to interact with GitHub, so there should be no issue there.
Opening up the existing GitHub repo sounds like a good idea :)
Cheers Tom M0LTE
On Fri, 2 Apr 2021 at 12:48, Marius Petrescu via 44Net < 44net@mailman.ampr.org> 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:
Marius,
I feel like you have not read the pricing information on the GitHub
website.
It is clear under the "Compare features" section that an organization
can
have unlimited private repositories on the free plan.
On Fri, Apr 2, 2021 at 12:12 PM Marius Petrescu via 44Net < 44net@mailman.ampr.org> wrote:
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: > Hi Marius > > GitHub is free unlimited public/private repos, unlimited
collaborators.
> > https://github.com/pricing https://github.com/pricing > > Beauty of git is there is no provider lock-in. Everyone has the full > repo and can push it (retaining the full history) wherever they like. > > Cheers > Tom M0LTE > > > On Fri, 2 Apr 2021 at 10:48, Marius Petrescu via 44Net > <44net@mailman.ampr.org mailto:44net@mailman.ampr.org>
wrote:
> > 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@mailman.ampr.org mailto:44Net@mailman.ampr.org > https://mailman.ampr.org/mailman/listinfo/44net > https://mailman.ampr.org/mailman/listinfo/44net > _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Hi Chris,
I don't know if it is part of the portal but the whois service is very often down still after like 2 years since we (me and a friend) started telling you about it. So clearly the code isn't perfect and would benefit from contributions.
Regardless of if there are contributions to it from others, I still think having the source code open and public (under some open source license) would be very good.
-Cynthia
On Fri, Apr 2, 2021 at 3:16 PM G1FEF via 44Net 44net@mailman.ampr.org 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
On 2 Apr 2021, at 12:51, Tom M0LTE via 44Net 44net@mailman.ampr.org wrote:
In the case that there was any reduction in service from the GitHub / Microsoft end, the whole repo (including branches) could be pushed from anybody’s local clone to any other git provider (including self-hosted) with no data loss and no need to interact with GitHub, so there should be no issue there.
Opening up the existing GitHub repo sounds like a good idea :)
Cheers Tom M0LTE
On Fri, 2 Apr 2021 at 12:48, Marius Petrescu via 44Net < 44net@mailman.ampr.org> 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:
Marius,
I feel like you have not read the pricing information on the GitHub
website.
It is clear under the "Compare features" section that an organization can have unlimited private repositories on the free plan.
On Fri, Apr 2, 2021 at 12:12 PM Marius Petrescu via 44Net < 44net@mailman.ampr.org> wrote:
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:
Hi Marius
GitHub is free unlimited public/private repos, unlimited collaborators.
https://github.com/pricing https://github.com/pricing
Beauty of git is there is no provider lock-in. Everyone has the full repo and can push it (retaining the full history) wherever they like.
Cheers Tom M0LTE
On Fri, 2 Apr 2021 at 10:48, Marius Petrescu via 44Net <44net@mailman.ampr.org mailto:44net@mailman.ampr.org> wrote:
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 underARDC
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 setupfrom
Atlassian if needed). Afterwards it is self-sustaining. 73s, Marius, YO2LOJ _________________________________________ 44Net mailing list 44Net@mailman.ampr.org <mailto:44Net@mailman.ampr.org> https://mailman.ampr.org/mailman/listinfo/44net <https://mailman.ampr.org/mailman/listinfo/44net>
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
On Fri, 2 Apr 2021, G1FEF 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?
Bit confused here:
already exists, so nothing needs creating. Just unticking the "keep everything sup3r s3cr3t" checkbox.
So I guess the question is, what would folk use it for?
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.
@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.
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).
Hello Paul,
..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 grant applications, the applications contain personal information including names, addresses, contact details, etc. If we were to open the repo to the public we would be in breach of several country’s privacy laws and likely end up with lawsuits costing a *lot* of money!
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…
Thanks, Chris - G1FEF
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?
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:
and to restore the deleted AMPR projects there and actually *use* it.
Chris: Would have be a simpler solution?
-Paul
On 3 Apr 2021, at 10:21, Paul Sladen 44net@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
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@mailman.ampr.org wrote:
On 3 Apr 2021, at 10:21, Paul Sladen 44net@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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Thanks Matthew, we are already using GitLab and I have committed to setting up an ARDC public GitLab instance for the membership. It is on my TODO list…
73, Chris - G1FEF
On 3 Apr 2021, at 15:06, Matthew Chambers via 44Net 44net@mailman.ampr.org wrote:
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@mailman.ampr.org wrote:
On 3 Apr 2021, at 10:21, Paul Sladen 44net@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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
-- 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. _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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
Registered and shared some stuff :-)
On 04/04/2021 22:02, G1FEF via 44Net wrote:
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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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:
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.
On Mon, 2021-04-05 at 18:27 +0200, Rob PE1CHL via 44Net wrote:
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?
You need to add your ssh pub key to the (and every other) gitlab interface so that you can clone repos.
-Jim P.
+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:
On Mon, 2021-04-05 at 18:27 +0200, Rob PE1CHL via 44Net wrote:
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?
You need to add your ssh pub key to the (and every other) gitlab interface so that you can clone repos.
-Jim P.
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
You just use git push. You can use https so that you don't have to deal with SSH keys. Like so:
git push --set-upstream https://git.ampr.org/username/reponame.git master
Replace username with your username and reponame with your repository name.
Ron W6RZ
On 4/5/21 09:27, Rob PE1CHL via 44Net wrote:
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:
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.
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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:
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 said it was for RF access?
On Thu, Apr 8, 2021, 22:51 Mark Herson, N2MH via 44Net < 44net@mailman.ampr.org> 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:
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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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
On 9 Apr 2021, at 15:25, K7VE - John via 44Net 44net@mailman.ampr.org wrote:
Who said it was for RF access?
On Thu, Apr 8, 2021, 22:51 Mark Herson, N2MH via 44Net < 44net@mailman.ampr.org> 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:
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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Well amprnet is first of all tcp/ip & Internet standards over amateur RADIO, we need more applications accessible from the radio side. Maybe you can find a way to encrypt the password part. There is already an exception in North-America with sending encrypted commands to amateur satellites. Maybe it is by separating ordinary read access from the uploading part.
73,
Bob VE3TOK
On 2021-04-09 10:36, G1FEF via 44Net 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
On 9 Apr 2021, at 15:25, K7VE - John via 44Net 44net@mailman.ampr.org wrote:
Who said it was for RF access?
On Thu, Apr 8, 2021, 22:51 Mark Herson, N2MH via 44Net < 44net@mailman.ampr.org> 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:
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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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:
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
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:
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
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 44net-bounces+traderbeckola=tahoma.com@mailman.ampr.org On Behalf Of Rob PE1CHL via 44Net Sent: Sunday, April 11, 2021 6:46 AM To: Bjorn Pehrson via 44Net 44net@mailman.ampr.org Cc: Rob PE1CHL 44net@pe1chl.nl 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:
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
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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…
A traditional solution to this kind of problem is to generate one-time passwords.
For example, see https://man.netbsd.org/skey.1
This arrangement ought to be compatible with rules that forbid encryption because the password goes over the wire in plain.
It is safe because once the password has gone over the wire, it is useless to anyone who has heard it.
Given motivation, it should not be difficult to integrate something like this.
VE0HAK
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:
My question is "what use case or situation *requires* using ham radio to access a source repository?"
Ham radio, RF, is what makes what we do special. We should aim at Ham RF with all our tools and projects as a matter of principle.
Bill
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
What use case requires you to use a ham radio ?
Every answer you give to this question, is quite possibly a valid answer as to why you are accessing a version control system (it's not just a software source repository) over ham radio.
On Wed., Apr. 14, 2021, 08:37 K7VE - John via 44Net, 44net@mailman.ampr.org wrote:
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 _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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:
Paul I think you misunderstood my position. It is great idea to use a service like gitlab. But we need to be carefull sbout how we do it.
Never said that we need to use github at all.
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 44net@mailman.ampr.org wrote:
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:
Paul I think you misunderstood my position. It is great idea to use a service like gitlab. But we need to be carefull sbout how we do it.
Never said that we need to use github at all.
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
On Fri, 2 Apr 2021, Tom M0LTE via 44Net wrote:
GitHub is free unlimited public/private repos, unlimited collaborators.
Chris/G1FEF already has a Github account for this:
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
As a part of the TAC I find this Idea pretty good.
But there is a small problem that I see is the management of such project.
Lets say we use Gitlab, poeple need a login to have access to the git. They also need to be either the "owner/maintener" of the project they are driving and some will give code modification and who will autorise it?
I like the idea..
Pierre VE2PF
________________________________________ De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de Marius Petrescu via 44Net 44net@mailman.ampr.org Envoyé : 2 avril 2021 05:46 À : 44Net general discussion Cc : Marius Petrescu Objet : [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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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:
As a part of the TAC I find this Idea pretty good.
But there is a small problem that I see is the management of such project.
Lets say we use Gitlab, poeple need a login to have access to the git. They also need to be either the "owner/maintener" of the project they are driving and some will give code modification and who will autorise it?
I like the idea..
Pierre VE2PF
De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de Marius Petrescu via 44Net 44net@mailman.ampr.org Envoyé : 2 avril 2021 05:46 À : 44Net general discussion Cc : Marius Petrescu Objet : [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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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@mailman.ampr.org On Behalf Of Marius Petrescu via 44Net Sent: Friday, April 2, 2021 04:47 To: 44Net general discussion 44net@mailman.ampr.org Cc: Marius Petrescu marius@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@mailman.ampr.org https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.am...
-
Alistair Mackenzie -
Bill Vodall -
Bjorn Pehrson -
Boudewijn (Bob) Tenty -
Cynthia Revström -
Darcy Buskermolen -
G1FEF -
Jason McCormick -
Jeff Parrish-Personal -
Jim Popovitch -
K7VE - John -
Marius Petrescu -
Mark Herson, N2MH -
Matthew Chambers -
Paul Sladen -
pete M -
Rob PE1CHL -
Ron Economos -
Rosy Wolfe -
Tom M0LTE -
traderbeckola＠tahoma.com -
William Waites