incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gunnar Tapper <>
Subject Re: Notes on branding
Date Sat, 02 Jul 2016 02:10:00 GMT
On Fri, Jul 1, 2016 at 5:39 PM, John D. Ament <> wrote:

> Some notes, but again only my opinion.
> <3
> My only nit pick with the disclaimer placement is that its even below your
> normal footer.  The more appropriate place is the about section on the home
> page.  My interpretation is that this needs to be on your website and in
> your documentation.  Not on every page.
> OK. I can move the text to the About section on the front page and remove
it from the footer.

> >
> > 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
> > the ASL text and the incubator-disclaimer text.
> >
> Inclusion in the documentation is required.  But see my note above.  We're
> not asking you to inundate the users with it (from my POV).  I would put it
> in an intro section if it were up to me.
> What's the preference? The disclaimer before or after the ASL text in
documentation? Do I need to have the disclaimer on wiki pages that provide
documentation, too? For example:

If both are required, then I'd suggest that a single ASL+disclaimer
statement with guidance is provided.

Also, I'd like to point out that graduation now means that the project has
to go hunt for every place it mentions incubation to pull out the

It's seems to me that the easier approach is to redirect $ to $ and do
something similar for the wiki. That way, the incubation status is quite



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