Hello all: I'd like to get going working on the kernel (I've tried getting started the last few times). On the kernelnewbies page, one of the kernel janitor projects is to balance out functions and clean up code. I'm curious if there would be someone, or a group of someone's who would mind assigning me a specific file or a small driver of some sort that needs this so I can get started helping out? -- Take care, Ty my website: http://tds-solutions.net my blog: http://tds-solutions.net/blog skype: st8amnd127 My programs don't have bugs; they're randomly added features!
On Fri, Aug 19, 2011 at 5:26 AM, Littlefield, Tyler <tyler@tysdomain.com> wrote:
Hello all: I'd like to get going working on the kernel (I've tried getting started the last few times). On the kernelnewbies page, one of the kernel janitor projects is to balance out functions and clean up code. I'm curious if there would be someone, or a group of someone's who would mind assigning me a specific file or a small driver of some sort that needs this so I can get started helping out?
--
Take care, Ty my website: http://tds-solutions.net my blog: http://tds-solutions.net/blog skype: st8amnd127 My programs don't have bugs; they're randomly added features!
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Hi Tyler! Have you read FAQ/WhereDoIBegin [1] and kernel-janitors TODO list [2]? [1] http://kernelnewbies.org/FAQ/WhereDoIBegin [2] http://code.google.com/p/kernel-janitors/wiki/TODO
Hi Tyler You can also get ideas from sitting on the mailing list and seeing what others are doing: kernel-janitors.vger.kernel.org (kernel-janitors@vger.kernel.org) Also driver staging is always looking for more contributors and you can get a good feel for what is going on on the mailing list: devel.linuxdriverproject.org (devel@linuxdriverproject.org) Read the TODO lists for various drivers in the in the kernel tree in drivers/staging/ and pick something you would like to do. Don't forget to read the relevant files in Documentation/ for preparing/submitting patches, etc, and make sure you cc the relevant maintainers when sending patches to their drivers to the list. If you're not doing it already by far the easiest way is to use git to manage your kernels, you will be expected to test your patches against linux-next or some branch specified by a particular maintainer which you can remote track (I think it's staging-next on Greg's tree for staging, but it wouldn't hurt to ask the maintainer once you have the patch ready). Cheers Julie
Also driver staging is always looking for more contributors and you can get a good feel for what is going on on the mailing list: devel.linuxdriverproject.org (devel@linuxdriverproject.org)
Read the TODO lists for various drivers in the in the kernel tree in drivers/staging/ and pick something you would like to do. Don't forget to read the relevant files in Documentation/ for preparing/submitting patches, etc, and make sure you cc the relevant maintainers when sending patches to their drivers to the list.
If you're not doing it already by far the easiest way is to use git to manage your kernels, you will be expected to test your patches against linux-next or some branch specified by a particular maintainer which you can remote track (I think it's staging-next on Greg's tree for staging, but it wouldn't hurt to ask the maintainer once you have the patch ready).
Cheers Julie
Oh, and another suggestion - find out what hardware you have and find out what corresponding drivers cater for it in the kernel. You can then join the appropriate mailing lists (filtering on their throughput if it's large) in order to catch any new patches or bugs that appear there for your hardware. You can then work on testing the patches/helping fix the bugs, which is especially helpful when done by people who have the actual hardware to test with. If it's new stuff in staging, I think the staging people would particularly appreciate this. Cheers Julie
Hi On Fri, Aug 19, 2011 at 11:44 PM, Julie Sullivan <kernelmail.jms@gmail.com> wrote:
Also driver staging is always looking for more contributors and you can get a good feel for what is going on on the mailing list: devel.linuxdriverproject.org This link is unavailable. (devel@linuxdriverproject.org)
Read the TODO lists for various drivers in the in the kernel tree in drivers/staging/ and pick something you would like to do. Don't forget to read the relevant files in Documentation/ for preparing/submitting patches, etc, and make sure you cc the relevant maintainers when sending patches to their drivers to the list.
If you're not doing it already by far the easiest way is to use git to manage your kernels, you will be expected to test your patches against linux-next or some branch specified by a particular maintainer which you can remote track (I think it's staging-next on Greg's tree for staging, but it wouldn't hurt to ask the maintainer once you have the patch ready).
Cheers Julie
Oh, and another suggestion - find out what hardware you have and find out what corresponding drivers cater for it in the kernel. You can then join the appropriate mailing lists (filtering on their throughput if it's large) in order to catch any new patches or bugs that appear there for your hardware. You can then work on testing the patches/helping fix the bugs, which is especially helpful when done by people who have the actual hardware to test with. If it's new stuff in staging, I think the staging people would particularly appreciate this.
Cheers Julie
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
On Sat, Aug 20, 2011 at 4:04 AM, esmaeil mirzaee <esmaeil.debian@gmail.com> wrote:
Hi
On Fri, Aug 19, 2011 at 11:44 PM, Julie Sullivan <kernelmail.jms@gmail.com> wrote:
Also driver staging is always looking for more contributors and you can get a good feel for what is going on on the mailing list: devel.linuxdriverproject.org This link is unavailable.
That's because it's a mailing list not a 'proper' link. You can subscribe here: http://driverdev.linuxdriverproject.org/mailman/listinfo/devel and you can subscribe to the kernel-janitors.vger.kernel.org one (amongst many others) here: http://vger.kernel.org/vger-lists.html HTH, Julie
participants (4)
-
esmaeil mirzaee -
Julie Sullivan -
Littlefield, Tyler -
Vladimir Murzin