On Sat, 31 Jul 2004, Chris Withers wrote:
Also, there's now documentation of what the various collector states
mean at:
http://dev.zope.org/CVS/CollectorStatuses
Some points of it are still up for discussion, so please join in at
[EMAIL PROTECTED] if you have a view!
I have a pretty
On Fri, 30 Jul 2004, Chris Withers wrote:
Apologies for the cross-posting, but I think this is relevent to all
these lists.
I think this is a valuable discussion. I don't think cross-posted
discussions work, though, so i'm replying in the various groups (except
zope-collector-monitor,
I noticed this when it went initially went by, but didn't have time to
follow up. The upshot is that there is absolutely no way *under the
current arrangement* that this is going to happen. I can see a way to
swing it, requiring earnest volunteer effort. Here are the details.
Being the
What proportion of the list traffic comes from valid members who are
posting from alternate accounts?
On Thu, 24 Jun 2004, Andrew Sawyers wrote:
Ken Manheimer wrote:
I noticed this when it went initially went by, but didn't have time to
follow up. The upshot is that there is absolutely no way
On Thu, 24 Jun 2004, Andrew Sawyers wrote:
Ken Manheimer wrote:
What proportion of the list traffic comes from valid members who are
posting from alternate accounts?
A huge percentage was - I don't know how much is making it through to the
lists though. I'm hearing a lot of complaints from
On Thu, 24 Jun 2004, Tim Peters wrote:
[Ken Manheimer]
I noticed this when it went initially went by, but didn't have time to
follow up. The upshot is that there is absolutely no way *under the
current arrangement* that this is going to happen. I can see a way to
swing it, requiring earnest
past because we neglected to
block them are not guaranteed to be preserved across the transfer.
I'll post a reminder soon before the outage time. Questions, concerns,
let me know.
Ken Manheimer
[EMAIL PROTECTED]
___
Zope-Dev maillist - [EMAIL
Reminder - CVS and SVN will be basically unavailable between 5:00 to 7:00
EST (21:00 to 23:00 GMT) this evening - in 1/2 hour from the time i send
this message.
On Thu, 17 Jun 2004, Ken Manheimer wrote:
As andrew mentioned last friday, we're migrating our public version-
control services
Yay!
On Fri, 18 Jun 2004, Tim Peters wrote:
[Ken Manheimer]
Most of the keys were not moved - i'm copied them, and you should now be
good to go.
Yay! Thank you, Ken. I'm back in. This is exactly what a programmer wants
to hear when he's struggling to make a critical bugfix release
- this was
a signficant bodily relocation of numerous bits, and it's possible i
missed something.
Ken Manheimer
[EMAIL PROTECTED]
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding
[This was mistaken for spam by our filter, and i was too quick to confirm
it as spam...]
-- Forwarded message --
Date: Fri, 28 May 2004 18:02:50 -0400
From: Paul Winkler [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Bug Day status report
Just a quick status report on today's
On Thu, 6 May 2004, Tim Peters wrote:
[Ken Manheimer]
All the actions are verbs, won't fix is not a verb. Can you
suggest a verb the more clearly indicates the result is won't
fix?
Sorry, I got lost on the first sentence: what difference does it make to
anything whether they're verbs
On Fri, 7 May 2004, Chris Withers wrote:
Ken Manheimer wrote:
All the actions are verbs, won't fix is not a verb.
Do we have to be this pedantic?
I wasn't meaning to be pedeantic. Sometimes inconsistencies in tense,
grammatical form, etc, can make a web form unbeably confusing - what's
On Fri, 7 May 2004, Casey Duncan wrote:
On Fri, 07 May 2004 09:56:45 +0100
Chris Withers [EMAIL PROTECTED] wrote:
Tim Peters wrote:
While that *should* be a good example, it isn't: I only knew that
bug existed because someone closed it on Bug Day (and I'm subscribed
to the
cvs.zope.org is wedged - you can connect to it (ping, web, ssh) but not
get any further. We've got a call in for attention, hopefully it'll be
back available soon...
Ken
[EMAIL PROTECTED]
___
Zope-Dev maillist - [EMAIL PROTECTED]
On Fri, 7 May 2004, Dieter Maurer wrote:
Ken Manheimer wrote at 2004-5-7 09:42 -0400:
...
It can sometimes pay off in workflow configuration to consistently pick
verbs that describe the actions in a generic way
You can view won't fix as a verb, like in
we won't fix this bug.
Well
On Thu, 6 May 2004, Chris Withers wrote:
Chris Withers wrote:
Yay! Does this mean we have a fully functional wont fix state now?
It does appear to, woohoo!
Can we change the action name from Refuse to Won't Fix? I took a while to
find it...
All the actions are verbs, won't fix is
On Thu, 6 May 2004, Andreas Jung wrote:
--On Donnerstag, 6. Mai 2004 12:37 Uhr +0100 Chris Withers
[EMAIL PROTECTED] wrote:
Ken Manheimer wrote:
Done. The piece you were missing is that the categories are actually
states in the collector_issue_workflow. I added a Wontfix state
On Thu, 6 May 2004, Lennart Regebro wrote:
From: Ken Manheimer [EMAIL PROTECTED]
All the actions are verbs, won't fix is not a verb. Can you suggest a
verb the more clearly indicates the result is won't fix?
Tough one...
Live with
Ignore
Keep this bug as is
Zenify
Featurize
On Thu, 6 May 2004, Leonardo Rochael Almeida wrote:
On Thu, 2004-05-06 at 11:56, Lennart Regebro wrote:
From: Ken Manheimer [EMAIL PROTECTED]
All the actions are verbs, won't fix is not a verb. Can you suggest a
verb the more clearly indicates the result is won't fix?
Tough one
On Thu, 6 May 2004, Lennart Regebro wrote:
Or maybe Deny as a action? Sounds less angry than reject and refuse.
What's being denied - the request to fix the bug, or the validity of the
bug report? Refuse suggests only that we are refusing to fix the bug,
there's no implication that the bug
Chris McDonough [EMAIL PROTECTED] wrote:
I think there needs to be another category named wontfix that
doesn't imply that it will ever be fixed like deferred seems to.
This category should also be selected in the default search settings.
Later, Chris McDonough wrote:
On Fri, 2004-04-30 at
Correction - use the HEAD version, so you get any fixes as they develop:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Misc/python-mode.el?rev=HEADcontent-type=text/vnd.viewcvs-markup
--
Ken
[EMAIL PROTECTED]
___
Zope-Dev
On Tue, 21 Jan 2003, Martijn Pieters wrote:
Due to the CVS vulnerabilities disclosed today, we have temporarily shut
down anonymous CVS access to cvs.zope.org through pserver. We'll reenable
this when we have upgraded CVS on the server.
People with write access through SSH and the web
I've just committed the change to the file that dictates checkin notice
routing so that Zope3 checkins are directed to the [EMAIL PROTECTED]
mailling list, instead of being included in the [EMAIL PROTECTED]
list. For those of you on the latter list interested in continuing to get
zope3
don't
know whether or not you've gotten acquainted with ZPT - the canonical
place is:
http://dev.zope.org/Wikis/DevSite/Projects/ZPT
Considering the approach of HyperTIES, you may find a lot to like
there.
--
Ken Manheimer
[EMAIL PROTECTED
We've changed the Zope issue collectors so that any authenticated
(logged-in) visitors can comment on issues, not just collector staff and
the requester.
This is all in the pursuit of quality information flow - some of you have
asked for the ability to include your illuminating experiences
I'm finding the wiki page notifications mechanism extremely helpful for
tracking wiki activity. While there's not much time available to tweak it
further for people's needs, i'd like to collect feedback about how it does
and doesn't serve other people's purposes, so that when we get around to
I'm going to be tinkering with the wikis on zope.org, to try installing my
adaptation (and extension) of simon michael's wiki page change
notifications to WikiForNow. I've exercised the changes as best i could
on a separate site, and don't expect any disruptions, but the unexpected
sometimes
I'm sorry, i'm unable to reprovoke the problem! Is there anything
unusual about how you were submitting? Did you try more than once, to
see if the problem is consistent?
On Fri, 07 Dec 2001 11:43:52 -0500, Chris Deckard wrote:
I tried submitting a new issue to the Zope collector at 11:42AM
On Fri, 7 Dec 2001, Christopher N. Deckard wrote:
I tried multiple times. I tried again this time, but deselected the
security related checkbox. It went in. The issue _is_ security
related, though not something that makes zope insecure.
Aha! My fault - it had neglected a setting in the
On Tue, 16 Oct 2001, Ken Manheimer wrote:
On Tue, 16 Oct 2001, Andy McKay wrote:
So what is going on with the Collector, its been what a month now?
See
http://dev.zope.org/Wikis/DevSite/Projects/CollectorReplacement/CurrentStatus
for current status.
In fact, i'm hoping to have
Shane Hathaway [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Personally, I think this really should be an integration issue instead of a
Zope issue: use a front-end proxy server (i.e. Squid) and set up ACLs to
prevent this...
This hasn't been fixed because it's not well
enable more help with the
increments.
I hope to have expore this some, internally, and have more to say
about it next week.
Ken Manheimer
[EMAIL PROTECTED]
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
as i could want. The addition of ZEO manages to significantly increase
that usefulness! The work we/pythonlabs (and andrew kuchling, etc) is
doing to enable use of it as an independent entity can only help improve
it's usefulness for everyone.
Ken Manheimer
[EMAIL PROTECTED
.) For those of us that read via digest mode, at least in some
interfaces, it makes increasingly hard to find messages. I'm taking the
liberty to include one example just to demonstrate the ridiculous length
this has gone.
Ken Manheimer
[EMAIL PROTECTED]
From: "Andy McKay" [EMAIL
On Wed, 10 Jan 2001, Morten W. Petersen wrote:
I do not think that "fuzzy logic" is strongly related to "regexp-like".
Anyway.
Fuzzy searching often means "finding matches with characters omitted,
replaced or inserted".
It seems I misunderstood the term fuzzy logic myself. Fuzzy
,
they'll refuse to run zope in droves - and well they ought to refuse.
Ken Manheimer
[EMAIL PROTECTED]
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists
e other access modes besides ENABLE and
DISABLE - eg, "ENABLE_METHODS", "ENABLE_ATTRIBUTES", etc...
Ken Manheimer
[EMAIL PROTECTED]
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cr
Recently (yesterday and today) we found a few files in the CVS repository
to be corrupt - different than the internal CVS files from which they were
mirrored. We've run a check to track down all such files, and have
corrected them all. However, we don't know at this point whether or not
the
(what got __of__'ed). If you're not sure the thing
is acquisition-wrapped in the first place, you'd probably want to check
for the existing of the 'aq_base' attribute before using it...
Ken Manheimer
[EMAIL PROTECTED]
___
Zope-Dev maillist - [EMAIL
On Wed, 6 Dec 2000, Chris Withers wrote:
Ken Manheimer wrote:
On Wed, 6 Dec 2000 [EMAIL PROTECTED] wrote:
Does anyone know how to disable acqusition ?
That is, with a simple method, and not disabling the Acqusition class,
something like self.aq_disabled('attribute') .
I
On Mon, 20 Nov 2000, Shane Hathaway wrote:
They are using an unreleased version of the Python Methods product.
AFAIK the only thing holding up the release of the new Python Methods is
the renaming.
(I believe the version in question is available from the public CVS
repository, as the
is problem - fortunately,
we now have some people with the time and leverage to shepherd, fix, etc
an upgrade to a newer version - will be happening soon. In the
meanwhile, sorry about the capture!)
Ken Manheimer
[EMAIL PROTECTED]
___
Zope-Dev maillist
a note here so
concerned parties (including me) know to check them out.
(This notification awkwardness is one of the things i think important
to address soon, hence part of the proposal...)
--
Ken Manheimer
[EMAIL PROTECTED]
___
Zope-Dev maillist
On Mon, 30 Oct 2000, Chris Withers wrote:
I went and had a look at dev.zope.org for the first time in a long time
and noticed that there's now _lots_ of proposals which no indication of
which ones are active/done/outdated/etc. I took off my cruft but I was
wondering what the process is for
Huh. We're looking for something neutral, to connote code that runs in
zope to do some business logic or similar effect. It should distinguish
the language used to express the logic - perl vs python vs xslt,
etc. I hate "script", but it occurs to me that the "-let" convention may
be useful:
On Fri, 29 Sep 2000, Rik Hoekstra wrote:
Karl Anderson wrote:
I read the 2-10 articles that I'm probably interested in, and miss the
95% which is almost always noise.
The question is why you'd want to receive all this if you don't have to
(as remarked above).
As I understood it, the
On Thu, 28 Sep 2000, Chris Withers wrote:
4.Some people think Wiki discussions are easily dispersed. Bad Wiki
discussions are, but discussion products are almost always dispersed by
nature. On many occasions I have (already) seen people summarize and
structure maillist discussions into a
On Thu, 28 Sep 2000, Chris Withers wrote:
Toby Dickenson wrote:
I dont see this as a problem: You only create a new list when the
traffic for that proposal gets too great for zope-dev. Threading is
good enough before that point.
Yes, but zope-dev has a relatively high traffic load...
On Thu, 28 Sep 2000, Chris Withers wrote:
These are the kinds of things i'm hoping to get at with WikiNG - a
smart content widget, with two essential features - good impedence
matching to authoring structured, linked content (structured text plus
wiki refs),
A lot of people I know
On Thu, 28 Sep 2000, Chris Withers wrote:
The only quoting you need to know is example::
The two colons after the word "example" indicate that this contained
block is all quoted.
How is a 'contained block' delimited?
As i did in my example, by indentation. (This is a primary
*This message was transferred with a trial version of CommuniGate(tm) Pro*
On Fri, 15 Sep 2000, Chris Withers wrote:
Ken Manheimer wrote:
Convenient for what? If you've ever tried to support a community
through a mailling list, you'll quickly notice that questions
*This message was transferred with a trial version of CommuniGate(tm) Pro*
[I'm running out of time here, so pardon the brief responses. Make no
mistake, though - i'm glad to be having this discussion! It's good to
be getting this input, seeing suggestions for other ways to look at
this
, *something*
is clearly needed - the wikis are just the best fit for part of the
job, right now.)
Ken Manheimer
[EMAIL PROTECTED]
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding
s a chance to happen, sigh.
Ken Manheimer
[EMAIL PROTECTED]
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zop
.
In the meanwhile, pdbtrack goes a long way towards doing what i want -
i hope it's useful to others. I've submitted an entry for vaults of
parnassus, not sure how long it takes to show. To repeat from above,
you can find it at:
http://www.zope.org/Wikis/klm/PDBTrack
Ken Manheimer
[EMAIL
57 matches
Mail list logo
