sticky HBLink's new home on GitHub


Randy AA6RH
 

Okay, here we go.

I've created a GitHub organization, named it "HBlink-org" and have added the repos that Cort made available to me in order to preserve maximum development history on the site. Cort's no longer on the mailing list, so I will just say that he's been awesome and really does care about the future of the project, just that he can't be the project lead any longer. He was kind enough to make his repos available to me to push into the new org for safekeeping.

https://github.com/HBLink-org

In that org, you will find all of the projects, named (I believe) the same way that they were named previously. These repos are full mirrors, so all branches (i.e. HB_Bridge and IPSC_Bridge for older HBLink and DMRlink repos) are there.

I would strongly suggest that if you have tools that build things like Docker images or whatever, you should update those tools to pull from GitHub at these new repo locations. This will be where they are located, going forward.

For those of you with clones of Cort's original repos, you should still be able to issue pull requests to these repos, I'm a bit more fuzzy on whether or not the commit ID's are the same (I think they are), so this whole rebasing of the repos might be a merge headache of epic proportions when time comes to actually attempt to merge pull requests. We'll just have to see, won't we...

There will obviously be more details as we progress through this. I will be adding people to the org as members based on expressed interest and being able to identify their GitHub accounts. For the moment, I will be the only one who can commit to the repos until we further establish ground rules for development.

In short, I'm taking care of the project until such time that someone better qualified and motivated steps up to manage it in a community-oriented manner.

--R
--
Randy Hall AA6RH (not K7AGE, quit asking) ūüėĀ


area51now@...
 

Thanks Randy for taking this on and I know everyone appreciates Cort keeping his work available to us all.

Bob
Kb6led


EA5GVK Joaquin
 

Hello, everybody. Great news and better idea to develop the great project that our friend Cort has started, to which I am very grateful.
I am not a programmer, but I can help in any way I can to spread the word, I love this project. I also manage the hblink registration database http://hblink-register.com.es
I would like with respect to my friend Waldek, who has created a functional hbmonitor together with other colleagues.
The HBmonitor could be improved by giving it a faster operation. These are just ideas. Congratulations to all of you.


Dan K2IE
 

OK, just catching up.

I did a successful pull from my local repo and it merged just fine.

Good work!

origin    https://github.com/hblink-org/hblink3 (fetch)
origin    https://github.com/hblink-org/hblink3 (push)
dan@lin2:~/git/hblink3$ git pull
remote: Enumerating objects: 58, done.
remote: Counting objects: 100% (57/57), done.
remote: Compressing objects: 100% (19/19), done.
remote: Total 46 (delta 33), reused 40 (delta 27), pack-reused 0
Unpacking objects: 100% (46/46), done.
From https://github.com/hblink-org/hblink3
   08f6669..d0d496b  master       -> origin/master
 * [new branch]      trimmed-down -> origin/trimmed-down
Updating 08f6669..d0d496b
Fast-forward
 .gitattributes    |    0
 Dockerfile        |   30 --
 app_template.py   |  150 --------
 blank_app.py      |  143 -------
 bridge.py         | 1069 +++++++++++++++++++++++++++++++++++------------------
 config.py         |   49 +--
 const.py          |    1 +
 entrypoint        |   19 -
 hblink-SAMPLE.cfg |   39 +-
 hblink.py         |   54 +--
 install.sh        |    6 -
 rules_SAMPLE.py   |   12 +
 voice_lib.py      |    0
 13 files changed, 748 insertions(+), 824 deletions(-)
 mode change 100644 => 100755 .gitattributes
 delete mode 100644 Dockerfile
 delete mode 100755 app_template.py
 delete mode 100755 blank_app.py
 delete mode 100755 entrypoint
 delete mode 100755 install.sh
 mode change 100644 => 100755 voice_lib.py


Dan K2IE
 

I did a a hard reset to my local tree after I found that the current code seems to omit XLXPEER type.

Somewhere between commit 08f6669bd315f8abb9bd80b5faad4cd43439c2f4 and today, the XLX support seems to have vanished.

I'll open an issue for further investigation.

73


Randy AA6RH
 

Please go check the issue on GH for comments. I think we can restore it with your help.

--R
--
Randy Hall AA6RH (not K7AGE, quit asking) ūüėĀ


Dan K2IE
 

Thanks for verifying.  It ended up as 3 commits because I first backed out the commit you identified via a diff and committed to my fork.  When creating the pull request, I saw that some other funtionality not related to XLX had been touched and had to identify and pull that back in.  So best always to look at my pull requests in its entirety rather than the individual commits.  Sometimes it takes me a few commits to get there and the pull request is a great comparative tool.

Of course if there is a better way that could work for me, I always want to know...

73


Randy AA6RH
 

I probably would've just had a side copy of the code with the XLX lines in it, and done a LOT of diffs on the code before the commit, just to see what other lines I might have affected.

It's not like it's a faux pas of some epic variety, just that I chose to look at each commit separately, instead of just looking at the final resulting diff from the three commits combined. As soon as I did that, it looked just fine to me.

--R
--
Randy Hall AA6RH (not K7AGE, quit asking) ūüėĀ


Dan K2IE
 

i understand.  It is all about preferences and work styles.

I could equally argue that a commit should only deal one issue at a time.  If Crufty Programmer (or any of us in the future) wants to add or remove a feature or cruft, let's not mix removing a major feature with adding unrelated code in the first place.  Then a rollback is as simple as removing that particular commit.

But all is well and I am enjoying the cruft.

73


JJ Cummings
 

Randy - it would be great if you could add other contributors to the repository so that others are able to contribute / respond to bug/support matters / review and accept PRs etc...


On Sun, Oct 25, 2020 at 12:02 PM Dan K2IE via groups.io <dan=islenet.com@groups.io> wrote:
i understand.  It is all about preferences and work styles.

I could equally argue that a commit should only deal one issue at a time.  If Crufty Programmer (or any of us in the future) wants to add or remove a feature or cruft, let's not mix removing a major feature with adding unrelated code in the first place.  Then a rollback is as simple as removing that particular commit.

But all is well and I am enjoying the cruft.

73


Randy AA6RH
 

Be careful what you ask for. Send me your Github ID.

--R
--
Randy Hall AA6RH (not K7AGE, quit asking) ūüėĀ