On Tue, Apr 6, 2010 at 8:56 PM, mrts <mrts.py...@gmail.com> wrote: > James has replaced the content of > > http://code.djangoproject.com/wiki/DjangoSpecifications/Core/Threading > > with the following disclaimer: > > "This page and several others were created by a > wiki user who was not and is not a member of the > Django core team. Previous contents of this and > other similar pages are not and should not be confused > with Django's own documentation, which remains > the sole source of official documentation for the Django project." > > I personally think that the information on that page [1] > was both useful and mostly correct, albeit incomplete. > As such I fail to see why it should be removed -- > the disclaimer given by James pertains to the majority > of pages in Django wiki; following that reasoning, > all of them should be removed :). > (Moreover, the disclaimer is implicit in most wikis' content.) > > That doesn't necessarily mean that the page should be > restored as-is. Something seems to disturb James, > so the contents should perhaps be updated, amended > and relocated to a better URL so that he and other members > of the core would be happy with it instead. > > Thoughts?
James spoke with me about this decision at the time, and I completely agree with and endorse his actions. While it is true that wikis contain all sorts of information, often unofficial, the naming of the wiki pages in question -- DjangoSpecifications/Core -- conveyed a *very* strong signal that the information contained was official in some capacity. Regardless of the merits of the information on that page, the simple fact remains that it *isn't* official, and it *wasn't* vetted or edited by anyone in the core. It isn't just a matter of moving it somewhere else in the wiki, either. The simple fact remains that the wiki is housed on djangoproject.com, and it's impossible to tell what is official and correct information, and what is not. This doesn't matter so much when we're discussing the location and participants in an upcoming sprint or brainstorming design ideas for a proposal, but it matters a great deal when a page is describing long term architectural decisions or guidelines. Django's position on "core specifications" is that: * If there is a bug, it should be logged in Trac, and (ideally) fixed * If there is some usage guidelines that need to documented, they should be documented formally and integrated into Django's own documentation. If you think there is some valuable information in the wiki pages that were deleted, then you need to turn that information into either tickets in Trac, or a draft for addition to the official documentation. If you think there is some information on that page that doesn't fit into the official locations that Django currently provides, then we need to have a meta-discussion around the right place to house information of that sort. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
