I'm not a branding expert. Has the Apache VP of Branding approved the look? You are correct that the word SourceForge is not on the site, but I thought branding included colors, icons, and layout and the goal is to prevent confusion, and I was definitely confused, but it could just be me. There are several Adobe links that take you to SourceForge so maybe I've experienced that more than others.
-Alex On 3/17/14 9:53 AM, "Cory Johns" <john...@gmail.com> wrote: >Alex, > >The project is Allura, which does power the developer tools at >SourceForge, >and we're using an Allura instance on an Apache VM to "self-host" the >project. Since Allura is a project management platform, in the interests >of "eating our own dogfood," we obviously want to continue to use Allura >to >manage the Allura project (and eventually open it up for other Apache >projects to use as well). > >There shouldn't be any SourceForge branding or references on the Apache >Allura instance, aside from the overall look and feel of the platform >being >similar, since it is in fact the same platform (though SourceForge does >theme Allura to some degree, for example in the tools menu). > > >On Mon, Mar 17, 2014 at 12:23 PM, Alex Harui <aha...@adobe.com> wrote: > >> Since we're still piling on, I just went to >> https://forge-allura.apache.org/p/allura/ >> and was pretty sure I had been redirected to SourceForge. It look and >> feel of that page looks like all of the other SourceForge projects like >> the Open@Adobe sites I have visited. I would think that: >> >> >> 1) Apache wouldn't want to have SourceForge branding on Apache >> infrastructure >> 2) SourceForge wouldn't want Apache to have SourceForge branding on >>Apache >> infrastructure. >> >> Are folks sure this is ok? >> >> -Alex >> >> On 3/17/14 9:09 AM, "sebb" <seb...@gmail.com> wrote: >> >> >On 17 March 2014 15:17, Cory Johns <john...@gmail.com> wrote: >> >> On Mon, Mar 17, 2014 at 6:58 AM, sebb <seb...@gmail.com> wrote: >> >> >> >>> On 15 March 2014 01:23, Justin Mclean <jus...@classsoftware.com> >> wrote: >> >>> > >> >>> > While it's clear in the text and from the domain that the project >>is >> >>>an >> >>> ASF one, the subtitles "Forge software for hosting software >>projects" >> >>>and >> >>> "Brought to you by: brondsem, masterbunnyfu, rbowen, vansteenburgh" >>and >> >>> lack of links back to the ASF don't immediately give that >>impression. >> >>> >> >>> That's a good point. >> >>> >> >>> The board decided a long time ago that @author tags were deprecated >>in >> >>> code; partly because they get out of date, but mainly because the >>ASF >> >>> is a community, and code is a co-operative effort. >> >>> >> >>> Seems to me the "Brought to you" sentence has similar problems, and >> >>> should be removed. >> >> >> >> >> >> Well, I should note that the "Brought to you by" line is actually >> >> automatically generated from the project permissions, so there is >>little >> >> chance of it getting out of date. >> > >> >What about when people move on from Allura and no longer have >>permissions? >> >That does not necessarily mean that their contribution to the project >> >is no longer important. >> >Even if their code has been entirely replaced by later changes, they >> >still contributed to the software. >> > >> >> That said, it will be more useful as we >> >> move more of the Allura work (specifically, ticket activity) over >>from >> >>the >> >> old SourceForge location to the Apache hosted Allura instance, as is >>the >> >> plan. >> > >> >Same issue; the ASF is about community-developed code, not individual >> >coders. >> >Individuals come and go; the ASF hopeully will outlast us all! >> > >> >> >> >>> >> >>> >> >> Also I think (almost?) all other TLPs include the ASF feather which >> >>> links back to the main ASF page. >> >>> >> >>> >> >> I have updated the page at https://forge-allura.apache.org/p/allura/ >>to >> >> include the ASF feather logo which links to >> >> http://www.apache.org/foundation/ >> > >> >The ASF feather is normally present in the header, not just the home >>page. >> >Is it possible to add it there? >> > >> >> >> >>> > It also quite hard for someone outside the project to see what is >> >>> happing on the mailing list due to the large amount at allure ticket >> >>> emails. Have you consider having a separate issues list? >> >>> >> >>> +1 >> >> >> >> >> >> This has been raised before and some things have been done to improve >> >>the >> >> tracker notifications on the mailing list (combining status change >>and >> >> comment notifications, fixing threading, etc) and it was decided at >>the >> >> time that it was reasonable to continue to include that traffic (with >> >> improvements) on the list. However, I believe the possibility of >> >>splitting >> >> it in the future was left open, should anyone continue to feel it >>was a >> >> problem. >> >> >> >> Still, this doesn't seem to me like something that should block >> >>graduation, >> >> as the tracker communications are indeed related to Allura >>development. >> > >> >Agreed the destination of tracker notifications is not a blocker to >> >graduation. >> >But could perhaps become a blocker to community growth, so needs to be >> >monitored. >> > >> >--------------------------------------------------------------------- >> >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> >For additional commands, e-mail: general-h...@incubator.apache.org >> > >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
