xmlsec/python-xmlsec

Time to fork python-xmlsec?

jimjag opened this issue · 7 comments

jimjag commented

Considering that the current version of python-xmlsec is not compatible with the current version of libxmlsec1, and there appears to be no official progress or response regarding the future of this project, is it time to consider a fork?

ayakael commented

Perhaps, especially since a new round of changes in libxml 1.3.3 breaks python-xmlsec even after applying #264.

Ref: #279

nkukard commented

Considering that the current version of python-xmlsec is not compatible with the current version of libxmlsec1, and there appears to be no official progress or response regarding the future of this project, is it time to consider a fork?

Definitely sounds like an idea ... who is going to press the button though and do it?

bgaifullin commented

I this it would be better to add new maintainers for this project.
If someone wants, please write to me.

  • ❤️1
jimjag commented

I volunteer

  • 👍6
mxamin commented

I also volunteer

  • 👍4
ryanhiebert commented

I'm willing to help.

bgaifullin commented

@mxamin and @jimjag congratulations.

  • 👍2