Differences between revisions 46 and 47
Revision 46 as of 2010-03-16 08:30:50
Size: 8855
Editor: techtonik
Comment: split wiki issues that can be resolved without admins
Revision 47 as of 2010-03-16 08:36:42
Size: 8945
Editor: techtonik
Comment: organize entries
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:
   * How to scan DeadLinks in Python? -- [[techtonik]] <<DateTime(2010-03-16T08:36:41Z)>>

 * Upgrade the Python theme to the one used by [[http://wiki.europython.eu/|the EuroPython Wiki site]].
Line 27: Line 30:

 * Shorten URLs - remove /moin/ prefix from http://wiki.python.org/moin/SiteImprovements#Wiki
Line 33: Line 38:
 * Update wiki SystemInfo to latest version

 * Enable the OpenID support.
Line 37: Line 46:

 * Upgrade the Python theme to the one used by [[http://wiki.europython.eu/|the EuroPython Wiki site]].

 * Shorten URLs - remove /moin/ prefix from http://wiki.python.org/moin/SiteImprovements#Wiki
Line 54: Line 59:
 * Update wiki SystemInfo to latest version
Line 63: Line 66:

 * Enable the OpenID support.

This page collects suggestions for improving the python.org web site.


improving means enhancing site user's experience to find information faster and easier using the way they've used to. Major things that need improvement are usually obvious for everybody, but they seem Epic (Single Sign On, OpenID, online docs editor). Minor features are on the surface for each of us in particular, but they are not obvious for everyone else (wiki page subscription on edit, boring design).

improving is a process. Key to make any process effective is to provide a feedback that should be easy to reach and visible to others (see PHP online manual comments).

A lot of information causes frustration. That's why twitter takes over blogger. Too much inventory in the room makes it hard to navigate and hard to notice needed things. cleanup should throw unused stuff from standing in the way. It's especially true for wiki, but various python.org pages are accounted as well. Big amount of information reduces fun factor. Separate status page will help people see what's going on and have more fun by focusing their work and working together.



wiki content

  • Clean up Community/Python Writers page, above all: remove dead links
  • Upgrade the Python theme to the one used by the EuroPython Wiki site.

  • Update oldschool page icons to a more hardcore/pop version. (Fixed in an upgraded theme.)

  • Shorten URLs - remove /moin/ prefix from http://wiki.python.org/moin/SiteImprovements#Wiki

  • Remove rarely used links in Wiki menu in the left.
  • Rationalise the natural language coverage (merging the "new" language pages with the old ones).

wiki engine

  • Update wiki SystemInfo to latest version

  • Enable the OpenID support.
  • Add autolinking to python tracker, e.g. issue #1024, issue 1024, issue1024, bug 1024 and bug #123
    • (./) Added to InterWikiMap as Issue. For example: 7942 in the tracker. -- PaulBoddie 2010-03-15 15:32:26

    • Even though natural syntax would be more welcomed this is a nice helper. Are there any side effects if the prefix is added lowercased? Seems like is still not possible for it to show word "issue" automatically. -- techtonik 2010-03-15 16:47:59

    • I'm just following the InterWiki conventions, really. I'm sure I should use PythonIssue:xxx instead, but I suppose Issue:xxx is unlikely to be used by accident. As for the prefix, it's only included in the title for the icon, I think. And as for autolinking, I think that would require a parser extension or modification. I'd personally be comfortable with a macro (like <<PythonIssue(xxx)>>), but then people would need to know how to use it, and it wouldn't obviously be natural to write. -- PaulBoddie 2010-03-15 16:56:18

  • Add "automatically subscribe to pages I edit" plugin from http://moinmo.in/MoinMoinPatch/AutomaticSubscriptionOnEditPreference to increase people awareness about changes going on on the wiki.

  • Fix bug can't rename the page (A page with the name 'xxx' already exists. Try a different name.)

    • Can you give a walk-through of how to reproduce this? -- PaulBoddie 2010-03-15 15:44:04

    • Open JedIt page, click "Rename Page" on the left, select *jEdit* as new name and try to save. Note that there is no jEdit page. This bug previously occurred with attempt to rename Vim page. -- techtonik 2010-03-15 17:54:32

    • I just managed to rename the page to jEdIt (by accident), and although I thought that this could be a privileges issue because I am allowed to delete pages and you probably aren't, I just tried to fix the name to jEdit and I got the error. This case-sensitivity issue might be the problem, and the workaround suggested won't work, apparently, because even with another jedit page removed, the rename action still insists that one of these original pages still exists. -- PaulBoddie 2010-03-15 19:21:55

    • I've just tested page renaming on some local Wikis (running 1.6.x and 1.8.x) and they don't seem to experience this problem. -- PaulBoddie 2010-03-15 21:32:02

  • Fix bug with PythonAroundTheWorld not appearing in CategoryAroundTheWorld (may have something to do with http://moinmo.in/HelpOnCategories).

  • Fix bug Admin/Wiki doesn't appear in CategoryPythonWebsite list

  • Remove annoying "captcha" for sane users who logged in
    • This just needs the feature to be configured properly. Then a system is required to add people to the exempt users list after their intentions have been verified. -- PaulBoddie 2010-03-15 15:44:04

    • Is there an automatic group for users with 10 or more successful edits? -- techtonik 2010-03-15 17:56:09

    • I think it all has to be done manually. It would be quite easy for spammers to make accounts, perform edits manually and then automate more spamming. The TextCha page has plenty of discussion about this, but I agree that it would be nicer to have some kind of workflow in the Wiki itself. -- PaulBoddie 2010-03-15 19:21:55

    • It is easier for them to automate TextCha entry than enter it 10 times manually and in the end have their accounts banned. -- techtonik 2010-03-16 08:25:16

  • Add improved event calendar support such as that provided by EventAggregator or another similar extension.

  • Switch to TracWiki syntax

    • Why? Trac's syntax, apart from the stuff that's identical to MoinMoin's syntax, is like the old MoinMoin syntax, and although it's better than MediaWiki syntax in various ways (take the link syntax and its inconsistencies), switching to it would be like reverting a number of fixes that MoinMoin applied when its syntax (particularly the link syntax) was changed in 1.6. I don't deny that bits of it can be complicated, but that's not usually the basic stuff. -- PaulBoddie 2010-03-15 15:32:26

    • Using Trac for various Python (and not only Python) I got used to separate [http://links with description using space] - as it is more readable. I can't see where [LinkPattern link syntax] will conflict with anything. Anyway it is the last point in this list. -- techtonik 2010-03-15 17:27:00

    • I've become accustomed to the newer syntax now, and I think there's probably some reason why they moved away from the older syntax, possibly for extensibility reasons where spaces can appear naturally and confuse the process of isolating arguments. I've not been too impressed by the Wiki capabilities of Trac, but that might have something to do with the visually unimpressive styling of Trac for most installations and the lack of MoinMoin conveniences, not the syntax as such. -- PaulBoddie 2010-03-15 19:21:55

    • MoinMoin is a general purpose wiki like MediaWiki and it may happen that old syntax created problems with porting content between them. However, for software projects, Trac and Google Code were inspired by the old variant of markup and there is no single ticket to switch to MediaWiki. I would really like to see reasoning behind the choice in MoinMoin 1.6, and know if there is a preference to turn on the old markup. -- techtonik 2010-03-16 08:20:29


SiteImprovements (last edited 2020-07-04 14:12:28 by ChrisM)

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