Howdy.. Recently, I worked with Tres to remove the funky old "$Id$" type lines from all the files in ZTK packages, and while touching every file in every package, roughly, I came up with some other thoughts on how to improve consistency, which are detailed in this launchpad bug: https://bugs.launchpad.net/zopetoolkit-project/+bug/588782 Today, I started by changing the setup.py for zope.browsermenu based on how zope.component is setup, and a Bzr branch is attached to this issue. As mentioned in this issue, I also noted that many packages have no categorization data. I originally, in followup to another issue where I changed all the zope3-dev emails to zope-dev, and started futzing with the categorization to change 'zope3' tag to 'zope', and remove the Framework :: Zope3 bit, which was discouraged by someone over IRC because other people's metadata is linked to this, so I abandoned those. I feel it's notable that this bug's original title focused on the general idea that package metadatas are inconsistent, and if there isn't already a policy, we should set some forth. I notice some packages even note specific versions of Python, esp. zope.interface, maybe we should work on that in others. I'm sure people are like, "Oh, why so focused on all this fritzy stuff?", but the thing is, touching each file in each package really helps me to gain familiarity with a system I've always wanted to be more of a contributor to, and am proud to have begun down the road for. As the Framework :: thing, does anyone object to two additions on top of Zope3: Framework :: Zope Toolkit Framework :: BlueBream I know the bluebream thing is wierd, I know there has been some tumult in the community lately, I don't know where all that really lies, or how it divides folks. I do know that the BB brand has helped to have the first ever message I've seen asking basically, by someone who decided for sure they want to use Python, and worked a bit with Django which is very tasty the first day, apparently, and then found they wanted to use Zope techs. Anyway, just touching base. What should the metadata reflect, etc.. Most of all, does anyone mind my making sure that all packages pull in their doctests, if available, to display on the front page of pypi. Also, have we considered a zope.org site which just pulls all these doctests together, because obviously as PyPI is often down, and that needs to be fixed, we can also reduce our reliance upon it. If I want to know how a zope.* package works, i can always google its' name and get a PyPI page. Howabout we try to supercede that with a documentation-only URL that links to a separate download location. And not count the visits against a Postgres database. Best! Happy Zoping! Justin Alan Ryan [ bitmonk ]
Couple of follow-up notes.. On Thu, Jun 17, 2010 at 5:43 PM, Justin Ryan <justin.ryan@reliefgarden.org> wrote:
Howdy..
Recently, I worked with Tres to remove the funky old "$Id$" type lines from all the files in ZTK packages, and while touching every file in every package, roughly, I came up with some other thoughts on how to improve consistency, which are detailed in this launchpad bug:
https://bugs.launchpad.net/zopetoolkit-project/+bug/588782
Today, I started by changing the setup.py for zope.browsermenu based on how zope.component is setup, and a Bzr branch is attached to this issue.
This was really sparked by, som
As mentioned in this issue, I also noted that many packages have no categorization data.
I originally, in followup to another issue where I changed all the zope3-dev emails to zope-dev, and started futzing with the categorization to change 'zope3' tag to 'zope', and remove the Framework :: Zope3 bit, which was discouraged by someone over IRC because other people's metadata is linked to this, so I abandoned those.
I feel it's notable that this bug's original title focused on the general idea that package metadatas are inconsistent, and if there isn't already a policy, we should set some forth. I notice some packages even note specific versions of Python, esp. zope.interface, maybe we should work on that in others.
I'm sure people are like, "Oh, why so focused on all this fritzy stuff?", but the thing is, touching each file in each package really helps me to gain familiarity with a system I've always wanted to be more of a contributor to, and am proud to have begun down the road for.
As the Framework :: thing, does anyone object to two additions on top of Zope3:
Framework :: Zope Toolkit Framework :: BlueBream
Obviously this would need some coordination with catalog-sig, and I redacted my willingness to work with them this week after in the course of 20 minutes or so of volunteering to help with PyPI issues I was accused of trying to grift the PSF for funds and ten other things because people can't count the number of ">" before each line of a quoted message.
I know the bluebream thing is wierd, I know there has been some tumult in the community lately, I don't know where all that really lies, or how it divides folks. I do know that the BB brand has helped to have the first ever message I've seen asking basically, by someone who decided for sure they want to use Python, and worked a bit with Django which is very tasty the first day, apparently, and then found they wanted to use Zope techs.
Anyway, just touching base. What should the metadata reflect, etc..
Most of all, does anyone mind my making sure that all packages pull in their doctests, if available, to display on the front page of pypi.
And of course, I know how Tres feels about doctests. I agree, they aren't the best docs (many packages like zope.annotation don't show how to register zcml, just how to test the code), or the best tests, having one that is both is better than neither of each, and even weak doctests in pypi are often informative..
Also, have we considered a zope.org site which just pulls all these doctests together, because obviously as PyPI is often down, and that needs to be fixed, we can also reduce our reliance upon it.
If I want to know how a zope.* package works, i can always google its' name and get a PyPI page. Howabout we try to supercede that with a documentation-only URL that links to a separate download location. And not count the visits against a Postgres database.
Best! Happy Zoping!
Justin Alan Ryan [ bitmonk ]
Justin Ryan wrote:
As the Framework :: thing, does anyone object to two additions on top of Zope3:
Framework :: Zope Toolkit Framework :: BlueBream
Obviously this would need some coordination with catalog-sig, and I redacted my willingness to work with them this week after in the course of 20 minutes or so of volunteering to help with PyPI issues I was accused of trying to grift the PSF for funds and ten other things because people can't count the number of ">" before each line of a quoted message.
Just for reference: http://mail.python.org/pipermail/catalog-sig/2010-June/002860.html http://mail.python.org/pipermail/catalog-sig/2010-June/002892.html cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
Just for reference:
http://mail.python.org/pipermail/catalog-sig/2010-June/002860.html
http://mail.python.org/pipermail/catalog-sig/2010-June/002892.html
Thanks, Chris.. Nice of you to point out that I joined catalog-sig to see what the community was like, for the purpose of possibly promoting a new Framework :: designation for ZTK, and encountered the equivalent of walking into a bar fight and being stabbed with a glass bottle after suggesting that perhaps I could help all parties reach their goals. While you and Guido took offense to my post, far more silent participants of the list expressed agreeance. And I want nothing more than to get far, far away from conversations like this. So, as I'm offering to bring consistency to the setup.py files of IIRC ~67 packages, perhaps you'd be interested in proposing to catalog-sig that there be a Framework :: Zope Toolkit, or Framework :: ZTK. I suspect we should discuss on this list what that may be. Peace, Love, and Components, Justin Alan Ryan [ bitmonk ]
On Mon, Jun 21, 2010 at 6:23 PM, Justin Ryan <justin.ryan@reliefgarden.org> wrote:
Just for reference:
http://mail.python.org/pipermail/catalog-sig/2010-June/002860.html
http://mail.python.org/pipermail/catalog-sig/2010-June/002892.html
Thanks, Chris..
Nice of you to point out that I joined catalog-sig to see what the community was like, for the purpose of possibly promoting a new Framework :: designation for ZTK, and encountered the equivalent of walking into a bar fight and being stabbed with a glass bottle after suggesting that perhaps I could help all parties reach their goals.
Just to be clear, during the two weeks I was on catalog-sig, the only thread active was entitled something like: PyPI Down Again I left in disgust with someone asking something like "exactly what problem I wanted to help solve" Human Communication can only be so poor. If I'm from Texas, and you're from Europe, and I don't feel you can communicate, something is wrong with your brain.
While you and Guido took offense to my post, far more silent participants of the list expressed agreeance.
And I want nothing more than to get far, far away from conversations like this.
So, as I'm offering to bring consistency to the setup.py files of IIRC ~67 packages, perhaps you'd be interested in proposing to catalog-sig that there be a Framework :: Zope Toolkit, or Framework :: ZTK.
I suspect we should discuss on this list what that may be.
Peace, Love, and Components,
Justin Alan Ryan [ bitmonk ]
Human Communication can only be so poor. If I'm from Texas, and you're from Europe, and I don't feel you can communicate, something is wrong with your brain.
FWIW, that is a derogatory statement from a native texan. Statistically, we're stupid. But if a thread has gone on for weeks with only one subject, about a website being down, and the website is down while the person offering to help is being flamed by tens of people not interested in fixing the website, that's just absurd. In fact, it could probably be some kind of Monty Python joke. I'm too Texan to remember them all.
participants (2)
-
Chris Withers -
Justin Ryan