The python-dev HOWTO has now been cut up and rearranged into a set of Web pages at http://www.python.org/dev/ . Please suggest additional things that should be explained in these pages, or that should be linked to. Comments on the accuracy of the "Python Culture" page are also welcome; it might be missing some important points, or it might describe my idealization of how we try to behave. :) And if anyone has suggestions on how make the pages more likely to attract new developers to Python, I'm all ears! --amk (www.amk.ca) It's more serious than death, Mr Stevenson. He's changing form. -- The Doctor, in "The Seeds of Doom"
The python-dev HOWTO has now been cut up and rearranged into a set of Web pages at http://www.python.org/dev/ .
Thanks, Andrew!
Please suggest additional things that should be explained in these pages, or that should be linked to. Comments on the accuracy of the "Python Culture" page are also welcome; it might be missing some important points, or it might describe my idealization of how we try to behave. :)
And if anyone has suggestions on how make the pages more likely to attract new developers to Python, I'm all ears!
Well, linking to it from the developer info on the home page would help... I wonder if the *only* developer link on the home page should go to /dev/. That means that all the info currently at the bottom of the home page (under the heading "For developers") should be folded into the /dev/ index page. The "Python at SF" link in the left sidebar should probably point to the /dev/ section. I also wonder of we can replace one of the 8 items in the page-top menu with a developers link? But which one? --Guido van Rossum (home page: http://www.python.org/~guido/)
Andrew Kuchling wrote:
The python-dev HOWTO has now been cut up and rearranged into a set of Web pages at http://www.python.org/dev/ .
Nice.
Please suggest additional things that should be explained in these pages, or that should be linked to.
You should stress the importance of running the test suite before committing any changes to CVS. I wonder sometimes if we could use a tool like Aegis to enforce this rule. Neil
[Neil Schemenauer]
You should stress the importance of running the test suite before committing any changes to CVS. I wonder sometimes if we could use a tool like Aegis to enforce this rule.
Most days it seems we already have a slightly-delayed tool for this, called "Tim" <wink>. Unfortunately, it doesn't catch non-Windows glitches. The new pages are great, Andrew! My only gripe: bulleted lists have no vertical whitespace between bullet points, when viewed under (at least) IE 6. This makes them hard to read, and even misleading when a bullet item contains more than one paragraph. o This is the first bullet point, and yadda yadda yadda. o This is the second bullet point, and so likewise. o This is the third bullet point. This is not the fourth bullet point, it's another paragraph in the third. o But this is the fourth bullet point. I guess the prime advantage of style sheets is that they're an easy way to screw up a whole site at once <wink>.
participants (5)
-
Andrew Kuchling -
barry＠zope.com -
Guido van Rossum -
Neil Schemenauer -
Tim Peters