Joachim Werner wrote:
> I think that there ARE problems that can not be solved on a mailing list or
> in the fishbowl. One of them is doing a good general design (which we MIGHT
> need for some of the Zope 3.0 issues). I followed all the stuff about the
> CMF and formerly PTK and knew that it was
> When we first opened the fishbowl, it was with the certainty that we
> wouldn't get it right immediately. That's why we went with the intentially
> low-tech approach of a pile of Wikis. That first step actually worked
> pretty well for a while until we hit critical-Wiki-mass and there were
> sud
> IMO, Bugzilla won't fix these kinds of problems. I think the first step
> is to refine what we have while finding better ways to work together.
We definitely need a ZOPE-based approach. What I really don't get is this:
We all seem to be building Zope-based systems for communities, public
adm
Brian Lloyd wrote:
[snip]
> When we first opened the fishbowl, it was with the certainty that we
> wouldn't get it right immediately. That's why we went with the
> intentially low-tech approach of a pile of Wikis. That first step
> actually worked pretty well for a while until we hit
> cri
Magnus Heino wrote:
>>This is just a guess, but I suspect that this is a sort of unfortunate
>>cycle developing: people post proposals, get (understandably) dismayed
>>at the response time and end up not spending much time there, either
>>contributing or providing feedback.
>>
>
> Well, lets
> This is just a guess, but I suspect that this is a sort of unfortunate
> cycle developing: people post proposals, get (understandably) dismayed
> at the response time and end up not spending much time there, either
> contributing or providing feedback.
Well, lets move this discussion to a w
> > Well, that checkin was done to the cvs 4 days ago. If you haven't
> > read the one line at dev.zope.org about it being available in the
> > cvs, or if you dont subscribe to the cvs mailinglist, how are you
> > supposed to know that it exists? :-P
>
> Actually, he sent an email to zope-dev
Brian Lloyd wrote:
>
spot on ;-)
> - The fishbowl needs to be integrated with email in order to stay on
> people's radar.
Hallelujah!
> - There needs to be a way to "filter the firehose" so that people on
> all sides can focus on the things they care about.
Praise be!
> - The
> It's been mentioning that ZC doesn't pay attention, so proposals go in
> and nothing happens. Bugzilla won't fix that problem. I'll add that
> the community doesn't always pay good enough attention. Sure, people
> will say "when will we have versioning" or "when will we have web
> service
Magnus Heino wrote:
> Well, that checkin was done to the cvs 4 days ago. If you haven't
> read the one line at dev.zope.org about it being available in the
> cvs, or if you dont subscribe to the cvs mailinglist, how are you
> supposed to know that it exists? :-P
Actually, he sent an email to
> This isn't a good track record. Brian produced 35 pages worth of
> almost-flawless docs on web services to go with his code. But no
> comments. And he's doing this on his own time. So let's remember that
> this is a two-way street.
Well, that checkin was done to the cvs 4 days ago. If you
From: "Chris Withers" <[EMAIL PROTECTED]>
> 1. We can build something better. I can list requirements but that's not
relevent here. However, this will take serious
> effort (it's a hard problem...) and as we know from bitter experience,
things that need serious effort either don't
> happen, take
Chris Withers wrote:
> Paul Everitt wrote:
>
>>Moral: there's a difference between correct and right. While we might
>>have good reasons for inattention, it will surely lead to an
>>unsatisfying conclusion. Thus, ZC needs to be smaller part of a larger
>>Zope, IMO, and do this by spending more
Ken Manheimer <[EMAIL PROTECTED]> writes:
> WikiForNow project. As soon as i'm clear form a current project i
> *may* be able to concentrate on at least formulating a reasonable
> quick-and-dirty way to do notifications, and getting it done for the
Hey Ken - since you used the magic words quick-
14 matches
Mail list logo