libkeepass maintainer

[Evidlo]

I'm not sure where else to ask, but who is the current maintainer of libkeepass? pypi says that the project homepage is phpwutz/libkeepass, but this project has many forks of which yours is the most recently updated.

[pschmitt]

Good question, I could not determine any official maintainer either. I'm not really qualified to maintain it myself, I just made a fix regarding unicode and that's about it.

EDIT: As a matter of fact I just uploaded a package containing unicode fixes.

[Evidlo]

I'm more concerned about the fact that there's no central location submit PR's or issues. Perhaps it would be a good idea to make a libkeepass Github group/repo and link pypi to that?

[pschmitt]

Yeah that'd be great to get some visibility for libkeepass. But we would not be able to reclaim the libkeepass package name on pypi, unless the original submitter deletes it beforehand. On Fri, Mar 24, 2017, 17:00 Evan Widloski <notifications@github.com> wrote: I'm more concerned about the fact that there's no one place to submit PR's or issues. Perhaps it would be a good idea to make a libkeepass Github group/repo and link pypi to that? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/pschmitt/pykeepass/issues/11#issuecomment-289064797>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACT_tmQ-vGyM_76K-IIrpl4g6uO19ewks5ro-ingaJpZM4Mnaoy> .

…

-- Philipp Schmitt

[Evidlo]

I'll see if I can message phpwutz about this. In the meantime, should we be interested in merging the commits from user crass? It looks like this person contributed a lot to the KDB3 code

[Evidlo]

I got in contact with phpwutz and he set up a libkeepass organization here.

[pschmitt]

Nice !