Mailing-List: contact infrastructure-dev-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: infrastructure-dev@apache.org
Received-SPF: pass (nike.apache.org: domain of joe_schaefer@yahoo.com
 designates 98.138.91.114 as permitted sender)
Date: Thu, 26 Mar 2015 03:21:53 +0000 (UTC)
From: Joe Schaefer <joe_schaefer@yahoo.com.INVALID>
Reply-To: Joe Schaefer <joe_schaefer@yahoo.com>
To: "infrastructure-dev@apache.org" <infrastructure-dev@apache.org>
Message-ID: <705035256.1864578.1427340113748.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: 
 <CAPbPdOYboCQmTqTDo60sGwur-AS1d_Qd8joznPZt7aKVrbWyWQ@mail.gmail.com>
References: 
 <CAPbPdOYboCQmTqTDo60sGwur-AS1d_Qd8joznPZt7aKVrbWyWQ@mail.gmail.com>
Subject: Re: FAQ on CMS decommissioning
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_1864577_1392370721.1427340113744"

------=_Part_1864577_1392370721.1427340113744
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Well no. =C2=A0You get to have input into the actual decision, along with o=
ther contractors and members of the infra President's committee. =C2=A0Infr=
a operates as a hierarchy, your decisions will bubble up to the VP and then=
 the President who reports to the board. =C2=A0The board doesn't have a dog=
 in this debate, so there's no reason for them to second guess the chain of=
 command.
All anyone outside=C2=A0the operational chain of command can do is to try t=
o influence that decision making process from the *outside*. =C2=A0It's up =
to you guys to choose the best course of action for=C2=A0the org as you see=
 fit.
Naturally there is a lot of responsibility in having that kind of decision =
making authority. =C2=A0I've said more than my peace on the subject to try =
to provide my experience with the service as it is currently used by projec=
ts. =C2=A0Basing=C2=A0your=C2=A0decision solely on my input and that of you=
r peers is not what I have in mind.
Projects need to give input on what the implications of the proposal mean f=
or them. =C2=A0And they need to do it themselves, not by sitting behind my =
"advocacy".Again all I want from this is a good solid well founded decision=
 and plan of action;none of the projects I work on are cms customers so I'd=
 like to step out of this conversation from a focal viewpoint.=20


     On Wednesday, March 25, 2015 11:08 PM, Andrew Bayer <andrew.bayer@gmai=
l.com> wrote:
  =20

 A preliminary decision. Note the key word. Rightly, infra doesn't want to
have to maintain an ever growing array of overlapping or duplicate
services. If we are going to "deprecate" the CMS, then obviously the end
game is decommissioning. But again, that decision has not been made one way
or the other, nor is it going to be made solely by the contractors, or the
infra team alone, etc. That's why infra presented the RFC in the first
place.

A.

On Wednesday, March 25, 2015, Joe Schaefer <joe_schaefer@yahoo.com.invalid>
wrote:

> According to the proposal Tony wrote infra plans to make a preliminary
> decision on the matter on March 31.=C2=A0 That the rhetoric has gone from
> deprecating to decommissioning is a significant clarification of intentio=
ns.
>
>
>=C2=A0 =C2=A0 =C2=A0 On Wednesday, March 25, 2015 10:55 PM, Chris Lambertu=
s <
> cml@apache.org <javascript:;>> wrote:
>
>
>
> > On Mar 25, 2015, at 7:35 PM, Joe Schaefer <joe_schaefer@yahoo.com.INVAL=
ID>
> wrote:
> >
> > Note that this explicitly states the intention to decommission the
> service as it now stands
>
> No, this is NOT the explicit statement. I thought I was very clear on tha=
t
> in section 1(a) of the FAQ, as was Tony in his initial email (=E2=80=9CSo=
 we would
> like to solicit feedback on our proposal=E2=80=A6=E2=80=9D), so I will ma=
ke it as clear as
> possible once again:
>
>
> Infra does not have any specific action related to the CMS planned at thi=
s
> time.
>
>
> This is ONLY a request for commentary from the community on a proposal by
> Infra to work towards decommissioning the CMS. It is NOT an express
> statement by the infra group that we will be taking any specific action(s=
).
> We seek input from the community on this proposal so that we can make mor=
e
> informed decisions on the future direction of CMS support, whether that b=
e
> via replacement, via resources applied to bring the existing CMS to
> acceptable support standards, or some other option TBD.
>
> Here is the link to the FAQ:
>
>
> https://cwiki.apache.org/confluence/display/INFRA/CMS+Decommissioning+RFC=
+-+Frequently+Asked+Questions
>
> -Chris
>
>
>

  
------=_Part_1864577_1392370721.1427340113744--