From Fedora Project Wiki
(New section: The great nesting debate) |
(inserting my username call) |
||
Line 13: | Line 13: | ||
Nesting is in place for a lot of sections, and since it isn't breaking search/indexing, we're at least going to need to take this in stages. It all comes down to the strength of the argument. | Nesting is in place for a lot of sections, and since it isn't breaking search/indexing, we're at least going to need to take this in stages. It all comes down to the strength of the argument. | ||
[[User:Kwade|quaid]] |
Revision as of 06:06, 29 June 2008
The great nesting debate
I don't disagree with the sentiment; I'm not clear myself what is right/wrong/best/worst. There is a lot of entrenched thinking that supports nesting, and to move away from that we need to address those ideas and needs. My biggest concerns are:
- Collision of names in the flat namespace as different subprojects have similar needs
- In a single-audience (e.g. "encyclopedia readers" for Wikipedia) this is less of a concern; with multiple audiences, confusion can arise. For example, is the User_Guide for the end-user audience or the contributor audience? User of what? Etc.
- Naming structure is similary to nesting without the visual cues
- Can we be sure that all instances will continue to work without being unreadable?
- Docs/Beats/Kernel => Docs_Beats_Kernel is a bit strange; that can be reimagined (Relnotes_Beats_Kernel)
- Can we be sure that all instances will continue to work without being unreadable?
Nesting is in place for a lot of sections, and since it isn't breaking search/indexing, we're at least going to need to take this in stages. It all comes down to the strength of the argument.