new PEP type: Process
Barry Warsaw and I, the PEP editors, have been discussing the need for a new PEP type lately. Martin von Löwis' PEP 347 was a prime example of a PEP that didn't fit into the existing Standards Track and Informational categories. We agreed upon a new "Process" PEP type. For more information, please see PEP 1 (http://www.python.org/peps/pep-0001.html) -- the type of which has also been changed to Process. Other good examples of Process PEPs are the release schedule PEPs, and I understand there may be a new one soon. (Please cc: any PEP-related mail to [EMAIL PROTECTED]) -- David Goodger <http://python.net/~goodger> signature.asc Description: OpenPGP digital signature -- http://mail.python.org/mailman/listinfo/python-list
Re: Pre-PEP Proposal: Codetags
Also, please update the Post-History header, adding the date(s) you posted the PEP to the mailing lists and/or newsgroups. And this time I'll remember to attach the file :-) -- David Goodger <http://python.net/~goodger> PEP: XXX Title: Codetags Version: $Revision$ Last-Modified: $Date$ Author: Micah Elliott Status: Draft Type: Informational Content-Type: text/x-rst Created: 27-Jun-2005 Post-History: XXX Abstract This informational PEP aims to provide guidelines for consistent use of Codetags, which would enable the construction of standard utilities to take advantage of the Codetag information, as well as making Python code more uniform across projects. Codetags also represent a very lightweight programming micro-paradigm and become useful for project managment, documentation, change tracking, and project health monitoring. This is submitted as a PEP because I feel its ideas are Pythonic, although the concepts are not unique to Python programming. Herein are the definition of Codetags, the philosophy behind them, a motivation for standardized conventions, a specification, a toolset description, and possible objections to the Codetag project/paradigm. This PEP is also living as a wiki_ for people to add comments. What Are Codetags? == Programmers widely use ad-hoc code comment markup conventions to serve as reminders of sections of code that need closer inspection or review. Examples of markup include ``FIXME``, ``TODO``, ``XXX``, ``BUG``, but there many more in wide use in existing software. Such markup will henceforth be referred to as *Codetags*. These Codetags may show up in application code, unit tests, scripts, general documentation, or wherever suitable. Philosophy == If you subscribe to most of these values, then Codetags will likely be useful for you. 1. As much information as possible should be contained **inside the source code** (application code or unit tests). This along with use of Codetags impedes duplication. Most documentation can be generated from that source code; e.g., by using help2man, man2html, docutils, epydoc/pydoc, ctdocgen, etc. 2. Information should be almost **never duplicated** -- it should be recorded in a single original format and all other locations should be automatically generated from the original, or simply be referenced. This is the *SPOT* rule. 3. Documentation that gets into customers' hands should be **auto-generated** from single sources into all other output formats. People want documentation in many forms. It is thus important to have a documentation system that can generate all of these. 4. Whenever information is subject to (and suited for) user feedback/input (e.g., FAQ, RFC, PEP), it should be contained in a **repository** (e.g. a wiki, usenet, or mailing lists). 5. There should not be a dedicated, disjoint **documentation team** for any non-huge project. The developers writing the code know the code best, and they should be the ones to describe it. 6. **Plain text** (with non-invasive markup) is the best form of writing anything. All other formats are to be generated from the plain text. 7. **Revision control** should be used for almost everything. And modifications should be checked in at least daily. Motivation == * **Various productivity tools can be built around Codetags.** See `Toolset Possibilities`_. * **Encourages consistency.** Historically, a subset of these Codetags has been used informally in the majority of source code in existence, whether in Python or in other languages. Tags have been used in an inconsistent manner with different spellings, semantics, format, and placement. For example, some programmers might include datestamps and/or user identifiers, limit to a single line or not, spell the Codetag differently than others, etc. * **Encourages adherence to SPOT/DRY principle.** E.g., generating a roadmap dynamically from Codetags instead of keeping TODOs in sync with separate roadmap document. * **Easy to remember.** All Codetags must be concise, intuitive, and semantically non-overlapping with others. The format must also be simple. * **Use not required/imposed.** If you don't use Codetags already, there's no obligation to start, and no risk of affecting code (but see Objections_). A small subset can be adopted and the Tools_ will still be useful (a few Codetags have probably already been adopted on an ad-hoc basis anyway). Also it is very easy to identify and remove if a Codetag is no longer deemed useful. Then it is effectively *committed* and recorded by revision control simply by checking in. * **Gives a global view of code.** Tools can be used to generate documentation and reports. * **A logical location for capturing CRCs/Stories/Requirements.** The XP community often does not electronically capture Stories, but Codet
PyCon TX 2006: Early-bird registration ends Dec. 31!
Early bird registration for PyCon TX 2006 ends on December 31st, so there are only a few days LEFT. To register, please visit: http://us.pycon.org/TX2006/Registration You can still register after Dec. 31st, but the cost will go up by US$65 (US$25 for students). This year PyCon will feature a day of tutorials before the three days of regular presentations. Course outlines for all the tutorials have been posted; see http://wiki.python.org/moin/PyCon2006/Tutorials All of the PyCon tutorials are still open for new registrations, but space is limited, and we suspect they'll all be filled up by the time early-bird registration closes. Don't forget to book your hotel room, too. PyCon TX 2006 is being held at a Dallas/Addison hotel, and we have negotiated a special low rate: http://us.pycon.org/Addison/Hotels We hope to see you in Texas! -- David Goodger (on behalf of A.M. Kuchling, Chair, PyCon 2006) signature.asc Description: OpenPGP digital signature -- http://mail.python.org/mailman/listinfo/python-list
Re: Python to use a non open source bug tracker?
Giovanni Bajo wrote: > The current request is: "please, readers of python-dev, setup a team of 6-10 > people to handle roundup or we'll go to a non-free software for bug > tracking". This is something which I cannot cope with, and I'm *speaking* > up against. Were the request lowered to something more reasonable, I'd be > willing to *act*. No, the announcement stated the situation in a very different way. Asking for a group of maintainers to commit to an essential piece of infrastructure is perfectly reasonable. Brett didn't ask for 6-10 full time developer/sysadmins. He asked for typical commitment, which is up to a few hours per week. The initial work will probably be significant, but will undoubtedly taper off over time. Go back to the original announcement: """ After evaluating the trackers on several points (issue creation, querying, etc.), we reached a tie between JIRA and Roundup in terms of pure tracker features. """ JIRA gets a leg up because of the hosting and administration also being offered. But... """ If enough people step forward we will notify python-dev that Roundup should be considered the recommendation of the committee and graciously turn down Atlassian's offer. """ That is a perfectly reasonable offer. Put up or shut up. > And besides the only thing I'm really sniping the PSF against is about > *ever* having thought of non-FLOSS software. This is something I *really* do > not accept. ... I just > disagree with their initial requirements (and I have not raised this point > before because, believe me if you can, I really thought it was obvious and > implicit). That just shows that you were being naïve. The initial requirements were published openly and clearly. > I do respect the fact > that the PSF committee did a thorough and correct evaluation: Yes, they did, and you should be thanking them instead of complaining. If you feel so strongly, please volunteer. -- David Goodger -- http://mail.python.org/mailman/listinfo/python-list
Re: Python to use a non open source bug tracker?
Giovanni Bajo wrote: > So we have a problem between the PSF and the "PSF infrastructure committee", > since the latter did not put "being written in Python" has a requirement for > the tracker. There was no problem. The committee had their mandate, to find the best candidate for a tracker for Python. The quality of the tracker was felt to be more important than the language it was written in or the license it uses. The committee members worked hard to fulfill their mandate, and they deserve the gratitude and appreciation of all of us. I know for a fact (having raised this very issue with the committee myself) that they took "written in Python" into consideration. Not as a requirement though -- the requirement was simply to decide on the best tracker, regardless of language or license. Look at the results again. Jira and RoundUp tied for functionality, but Jira has a hosting/admin offer behind it. That's huge. But rather than declaring Jira the outright winner, which they could have done, the committee has allowed the community to decide the matter. If enough admins come forward, RoundUp will win. I read that as a big push for "written in Python". David Goodger -- http://mail.python.org/mailman/listinfo/python-list
Re: Python to use a non open source bug tracker?
Giovanni Bajo wrote: > You're cherry picking your quotes: > > """ > In order for Roundup to be considered equivalent in terms of an overall > tracker package there needs to be a sufficient number of volunteer admins > (roughly 6 - 10 people) who can help set up and maintain the Roundup > installation. > """ > > This is *NOT* a perfectly reasonable offer, Yes it is: Jira = 1st place functionality + hosting/admin provided RoundUp = 1st place functionality Jira wins. But the offer is to allow the community to make up the difference. If anything, that's unfair to Jira. So why are you complaining? > because you do not see 6-10 people > stepping up at the same time for almost *anything* in the open source world. Then that's a failure of the open source world. But I *do* see it happening right now. People *are* stepping up. David Goodger -- http://mail.python.org/mailman/listinfo/python-list
PyCon Organizers' Meeting
I'd like to hold the inaugural organizers' meeting for PyCon 2008 on Tuesday, July 17, at 2PM Eastern/1PM Central/11AM Pacific (6PM UTC). Further meetings will be every other week. The meetings will be held via Google Talk/Jabber (group chat). We'll use the 'pycon' room on conference.jabber.org. Agenda: * Staff roles * Keynote speakers * PyCon tech * Chicago visit Please send any further agenda items to me, or edit the wiki page: http://wiki.python.org/moin/PyCon2008/OrganizersMeetings See you there! David Goodger PyCon 2008 Chai signature.asc Description: OpenPGP digital signature -- http://mail.python.org/mailman/listinfo/python-list
Next PyCon Organizers' Meeting Tuesday, 11 September
Next meeting: Tuesday, September 11, at 18:00 UTC (2PM Eastern, 1PM Central, 12PM Mountain, 11AM Pacific). I'll post some agenda items, but feel free to add more: http://wiki.python.org/moin/PyCon2008/OrganizersMeetings Connection details: http://wiki.python.org/moin/PyCon2008/OrganizersMeetingsConnectionDetails PyCon is a community conference. Please join in and help out! David Goodger PyCon 2008 Chair signature.asc Description: OpenPGP digital signature -- http://mail.python.org/mailman/listinfo/python-list
PyCon 2008: Call for Talk & Tutorial Proposals
Proposals for PyCon 2008 talks & tutorials are now being accepted. The deadline for proposals is November 16. PyCon 2008 will be held in Chicago, Illinois, USA, from March 13-20. http://us.pycon.org/2008/ Tutorial Day: Half-Day Tutorials Do you enjoy teaching classes or tutorials? Are you good at it? PyCon is looking for proposals for tutorials. The PyCon Tutorial Day will be March 13, 2008 (Thursday). There will be morning and afternoon tutorial sessions (3 hours each, plus a 30-minute break); presenters may request two sessions in order to make up a full day. Tutorials may be on any topic, but obviously should be instructional in nature. Full details and instructions here: http://us.pycon.org/2008/tutorials/proposals/ Conference Days: Scheduled Talks Want to share your experience and expertise? PyCon is looking for proposals to fill the formal presentation tracks. The PyCon Conference Days will be March 14-16, 2008 (Friday-Sunday). Previous PyCon conferences have had a broad range of presentations, ranging from reports on academic and commercial projects to tutorials and case studies. We hope to continue that tradition this year. As long as the presentation is interesting and potentially useful to the Python community, it will be considered for inclusion in the program. We're especially interested in short tutorial presentations that will teach conference-goers something new and useful. Can you show attendees how to: use a module? explore a Python language feature? package an application? Full details and instructions here: http://us.pycon.org/2008/conference/proposals/ Development Sprints === Four days of development sprints will follow the conference days, March 17-20 (Monday-Thursday). Start thinking about sprints you'd like to lead or join. We'll have an announcement about these soon! http://us.pycon.org/2008/sprints/ Lightning Talks & Open Space If you don't want to make a formal presentation, you can still bring your new project or idea to PyCon. There will be several sessions of Lightning Talks (five minute mini-talks, scheduled at the conference). http://us.pycon.org/2008/conference/lightning There will also be several Open Space rooms for informal and spur-of-the-moment presentations. Open Space slots are allocated during PyCon on a first-come first-served basis. These slots can be used for presentations, round table discussions, hands-on tutorials, follow-up discussions after scheduled talks, or anything else you wish to present. http://us.pycon.org/2008/conference/openspace/ Help Out! = PyCon 2008 planning is in full swing, but we can still use more help, *your* help! http://us.pycon.org/2008/helping/ -- http://mail.python.org/mailman/listinfo/python-list
Only one week left for PyCon proposals!
There is only one week left for PyCon tutorial & scheduled talk proposals. If you've been thinking about making a proposal, now's the time! Tutorial details and instructions here: http://us.pycon.org/2008/tutorials/proposals/ Scheduled talk details and instructions here: http://us.pycon.org/2008/conference/proposals/ The deadline is Friday, November 16. Don't put it off any longer! PyCon 2008: http://us.pycon.org -- David Goodger PyCon 2008 Chair signature.asc Description: OpenPGP digital signature -- http://mail.python.org/mailman/listinfo/python-list
Last chance for PyCon talk & tutorial proposals!
Thanks to all the proposal authors so far, we have received lots of proposals for PyCon talks & tutorials. But we'd like to have even more. Alas, the proposal submission deadline should have been set after a weekend, not before. So we have decided to extend the proposal submission deadline to Monday, November 19 at midnight (Chicago time). This gives you a *whole extra weekend* to write up your talk and tutorial ideas! If you've been procrastinating, stop! Get started on a proposal instead! See the call for conference talk proposals: http://us.pycon.org/2008/conference/proposals/ Topic ideas: http://wiki.python.org/moin/Talk_Subjects http://wiki.python.org/moin/PyCon2007/Feedback#head-e2dca74d1492e49fae11550e6cbc40fa18a17f40 See the call for tutorial proposals http://us.pycon.org/2008/tutorials/proposals/ Topic ideas from the PyCon 2007 feedback: http://wiki.python.org/moin/PyCon2007/Feedback/TutorialIdeas I hope to see (and hear) you at PyCon 2008! http://us.pycon.org -- David Goodger, PyCon 2008 Chair signature.asc Description: OpenPGP digital signature -- http://mail.python.org/mailman/listinfo/python-list
PyCon 2008 Registration Open!
I am pleased to announce that PyCon 2008 registration is now open! http://us.pycon.org/2008/registration/ Early-bird registration is open until February 20, so there's one month to register at the low rates. Regular on-line registration will be available from February 21 through March 7. PyCon 2008 will be held from March 13 through 20 in Chicago: * Tutorials: Thursday, March 13 * Conference: Friday, March 14, through Sunday, March 16 * Sprints: Monday, March 17 through Thursday, March 20 Register early, especially if you'd like to attend a tutorial or three, as tutorials fill up early. And yes, you heard that correctly -- this year, we have three tutorial sessions: morning, afternoon, and evening. There are 29 great tutorials to choose from. More about the tutorials soon, but for now, you can check out the descriptions yourself here: http://us.pycon.org/2008/tutorials/schedule/ The talk schedule is also up (in a preliminary form), although some changes are expected: http://us.pycon.org/2008/conference/schedule/ Hotel reservations are also open: https://www.cteusa.com/pycon1/ The rate is $99/night plus tax ($112/night net), also until February 20. More hotel information is here: http://us.pycon.org/2008/registration/hotel/ See the PyCon web site for complete details: http://us.pycon.org/2008/ Thanks to the PyCon organizers for developing the software, providing the website content, testing & debugging. PyCon is a community conference, of, by, and for the Python community. There is still much to do, and you can help! http://us.pycon.org/2008/helping/ See you in Chicago! David Goodger PyCon 2008 Chair signature.asc Description: OpenPGP digital signature -- http://mail.python.org/mailman/listinfo/python-list
PyCon: deadline for hotel reservations and early-bird registration coming soon!
If you haven't registered for PyCon yet, now is the time! The early-bird registration deadline is February 20, one week away. After that, the price for registration will be going up. http://us.pycon.org/2008/registration/ The deadline for hotel reservations at the conference rate is also February 20. Act now, because the regular rate is considerably higher! http://us.pycon.org/2008/registration/hotel/ A reminder to tutorial and talk speakers: you are responsible for your own registration and hotel reservations. So don't delay! PyCon 2008: March 14-16, 2008 (& tutorials March 13, & sprints March 17-20) David Goodger PyCon 2008 Chair signature.asc Description: OpenPGP digital signature -- http://mail.python.org/mailman/listinfo/python-list
