Quoting Eric W. Biederman (ebiederm@xxxxxxxxxxxx): > Yes. It looks like we are going to have to setup a public repository > somewhere to collect all of the changes and bug fixes. Not that I > expect too many but clearly there are a few needed. That exists. Shadow upstream (and Debian package) is maintained in an SVN repository hosted on alioth.debian.org. I can make it as easy as possible to people to contribute by opening commit access there. We can also, if that helps in attracting contributors, convert the repo to git (I will need help there because the repo has a quite long history and we want to keep it). I know that, nowadays, svn often looks a bit scary (and, TBH, feature-limited) to many FLOSS contributors. In short, nothing is hidden nor closed. Indeed, I think that shadow might benefit from more input, given that my friend Nicolas has limited time. The only constraint is indeed giving French cheese names to releases. This is something I won't compromise with...:-). We invented this tradition when we took shadow over, back in 2005 (doh!) and that has to remain the French Touch in the software..:-) I can act as a facilitator for all this. I definitely *don't have the skills to decide what contributions are "good" or not. Shadow being a sensitive piece of software, we might need to be careful at the beginning and include fixes and new features with care. This is indeed where git and its great branching features might help a lot. May I welcome interested people to join the Pkg-shadow-devel@xxxxxxxxxxxxxxxxxxxxxxx mailing list so that we reduce the CC list of this thread?
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/containers
