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

Maintained? #108

Closed
AeolusDraco opened this issue Jul 6, 2017 · 16 comments
Closed

Maintained? #108

AeolusDraco opened this issue Jul 6, 2017 · 16 comments

Comments

@AeolusDraco
Copy link

AeolusDraco commented Jul 6, 2017

There has not been much activity for this project for over a year.
I also see there quite a few issues related to general maintenance such updating the pypi package and supporting a new feed type.
I was wondering if this is still being maintained.

@tabbymarie
Copy link

Yeah, I was wondering the same. There's 13 pull requests that would really enhance feedparser.

@Miserlou
Copy link

Bump for this. Have patches to discuss and send, but not sure if it's worth opening them..

@anarcat
Copy link

anarcat commented Sep 21, 2017

@Miserlou i'd say it's better to send than to keep them in the dark. at least then they can be reused by a motivated fork, if needs be.

@AndroKev
Copy link

in September @kurtmckee was working on this repo: https://github.com/kurtmckee/listparser while the commit before this, was in the year 2016.
So maybe he has more time now to work on this.

But i think we need an maintainer because now there are also duplicated pullRequestes.
(see #102 and #80)

@buhtz
Copy link

buhtz commented Dec 18, 2017

I contacted @kurtmckee today by email and asked him to give an official statement about the current status and future plans here in the Issue.

@buhtz buhtz mentioned this issue Dec 24, 2017
@buhtz
Copy link

buhtz commented Dec 24, 2017

I would trully support a new maintainer team. But as one person I have not enough ressources in time and knowledge doing this alone.

@buhtz
Copy link

buhtz commented Dec 25, 2017

I also tried to contact @kurtmckee via an Issue in another project where the last commit is only some days old. Of course it is christmas and new year holiday. We have to wait.

To all others

I really would like to see this project coming back to life. I am not a well Python programmer or knowing a lot about web-communication (urllib, etc). So I can not do this by my own. But I really would like to join a new maintainer team and take some of the burden. ;)

@twm
Copy link
Contributor

twm commented Jan 14, 2018

I, too, would be happy to join a maintainer team. As a first step I've gone through the recent issues and asked the folks who filed them to clarify where necessary.

@rachmadaniHaryono
Copy link

Hi @twm, will you merge the pr on this repo to your fork? It would be great if your fork have all the pr merged and hopefully some fix from the issue as well

@buhtz
Copy link

buhtz commented Jan 28, 2018

Just for your information. I was in contact with the maintainer per e-mail.
I don't want to give to much detailes here because he told me that he will post an official statement about the state of the project and future plans.
In summary he is alive and there is will and energy to keep the project alive and improve it.

Because of that there is no reason to do a official fork.

@rachmadaniHaryono
Copy link

ok, i will wait

@kurtmckee
Copy link
Owner

Hey guys, I appreciate your patience, particularly in the face of my silence and apparent abandonment. Life and work colluded to drain me of both time and energy to do coding outside of work. I've been working on side projects for the past month or two to start picking up steam and get my head back in the game.

I apologize again for the extended delay. I'm going to leave this ticket open until I've done enough work to demonstrate that feedparser is being maintained again. It'll take time.

@Miserlou, send those patches and reports in! =)

@rachmadaniHaryono
Copy link

@kurtmckee would you mind add someone as collaborator, so they can merge the fix or answer the issue when you are not active?

@6a7070
Copy link

6a7070 commented Jan 30, 2018

This is exciting, I'm also interested in a new release of this project. Thank you.

@AeolusDraco
Copy link
Author

So how is the progress so far?

@rachmadaniHaryono
Copy link

just give it some time, recent commit 5646f4c is jan 29,

from related issue he also answer on feb 7 on # 122

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

No branches or pull requests

10 participants