Differences between revisions 16 and 17
Revision 16 as of 2002-07-17 13:20:31
Size: 3057
Editor: ipd54b5964
Comment:
Revision 17 as of 2002-07-17 19:24:51
Size: 3263
Editor: pD9E39CC8
Comment:
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:
Imposing (widely accepted) structure is not unwiki, actually it is a goal of refactoring. Otherwise, you end up with a spaghetti wiki, i.e. chaos. -- jh
Line 37: Line 39:
Imposing (widely accepted) structure is not unwiki, actually it is a goal of refactoring. Otherwise, you end up with a spaghetti wiki, i.e. chaos. -- jh   That still means that you can capture from news, or from the wiki itself. Both ways are valid, but always refactoring/summarizing is A Good Thing. -- JürgenHermann [[DateTime(2002-07-17T21:24:51)]]

Things that need doing...

  • Update MoinMoin software. (./)

  • Fix up the ["Python"] and FrontPage's (./)

  • Python logo instead of MoinMoin logo, and changing the sitename (below the logo). (./)

  • Announce on c.l.p and Daily Py URL when we're fully alive

IMO we're not ready to go live yet - we need to do more:

  • We need a mission statement on the front page. What it's for, who can/should participate.
  • Links to wiki-etiquette.
  • The FrontPage is little more the a list of links right now. Some information on what a wiki is and how to use it should be added.

  • Possibly software, documentation and community should have their own head pages
  • Need to create a discussion / ask for help section(s)
  • Tell Guido to link from python.org to FrontPage. Too late! (./)

    • I don't think that's so bad, a wiki lives from its community, and is not something you prepare in a dark chamber and then present (set in stone) to the world. Still, the above observations are valid, and we'll want to steer the growth into a sane structure. --jh

Some ideas about the aims of this wiki:

What I would like to use this Wiki for is for comparisons between Python packages. Most areas seem to have multiple solutions. Is it very unwiki to impose some structure like I did in WebProgramming and trying to keep it up? GuiProgramming and IntegratingPythonWithOtherLanguages are also candidates for this kind of style. -- DanielDittmar DateTime(2002-07-15T02:21:48)

Imposing (widely accepted) structure is not unwiki, actually it is a goal of refactoring. Otherwise, you end up with a spaghetti wiki, i.e. chaos. -- jh

There are areas which could be moved from the regular web site to the wiki, because they live from contributions anyway. Examples would be some of the SpecialInterestGroups or the page listing editors suitable for Python. -- DanielDittmar DateTime(2002-07-15T02:21:48)

Should we get permission to move content from the python.org webmasters first? I'd like to take up the editors page. -- -- JohannesGijsbers DateTime(2002-07-16T02:42:17)

  • Real moving implies getting such a permission, since the HTML page has to be removed, and the links redirected to the wiki pages. Please don't just copy pages w/o informing anyone, and consider how often a page changes (i.e. if there's a real reason to take it into the wiki). -- JürgenHermann DateTime(2002-07-16T03:54:04)

    I think the editors page is an excellent candidate for moving, as it will lower the bar for contributing new editors, configurations for editors, etc. I'll mail the python.org webmasters and see what their response is. -- -- JohannesGijsbers DateTime(2002-07-17T15:20:31).

Discussions about Python should be held on comp.lang.python and the SIGs, but it is OK to summary those discussions in the wiki. -- DanielDittmar DateTime(2002-07-15T02:21:48)

The entire point of a wiki is to capture discussion in such a way that it will be remembered IMO - dhl 20020716

PythonWikiTasks (last edited 2012-06-10 08:59:59 by techtonik)

Unable to edit the page? See the FrontPage for instructions.