incubator-bluesky-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "chen hecky" <>
Subject Re: Multiple concerns reviewing BlueSky podling website
Date Mon, 11 Aug 2008 13:44:18 GMT
Dear all,
       At first, I want to say that we can't upload the code to Apache now
because that the code is non-ASF. We now have to change the code which
includes GPL(  you
will see the problem of our code from  there, there are some lib of GPL
inluding in our code.). So we can't submit the code to Apache. We are
changing it to ASF, and we need help from you, community and Apache.
However, somebody want to see our code, so we have to setup a website(It's
not a Apache's) for downloading the code. The code are not ASF.

We are now trying our best to change the code from non-ASF to ASF, but we
are short of experience. I think the community is a place of communicating
and studing with others, so I hope get help from the community.

2008/8/9, Bertrand Delacretaz <>:
> On Thu, Jul 31, 2008 at 10:18 PM, Luciano Resende <>
> wrote:
> > While reviewing the BlueSky podling website, I noticed the following
> issues :
> >
> > - The BlueSky podling website have a download page, that is pointing
> > to non-apache bluesky released artifacts. I think this is at least
> > very confusing, as it can allude users to think this is a endorsed ASF
> > release. Is this OK ?....
> As others have indicated, the download links at
> point directly to non-ASF servers
> hosting, in some cases, GPL-licensed code (XPlayer), without any
> mention that said "releases" were made outside of the ASF.
> This is totally unacceptable.
> What would be ok, IMHO, is for the bluesky pages to point
> to a download page on another server, which lists the downloads and
> their licenses, and is clearly labelled as non-ASF.
> Bluesky mentors, is this being fixed?
> vaguely hints at
> "correcting things as quickly as possible", but it's been nine days
> since Luciano's message, and the download links are still up at
> -Bertrand

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