Since we've been discussing YTEPs lately, I thought I would forward this, which covers how IPython handles their similar items. We could discuss them in issues rather than pull requests, which would perhaps also be quite a nice fit for them.
---------- Forwarded message ---------- From: Brian Granger firstname.lastname@example.org Date: Wed, May 1, 2013 at 7:12 PM Subject: [IPython-dev] A few notes on IPEPs To: IPython Development list email@example.com
Our usage of IPEPs is going really well - they are quickly becoming a useful way of working out and documenting the design of larger features. I have updated the main IPEP page with improved guidelines:
Some of the main points:
* Let's open an issue for each IPEP and use that to track the discussion and implementation. * Let's add a table to the top of each IPEP that tracks its basic information and status.
I wanted to encourage everyone to revisit the IPEPs you have authored and check on the following:
* Make sure the IPEP is updated to reflect the current state of the discussion and implementation. * Add the table at the top of the IPEP with the basic information (see the index page for an example) * Make sure the table has an updated status - we might eventually want to add the status to the main IPEP index so we can see the status of each of them easily.
-- Brian E. Granger Cal Poly State University, San Luis Obispo firstname.lastname@example.org and email@example.com _______________________________________________ IPython-dev mailing list IPythonfirstname.lastname@example.org http://mail.scipy.org/mailman/listinfo/ipython-dev