Hi,
so, we've been running with the steering group for a few weeks now and
I'm losing track of things, because we're letting the mailing list do
the job of an issue tracking system. (And the one document in SVN.)
We need to start using Launchpads tracking mechanisms for issues, filing
bugs or
Previously Christian Theune wrote:
We need to start using Launchpads tracking mechanisms for issues, filing
bugs or blueprints much earlier and much more often than having threads
just sit around in the zope-dev archive and *maybe* get picked up.
Can someone document how they work? I have
On Wed, 2009-03-25 at 09:01 +0100, Wichert Akkerman wrote:
Previously Christian Theune wrote:
We need to start using Launchpads tracking mechanisms for issues, filing
bugs or blueprints much earlier and much more often than having threads
just sit around in the zope-dev archive and *maybe*
Hi Christian
Betreff: [Zope-dev] Please use launchpad bugtracking/blueprints more
Hi,
so, we've been running with the steering group for a few
weeks now and I'm losing track of things, because we're
letting the mailing list do the job of an issue tracking
system. (And the one
Hey,
I'm okay with using launchpad more, though I do think we shouldn't
underestimate the power of a mailbox (I use gmane and a newsreader
myself :) and a document with decisions recorded. People can simply
bring up an issue again if it hasn't resolved itself, after all. I
really don't want
Hi Martijn,
On Wed, Mar 25, 2009 at 11:54 AM, Martijn Faassen
faas...@startifact.com wrote:
One question is what launchpad project we should use.
The current launchpad is for Zope 3. The steering group isn't about
Zope 3. It's about a whole bunch of libraries. Creating a separate
launchpad
On Mar 25, 2009, at 11:52 AM, Sidnei da Silva wrote:
Hi Martijn,
On Wed, Mar 25, 2009 at 11:54 AM, Martijn Faassen
faas...@startifact.com wrote:
One question is what launchpad project we should use.
The current launchpad is for Zope 3. The steering group isn't about
Zope 3. It's about a
On Wed, 2009-03-25 at 15:54 +0100, Martijn Faassen wrote:
Hey,
I'm okay with using launchpad more, though I do think we shouldn't
underestimate the power of a mailbox (I use gmane and a newsreader
myself :) and a document with decisions recorded. People can simply
bring up an issue again
On Wed, Mar 25, 2009 at 10:52 AM, Sidnei da Silva
sidnei.da.si...@canonical.com wrote:
Hi Martijn,
On Wed, Mar 25, 2009 at 11:54 AM, Martijn Faassen
faas...@startifact.com wrote:
One question is what launchpad project we should use.
The current launchpad is for Zope 3. The steering group
On Wed, Mar 25, 2009 at 1:49 PM, Baiju M mba...@zeomega.net wrote:
If possible, I think it is better to rename current 'zope3' as
'zope-framework',
then create another 'zope3' project. So that we will get all bugs
and blueprints as part of 'zope-framework'.
If 'zope-framework' is a project
On Wed, Mar 25, 2009 at 12:16 PM, Sidnei da Silva
sidnei.da.si...@canonical.com wrote:
On Wed, Mar 25, 2009 at 1:49 PM, Baiju M mba...@zeomega.net wrote:
If possible, I think it is better to rename current 'zope3' as
'zope-framework',
then create another 'zope3' project. So that we will get
Sidnei da Silva wrote:
Hi Martijn,
On Wed, Mar 25, 2009 at 11:54 AM, Martijn Faassen
faas...@startifact.com wrote:
One question is what launchpad project we should use.
The current launchpad is for Zope 3. The steering group isn't about
Zope 3. It's about a whole bunch of libraries.
Hey,
Baiju M wrote:
[snip]
If possible, I think it is better to rename current 'zope3' as
'zope-framework',
then create another 'zope3' project. So that we will get all bugs
and blueprints as part of 'zope-framework'.
I don't think that's correct at all, as Zope 3 isn't the Zope Framework.
On Wed, 2009-03-25 at 19:21 +0100, Martijn Faassen wrote:
Why would the steering group be a project as part of the Zope Framework?
The steering group isn't a project?
I'm all for setting something up, but I'm still not clear on what you'd
set up. A Zope Framework project group with what
Hey,
Baiju M wrote:
[snip]
But making 'zope3' as a part of 'zope-framework' is not not good idea.
Agreed. It's more likely the other way around, but I'm not going to
suggest any alterations to the Zope 3 project, as I'm not involved in
steering that. :)
Regards,
Martijn
On Mar 25, 2009, at 2:21 PM, Martijn Faassen wrote:
Sidnei da Silva wrote:
Hi Martijn,
On Wed, Mar 25, 2009 at 11:54 AM, Martijn Faassen
faas...@startifact.com wrote:
One question is what launchpad project we should use.
The current launchpad is for Zope 3. The steering group isn't
Sidnei da Silva wrote:
On Wed, Mar 25, 2009 at 1:49 PM, Baiju M mba...@zeomega.net wrote:
If possible, I think it is better to rename current 'zope3' as
'zope-framework',
then create another 'zope3' project. So that we will get all bugs
and blueprints as part of 'zope-framework'.
If
Good analysis Gary,
Though I would tend to see Zope3 as the umbrella and the various
projects (components) under it.
Is there REALLY too much bad press vs. good press about Zope3?
I don't think so. I think inventing a new name ala, Zope Umbrella is a
bad thing. Presenting Zope3 as the
18 matches
Mail list logo
