Is this project abandoned? Would you be willing to hand the reins over to another maintainer?

[subssn21]

Hello Dmitry,

I noticed that there haven't been any commits to the repository in several years, but it is the defacto LTI 1.3 implementation in Python.

There are some new features that should be added (Like the existing pull request for dynamic registration)

As well as several bug fixes.

If you don't have the time to maintain this library would you be willing to turn over maintenance of this project to someone else. For instance pypi points to your repository.

It looks like there are several committers that have maintained active forks of this repository. Perhaps one of them would be interested in becoming the maintainer?

I haven't committed to this repository myself yet, so I probably wouldn't be the ideal candidate, but I am actively using the LTI library in my product.

Thanks,

Mike

[mkhawam]

Hey Mike, im also looking into using this repo but a bit considered about its maintainability. I've been looking into using it with a tornado server but there's no documentation or commits from the owner for the past 2 years. What did you end up using?

[sebPhilippot]

Hi everyone,

I completely understand your concerns. I’m in the same situation: pylti1.3 is currently the de facto Python implementation of LTI 1.3, but it seems unmaintained for several years now. However, I have never made a commit to this repo either, so I may not be the right candidate, and if you would prefer to take over this project, Mike, that is perfectly acceptable. I am available to assist or maintain this project.

For my part, I work with LTI 1.3 and I actively use the standard in my projects. Even though I haven’t contributed directly to this repository yet I’m motivated to help maintain and/or evolve this library.

If there is still interest in this project, I’m willing to take over as a maintainer, or at least initiate an active fork to ensure continuity.

What do you think? Are there other active users who would like to see this project continue?

Thanks,

[hmoffatt]

I would like to see this under active maintenance too. I use it and have submitted some fixes. There are also a lot of non-bugs reported as issues which should be cleaned up.

Unfortunately without Dmitry's blessing it won't be possible to take over the pypi listing, afaik.

[sebPhilippot]

Hi everyone,

Maybe one option would be to create a community fork and continue evolving the project under a new name, so that we don’t lose the momentum around pylti1.3.

Has anyone already tried to reach out to Dmitry by email? I’d be happy to do it if nobody else has, but of course if someone else prefers, no problem either.

This way we can keep the library alive while still leaving the door open for the original maintainer if he wants to come back.

[hmoffatt]

Good idea to reach out, I see Dmitry has recent contributions to other (private) repositories so he is still active.

[subssn21]

One thing I have done is look through the various forks of the project and found that https://github.com/christianp/pylti1.3/tree/numbas by https://github.com/christianp seems to have the best maintained version of the project. It includes the registration api and a number of bug fixes from the existing 17 pull requests.

I actually forked it myself and if I couldn't come up with a community solution to the problem, that's what I was going to build off of going forward.

As far as the community part I was thinking of creating an organization so that no one person had full ownership. and put a fork under and give it a new name if necessary. Then if we wanted to implement other Educational Integration Standards from IMSGlobal or elsewhere we would have a common place for them.

I did try reaching him but did not get a response when I started this issue on this project. Maybe someone else would have better luck?

[sebPhilippot]

I sent an email just in case. The ownerless organization is also a good idea. I will keep you informed if I receive a reply to the email. Maybe we should turn to ChristianP's fork?

[hmoffatt]

I think there is merit in having all changes go through pull request and review. ChristianP's fork is 30 commits ahead and it isn't necessarily clear which of the existing pull requests have been applied.

[sebPhilippot]

Hello, I haven’t heard back from Dmitry, so I’ve forked the project and started integrating the existing pull requests to preserve the full history.

I’ll also reach out to @ChristianP to see if we can merge efforts into a single repository — either his or mine — so that we don’t end up with two parallel projects. The goal is to pool our efforts and publish a maintained library.

I also plan to leave a message on each pull request in Dmitry’s repository to point contributors to the new maintained fork, so their work doesn’t get lost.

Do you plan to continue contributing to this project?

[christianp]

@sebPhilippot if you're happy to take charge, I'll gladly work with your fork.

Publishing a renamed package on PyPI would be a useful step.

[subssn21]

Should we create a github organization to put it under instead of putting it under an individual's account?

[DrJKevan]

Ha, k.

Well I signed the one thing they asked me to.

We are getting a notary today for the 6 partner signatures. I will send it over when I can.

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Michael Robellard @.> Sent: Friday, September 19, 2025 7:48:27 AM To: dmitry-viskov/pylti1.3 @.> Cc: Subscribed @.***> Subject: [EXT] Re: [dmitry-viskov/pylti1.3] Is this project abandoned? Would you be willing to hand the reins over to another maintainer? (Issue #155)

[https://avatars.githubusercontent.com/u/721299?s=20&v=4]

External Email

---

subssn21 left a comment (dmitry-viskov/pylti1.3#155)https://github.com/dmitry-viskov/pylti1.3/issues/155#issuecomment-3312503556

Should we create a github organization to put it under instead of putting it under an individual's account?

— Reply to this email directly, view it on GitHubhttps://github.com/dmitry-viskov/pylti1.3/issues/155#issuecomment-3312503556, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6WPUKZVCDGBR6U2YKECMST3TQJTXAVCNFSM6AAAAAB5KVE57GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMJSGUYDGNJVGY. You are receiving this because you are subscribed to this thread.Message ID: @.***>

[sebPhilippot]

I started with an individual repository with several contributors and maintainers, but a PymsGlobal organization would also work for me. However, is there a fee for that? Can an individual repo have several members with sufficient rights to continue validating pull requests? Otherwise, here is my repo https://github.com/sebPhilippot/pylti1.3 and for the organization I started https://github.com/pymsglobal. I am currently getting to grips with the code and testing everything, etc. If you want to join me either on the repo or on the organization, and if you prefer the organization, I'll put the repo in the organization. Dmitry replied that he would prefer us to do a fork.

[sebPhilippot]

if you prefer organization https://github.com/pymsglobal/pylti1.3

[hmoffatt]

I suggest an organization would be preferred to ensure the owner can't disappear again.

Dmitry replied that he would prefer us to do a fork

What about the pypi entry? Can the new team take it over, or will the package need to be renamed?

[sebPhilippot]

Can we continue this conversation in this discussion? https://github.com/pymsglobal/pylti1.3/discussions/1 . Anyone who would like to contribute to this project, please feel free to join this conversation so we can put together a team with roles and integrate pull requests into the new repository. Unfortunately, I think we'll have to create a new library. The idea behind this pymsglobal organization is to implement other global IMS standards if you want too.

[sebPhilippot]

Hello, for those who wish to continue contributing, the discussion is now available at this link. https://github.com/pymsglobal/pylti13advantage/discussions/2