Proposing django-taggit-serializer

[Fohlen]

Hello there folks! On behalf of @mecodia and @glemmaPaul I am proposing to move the django-taggit-serializer project to jazzband, so that it can have more attention being paid to it in the future. Please let us know what you guys think over here:

• will it be feasible for the jazzband organisation to handle this package?
• what steps need to be taken in order to make this happen?
• @glemmaPaul would of course still like to be involved in maintaining the package. Is this feasible with your community guidelines?

[nat-yaml]

+1

[ksitko]

Hey guys, any chance this could be further considered? django-taggit already is under jazzband's umbrella, given the rather significant popularity of django-rest-framework it seems almost like taggit is incomplete without a serializer.

[jezdez]

@Fohlen @glemmaPaul @ksitko Hey friends, this is long overdue to say the least, but yeah, this project looks like a good match.

Just join the Jazzband org on https://jazzband.co/ and transfer the repo using the regular GitHub repo transfer tool. A separate issue with TODOs to finalize the transfer will be created automatically and can be worked on once the project is under the Jazzband.

[kasteph]

Would it be possible to just have a fork of django-taggit-serializer under jazzband?

[jezdez]

Would it be possible to just have a fork of django-taggit-serializer under jazzband?

Unfortunately that won't give access to the PyPI project and complicates maintenance. I would suggest to reach out to @glemmaPaul by email to figure out if glemmaPaul/django-taggit-serializer#44 is still something that they'd be interested. Alternatively I would suggest to propose the functionality to django-taggit itself.

[rtpg]

I have reached out to Paul regarding this topic. I believe that having django-taggit absorb the serializer code makes the most sense overall, as it's a pretty relevant piece of functionality.

[ksitko]

That would be best. Serialization is crucial enough to warrant its inclusion.

[rtpg]

Alright, I had tried reaching out to Paul and didn't get a response (on top of non-responses to other people on this topic).

Given the license compatibility (see this issue) for the projects, I opted for vendoring in the project and including attribution to Paul in several places in the codebase.

I believe this is following the licensing of the respective codebases correctly, and I also believe this is what makes sense on an organizational level as well (the serializer stuff was just one file, having it all in one package is just easier to maintain)