From general-return-44365-apmail-incubator-general-archive=incubator.apache.org@incubator.apache.org Mon Mar 17 17:06:17 2014 Return-Path: X-Original-To: apmail-incubator-general-archive@www.apache.org Delivered-To: apmail-incubator-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7606DCE4A for ; Mon, 17 Mar 2014 17:06:17 +0000 (UTC) Received: (qmail 74574 invoked by uid 500); 17 Mar 2014 17:05:59 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 73777 invoked by uid 500); 17 Mar 2014 17:05:58 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 73334 invoked by uid 99); 17 Mar 2014 17:05:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Mar 2014 17:05:58 +0000 X-ASF-Spam-Status: No, hits=0.3 required=5.0 tests=FRT_ADOBE2,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: unknown (nike.apache.org: error in processing during lookup of aharui@adobe.com) Received: from [207.46.163.235] (HELO na01-by2-obe.outbound.protection.outlook.com) (207.46.163.235) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Mar 2014 17:05:52 +0000 Received: from BL2PR02MB500.namprd02.prod.outlook.com (10.141.95.147) by BL2PR02MB500.namprd02.prod.outlook.com (10.141.95.147) with Microsoft SMTP Server (TLS) id 15.0.898.11; Mon, 17 Mar 2014 17:05:28 +0000 Received: from BL2PR02MB500.namprd02.prod.outlook.com ([10.141.95.147]) by BL2PR02MB500.namprd02.prod.outlook.com ([10.141.95.147]) with mapi id 15.00.0898.005; Mon, 17 Mar 2014 17:05:28 +0000 From: Alex Harui To: "general@incubator.apache.org" Subject: Re: [VOTE] Graduation of Apache Allura from the Incubator Thread-Topic: [VOTE] Graduation of Apache Allura from the Incubator Thread-Index: AQHPOkJWlmGvwfDzP0mNHgsmweYVLprdwiWAgAALtgCAAYEpAIAAjR6AgAAB04CAACp5AIAAgi2AgACFYICAAEPkAIAAEgoAgAPFLoCAAEhZgIAADnmA//+OvwCAAH23gP//jfsA Date: Mon, 17 Mar 2014 17:05:27 +0000 Message-ID: References: <531A2930.4040006@brondsema.net> <53209E05.5020609@rcbowen.com> <5322867A.8070801@brondsema.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.9.131030 x-originating-ip: [192.150.22.5] x-forefront-prvs: 0153A8321A x-forefront-antispam-report: SFV:NSPM;SFS:(10019001)(6009001)(428001)(24454002)(252514010)(51704005)(189002)(199002)(377454003)(30844003)(479174003)(97336001)(97186001)(74366001)(81542001)(19580395003)(83322001)(15202345003)(95666003)(81816001)(74706001)(74876001)(90146001)(19580405001)(56816005)(80976001)(74662001)(81686001)(83506001)(20776003)(63696002)(2656002)(59766001)(77982001)(4396001)(47976001)(50986001)(94316002)(49866001)(47736001)(86362001)(93516002)(93136001)(92726001)(92566001)(95416001)(46102001)(66066001)(76786001)(65816001)(80022001)(54356001)(81342001)(83072002)(54316002)(85852003)(79102001)(87936001)(31966008)(56776001)(94946001)(74502001)(47446002)(69226001)(53806001)(15975445006)(87266001)(76796001)(36756003)(85306002)(76482001);DIR:OUT;SFP:1102;SCL:1;SRVR:BL2PR02MB500;H:BL2PR02MB500.namprd02.prod.outlook.com;FPR:6E7BF1C5.9EC2DF89.9C12DB7.C6EDE140.20545;MLV:sfv;PTR:InfoNoRecords;MX:1;A:1;LANG:en; received-spf: None (: adobe.com does not designate permitted sender hosts) Content-Type: text/plain; charset="us-ascii" Content-ID: <93E70F9B1DA9794AB50B35DC50360013@namprd02.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: adobe.com X-Virus-Checked: Checked by ClamAV on apache.org 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" 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 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" wrote: >> >> >On 17 March 2014 15:17, Cory Johns wrote: >> >> On Mon, Mar 17, 2014 at 6:58 AM, sebb wrote: >> >> >> >>> On 15 March 2014 01:23, Justin Mclean >> 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-unsubscribe@incubator.apache.org >> >For additional commands, e-mail: general-help@incubator.apache.org >> > >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org >> For additional commands, e-mail: general-help@incubator.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org