Is kernel Bugzilla a good way to start?

Is kernel Bugzilla a good way to start?

[Dennis Semakin]

An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161222/f5f7c6d6/attachment.html 

Is kernel Bugzilla a good way to start?

[Rik van Riel]

On Thu, 2016-12-22 at 19:21 +0300, Dennis Semakin wrote:
> 
> Hi everybody.?
> I just thought that may be it will be quicker to start to develop for
> kernel.

It can be, but one word of caution. ?Sometimes bugs
get fixed independently from the bug report, and the
bug described in the bug report may no longer be
happening in the current kernel.

It would be good to test the bugs people have filed,
to make sure they still exist, before trying to "fix
them again" :)

-- 
All rights reversed
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161222/05054f5d/attachment.bin 

Is kernel Bugzilla a good way to start?

[Peter Senna Tschudin]

I would give http://eudyptula-challenge.org/ a try. Guess is the
fastest and coolest way to get started.

2016-12-22 17:21 GMT+01:00 Dennis Semakin <insane79@yandex.ru>:
>
> Hi everybody.
> I just thought that may be it will be quicker to start to develop for
> kernel.
>
> --
> ?????????? ?? ?????????? ?????????? ??????.?????
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>



-- 
Peter

Is kernel Bugzilla a good way to start?

[Dennis Semakin]

Ok, thanks. But actually I was confused and disappointed little bit when opened kernel bugzilla.
I found old and very old bugs and I don't suppose that they are actual. 
As for education and understanding how kernel sub-systems works it could be very useful try to fix some of them.
 

22.12.2016, 19:30, "Rik van Riel" <riel@surriel.com>:
> On Thu, 2016-12-22 at 19:21 +0300, Dennis Semakin wrote:
>> ?Hi everybody.
>> ?I just thought that may be it will be quicker to start to develop for
>> ?kernel.
>
> It can be, but one word of caution. ?Sometimes bugs
> get fixed independently from the bug report, and the
> bug described in the bug report may no longer be
> happening in the current kernel.
>
> It would be good to test the bugs people have filed,
> to make sure they still exist, before trying to "fix
> them again" :)
>
> --
> All rights reversed

Is kernel Bugzilla a good way to start?

[Dennis Semakin]

Well... I'm already involved there. But there is no response over one month.
This situation reminds me that something similar has been happened with Eudyptula a couple months ago.
Moreover I think that their tasks are too easy, at least first 6 of them.

22.12.2016, 19:30, "Peter Senna Tschudin" <peter.senna@gmail.com>:
> I would give http://eudyptula-challenge.org/ a try. Guess is the
> fastest and coolest way to get started.
>
> 2016-12-22 17:21 GMT+01:00 Dennis Semakin <insane79@yandex.ru>:
>> ?Hi everybody.
>> ?I just thought that may be it will be quicker to start to develop for
>> ?kernel.
>>
>> ?--
>> ??????????? ?? ?????????? ?????????? ??????.?????
>>
>> ?_______________________________________________
>> ?Kernelnewbies mailing list
>> ?Kernelnewbies at kernelnewbies.org
>> ?https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
> --
> Peter

Is kernel Bugzilla a good way to start?

[Dennis Semakin]

Thanks for such detailed information. Now I have a subject what I should think about.
And yes, I'll chose my own way :)


22.12.2016, 20:26, "valdis.kletnieks at vt.edu" <valdis.kletnieks@vt.edu>:
> On Thu, 22 Dec 2016 19:21:18 +0300, Dennis Semakin said:
>> ?I just thought that may be it will be quicker to start to develop for kernel.
>
> The quickest way to start will depend on why you're thinking of doing
> kernel development at all.
>
> Did your boss just tell you that you have 13 weeks to ship a Linux driver
> for your company's new USB widget?
>
> Do you have a device that Linux doesn't support?
> Do you have a device that Linux *claims* to support, but it doesn't work quite right?
> Do you have a device that used to work, but broke recently?
>
> (And yes, the approaches for the 3 are different)
>
> Do you have a deep desire to do something specific? "Wow, filesystems are
> really cool"? "I want to push my laptop to the limits"? Something else?
>
> Do you just want to give back to the community? If so, skip developing and
> just build and run a new linux-next kernel once a week. Lots easier to get
> started, and we have plenty of developers - but lots fewer people actually
> testing the 600,000 lines of new code every release. And how do I know there's
> less testers than developers? Because if we had as many testers, I wouldn't
> personally trip over an average of 3 to 5 bugs in linux-next per release cycle.
>
> Did you think it would be a babe magnet? Or looking for something to put
> on your resume?
>
> All these have different paths....
>
> (And here's the quick hint on how to get started with linux-next:
>
> $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> (the clone created a subdirectory, so cd to it for the following)
> $ cd linux
> $ git remote add linux-next git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> $ git fetch linux-next
> $ git fetch --tags linux-next
> ... # later on
> $ git remote update
> ...
>
> Once a week, do a 'git remote update' and build/install/run the new kernel.
> If anything explodes, send an email to linux-kernel at vger.kernel.org
>
> And yes, it really *is* that easy.