Re: guidelines, faqs and dos and don'ts document

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 19 November 2010 19:12, Bond <jamesbond.2k.g@xxxxxxxxx> wrote:
> On Fri, Nov 19, 2010 at 11:13 PM, Alison Chaiken <alchaiken@xxxxxxxxx> wrote:
>> Anuz, I think your document is right on-target. Â ÂI would just add,
>> "Don't ask for help with basic C programming." Â ÂYes, there are lots
>> of idioms in the kernel that are not found elsewhere in C, and asking
>> about those is on-topic, but questioners should not (intentionally)
>> ask questions that will be answered by consulting K&R.

I totally agree with Alison's reply. This is not a place to discuss
general / beginner C programming topics, and we should make sure this
guide makes that clear.

> It would be a difficult task to mention what structures or data types
> occur again and again which are not present in K &R to make a wiki
> page on kernelnewbies and point to it but this would be worth than
> making a lecture note and when some one asks some question which is a
> common fault then give them a 5 page lecture to read that doc.
> I do not see any value in such a doc most of the people would be happy
> with a guide of how to ask questions smart way.

So are you agreeing or disagreeing with Anuz's (cool) document and
Alison's suggestion?

I have seen this kind of problem in another mailing list, and the
issue seems to be more of a language barrier than technical
understanding of the topic.

I doubt any FAQ or lecture will help in that situation, unless there
are translations to other languages.

I like so far of what I've read of Anuz's document - though it could
be tidied up so that you don't have to turn on word-wrapping to be
able to read it.

>> Also, readers should not ask questions relevant to particular boards
>> or drivers. Â Those questions should be asked (if at all) on
>> specialist mailing lists.
> If I am aware of what I am asking why would I be a kernel newbie.

Knowing what you are asking is not the same as knowing the answer, is it?
And knowing the answer would not mean you are no longer a kernel newbie.

> Why don't you make relevant pages to point to some guides like crashcourse.ca
> and some simple things which make a newbie a safer dive rather than
> saying him to jump to I2C and discuss some thing.
> Sorry if I am too harsh here but I mean it.

I don't understand what you mean here. This is not supposed to be a
tutorial that teaches you kernel topics - this is a guide on how to
conduct yourself on a public, archived mailing list on the topic of
kernel programming.

> --
> Most of the free documentation and kernel books are not worth reading.

Does your signature qualify as ironic? :)

Regards,
Srdjan

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ




[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux