[TangerineSDR] Tangerine Code Repo
kv0s.dave at gmail.com
Thu Apr 2 11:47:44 EDT 2020
I agree with you, I just prefer not having a code monolith but several
project specific locations.
As opposed to the TAPR GitHub we have now, which, as set up does not work
well for development. We may have a repository for code distribution later.
We have multiple client code producers and software consumers. Interfaces
for each are different and from experience with with the old SVN and the
TAPR github experience differs widely. What is easy for some is difficult
And then we have the issue of keeping all the parts up to date and tested.
On Thu, Apr 2, 2020, 10:26 AM John Ackermann N8UR via TangerineSDR <
tangerinesdr at lists.tapr.org> wrote:
> It seems we have a couple of different discussions going on under a
> non-inutuitive subject line. :-)
> So this thread is to talk about where we store *code*, not data, for the
> TangerineSDR and maybe broader PSWS-related projects.
> I don't know enough to have a view as to what is the best approach.
> What I do know is that TAPR has a github.org account that's available,
> and we also have a Linux VM hosted at a small but pretty decent hosting
> company that we could install GitLab or whatever on. Either of those
> are available to the group if desired.
> But we should decide on an approach now, as it seems various people are
> developing or offering bits of code that we should deal with in an
> organized way.
> We should also consider whether hardware design documents should be
> stored in the same manner, or with a different approach (as far as I'm
> concerned a github-like repo works fine for my hardware stuff).
> TangerineSDR mailing list
> TangerineSDR at lists.tapr.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the TangerineSDR