On Mon, Aug 8, 2016 at 9:00 PM John D. Ament <johndam...@apache.org> wrote:
> Christopher, > > I wanted to start a separate thread regarding some of your branding > comments below, to make sure we're all on the same page. > > On Mon, Aug 8, 2016 at 5:24 PM Christopher <ctubb...@apache.org> wrote: > > > IPMC, > > > > Please consider the following candidates for Fluo Parent POM 1-incubating > > and Fluo Build Resources 1.0.0-incubating. There are two artifacts, which > > we are releasing together. They do not contain Fluo itself, but are > > prerequisites for the Maven build of Fluo, which will be released via > Maven > > upon successful passing of this vote. Releasing these to Maven will bring > > us a step closer to preparing release candidates for Fluo itself. > > > > Passing PPMC release vote thread: > > > > > > > https://lists.apache.org/thread.html/7f9a1db3798ddc4123ba3c66c632cedde6272ba55f1132d556f24a67@%3Cdev.fluo.apache.org%3E > > > > Since the last attempted vote, we have taken significant steps to ensure > > that Apache retains exclusive use of the Fluo trademark. Historical > > releases still exist in Maven Central under the "io.fluo" groupId, but > the > > original fluo.io site has been redirected to fluo.apache.org (until its > > domain registration expires, at which point our plan is to let it lapse), > > > > This is all expected. We don't replace those releases, just need to make > sure they're pre-apache releases and regarded as such. Its really just a > call out to make sure its clear they're not vetted the way releases will be > vetted. > > We're on the same page here. I mentioned it because it was raised as a concern in the previous (canceled) vote thread, and I wanted to report back on our progress. :) > Regarding the domain name, an option there for you is to donate fluo.io to > the ASF as a part of joining the incubator. You may want to follow up with > infra directly, but typically they do maintain domain names for projects, > as long as its all hosted on our infrastructure. > > We (the current owners of fluo.io) discussed this off list. We'd be willing to donate it to ASF, but we don't feel we really need the domain, so there's not really a motivation on our end to burden the ASF with the cost of maintaining it. If the Foundation has an interest in managing the domain, we'd gladly transfer it, but it's not something we think will benefit the project. So, we thought it best to just let it lapse.
