search

partkeepr / PartKeepr

Open Source Inventory Management
http://www.partkeepr.org
GNU General Public License v3.0
1.4k stars 403 forks source link

working towards a v1.5.0 release candidate #1225

Open ptaylor2018 opened 3 years ago

ptaylor2018 commented 3 years ago

Feature description

Given the update to the v4 octopart API means that the current release v1.4.0 can't currently use this (in my opinion, essential) feature, I propose that either the current master branch be released as v1.5.0, or at the very least we roadmap what features/fixes are need before that can happen.

As it currently stands, all documentation/existing tooling primarily points towards installing with v1.4.0, with installing from git only as a secondary option. This creates a difficulty for new users, as they will probably have gone through the entire install process before realizing that octopart search doesn't work. Only after troubleshooting this issue to find out they need to build from source and reinstalling does this problem go away. If a v1.5.0 existed (and documentation pointed to installing with it), this troublesome scenario would be eliminated.

Sebigamer4 commented 3 years ago

The problem is that the current status of this project is unmaintained. So theres currently nobody who works on a new version.

the other problem is, that it needs major changes to get uptodate just so it can run on not outdated systems.

Its a great project and it got everything you need for parts keeping, but you need to know that its complicated to get it running and that its a whole blob of legacy stuff....

Sadly i personally dont have knowledge in PHP and also not the time to get into it, but i would love an up to date version as well :)

It seems like a few ppl already trying to get it more up to date, but its probably not easy

dromer commented 3 years ago

@Sebigamer4 this is the main problem: nearly nobody that is interested in the project is a proficient PHP coder (and more specifically: proficient in Symfony).

However we are investigating the possibilities of replacing the back-end/API with something else, while keeping the database structure and fantastic front-end UX. Since everybody looking at this is doing this in their spare time don't expect anything new any time soon.

A 1.5.0 release with at least as many bug-fixes as we can would be nice of course. This was actually the plan for the past year, but hasn't panned out as we had hoped.