https://bugzilla.redhat.com/show_bug.cgi?id=1379651 --- Comment #17 from jibecfed <jean-baptiste@xxxxxxxxxxx> --- Licence issue is fixed: https://github.com/getpelican/feedgenerator/issues/10 This thread explains the reason why the Pelican maintainer created a new project for a standalone feedgenerator: https://github.com/getpelican/pelican/issues/2202 Here is copy/paste for history: > Pelican already uses feedgenerator in a way that produces correct output. > Pelican needed, and still needs, a standalone Pip-installable package for feedgenerator. No such package existed, so we created one years ago. When doing so, we needed a source code repository from which to build said package — a repo that isn't burdened by all the rest of Django, none of which applies to Pelican. That's why feedgenerator exists. > When issues came up that needed fixing for Pelican's purposes, we fixed them in feedgenerator. As is the nature of open source, anyone is welcome to submit pull requests containing those fixes to Django's repository. > Hopefully that clears up some of the history. I'm open to suggestions and would like to help if I can, but so far I have not yet heard anything sensible/actionable from the perspective of Pelican's project management. Please help us to have blogs that includes the whole content, I really dislike forcing my readers to go on my website to access information. Have a nice day, and thanks for your actions! -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
