Skip to content

Time to fork python-xmlsec? #275

Closed
Closed

Description

@jimjag

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?

Activity

  1. ayakael commented on Jan 9, 2024

    @ayakael
    Contributor

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

    Ref: #279

  2. nkukard commented on Feb 1, 2024

    @nkukard

    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?

  3. bgaifullin commented on Feb 25, 2024

    @bgaifullin
    Collaborator

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

  4. jimjag commented on Feb 26, 2024

    @jimjag
    CollaboratorAuthor

    I volunteer

  5. mxamin commented on Feb 27, 2024

    @mxamin
    Collaborator

    I also volunteer

  6. ryanhiebert commented on Mar 1, 2024

    @ryanhiebert

    I'm willing to help.

  7. bgaifullin commented on Mar 2, 2024

    @bgaifullin
    Collaborator

    @mxamin and @jimjag congratulations.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions