User talk:Laibsch

ToDo

• think about policy for allowing and denying access to certain pages and groups of pages
• interwiki links to bug tracker, etc.
• is mail working correctly? I don't seem to receive any. Maybe my addy is incorrect.

Naming again

Hi Laibsch, your change is an example for additional work resulting from misunderstanding abbreviations by wiki users (see Category talk:Dev). For a casual user it is not clear what Dev stands for. Developer? Development? Device? Once again i suggest to rename ambiguous pages and categories. -- Sledz 07:58, 11 May 2009 (UTC)

A wiki is a wiki and that is what it should remain being. The Category:Dev page clearly states what it is about. No matter what you do, people will have different perceptions or plainly not read what is there. I think it is a question of overhead vs. flexibility. I choose flexibility to make users want to contribute to the wiki. The overhead is far less than the time we spent arguing about it. --Laibsch 12:08, 11 May 2009 (UTC)

PS: What about putting Openembedded:Help to the sidebar now?

Header Level

Hi Laibsch, once again me, the nitpicker. ;-)

You reverted my header level fixup at the Infrastructure page. In MediaWiki applications it is common practise, that the page title itself is header level 1, so all subheaders should be level 2 (see e.g. Wikipedia.org). This clear structure is very helpful if you want to export the pages to other formats (e.g. PDF for printing). -- Sledz 15:49, 17 May 2009 (UTC)

I was unaware of this, but it looks like indeed Wikipedia follows this practice. Not sure if this wiki will be exported to PDF, but how would we do this? IOW, where would it make a practical difference? Until now, I just found it natural to start header level at 1. --Laibsch 20:38, 17 May 2009 (UTC)

For PDF export there are a lot of MediaWiki extensions e.g. PDF Writer together with Collection or PdfBook and PdfExport. And as said before header level 1 is used for the page title itself. -- Sledz 15:41, 18 May 2009 (UTC)