|
Size: 2772
Comment:
|
Size: 3096
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Things that need doing... | == News / Changes == |
| Line 3: | Line 3: |
| * Update MoinMoin software. (./) | * [[Date(2003-03-13T00:13:44Z)]] - activated ''edit locks'' (warnings only for now) * [[Date(2003-03-07T17:35:38)]] - update from cvs should have fixed RecentChanges problems for anon users; installing PyXML should have fixed any RSS problems * [[Date(2003-02-13T00:46:26)]] - update to rev 1.168, which especially means backups on editor submits for people having a homepage, and spam protection via the `MailTo` macro * [[Date(2003-02-07T20:44:54)]] - update to CVS head * [[Date(2002-12-29T15:29:08)]] - Split up the too large frontpage into multiple head pages. * [[Date(2002-12-13T03:32:56)]] * updated to CVS current (rev 1.166) * Friday the 13th lived up to the promise... several bugs fixed * linksThatStartWithLowerCase are not links anymore, thus boost.python/InternalDataStructures stopped to work; but ["boost.python/InternalDataStructures"] works, and on the ["boost.python"] page, `/InternalDataStructures` works too (i.e. use the short form of subpage links). * [[Date(2002-11-21T06:16:54)]] - updated to CVS current (rev 1.163) * [[Date(2002-11-06T22:40:50)]] - You can now refer to PEPs like so: '''`PEP:0123`''' -> PEP:0123 * [[Date(2002-08-02T00:19:27)]] - Outgoing mail works now |
| Line 5: | Line 16: |
| * Fix up the ["Python"] and FrontPage's (./) | == Things that need doing, unless they're done == |
| Line 7: | Line 18: |
| * Python logo instead of MoinMoin logo, and changing the sitename (below the logo). (./) | * Decide explicitly a convention for page deletion for unpriviliged users. * We need a mission statement on the front page. What it's for, who can/should participate. * Need to create a discussion / ask for help section(s). |
| Line 9: | Line 22: |
| * Announce on c.l.p and Daily Py URL when we're fully alive | == Discussion == ''Unfortunately, the ISBN links point to amazon.com, not amazon.de'' -- DanielDittmar |
| Line 11: | Line 25: |
| 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) |
Well, this is hardly surprising in an English wiki. You can use full http links, though. -- JürgenHermann [[DateTime(2002-07-26T02:01:40)]] |
| Line 18: | Line 27: |
| * 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 |
''I wasn't surprised, but I was thinking of adding ISBN.de http://www.amazon.de/exec/obidos/ASIN/ to intermap.txt (now that I found how ISBN works).'' -- DanielDittmar [[DateTime(2002-07-26T21:14:18)]] ---- |
| Line 25: | Line 33: |
| 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 SpecialInterestGroup''''''s 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)]] 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)]] |
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 ---- Discussions about Python should be held on comp.lang.python and the SIGs, but it is OK to summarize those discussions in the wiki. -- DanielDittmar [[DateTime(2002-07-15T02:21:48)]] |
| Line 35: | 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)]] |
News / Changes
Date(2003-03-13T00:13:44Z) - activated edit locks (warnings only for now)
Date(2003-03-07T17:35:38) - update from cvs should have fixed RecentChanges problems for anon users; installing PyXML should have fixed any RSS problems
Date(2003-02-13T00:46:26) - update to rev 1.168, which especially means backups on editor submits for people having a homepage, and spam protection via the MailTo macro
Date(2003-02-07T20:44:54) - update to CVS head
Date(2002-12-29T15:29:08) - Split up the too large frontpage into multiple head pages.
- updated to CVS current (rev 1.166)
- Friday the 13th lived up to the promise... several bugs fixed
linksThatStartWithLowerCase are not links anymore, thus boost.python/InternalDataStructures stopped to work; but ["boost.python/InternalDataStructures"] works, and on the ["boost.python"] page, /InternalDataStructures works too (i.e. use the short form of subpage links).
Date(2002-11-21T06:16:54) - updated to CVS current (rev 1.163)
Date(2002-11-06T22:40:50) - You can now refer to PEPs like so: PEP:0123 -> 0123
Date(2002-08-02T00:19:27) - Outgoing mail works now
Things that need doing, unless they're done
- Decide explicitly a convention for page deletion for unpriviliged users.
- We need a mission statement on the front page. What it's for, who can/should participate.
- Need to create a discussion / ask for help section(s).
Discussion
Unfortunately, the ISBN links point to amazon.com, not amazon.de -- DanielDittmar
Well, this is hardly surprising in an English wiki. You can use full http links, though. -- JürgenHermann DateTime(2002-07-26T02:01:40)
I wasn't surprised, but I was thinking of adding ISBN.de http://www.amazon.de/exec/obidos/ASIN/ to intermap.txt (now that I found how ISBN works). -- DanielDittmar DateTime(2002-07-26T21:14:18)
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
Discussions about Python should be held on comp.lang.python and the SIGs, but it is OK to summarize 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
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)