Introducing Keybase for SK
in Hydejack / Git / Repos
It’s been a while since we’ve updated our development log, but we’ve still been working hard on tons of projects (as seen in our updated docs pages).
An update about git, and where we’ve been:
We’ve made the decision to create a second Github organisation, github/signal-k which houses the “root” repositories. github/acord-robotics will house smaller components, like specific api components, legacy repositories, forks and spare branches, as well as forks of other projects like the OSR, and will be hooked into github/signal-k via submodules/forks. In addition to this update, we’re also spending a lot of time on Keybase (more on this below).
We’re taking a little bit of time off compared to the start of the year where everyone had plenty of time to work on the team and our projects, but I’m still going to be around and am still spending plenty of time filling in the gaps on our projects.
If you don’t know much about keybase, I’d recommend having a look through their documentation. Basically, we’re combining our Github orgs (through a flask-based RESTful API) with Keybase which will take over as our main method of inhouse communication.
Leave a comment here if you’d like to be added to the group!
GeminiStation
Deployment | Platform | |
---|---|---|
Flask Material Dashboard | Codeship: | |
Documentation/Code | Github Tree | / |
FMD -> Customised Gunicorn | Codeship: | |
signalkinetics | / | |
FMD -> run.py | Vercel |