On Tue, Dec 30, 2014 at 3:08 AM, Eric W. Biederman <ebiederm@xxxxxxxxxxxx> wrote: > Timothy Chen <tnachen@xxxxxxxxx> writes: > > > Thanks Eric for the detailed reply! > > > > I want to gain more understanding and context around namespaces in the > > kernel, and thought contributing is the best way to do so. > > It can't hurt. > > > I wonder if there is a public backlog that lists open issues that you > > mentioned or haven't get to work on yet? > > Nothing more than I have posted. That isn't how I work, and it isn't > how folks in the kernel tend to work. > Setting up a wiki page could make for a good first contribution ;-) > > Start with assuming there aren't bugs in the kernel implementation. > The certainly are no known bugs that someone who is not familiar with > the kernel is likely to be able to fix. > > So find something you would like to do with a container, and figure out > why you can't, and then send a patch or ask a question about how to make > it work. > Sharing from my personal experience, I learned about Google summer of code in 2011 and found the program to be very helpful in matching itches to scratch with potential open source contributors. The Linux Foundation has been a participating organization in the program in recent years as well as several of the Linux distros. With the rising interest in containers, open source projects looking for new blood should consider applying to the program and propose containers related projects. As a mentor, it was very rewarding for me to help a new kernel developer join the community. Amir. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/containers
