Hey guys
At this point, to quote myself in a separate email, I've kicked up enough
dust to get the right answers and discussion points happening.
I'm canceling this vote. Its clear that for this to be effective, we need
to get branding in order first across all of the podlings.
John
On Wed,
> On Jun 29, 2016, at 7:03 AM, Marvin Humphrey wrote:
>
> An even worse example than Eagle
I’m a mentor of Eagle. Mea culpa, I took my eye off the ball. I’m asked them to
do a branding audit and fix themselves.
Julian
On 6/29/16, 9:13 AM, "Shane Curcuru" wrote:
>
>>
>> Hmmm not a bad idea. I'd still like to see us re-double the effort on
>> resolving branding issues on the websites. Ultimately I'd like for
>>mentors
>> to own it, but that doesn't seem to happen due to mentor
John D. Ament wrote on 6/29/16 9:21 AM:
> On Wed, Jun 29, 2016 at 9:18 AM Justin Mclean
> wrote:
>
>> Hi,
>>
>>> The presence of the word "incubator" in the URL is deliberate: it alerts
>> users
>>> that a podling is incubating. I'd feel better about this proposal if
On Wed, Jun 29, 2016 at 6:17 AM, Justin Mclean wrote:
> Hi,
>
>> The presence of the word "incubator" in the URL is deliberate: it alerts
>> users
>> that a podling is incubating. I'd feel better about this proposal if
>> podlings
>> weren't so successful about
On Wed, 2016-06-29 at 14:43 +0200, Jochen Wiedmann wrote:
> We are not only talking about web sites. The discussion is, for
> example, also about aliases for mailing lists.
I'm aware that mailinglists work at either: it took me by surprise
a while back. For them too there are a couple of
On Wed, Jun 29, 2016 at 9:18 AM Justin Mclean
wrote:
> Hi,
>
> > The presence of the word "incubator" in the URL is deliberate: it alerts
> users
> > that a podling is incubating. I'd feel better about this proposal if
> podlings
> > weren't so successful about
Hi,
> The presence of the word "incubator" in the URL is deliberate: it alerts users
> that a podling is incubating. I'd feel better about this proposal if podlings
> weren't so successful about concealing their incubation status[1][2].
>
> -0, since the Incubator remains unserious about
+1 (binding)
Andy
On 28/06/16 15:28, John D. Ament wrote:
All,
Its been discussed a few times, and I'd like to provide clear feedback to
the infra team on how to implement going forward.
Typically, the addresses $podling.apache.org and $
podling.incubator.apache.org work, and have
On Wed, Jun 29, 2016 at 8:41 AM Marvin Humphrey
wrote:
> On Tue, Jun 28, 2016 at 8:01 PM, John D. Ament
> wrote:
>
> > Marvin had sent out an audit of podlings out of alignment, we should
> double
> > check that as going through quarterly reports.
On Wed, Jun 29, 2016 at 2:40 PM, Marvin Humphrey wrote:
> This vote makes me cranky. Everyone is focused on making it easier for
> podlings. Is the goal of incubation to pass a graduation vote or to learn?
True, but I don't think that life should be more difficult for
On Wed, Jun 29, 2016 at 1:58 PM, Nick Kew wrote:
> Perhaps it would make sense for $podling.apache.org to
> issue a 302 redirect to the incubator? Then it's there
> for people and search engines, but the potential for
> being accidentally misleading is much reduced.
We are not
On Tue, Jun 28, 2016 at 8:01 PM, John D. Ament wrote:
> Marvin had sent out an audit of podlings out of alignment, we should double
> check that as going through quarterly reports.
This vote makes me cranky. Everyone is focused on making it easier for
podlings. Is the
On Tue, 2016-06-28 at 14:28 +, John D. Ament wrote:
> All,
>
> Its been discussed a few times, and I'd like to provide clear feedback to
> the infra team on how to implement going forward.
I don't recollect it being discussed in these terms. Could it
be that it's appeared as a sub-thread of
+1 (binding) for the reasons already stated by others - reduces
engagement friction as projects pass through the incubator.
Having a clear indication on the site that the project is in incubation
works better than the URL segment.
Regards,
Tim
On 28/06/16 15:28, John D. Ament wrote:
> All,
>
>
I'm eyeing some changes to http://incubator.apache.org/guides/mentor.html as
well, so I don't mind picking this up.
The issue originally came up as we found that many newly created podlings
had working websites as $podling.apache.org in addition to $podling.i.a.o.
Marvin had sent out an audit of
Hi,
+1 but only if poddlings follow branding guidelines [1] (i.e. include
disclaimer on website)
I's also suggest that the inclusion of the incubator logo be changed to a MUST
rather than a SHOULD as the URL may no longer include “incubator”.
The page [1] may require a couple of minor edit as
+1
On Tue, Jun 28, 2016 at 7:58 PM, John D. Ament
wrote:
> All,
>
> Its been discussed a few times, and I'd like to provide clear feedback to
> the infra team on how to implement going forward.
>
> Typically, the addresses $podling.apache.org and $
>
+1
Looking forward to this one :)
On Tuesday, June 28, 2016, John D. Ament wrote:
> All,
>
> Its been discussed a few times, and I'd like to provide clear feedback to
> the infra team on how to implement going forward.
>
> Typically, the addresses $podling.apache.org and
+1
Niall
On Tue, Jun 28, 2016 at 3:28 PM, John D. Ament
wrote:
> All,
>
> Its been discussed a few times, and I'd like to provide clear feedback to
> the infra team on how to implement going forward.
>
> Typically, the addresses $podling.apache.org and $
>
+1
It’s easy to change content (e.g. the incubation disclaimer at the top of the
home page and in files that are part of the release) but it’s difficult to
change URLs. Remember that projects are ongoing operations, before and after
graduation, and they are trying to reduce friction in their
+1 (binding)
Having to switch domain names during graduation is a pain for users, SEO,
printed t-shirts, etc. Especially after many podlings arrive from outside
the ASF and already have to switch once when entering incubation, adding
the second switch is aggravating.
-Todd
On Tue, Jun 28, 2016
+1 (non-binding)
On 28 Jun 2016 3:29 p.m., "John D. Ament" wrote:
> All,
>
> Its been discussed a few times, and I'd like to provide clear feedback to
> the infra team on how to implement going forward.
>
> Typically, the addresses $podling.apache.org and $
>
+1 to implementing this in the future.
-0 for retroactive implementation.
On Tue, Jun 28, 2016 at 5:41 PM, Flavio Junqueira wrote:
> +1
>
>> On 28 Jun 2016, at 15:28, John D. Ament wrote:
>>
>> All,
>>
>> Its been discussed a few times, and I'd like to
+1
> On 28 Jun 2016, at 15:28, John D. Ament wrote:
>
> All,
>
> Its been discussed a few times, and I'd like to provide clear feedback to
> the infra team on how to implement going forward.
>
> Typically, the addresses $podling.apache.org and $
>
All,
Its been discussed a few times, and I'd like to provide clear feedback to
the infra team on how to implement going forward.
Typically, the addresses $podling.apache.org and $
podling.incubator.apache.org work, and have worked for a while.
This is a call to vote on whether the IPMC agrees
26 matches
Mail list logo