camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <christian.muel...@gmail.com>
Subject Re: [VOTE] Hide 'issues' tab in the Camel-Extra Google Project site
Date Wed, 26 Sep 2012 22:03:33 GMT
You can follow the discussion here [1].

[1]
http://mail-archives.apache.org/mod_mbox/community-dev/201209.mbox/%3CCALvzYd-h4Q=cTEgGqCNEEninhVose8uiGt2gTK22n9cMr_kVyg@mail.gmail.com%3E

Best,
Christian

On Wed, Sep 26, 2012 at 1:29 PM, James Carman <james@carmanconsulting.com>wrote:

> There is some discussion about this, though.  We aren't sure if it's
> the "hosting" or the "management" of the code that is the sticking
> point.  The hosting is definitely out, but merely using an external
> source control system and all the other infrastructure/management
> services here at the ASF might not work either.  Perhaps we need to
> talk to the board or legal-discuss?
>
> James
>
> On Wed, Sep 26, 2012 at 4:04 AM, Willem jiang <willem.jiang@gmail.com>
> wrote:
> > +1 if we can unify the wiki and issue for Camel and Camel-Extra.
> > The reason which we setup the Camel-Extra project is we cannot host the
> code of GPL license in Apache.
> > I don't think we cannot add the document or issues into Apache Camel due
> to that kind of issue.
> >
> > Any thoughts?
> >
> >
> > On Wednesday, September 26, 2012 at 3:19 PM, Henryk Konsek wrote:
> >
> >> > - Using Apache JIRA for Camel extra
> >>
> >>
> >>
> >> For now, I'll keep Camel Extra issues in Google Issue tracker. We
> >> shouldn't have Camel Extra issues spread around two places. However it
> >> will be nice if eventually we could use Jira for that.
> >>
> >> > (- Using Issue notifications on issues@camel.apache.org (mailto:
> issues@camel.apache.org) for issues raised
> >> > in Camel extra)
> >> > - Using Commit notifications on commits@camel.apache.org (mailto:
> commits@camel.apache.org) for changes in
> >> > Camel extra
> >>
> >>
> >>
> >> Yeah, since from the developer point of view it doesn't matter if
> >> somebody commits to Regular Camel or Extra Camel.
> >>
> >> > - Using the Apache Confluence WIKI for Camel extra components
> >>
> >> IMHO This is a must. We need uniform documentation format for all
> >> Camel stuff. I can't imagine redirecting end users to another
> >> documentation site.
> >>
> >> Camel by nature integrates technologies with various licenses. If we
> >> make non-Apache components a second class citizens, will be a
> >> second-class integration framework when it comes to non-Apache
> >> software. And Mule users will laugh at us :) .
> >>
> >> --
> >> Henryk Konsek
> >> http://henryk-konsek.blogspot.com
> >
> >
> >
>



--

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message