On Apr 24, 2011, at 18:30, Moritz Mühlenhoff wrote:

> Jeremiah C. Foster <jerem...@jeremiahfoster.com> schrieb:
>> Hi!
>> 
>> My name is Jeremiah Foster and I thought I'd join this list to
>> learn more about the process of creating a kernel for Debian.
>> 
>> I thought I'd lurk at first, though I may have a question or two
>> since I'd like to get to work creating a kernel for the TrimSlice.
>> (The TrimSlice is a Tegra2 board.)
>> 
>> I'm happy to do QA tasks and documentation (I'm a native English
>> speaker and speak Swedish) so I'll try to contribute where I can.
> 
> Feel free to help with the bug triage if you're interested.

Sure, seems like a good place to start.

> E.g. by repoking the status of forwarded bugs.

So the start might be to look through the BTS, find kernel bugs that were 
forwarded and if it looks like they are dormant, see if they can be brought to 
life?

> If a bug is producible
> with the upstream kernel and the Debian kernel doesn't deviate patchwise
> we ask people to report it at bugzilla.kernel.org. This often leads to
> the issue being fixed upstream, but sometimes there is no upstream
> reaction. 
> 
> You could ping the submitters if the issue been resolved in the mean
> time - without the Bugzilla status being updated - or if it's still
> present. It makes sense to reraise the issue upstream in such a case.

So essentially we want to make sure the BTS and kernel bugzilla data is fresh 
and up-to-date and in sync. Makes sense to me and might give me a good overview 
to start. :^)

Regards,

Jeremiah


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/c8c46ab6-f564-41bf-87da-a75ba8bbc...@jeremiahfoster.com

Reply via email to