If I am not mistaken, the new version of the page is based of
https://cwiki.apache.org/confluence/display/BIGTOP/Powered+By+Bigtopwhich was populated by the 'powered-by' projects themselves. So, yes - we know for sure. Besides, a simple look into vendors' package dependencies shows the foot-print of Bigtop all over the place. But I am fine with your proposed wording, although we are providing more than just build. Runtime as well ie bigtop-utils, etc. Cos On Tue, May 17, 2016 at 07:17PM, Olaf Flebbe wrote: > Hi Cos, > > Of course anyone need permission to use trademark logos. > > The point is not logos itself. What is the message we want to share ? > > Bigtop should not claim that any entity is a downstream user of bigtop. We > do not know for sure. The downstream user itself should agree to be named > here. I can live with the section "powered by" in the current website. That > page has a very differentiated view. Maybe we can reuse this page optically > pimped. > > I am very ok if Nate ask entities, if they approve to be named . > > Maybe the Mission statement can be made clear: > > To provide a generic build system for a vanilla distribution of Apache > Hadoop ecosystem projects, integrating other components early. > > Olaf > > > Am 17.05.2016 um 18:58 schrieb Konstantin Boudnik <[email protected]>: > > > > Take it with as many graines of salt you want, but I don't think using logos > > from someone's publicly available media kit for the purpose of referring to > > the owner of it, requires any special permissions. But I'm not a lawyer. > > > > Cos > > > > On Mon, May 16, 2016 at 02:02PM, [email protected] wrote: > >> No official logo approval. For having clear and concise communication > >> about > >> the project and what it provides to first time visitors feel that will be > >> the most important part of the homepage. We went through similar > >> conversation bit over a year ago when working through the flyer design and > >> the number one thing in most conversations, and presentation q&a's is > >> usually along lines of "who is using it" and "what do you do with it". > >> The > >> resounding way to communicate that has been to say "x,y,z use it as a base > >> to build their distributions and custom component versions/packages...". > >> > >> I can take on task of getting approvals, and can add a related/dependent > >> jira for the main site one > >> > >> > >> -----Original Message----- > >> From: Olaf Flebbe [mailto:[email protected]] > >> Sent: Monday, May 16, 2016 1:50 PM > >> To: [email protected] > >> Cc: [email protected] > >> Subject: Re: new bigtop website > >> > >> Hi Nate, > >> > >> I like the design very much! The big tents are very good! > >> > >> But I would refrain from using the logos in the "powered by" section. Do > >> we > >> have have permissions to use these trademarks? AFAIK we do not. > >> > >> Olaf > >> > >> > >> > >>> Am 16.05.2016 um 22:12 schrieb [email protected]: > >>> > >>> Hello Bigtoppers, > >>> > >>> During some downtime I rekindled the effort for new site for the project. > >> I based the initial design on ideas flushed out mid/late last year and > >> borrowing from the bigtop flyer we have been using the past 12+ months at > >> various events, as well as the workshop site/content I setup for some past > >> conference related events. As such, the content is all in flux, including > >> menu at top, this is meant to get the ball rolling > >>> > >>> Initial rev of design and homepage mock can be found here: > >>> > >>> http://kaiyzen.github.io/bigtop/ > >>> > >>> It is currently setup as a github pages project. Given some feedback on > >> the list ways back with asf supporting it, and the great tooling around > >> Jekyll, figured it was easiest for my dev and collaboration efforts. As we > >> get things finalized we can decide how the group wants to manage/host the > >> new site > >>> > >>> I am keeping notes that anyone who is interested in helping on content can > >> add to: > >>> > >>> > >> https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+Website+Notes+and+ > >> Ideas > >>> > >>> Most important I feel will be the Getting Started content which should > >> fill in the average user(s) to carry out a lot of common tasks, > >> centralizing > >> the details. > >>> > >>> I will update the old jira item with relevant content updates and we can > >> use that for tracking the finer details and delivery. The rest of this > >> week > >> will be some minor tweaks to design and fixing some cross browser and > >> mobile > >> related layout issues (mobile friendly on day 1 is the goal), as well as > >> starting to flush out the template/framework for getting started content > >> > >> >
signature.asc
Description: Digital signature
