On Wed, Aug 3, 2016 at 12:38 PM Josh Elser <[email protected]> wrote:
> So would you think a new repo is appropriate for this? Would you want to > just use the same Git repo that the parent pom exists in (put two > separate maven projects inside)? > > As far as tech goes, I don't think this is super critical, but the > feelings aspect of it might require more immediate action. > > For now, the parent POM is in the fluo-parent branch of the main incubator-fluo git repo. I was going to create another branch for the resources. If we want to move it over to its own repo later, that's fine... it'll be very infrequently released, and trivially small, so it's probably not worth it. I got held up yesterday with another task, so I'll be pushing this resources object up today, and hopefully preparing a release candidate containing both it, and a new parent POM (they are independent, so it's basically 2 releases, for 1 vote). > Yeah, I'm not sure what to recommend for maintaining such an org. Let's > make sure to tread very carefully. Because the maintainers/creators of > these tools that were not brought to Apache are the PPMC now, this has > the potential to be misconstrued. > > Would it be out of line for me to suggest that for the projects > currently at github.com/fluo-io: > > * Specifically decree those with no interest to maintain as such > ^ I don't understand this sentence. We ended up renaming the organization so it's now astralway on GitHub. Today, we'll drop the redirect from astralway.github.io to fluo.apache.org. On Thursday, we'll drop the fluo.io domain pointer to astralway.github.io, and leave it pointing directly to fluo.apache.org, until it expires naturally (unless ASF really wants to take it, in which case, we can donate it to them to maintain; we don't have an interest in maintaining it). We've updated the description of any repos at astralway to refer to "Apache Fluo", if they are related to Fluo at all, and we'll update their READMEs soon. We'll also soon be removing any repos from astralway which have already migrated to fluo.apache.org (parent pom, resources, soon), and any repos which are staying have been renamed to avoid use of the term "fluo" in their names. So, we've taken significant action to cease using the Fluo trademark to identify anything other than the Apache Fluo project.
