On 25 November 2016 at 14:55, Free Ekanayaka <fr...@debian.org> wrote:
> On 25 November 2016 at 14:45, Mathias Ertl <m...@restauth.net> wrote: > > >> > Any reason for not using git.debian.org? It just requires an account on >> > Alioth and possibly a request to join a team like python-modules or >> > collab-maint. >> > >> > That would make the situation more "standard". Please let me know if you >> > are unfamiliar with this process and I can provide more pointers. >> >> Yes - The large maintenance overhead that comes with it. > > > I understand that since the process is unfamiliar to you it might look as > a (scary?) overhead. However you are already at 90% of the learning curve > if you are using git/git-buildpackage, and I'm simply suggesting to use > git.debian.org as GIT server (because it will be easier to collaborate > with other Debian devs, like me). So the only additional overhead that I > see for you is to create an account on Alioth and join a team, please > correct me if I'm wrong. Happy to help with any assistance. > PS: if you really don't want to host the package on git.debian.org (but really it's really a trivial thing to do) and prefer to stick to GitHub, I can add you to https://github.com/debian-python, which in theory should be just a git.debian.org mirror, but at least a bit better than a private github namespace (for collaboration).
