Moving django-seo-js forward! :)

[skoczen]

Hey everyone,

So it's super-clear that I haven't had time to keep this project rolling forward and that's hurting a lot of people who use this project. It's also clear that we have smart, talented people who are interested and have time to take it forward.

So I'm doing the obvious thing: giving you all of them the ability to move it forward, and getting out of your way.

@pjdelport and @pcraciunoiu - I've just added you as contributors to this repo.

I'm happy to have you all decide how and who should carry this forward, and I'm very open to moving it to Jazzband as mentioned in #26.

Please also pass along a pypi username, so I can add one/both of you for releases. Thank you - and everyone for your patience in some too-long delays.

In terms of the current code, I've merged in a few of the biggest PRs, but in digging into testing, I've realized that I have no business testing this, since I don't currently run django-seo-js in any production environments.

Please let me know what else would be helpful in getting people unstuck, and I'm super happy to do it. Thank you all for your patience and understanding. I appreciate you.

[PiDelport]

Cool! 🎉

I am no longer actively using this library in our projects, but I'm a member of Jazzband, and I definitely think it's a good way forward.

[PiDelport]

Would you like me to file a proposal for the Jazzband roadies?

[pcraciunoiu]

I'm embrangler on pypi. Still using it for a small project, so I may be slow to help, but it beats nothing for now right? I have no experience with Jazzband, but I'm open to it.

[skoczen]

@pjdelport fantastic! I know basically nothing about the process to shift a project to Jazzband, but I'd love to understand more, and if a proposal is the next reasonable step, let's do it!

@pcraciunoiu awesome - really appreciate your support. I've added you to Pypi, so new releases are at least possible.

Maybe this thread is a good place to hash out how the project moves forward?

(Also, as an aside, I'm currently doing a similar thing with my larger project, Will. I wrote a big thing over there, and while the specific technicals don't apply here, a lot of the ethos does. I didn't re-type a version of it here largely because I was pretty beat, but I'm linking it for folks who are interested - please especially take the parts of gratitude to heart here. :) )

[pcraciunoiu]

We probably want to create an organization for this, like django-ses has for example, so it looks more official and is not under your username. @skoczen I think that's something you can do?

[skoczen]

Hey @pcraciunoiu I certainly can if we want.

My 2 cents from having done the org thing on other projects: if there's not a pressing need, it's not worth the cost. Moving the repo will mean people with old git clients have to re-point their repo to the new one, and SEO for people looking for "django seo js" will take a hit.

That said, if you'd prefer it, I'm happy to move it - just let me know!

[pcraciunoiu]

I tried my first hand at creating a release, 0.3.2 is out on pypi. Would love some help with the open PRs :)