|
Size: 2960
Comment:
|
← Revision 71 as of 2012-06-10 08:59:59 ⇥
Size: 4056
Comment: clean up old discussions
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from WikiTasks |
|
| Line 3: | Line 5: |
| * Update MoinMoin software. (./) | * 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). * Theme-related suggestions by LionKimbro <<DateTime(2006-03-25T16:48:34Z)>>: * Replace current icons with more common images - for example, current edit icon `python.org/img/moin-edit.png` is hard to associate with action * If possible, make the icons text, instead of icons? * "Toggle Line Numbers" draws way too much attention to itself; ''Especially'' when you have only 2 or 3 lines of code! Remove it entirely, or make it much smaller, or (whatever.) * Or use `numbers=disable` in the code regions. -- PaulBoddie <<DateTime(2009-12-09T17:07:42+0100)>> * Bullet point items are spread too far apart. Less white space above and below them. * If I could, I'd make the top bar half as tall as it is. * I'd try to find a way to either (A) eliminate the sidebar, or (B) make it editable. That way, regulars could maintain it. (ex: see [[http://www.communitywiki.org/en/FrontPage|the CommunityWiki SideBar,]] which [[http://www.communitywiki.org/cw?action=edit;id=SideBar|is editable]]) |
| Line 5: | Line 16: |
| * Fix up the ["Python"] and FrontPage's (./) | == News / Changes == |
| Line 7: | Line 18: |
| * 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 |
* [[PythonWikiChanges]] |
| Line 12: | Line 21: |
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) |
|
| Line 22: | Line 23: |
| 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)]] | 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)>> |
| Line 25: | Line 26: |
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)]] ''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)]] |
---- 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 38: | Line 31: |
| 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)]] | 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)>> |
| Line 40: | Line 33: |
| What kind of conversation are we talking about? * Philosophy - I don't care where it goes (usenet, here, C2, elsewhere) * "How does this piece work?" - it works great here "How does this work" has been great. If you need me to back this up for you, I can back it up with many anecdotes; Most of the pages I write here have seen some related action. People tell me that they read and use (and correct) my pages, and it'd be sad to see that come to an end. The only thing that annoys me are pages with questions for names. Instead, the page name should be the name of the piece, and then the question should appear on the page. That is, [[How can "normal" users report bugs in Python or the documentation?]] should be a page called PythonDocumentation, and then the question attached to ''that'' page. -- LionKimbro <<DateTime(2005-09-15T22:31:31Z)>> [[[lwickjr]]: Sorry about that, Lion. :I ] ---- I think this Wiki would best serve as continuing from where standard Python documentation left off: showing examples of use, adding information about good packages not existing in the standard distribution, and talking about higher-level stuff like 'tips for parallel processing'. Examples are very important for newcomers, and hey, many people like to learn new things first from examples, and dive into reference when details become important (including me). As for discussing Python in general, I think c.l.p is invaluable and needs no replacement - so I guess I'm along the same lines as DanielDittmar and JürgenHermann. -- EdvardMajakari <<DateTime(2005-09-15T15:14:13Z)>> ---- CategoryPythonWebsite |
Things that need doing, unless they're done
- 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).
Theme-related suggestions by LionKimbro 2006-03-25 16:48:34:
Replace current icons with more common images - for example, current edit icon python.org/img/moin-edit.png is hard to associate with action
- If possible, make the icons text, instead of icons?
"Toggle Line Numbers" draws way too much attention to itself; Especially when you have only 2 or 3 lines of code! Remove it entirely, or make it much smaller, or (whatever.)
Or use numbers=disable in the code regions. -- PaulBoddie 2009-12-09 16:07:42
- Bullet point items are spread too far apart. Less white space above and below them.
- If I could, I'd make the top bar half as tall as it is.
I'd try to find a way to either (A) eliminate the sidebar, or (B) make it editable. That way, regulars could maintain it. (ex: see the CommunityWiki SideBar, which is editable)
News / Changes
Discussion
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 2002-07-15 02: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 2002-07-15 02: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 2002-07-17 21:24:51
What kind of conversation are we talking about?
- Philosophy - I don't care where it goes (usenet, here, C2, elsewhere)
- "How does this piece work?" - it works great here
"How does this work" has been great. If you need me to back this up for you, I can back it up with many anecdotes; Most of the pages I write here have seen some related action. People tell me that they read and use (and correct) my pages, and it'd be sad to see that come to an end.
The only thing that annoys me are pages with questions for names. Instead, the page name should be the name of the piece, and then the question should appear on the page. That is, How can "normal" users report bugs in Python or the documentation? should be a page called PythonDocumentation, and then the question attached to that page.
-- LionKimbro 2005-09-15 22:31:31 [lwickjr: Sorry about that, Lion. :I ]
I think this Wiki would best serve as continuing from where standard Python documentation left off: showing examples of use, adding information about good packages not existing in the standard distribution, and talking about higher-level stuff like 'tips for parallel processing'. Examples are very important for newcomers, and hey, many people like to learn new things first from examples, and dive into reference when details become important (including me). As for discussing Python in general, I think c.l.p is invaluable and needs no replacement - so I guess I'm along the same lines as DanielDittmar and JürgenHermann. -- EdvardMajakari 2005-09-15 15:14:13