Django summernote unmaintained?

[claudep]

The last commit was done two years ago, looks like nobody is caring any longer for the package.

@lqez, @DiemenDesign, any news for future plan? Are you looking for help?

[silentjay]

@claudep it's definitely abandoned, which is a shame as I added it to a new project and now have to rip it out.

[DennisSuitters]

There's no reason others can't contribute, that's the beauty of Open Source. I'm not a django use myself, hence why I don't do anything on this repository. If someone wanted to help maintain, I'm sure we could add them to do that upon the agreement of the other maintainers.

[claudep]

I would be OK to help maintain the package.

[DennisSuitters]

@lqez @hackerwins what's your thoughts on this?

[claudep]

Any news?

[advancedsoftwarecanada]

I'm actively using it. There's nothing else like it that's free....

[beOn]

I added it to a project that I started a couple years ago, and just returned to. @DiemenDesign, if the other maintainers are MIA can you bring @claudep on yourself?

[DennisSuitters]

I'm not sure, I should however be able to merge PR's, but I won't be able to test them, so I would be relying on those who submit PR's to do the right thing. So if anyone wants to fix issues, I'm more than happy to merge them. I guess if anyone wants to comment on PR's and indicate that they in fact do work, I could go from there, and if I can add people I will consider it, or at least advocate for them to the owners. I would also need to check commit history and quality of past PR's.

[claudep]

So what about starting with #466? I guess #484 is straightforward too. At some point, we'll need a new release, @DiemenDesign , do you think you would be ablte help for this too?

[DennisSuitters]

I've merged #466, only has there was confirmation that the fixes worked. #484 was just docs, so I merged that as well.

Future merges, until I get confirmation that it's ok to add maintainers, I'll require that another source confirms that the changes work, just so we can make sure, or at least reduce merging breaking changes.

[claudep]

Thanks ❤️ . That makes sense, of course!

[beOn]

#492 is also an issue. I've just addressed it on my own fork, and will try to remember to submit a PR when the team gets around to testing it.