You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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?
Activity
ayakael commentedon Jan 9, 2024
Perhaps, especially since a new round of changes in libxml 1.3.3 breaks python-xmlsec even after applying #264.
Ref: #279
nkukard commentedon Feb 1, 2024
Definitely sounds like an idea ... who is going to press the button though and do it?
bgaifullin commentedon Feb 25, 2024
I this it would be better to add new maintainers for this project.
If someone wants, please write to me.
jimjag commentedon Feb 26, 2024
I volunteer
mxamin commentedon Feb 27, 2024
I also volunteer
ryanhiebert commentedon Mar 1, 2024
I'm willing to help.
bgaifullin commentedon Mar 2, 2024
@mxamin and @jimjag congratulations.