The future about dce_lti_py HOT 4 OPEN

Ryan, you just made my day. I am 👍 on all of your bullet points, and collaboration would be most welcome.

Some background: at the time I created this my team was spiking and developing a few LTI tools, but then had our attention shifted to another priority, which is why progress stalled. Just in the past few weeks there is talk of getting back to lots of LTI work, so your timing is good.

FYI, I've also had some sporadic contact with the developers of the "upstream" ims_lti_py package. I was granted admin access to that repo, as well as an OK to get push rights to the pypi index (hasn't happened yet). I'm on the fence about the value of trying to push all the wholescale changes back upstream, but haven't had the time to really worry about it anyway. The idea of making a clean break and renaming to just lti is attractive.

There is currently a wheel up at https://pypi.python.org/pypi?:action=files&name=dce_lti_py&version=0.7.4

I think for both of us to collaborate equally it would have to be via a new org/project.

from dce_lti_py.

Alright, I guess we could either have it on one of our personal github profiles (yours makes more sense than mine, since you've actually done work on it, but I'd be fine/happy going the other way), or we could come up with an organization. I'm a bit unimaginative in the name department, but perhaps pylti, trying to take inspiration from pyca, pypa, etc? Or perhaps we could get a repo at @imsglobal? I might be able to get @aspiredu to host the repository, though in that case I can see it making more sense for it to be at an organization of your choosing.

Sorry for complaining about the wheel. I didn't see a setup.cfg, but I realize that's only for universal wheels, and since you're only supporting 2.7 currently, that's not yet necessary.

I think the next step is to decide where the new repository should be. Then we can get to work cleaning things up to our liking before our 1.0!

from dce_lti_py.

It looks like you suggested "python-lti" over on the upstream repository as an org name. That works for me too. Let me know what you think would be best for the name / org, and I'll be happy to get going setting up whatever I'm able to.

from dce_lti_py.

Nothing's irreversible, but I went ahead and created a new GitHub organization called pylti, and added you to it, @lbjay . I changed the name of the package and the file structure a bit, and got it set up for testing, which involved fixing a few broken tests. If you're happy with that org and repo name, then we're good to go, and we can have further conversation over there. I've already added you to the organization, you just need to accept the invite.

from dce_lti_py.