Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add warning to README.rst #1998

Closed
wants to merge 3 commits into from
Closed

Add warning to README.rst #1998

wants to merge 3 commits into from

Conversation

B3QL
Copy link
Contributor

@B3QL B3QL commented Jun 22, 2023

Hi folks,
since nothing much had happened from the beginning of 2023
in terms of finishing version 2.0 or building a team around the project.

I see no choice but to warn other developers to not depend on MoviePy.

@coveralls
Copy link

Coverage Status

coverage: 84.484% (-0.2%) from 84.697% when pulling 00d35f5 on B3QL:1874-add-warning into b5bb086 on Zulko:master.

@B3QL
Copy link
Contributor Author

B3QL commented Jun 26, 2023

@keikoro can you take a look?

@keikoro
Copy link
Collaborator

keikoro commented Jul 11, 2023

@keikoro can you take a look?

I wouldn't agree it's "not maintained" – I'm still labelling issues here. ^^ But agree that a warning makes sense.

Maybe you could change it to something that doesn't make it sound like it's dead dead, but lets users know that what's on PyPI is outdated and that the project is struggling with releasing a new version? Otherwise people will be confused why the repo wasn't also set to archived.

@B3QL
Copy link
Contributor Author

B3QL commented Jul 17, 2023

Hey @keikoro, you're right. The message was crafted before the rebirth of the discussion. I'll reword it next week when I will return from holidays. Sorry for late response :)

@coveralls
Copy link

coveralls commented Jul 19, 2023

Coverage Status

coverage: 81.904%. remained the same when pulling 986351e on B3QL:1874-add-warning into bc8d1a8 on Zulko:master.

@B3QL
Copy link
Contributor Author

B3QL commented Jul 19, 2023

@keikoro I tried to make it more informative and less scary, let me know if it's OK :)

@B3QL
Copy link
Contributor Author

B3QL commented Jul 27, 2023

@keikoro depending on #1874 (comment) the PR might not be needed :) I would love to close it, but let's wait.

@B3QL
Copy link
Contributor Author

B3QL commented Oct 13, 2023

Closing in favour of #2024

@B3QL B3QL closed this Oct 13, 2023
@B3QL B3QL deleted the 1874-add-warning branch October 13, 2023 09:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants