curious: why use own hosting rather than github?

yanchenko.igor at yanchenko.igor at
Fri May 22 18:36:41 CEST 2020

On Fri, May 22, 2020 at 6:29 PM Erazem Kokot <contact at> wrote:
> While what you said is mostly true, forking a project without a good
> reason (e.g. the old one being abandoned) doesn't benefit the old
> project. Also forking a project without the permission of the original
> owner would mean that fork being a new project in which case the name
> would have to be changed for copyright reasons (afaik).
> An unofficial mirror doesn't make much sense, think about how you would
> manage contributions. If you as a Github maintainer of the mirror accept a pull
> request, how are you going to make sure that the PR you already merged
> is going to be accepted upstream? This also means that most clueless
> users will contribute to the Github repo, possibly not even knowing
> about the mailing list and most likely won't discuss their pull requests
> and or bug reports here, but on Github, which would mean that the
> contributors wanting to fix bug would have to watch Github to see bug
> reports.
> So unless an official mirror is made (which would mean more work for the
> current maintainers), this would in my opinion be a bad idea.

You are assuming that the problems of the maintainer of the fork will
become problems of the community, if maintainer of the fork(or
unofficial mirror, whatever) cannot solve those issues, it will be his
own issues, not the community's, if he manages to solve them none of
those issue will matter as they will be solved.

More information about the Password-Store mailing list