Re: [ALC] Branding and logo
I am afraid rules of Apache logo are rather strict about it. Not sure about ALC, but I think Apache Feather is the most protected asset of ASF :). I think I have not seen that apache logo used anywhere except ApacheCon and there are specific rules for NOT using Apache logo in the events: http://www.apache.org/foundation/marks/events.html#graphics " Events may not normally use any Apache logos or graphics as part of their primary event branding. Apache product logos may only be used to refer to the Apache products or projects themselves, and must be clearly set off from any of the events' own branding and logos. If your event wishes to use an Apache project logo within your event branding, you must work with VP, Brand to explicitly grant trademark and goodwill rights for the brand and event logo to the ASF. Event branding may not include the Apache feather in any way. The only use of the bare Apache feather on event materials allowed is to provide a single link to http://www.apache.org/ as a reference to The Apache Software Foundation, typically as a Community Partner or to otherwise refer to Apache as a whole. " Maybe what we can do instead is just ALC specific branding guidelines? J. On Mon, Feb 17, 2020 at 8:41 AM Tomasz Urbaszek wrote: > Hi all, > > I think it would be a good idea to have Apache Local Community logo. > Having branding can help increase recognition and underline attachment > to ASF. In my opinion, each chapter should have its own logo > customized by the name of the city. > > What is the process for such things? Should we engage > tradema...@apache.org ? > > Have a good day, > Tomek Urbaszek > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > > -- +48 660 796 129
[ALC] Branding and logo
Hi all, I think it would be a good idea to have Apache Local Community logo. Having branding can help increase recognition and underline attachment to ASF. In my opinion, each chapter should have its own logo customized by the name of the city. What is the process for such things? Should we engage tradema...@apache.org ? Have a good day, Tomek Urbaszek - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Update information on community.apache.org
Hi, The date should change when the site is updated, please don't update it automatically via JS. Thanks, Justin On Mon, 17 Feb 2020, 09:18 Austin Bennett, wrote: > When looking at that code for the page, I had thought that perhaps would > not hard-code the year, but would use a javascript function to get the > date/year and include that when the site gets rendered -- but that makes > sense in my head, which easily doesn't translate to being > easy-to-impliment. > > On Sun, Feb 16, 2020 at 1:39 PM Tomasz Urbaszek > wrote: > > > Thanks for the quick response! It seems that https://www.apache.org is > > also little bit out of date (2019 instead of 2020). Is there any > > possibility to use some auto-update? > > > > T. > > > > > > On Sun, Feb 16, 2020 at 3:51 PM Shane Curcuru > > wrote: > > > > > > Roy Lenferink wrote on 2020-2-16 6:34AM EST: > > > > Following the WEBSITE-HOWTO [1] I just updated the year from 2018 to > > 2020. > > > > However, a comdev-er still needs to publish the site [2] as I was > > unable to. > > > > "svnmucc: E175013: Access to > > > > > > > '/repos/infra/!svn/txr/1056611-mpm7/websites/production/community/content' > > > > forbidden" > > > > > > Done! Excellent instructions, I had forgotten about the cms publish > > > links. Thanks to Tomasz for reporting. > > > > > > > [1] > https://github.com/apache/comdev-site/blob/trunk/WEBSITE-HOWTO.txt > > > > [2] https://cms.apache.org/community/publish?diff=1 > > > > > > -- > > > > > > - Shane > > > Comdev PMC > > > The Apache Software Foundation > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > >
Re: Update information on community.apache.org
When looking at that code for the page, I had thought that perhaps would not hard-code the year, but would use a javascript function to get the date/year and include that when the site gets rendered -- but that makes sense in my head, which easily doesn't translate to being easy-to-impliment. On Sun, Feb 16, 2020 at 1:39 PM Tomasz Urbaszek wrote: > Thanks for the quick response! It seems that https://www.apache.org is > also little bit out of date (2019 instead of 2020). Is there any > possibility to use some auto-update? > > T. > > > On Sun, Feb 16, 2020 at 3:51 PM Shane Curcuru > wrote: > > > > Roy Lenferink wrote on 2020-2-16 6:34AM EST: > > > Following the WEBSITE-HOWTO [1] I just updated the year from 2018 to > 2020. > > > However, a comdev-er still needs to publish the site [2] as I was > unable to. > > > "svnmucc: E175013: Access to > > > > '/repos/infra/!svn/txr/1056611-mpm7/websites/production/community/content' > > > forbidden" > > > > Done! Excellent instructions, I had forgotten about the cms publish > > links. Thanks to Tomasz for reporting. > > > > > [1] https://github.com/apache/comdev-site/blob/trunk/WEBSITE-HOWTO.txt > > > [2] https://cms.apache.org/community/publish?diff=1 > > > > -- > > > > - Shane > > Comdev PMC > > The Apache Software Foundation > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: Update information on community.apache.org
Thanks for the quick response! It seems that https://www.apache.org is also little bit out of date (2019 instead of 2020). Is there any possibility to use some auto-update? T. On Sun, Feb 16, 2020 at 3:51 PM Shane Curcuru wrote: > > Roy Lenferink wrote on 2020-2-16 6:34AM EST: > > Following the WEBSITE-HOWTO [1] I just updated the year from 2018 to 2020. > > However, a comdev-er still needs to publish the site [2] as I was unable to. > > "svnmucc: E175013: Access to > > '/repos/infra/!svn/txr/1056611-mpm7/websites/production/community/content' > > forbidden" > > Done! Excellent instructions, I had forgotten about the cms publish > links. Thanks to Tomasz for reporting. > > > [1] https://github.com/apache/comdev-site/blob/trunk/WEBSITE-HOWTO.txt > > [2] https://cms.apache.org/community/publish?diff=1 > > -- > > - Shane > Comdev PMC > The Apache Software Foundation > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Update information on community.apache.org
Roy Lenferink wrote on 2020-2-16 6:34AM EST: > Following the WEBSITE-HOWTO [1] I just updated the year from 2018 to 2020. > However, a comdev-er still needs to publish the site [2] as I was unable to. > "svnmucc: E175013: Access to > '/repos/infra/!svn/txr/1056611-mpm7/websites/production/community/content' > forbidden" Done! Excellent instructions, I had forgotten about the cms publish links. Thanks to Tomasz for reporting. > [1] https://github.com/apache/comdev-site/blob/trunk/WEBSITE-HOWTO.txt > [2] https://cms.apache.org/community/publish?diff=1 -- - Shane Comdev PMC The Apache Software Foundation - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Update information on community.apache.org
Following the WEBSITE-HOWTO [1] I just updated the year from 2018 to 2020. However, a comdev-er still needs to publish the site [2] as I was unable to. "svnmucc: E175013: Access to '/repos/infra/!svn/txr/1056611-mpm7/websites/production/community/content' forbidden" [1] https://github.com/apache/comdev-site/blob/trunk/WEBSITE-HOWTO.txt [2] https://cms.apache.org/community/publish?diff=1 Roy Op zo 16 feb. 2020 om 00:51 schreef Austin Bennett < whatwouldausti...@gmail.com>: > Looks like would change the file > https://github.com/apache/comdev-site/blob/trunk/templates/standard.html > > Still didn't read as to exactly the process for updating and getting the > site built, so I didn't put in a PR (to modify master and/or trunc). > > > > On Sat, Feb 15, 2020 at 11:03 AM Tomasz Urbaszek > wrote: > > > Hi all, > > > > I've just spotted that footer on community page > > https://community.apache.org has "Copyright© 2018". I think this > > should be updated to avoid "this page is dead" feeling. Who should I > > contact to request the update? > > > > Best, > > Tomek Urbaszek > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > >
