Skip to content

Looking for developers #285

Open
Open
Looking for developers#285

Description

@eeintech
eeintech
opened on Dec 9, 2025

Hello Ki-nTree users,

@T0jan and I have been trying to keep Ki-nTree up and running and compatible with the latest versions of KiCad, InvenTree, and all the APIs. However, after a year of no new update, you may be wondering what's up.
It turns out that life got in our way and we are not able to keep up with the pace of development we wished for.

So we are turning to you, in case that you stumble on this message, to find out if you can help 😄
Please reach out here and we will make sure to hook you up!

Cheers,
eeintech

Activity

  1. jscott82bx commented on Dec 11, 2025

    @jscott82bx
    jscott82bx
    on Dec 11, 2025

    If you’d like message me what exactly needs to be updated and I’m sure I can get it done for you.

  2. eeintech commented on Dec 16, 2025

    @eeintech
    eeintech
    on Dec 16, 2025
    CollaboratorAuthor

    @jscott82bx As far as I am aware Github doesn't have a private messaging system 😄
    I also would like to keep things transparent.

    Basically, what's needed right now is:

    • help with the recent bugs
    • validation of the different APIs, and update if needed
    • validation with latest version of Inventree (1.0), Inventree API and Kicad (9.0), and update if needed

    Are you comfortable with the codebase of the project? Do you need pointers?

  3. T0jan commented on Dec 17, 2025

    @T0jan
    T0jan
    on Dec 17, 2025
    Collaborator

    @jscott82bx @eeintech I think the major issue for now is that we still weren't able to publish 1.2.0 on pip, but there is only a bit of testing and the actual publishing left to do: #281

    I daily drive Ki-nTree with quite a few colleagues at my workplace and it works pretty flawlessly with Inventree >1.0.

  4. Keybored02 commented on Apr 4, 2026

    @Keybored02
    Keybored02
    on Apr 4, 2026
    Contributor

    I've been implementing more and more of my fixes and workflows into Ki-nTree. I'll be pushing a couple PRs soon, let me know what you think.

    The main one is the one using a dedicated pip package for the DigiKey API v4, https://pypi.org/project/digikey-apiv4 , which could solve the issues linked to the pip publishing. I have not tested it though for the publish pipeline.

  5. eeintech commented on Apr 24, 2026

    @eeintech
    eeintech
    on Apr 24, 2026
    CollaboratorAuthor

    Hello @Keybored02

    Sorry for the delay responding.

    The main one is the one using a dedicated pip package for the DigiKey API v4, https://pypi.org/project/digikey-apiv4

    It looks like an auto-generated library, do you know who maintains it, if any?

    I see you opened a PR, unfortunately our pipeline seems broken, as InvenTree may have updated their set of installation commands... I don't have much time right now to fix it. @T0jan do you?

  6. Keybored02 commented on Apr 26, 2026

    @Keybored02
    Keybored02
    on Apr 26, 2026
    Contributor

    Hi @eeintech

    As far as I can tell, it's an official package created by the DigiKey API team. I'm not sure it is actively maintained, as there were no major API releases after the package launch. I would be inclined to say that it is. I also went though all the packages for v4 that pip offers, and this came out on top. The rest are either old, vibe coded, or lacking in documentation/structure.

  7. T0jan commented on Jul 9, 2026

    @T0jan
    T0jan
    on Jul 9, 2026
    Collaborator

    hey @eeintech @Keybored02 I finally have some time to look into Ki-nTree development again, and will check on the open merge requests in the upcoming weeks

  8. Keybored02 commented on Jul 9, 2026

    @Keybored02
    Keybored02
    on Jul 9, 2026
    Contributor

    That's great to hear! I've also been working on a fix for the new TME v2 API and TME price breaks. That said, my fork has diverged so much that I'll probably need to revisit the code before submitting it.

  9. eeintech commented on Jul 10, 2026

    @eeintech
    eeintech
    on Jul 10, 2026
    CollaboratorAuthor

    Thank you! I definitely am far from coming back to this project ATM sorry 😞

  10. jscott82bx commented on Jul 10, 2026

    @jscott82bx
    jscott82bx
    on Jul 10, 2026 via email

  11. neonflux-io commented on Jul 13, 2026

    @neonflux-io
    neonflux-io
    on Jul 13, 2026

    Hi @eeintech, thanks for the update and for all the work you and @T0jan have put into keeping Ki-nTree running.

    I’d be interested in contributing to the project and helping maintain or improve it. I can help with areas like bug fixing, compatibility updates, testing, documentation, or general development tasks.

    Please let me know what areas currently need the most attention and how I can get started.

    Thanks for keeping the project open and looking for contributors!

  12. T0jan commented on Jul 13, 2026

    @T0jan
    T0jan
    on Jul 13, 2026
    Collaborator

    Hey @neonflux-io thanks for your offer, really appreciate it! I'm currently working on a small release to get the latest contributions online and finally getting the latest version to pip again. You could help there by fixing some of the minor bugs or getting the GitHub runners working again, which broke over the last year, so the integration tests run again for the next releases.

    Otherwise, if you want to work on a bit more complex task: We are very far behind in regards to the flet package as moving forward there breaks the gui significantly, so the limited time we had never allowed us to fix the issue.

    There is also still the idea floating around to make Ki-nTree available as an InvenTree plugin which at least my colleagues would really appreciate :D

    Let me know if any of that is something of interest for you and I will try to point you in the right directions.

  13. neonflux-io commented on Jul 14, 2026

    @neonflux-io
    neonflux-io
    on Jul 14, 2026

    Hi @T0jan , thanks for the details!

    I’d be happy to help with the GitHub runners/integration tests and minor bug fixes first. I’ll take a look at the current setup and open issues to see where I can contribute.

    The InvenTree plugin idea also sounds interesting, so I may explore that once I’m familiar with the codebase.

    Can we meet in Whatsapp or Telegram?
    +353 83 098 1869 -> Whatsapp
    @czusx -> Telegram

    I will wait.

  14. T0jan commented on Jul 23, 2026

    @T0jan
    T0jan
    on Jul 23, 2026
    Collaborator

    @neonflux-io added you on telegram, you may want to remove your private contact info from an open accessible platform like this one here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions