alas - my intermittently super crummy spine is still crummy. Realistically it will be a couple of weeks before I can get beck to coding on this fun project. We have a great group of fairly active devs (sorry I’ve been away from the discord channel). Any of ya’ll willing to be the other ‘main’ device code developer? At least for stuff like pushing out official builds and screening github issues.
I’m eager to get back at it - but it would help to have some more coverage in that area.
I do C# mostly for my day job and have been working on a iOS app for meshtastic I would be happy to help out with some issue triage and such.
Feel Better!
hi ya’ll, alas I’m still on my “away from computers and working on posture, exercises” break. If any of the fellow devs need to reach me please send me an email. Otherwise I’ll be back on oct 10th and will be merging all the stuff ya’ll have added!
also - if anyone is willing to step up as the ‘co-device lead’ (and has previously submitted some PRs), please let me know and I’ll bless you in the github org so you can do releases and merge PRs.
Sorry about the delay. 
@geeksville How can I help?
Happy to tag team with you or anyone else.
Yay! @mc-hamster I’ll bless you today and I’m back and merging the many and awesome PRs everyone sent in while I’m away. In the next couple of days let’s all chat on discord and work out a longer term plan.
I think you have my ph#. Message any time if not on discord, I’m usually around.
Welcome back @geeksville! and thank you for the invitation; unfortunately I am not sufficiently competent to handle other contributors’ code, also I have no Discord access and my availability is somewhat unpredictable.
Big thanks to @mc-hamster for volunteering to help - I was secretly hoping that you would 
Now let’s build something awesome.
@geeksville whilst I’m not proficient enough to review any substantial PR’s. I’m happy to handle/co-ordinate any other stuff, CI, minor features, overlapping PR coordination etc. As I appear to have the most amount of free time.
I wanted to say thank you very much to the folks that work in this space. The total volume of work at play boggles my mind sometimes.
Thanks for all the hard work… for looking at the issues, and lending your brain power to the project.
With some luck, I can continue to learn enough to be of some value… right now I find myself starting at some of the code and having to really dig to figure out what’s going on.
I hope during 2022 to author a plugin or two… and do some python work to make use of that new plugin.
But mostly, this is just to say thank you!
hi ya’ll - alas my crummy back is still crummy ;-). And I’m trying to obey my personal rule of ‘no standing in front of the computer when it is painful’, so I’ll be away a bit longer (hopefully less than a month). I just checked github and the other devs are doing great things. @sachaw, @mc-hamster, @a-f-G-U-C thanks for stepping up!
If you’d like to do ‘real’ releases with your changes, the procedure is:
for device:
for python: (if any dev wants to take this on, send me a note and I’ll bless you with pypi)
for android:
If someone wants to take this on, please let me know @AndreK ?
i’d love to help. sent you a PM.
for device:
- edit version.properties and check it into the root project
- run bin/promote-release.sh - this should cause github to start a release build (see the CI actions)
- edit the draft release text and click publish
I have contributed a bit and done custom builds of meshastic-device. I have no problems tracking down basic logic issues in the firmware. However, I’m not a hardware level C++ developer by trade so I have some knowledge gaps in some areas.
If the task is mostly dev-ops centric though, such as making sure Github actions produce proper artifacts and doing basic release management, I will throw my hat in with helping with that effort if I can help keep things pushing forward.
@thebentern You’ve been rocking it! You can totally do it
Build instructions are much more streamlined than I remember it. Wow.
Please bless me with pypi … I’d like to throw my hat into the ring to do a release of the python sdk.
… I got a device build out with the new CI action, but using promote-release.sh didn’t work. I was able to work around it, but I got the error even though I was able to create a new tag:
fatal: 'root' does not appear to be a git repository
fatal: Could not read from remote repository.
Thanks mate!