search

motioneye-project / motioneye

A web frontend for the motion daemon.
GNU General Public License v3.0
4.01k stars 662 forks source link

Plan for continuing with this project #2307

Open MichaIng opened 2 years ago

MichaIng commented 2 years ago

@cclauss @Mictronics @jmichault and everyone else, let's make a plan how to continue with this project, now moved to the new @motioneye-project GitHub organisation.

First of all, everyone who has contributed to motionEye before, or wants to do so, please feel free to join in, also I think we can add everyone who is interested to the organisation.

I think we agree that Python 3 support is the first thing to achieve, given that Python 2 has reached EOL since over 2 years already, @jmichault and @Mictronics have Python 3 compatible forks from where we can commit back, and on this repo we have the python3 branch and a bunch of open pull requests for further related fixes.

I personally would go this way:

Approximately from simple to difficult, regarding possible conflicts 😉.

theGiuMac commented 1 year ago

@cclauss thank you for the prompt answer. The state of development is clearer now. And indeed, "Sit tibi terra levis" Python 2.

I probably wrote my comment in the wrong place, I've found the link in the homepage. I was looking for info specifically on motionEyeOS or if I could help in anything related to the coding side.

I guess you're keeping issues open about current problems and I've read that DevOps seems in place (at least for the CI/CD pipeline).

cclauss commented 1 year ago

Can the default branch please be changed to something more modern than Python 2?

McMagnus commented 11 months ago

I 2nd this. I've been digging into motion/motioneye since last year, haha, but just now did I realize there's a (working?) Python3 implementation.

What could be the downside of using it as default?

I can help on the dev side if needed. And I'll try that dev branch right now.

nullr0ute commented 11 months ago

There is now a beta release with a move to python3 here https://github.com/motioneye-project/motioneye/releases/tag/0.43.1b1

With luck that should be a stable release soon. Testing I suspect is the most important thing :)

cclauss commented 11 months ago

With luck that should be a stable release soon.

In our lifetimes? Python 2 died 1,463 days ago on 1/1/2020.

MichaIng commented 10 months ago

I thought to keep a branch as default which contains a stable release, which is currently python2 or master only. But I agree in the meantime, the Python 3 compatible beta version should work much better than the old release. I'll create a main branch from beta and make this the new default.