On Mon, Aug 1, 2016 at 3:50 PM John D. Ament <johndam...@apache.org> wrote:
> On Mon, Aug 1, 2016 at 10:29 AM Keith Turner <ke...@deenlo.com> wrote: > > > On Mon, Aug 1, 2016 at 9:36 AM, John D. Ament <johndam...@apache.org> > > wrote: > > > I'm -1 until the website issues are resolved. > > > > > > - Make sure its clear that any existing releases are not apache > endorsed. > > > - Make sure the website points to resources contained within the ASF, > > e.g. > > > fluo-dev is a bit of an oddity same for zetten. > > > > Is there a policy on what ASF websites can link to? > > > > Yes. You have a branding issue. Fluo is a name owned by the ASF at this > point. I'm not sure that's been determined yet. Fluo has not yet completed the podling name search, and the name "Fluo" did not originate at Apache. It was in use at "fluo.io" first, and is in the process of being granted to the ASF during its incubation, while "fluo.io" transitions to what is essentially a "Fluo fan site" which provides third-party Fluo-related projects, which the Fluo community may find useful. I'd expect these branding issues to block graduation, but I wouldn't normally expect these sorts of issues to prevent incubating releases. There's got to be some precedent in Incubator for projects which have been transitioned like this? > Is there a reason why these resources (fluo dev and zetten) aren't > hosted within ASF managed git repos? > > Yes. They are not being granted to the ASF for various reasons. First, fluo-dev and zetten don't have "releases" in any ASF sense, and Zetten has dependencies whose licenses are not suitable for an ASF project by policy. The plan was that the originating community for Fluo would continue to operate Fluo.io as a third-party Fluo-related website hosting Fluo-related community projects in the same way that many other Apache projects have communities larger than what fits inside ASF.
