> Giacomo Pati wrote:
>
> Quoting Carsten Ziegeler <[EMAIL PROTECTED]>:
>
> > > Giacomo Pati wrote:
> > >
> > > Quoting Carsten Ziegeler <[EMAIL PROTECTED]>:
> > >
> > > > > Bruno Dumon wrote:
> > > > >
> > > > > > Wow,
> > > > > >
> > > > > > realy great work. It is very cool!
> > > > > >
> > > > > > Dumon, do you think we could add it to the cocoon2 project?
> > > > >
> > > > > My firstname is actually Bruno, so it should be "Mr. Dumon" or
> > > > > just "Bruno"
> > > > > :-)
> > > > >
> > > > Oh, sorry, Bruno, but my emailer displayes you as "Dumon Bruno".
> > Sorry!
> > > >
> > > >
> > > > > I don't have a problem with adding it to the cocoon2 project, but
> > I'm
> > > > not
> > > > > sure that it's a good idea to add GUI tools to the main cocoon
> > tree.
> > > > It
> > > > > seems better that such tools would have their own cvs. What do you
> > > > think?
> > > > >
> > > > Yes, this is right. GUI tools shoudn't be add directly to the main
> > tree
> > > > of cocoon2, but we could either make a subdirectory tools in the cvs
> > > > branch of cocoon2 or create a new cvs tree cocoon2-tools or
> > something
> > > > like that.
> > > >
> > > > Giacomo, what do you think what we can do?
> > >
> > > Hmm... I'm not sure but would prefer the separation into its own
> > > CVS repo. But
> > > also how concerned should such tools be to Cocoon 2? I might put
> > > in other tools
> > > that we've developed in conjuction with C2 but are usable in any
> > > other context
> > > (I'm talking about our xml-java toolkit).
> > >
> > Sounds interesting!
> >
> > We could set up a new cvs with a more open name, like xml-tools
> > and make there a subtree cocoon2.
>
> Ehm... this touches other areas in the XML project. I don't know
> if it will be a
> good idea to go through the approval process for it, but it will
> make sense,
> sure. Would you commit yourself to such a project? Any other
> developers?
Yes, of course, I would.
But if I understand you right, this would need some time to establish
the project, right?
Could we find a simple intermediate solution for the sitemap editor?
Perhaps adding it to cocoon2 in a separate directory and moving it
later?
Carstne
> This
> needs to be checked out because the PMC will not allow a new
> projects without a
> Apache member holding hands (that would probably be me) and some fund of
> developers pushing it forward.
>
> Dims, can you check that at the next PMC meeting?
>
> Giacomo
>
> >
> > Carsten
> >
> > > Giacomo
> > >
> > > >
> > > > Carsten
> > > >
> > > > > >
> > > > > > This tool would raise a lot of attraction to cocoon2 and the
> > > > > > whole cocoon2
> > > > > > community could help developing it.
> > > > > >
> > > > > >
> > > > > > Carsten
> > > > > >
> > > > > > Open Source Group sunShine - b:Integrated
> > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > > For additional commands, email: [EMAIL PROTECTED]
> > > > >
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, email: [EMAIL PROTECTED]
> > > >
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, email: [EMAIL PROTECTED]
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
