Respond to Wiki syntax suggestion. Add "Issue" InterWiki note.
Added more responses.
|Deletions are marked like this.||Additions are marked like this.|
|Line 36:||Line 36:|
|* Can you give a walk-through of how to reproduce this? -- PaulBoddie <<DateTime(2010-03-15T16:44:04+0100)>>|
|Line 44:||Line 45:|
|* This just needs the feature to be [[HelpOnTextChas|configured properly]]. Then a system is required to add people to the exempt users list after their intentions have been verified. -- PaulBoddie <<DateTime(2010-03-15T16:44:04+0100)>>|
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.
Add website repository to http://svn.python.org/view/
add release timer and calendar to Core Development page
report bug or suggest a change link leading to corresponding bug tracker (PythonWebsiteCreatingNewTickets wiki link) (issue #8146)
http://www.python.org/Jobs.html should be moved to a database with a secure and user-friendly front-end. (Wikis won't do it for many people we're targeting.)
- Add autolinking to python tracker, e.g. issue #1024, issue 1024, issue1024, bug 1024 and bug #123
- Clean up Community/Python Writers page, above all: remove dead links
Upgrade the Python theme to the one used by the EuroPython Wiki site.
Shorten URLs - remove /moin/ prefix from http://wiki.python.org/moin/SiteImprovements#Wiki
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
Update wiki SystemInfo to latest version
- Remove annoying "captcha" for sane users who logged in
Update oldschool page icons to a more hardcore/pop version. (Fixed in an upgraded theme.)
- Remove rarely used links in Wiki menu in the left.
Add improved event calendar support such as that provided by EventAggregator or another similar extension.
- Enable the OpenID support.
- Rationalise the natural language coverage (merging the "new" language pages with the old ones).
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
Link for homepage and download on http://pypi.python.org/pypi?%3Aaction=search&term=scapy&submit=search