Thanks Ted. FYI, "Apache Trafodion" is part of the logo. I'm not putting the project through another round of voting on that one. :)
It strikes me that the left (or right) part of a project's web site menu could contain "Apache Incubator Project" as a standard. Such an approach wouldn't impede website design much while making the status of the project very clear. Honestly, I don't want to spend a lot more time of the website itself given that the technology is quite limited. (The project wanted a Maven-based website so I did what I could.) It would have been another matter if I could have use Wordpress with a good theme or something like that. :) Gunnar On Fri, Jul 1, 2016 at 9:16 PM, Ted Dunning <ted.dunn...@gmail.com> wrote: > Gunnar, > > Think that page looks pretty good (not referring to the standards, just > looking at the page). > > Having the word incubator near the logo might be slightly nicer, but that > isn't such a big deal since you have that on the project name just above > the logo and you have the Incubator logo in the banner as well. > > You guys nailed the spirit part of the policy. > > As a design note, you have the project name in the upper left hand corner > twice. You might be able to merge those (preserving the "Incubating", of > course) to save some real estate and make your image case more forcefully. > > > > On Fri, Jul 1, 2016 at 3:44 PM, Gunnar Tapper <tapper.gun...@gmail.com> > wrote: > > > Let me offer up a concrete example since I struggle with the issue of > > branding: http://trafodion.apache.org/documentation.html > > > > I chose the following approach based on input from out mentor Stack: > > > > - Added (incubator) to the menu bar > > - Added the incubator logo on the top of the page > > - Placed the disclaimer on the bottom of the page > > > > I did you placeholders in the documentation for things like mailing list, > > project names, and cross-documentation links to make renaming a matter of > > updating pom.xml files and rebuilding. > > > > However, I did NOT put incubator disclaimers or even an incubator status > in > > the documentation simply because it felt like over communication of > > incubator status. As you'll see, the Apache license language is included > in > > PDF and web-book formats but not the incubator disclaimer. I don't know > > whether I made the right choice. If I didn't, then I'd think that the > > guidance should state that web pages and documentation should include > BOTH > > the ASL text and the incubator-disclaimer text. > > > > I hope this helps with the discussion. > > > > Thanks, > > > > Gunnar > > > > On Fri, Jul 1, 2016 at 1:31 PM, Mike Jumper <mike.jum...@guac-dev.org> > > wrote: > > > > > On Fri, Jul 1, 2016 at 12:05 PM, Marvin Humphrey < > mar...@rectangular.com > > > > > > wrote: > > > > > > > On Fri, Jul 1, 2016 at 9:35 AM, Greg Chase <g...@gregchase.com> > wrote: > > > > > > > > > The branding guidelines do not address feedback such as "logo in > > > footer" > > > > or > > > > > "disclaimer is buried deep or below the fold". > > > > > > > > Incubation disclaimers are intended to be substantive. They are not > > CYA > > > > legal > > > > boilerplate that can be are buried in fine print. The intent is to > > > > communicate > > > > (effectively!) to consumers that a project is incubating. That way, > > > people > > > > will know that certain caveats apply: > > > > > > > > Apache Foo is an effort undergoing incubation at The Apache > > Software > > > > Foundation (ASF), sponsored by the Apache Incubator. Incubation > is > > > > required of all newly accepted projects until a further review > > > > indicates > > > > that the infrastructure, communications, and decision making > > process > > > > have > > > > stabilized in a manner consistent with other successful ASF > > projects. > > > > While incubation status is not necessarily a reflection of the > > > > completeness or stability of the code, it does indicate that the > > > > project > > > > has yet to be fully endorsed by the ASF. > > > > > > > > What would be best is if podlings just understood that intent, and as > > and > > > > took > > > > it upon themselves to ensure that their incubating status was > > > communicated > > > > effectively -- in websites, in release announcements, etc. > > > > > > > > > > > Can you cite, as an example, an incubating project's website where you > > > would consider the incubating status effectively communicated, and the > > > disclaimer not buried? > > > > > > > > > > > -- > > Thanks, > > > > Gunnar > > *If you think you can you can, if you think you can't you're right.* > > > -- Thanks, Gunnar *If you think you can you can, if you think you can't you're right.*
