eggs are explained here - https://stackoverflow.com/questions/2051192/what-is-a-python-egg
|Deletions are marked like this.||Additions are marked like this.|
|Line 42:||Line 42:|
| * Fix email@example.com response bug (per Issue:7929)
* Add website repository to http://svn.python.org/view/
| * (done) Fix firstname.lastname@example.org response bug (per Issue:7929)
* Add link to website repository at https://github.com/python/pythondotorg see [[https://github.com/python/pythondotorg/pull/217|this pull request]].
pydotorg Improvement Ideas
This page collects suggestions for improving the PythonWebsite, this wiki and related tools.
Discussion of various bits around Python websites takes place on the following mailing lists:
- General Web site (architecture, design, integration)
- Bug tracker
- Package index
- Development workflow
Please choose the correct list, and try not to cross-post.
A bigger picture
Improving a web site is a process of enhancing user experience so that information is found faster and easier. Major things that need improvement can be obvious to many people, but they may seem like tasks of epic proportions, too big for an individual to consider tackling on their own. For example, implementing single sign-on for all Python services, OpenID support, an online edito for docs - these are all non-trivial tasks that require knowledge of the existing site architecture and access to the site code and supporting tools. There are also features that matters to every one personally, and these are not obvious for everyone else: automatic subscription to Wiki pages upon editing, various design improvements.
But the process of improvement has to solicit feedback in order to capture ideas about areas of improvement, and this channel for feedback should be easy to reach and visible to others. An example of such a channel is the online manual comments that one sees in the documentation for technologies such as PHP, MySQL (example) and PostgreSQL.
A lot of information causes frustration: that's why people prefer Twitter to Blogger. Too much "inventory" in the room makes it hard to navigate and notice things that are needed. The process of cleanup should involve throwing unused stuff away, leaving relevant and updated information in place. Naturally, the Wiki has accumulated lots of arguably unused and dated pages, but various python.org pages are affected as well. Too much information reduces the "fun factor": a separate status page will help people see what's going on and let them have more fun by focusing their work and enabling them to work together with others.
Badly need bug tracker for python.org website (metatracker issue340)
I wonder if roundup is better than some hosted solution -- techtonik 2010-04-06 14:06:34
- python.org should have a poll/settings for active python.org accounts to allow people mark when they switch to Python 3 - the data should be used to show progress bar of converted people, there should be a 130 symbols field to comment about the reason when you switch forward and backward
Add #pydotorg to http://python.org/community/irc/
- Rename "Internet Relay Chat" in navigation menu to IRC as it is the preferred name most people look for
- Add paragraph anchors to site generator
- Add an RSS feed and/or mailing list for python security advisories
Add release timer and calendar to Core Development page
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 core development/source page with a table of
Clean up CategoryJython
- Clean up Community/Python Writers page, above all: remove dead links
Shorten URLs - remove /moin/ prefix from http://wiki.python.org/moin/SiteImprovements#Wiki
- Rationalise the natural language coverage (merging the "new" language pages with the old ones)
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.)
- Remove annoying "captcha" for sane users who logged in
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
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
- There should be a "Logout" link in the left navigation (Actions)
Don't you see a "Logout" link under "User" or are you not using the new (and awesome) default theme? -- PaulBoddie 2011-03-25 20:53:00
I was using the "python" theme, now I changed to "<Default>" and I can see the "Logout", Thanks ! But it would be nice, if we can add a "Logout" link for the "python" theme. -- BaijuMuthukadan 2012-10-22 07:18:08
I think the "python" theme is unmaintained. There was a suggestion that the new default theme, also known as "europython", be renamed to "python" and thus appear for everyone who has chosen "python" as their theme, but that could be confusing for people. -- PaulBoddie 2011-03-25 23:01:36
Link for homepage and download on http://pypi.python.org/pypi?%3Aaction=search&term=scapy&submit=search
Core Developer Web Resources
The Core Development Helper Tools page discusses enhancements for version control and bug tracking, particularly with regard to integration.