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

Project status #705

Open
apie opened this issue Nov 28, 2019 · 12 comments
Open

Project status #705

apie opened this issue Nov 28, 2019 · 12 comments

Comments

@apie
Copy link

apie commented Nov 28, 2019

Hello,
First of all I would like to thank you for this project!

I was wondering what the project status is? The issues and pull requests seem to pile up, and it has been quite some time since the last release.

Will this project be maintained in the future? Are you looking for help/maintainers?
Is this project abandoned? If so, is there a maintained fork or alternative?

Thanks

@Pyvonix
Copy link

Pyvonix commented Dec 5, 2019

I think, it's a very good question. I use pipeline on many of my projects this library and I would like to know too the status of the project.

If I dedicated some time to propose fixes and features, I would like to see them validated (or checked by one of the maintainers). And as we can see many MR are waiting and a lot of issues without any reply... A good example is #706 we just passed in Django 3.0 and MR for 2.2 not process....

In another way, we can see @danielleknudson pushing the #704 14 days ago. Did we need to consider the project maintained?

This is an important question, because Django evolve fast and if the librariy doesn't follow the rhythm, it might be nice to put the tag "maintained" to inform users to find something else.

@gatsinski
Copy link
Contributor

The number of issues and pull requests is proof that the project is alive and has a huge community but the lack of attention from the maintainers is a noticeable problem. I believe that there are many people who want to get involved in the project and they should be allowed to. Introducing more developers as maintainers is the obvious solution.

@cyberdelia
Copy link
Member

Since this project is part of Jazzband, y’all are empowered to contribute and maintain django-pipeline.

@Pyvonix
Copy link

Pyvonix commented Dec 25, 2019

@cyberdelia many thank for your reply. I don't know we can join the Jazzband easily and participate in this project (commit and merge) after joins it. It could be great to notice it somewhere in each project, no? If you have some time, can you give me your opinion about, what we can do and what we can't for this project (I will explain my self).

All my interrogations is about the evolution of this project. I would like to help to maintain it, that the reason why I join Jazzband and maybe others will join it later too. But that involves some questions. For example, I do some stuff on the MR #708 but the better evolution possible will be to drop the support to python 2 because python 2 support is over in 2020 and no more Django release for python 2. Can I take this decision by my self? And merge it in master?

In another way many people have proposed very great MR (but don't know who to join Jazzband or i don't want Jazzband), can we take the decision to merge MR for them? (after code review and tests passed as well).

All these questions seems important to me to be posed for not making me shit on the project. I hope you have time to answer me so that I can make the right decisions.

@cyberdelia
Copy link
Member

We’ve essentially followed the same guidelines as Django regarding python versions. So if you add support for a newer django version, that new major version of pipeline can drop support for whatever Django dropped support for.

@Pyvonix
Copy link

Pyvonix commented Dec 27, 2019

@cyberdelia Did you have any idea, how to release the new version on PyPI?

I push the version 1.7.0 on test.PyPI to test on confirm it correctly work, but how make it accessible on PyPI?
Did I miss something?

@cyberdelia
Copy link
Member

cyberdelia commented Dec 27, 2019

@TheBuky Publication should be automatically done by CI. Unless it broke.

Yep, it broke: https://travis-ci.org/jazzband/django-pipeline/jobs/629717022

@Pyvonix
Copy link

Pyvonix commented Dec 28, 2019

If I correctly understand the error HTTPError: 403 Client Error: Invalid or non-existent authentication information. for url: https://upload.pypi.org/legacy/ in the Travis job.

We need new (or valid) authenticate information to push on pypi.org with the correct permissions to jazzband/django-pipeline. One of the maintainers is Jazzband Bot can check permissions on the project and validate password?

@hugovk
Copy link
Member

hugovk commented Nov 23, 2021

There have been six releases since this issue was opened, most recently last month:

image

https://pypi.org/project/django-pipeline/#history

Shall we close this issue?

@cyberdelia
Copy link
Member

I'd be more than happy to have another lead to help maintain and release django-pipeline more smoothly.

@peymanslh
Copy link
Member

peymanslh commented Feb 4, 2023

@cyberdelia
I'm in jazzband for a while and currently, I'm looking for a project to contribute most of my time.
I'd be happy if there is anything that I can help with.

@fdemmer
Copy link

fdemmer commented May 24, 2024

Maintainance is happening ❤️ ... time to closes this issue?

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

No branches or pull requests

7 participants