You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cmda.apache.org by "John D. Ament" <jo...@apache.org> on 2017/01/25 03:01:38 UTC
[DISCUSS] Retire the CMDA Podling
Dear CMDA Podling,
Last summer, a discussion started to retire the CMDA podling. A vote was
started shortly after and it was decided to give more time to see how the
podling grows. Unfortunately at this point, public discussions around the
podling have ceased. There is still no website, no releases. The last
commit to the repo is still November 2015.
At this point, the only path forward I believe is retirement of the podling.
John
Re: [DISCUSS] Retire the CMDA Podling
Posted by "John D. Ament" <jo...@apache.org>.
Jia,
For the benefit of the doubt, I double checked your initial committers vs who had accounts. The following do not have accounts yet (as a result cannot commit to the repo):
- Benyang Tang
- Wei Wang
- Chris Lee
The other 5 committers have access to all incubator projects, as is the norm. If you've tried to commit in the past, you can share the error you received and I can provide some input on what it means.
John
On 2017-01-24 23:55 (-0500), Jia Zhang <ji...@sv.cmu.edu> wrote:
> Dear John:
>
> Happy New Year!
>
> I believe there is some miscommunication.
>
> We have been waiting for permission to commit to repo for a long time,
> after quite some applications. None of the members in our team have
> received accounts to commit, including myself. My previous student had
> permission, but he graduated. We reported.
>
> As a matter of fact, the CMDA team has developed project website, also we
> have set up various ways to publish our code, in github as well as
> dockerhub.
>
> We hope mentors could give us more advice.
>
> Thanks a lot.
>
> Best regards,
> Jia
>
> On Tue, Jan 24, 2017 at 7:01 PM, John D. Ament <jo...@apache.org>
> wrote:
>
> > Dear CMDA Podling,
> >
> > Last summer, a discussion started to retire the CMDA podling. A vote was
> > started shortly after and it was decided to give more time to see how the
> > podling grows. Unfortunately at this point, public discussions around the
> > podling have ceased. There is still no website, no releases. The last
> > commit to the repo is still November 2015.
> >
> > At this point, the only path forward I believe is retirement of the
> > podling.
> >
> > John
> >
>
Re: [DISCUSS] Retire the CMDA Podling
Posted by Ted Dunning <te...@gmail.com>.
I am in favor of retirement.
There just isn't any perceptible inclination to be an Apache community
here. Without that, further incubation doesn't make much sense.
On Wed, Jan 25, 2017 at 8:50 AM, Chris Mattmann <ma...@apache.org> wrote:
> Hi Jia, and community,
>
> The basic situation we have here is:
>
> 1. The CMDA podling doesn’t send email to the lists. There are
> 0 new threads started by the PPMC in months, and 0 communication other
> than report reminders (and late reports), and questions about the podling’s
> status: https://lists.apache.org/list.html?dev@cmda.apache.org
> 2. Communication and work on CMDA are occurring, just not at Apache.
>
>
> Regardless of the account requests (which I had a spreadsheet early on,
> here, and asked the team to track where they were with submitting and the
> process which
> they never updated), the podling has not met the minimum bar for being an
> open and transparent
> community despite many threads regarding this. In addition, due to my own
> limited time
> for mentorship and the limited time of other mentors there was difficulty
> in actively
> monitoring this and overall I believe there was the hope that somehow this
> would be
> figured out and corrected.
>
> I am +1 for John, because of this, to start and continue the Retirement
> discussion.
>
> We tried, and this isn’t a repudiation of the project by any means. It’s
> simply a
> recognition the experiment here at Apache didn’t work out, and it’s the
> correct thing to do for both sides.
>
> Sincerely,
> Chris
>
>
>
>
> On 1/24/17, 8:55 PM, "Jia Zhang" <ji...@sv.cmu.edu> wrote:
>
> Dear John:
>
> Happy New Year!
>
> I believe there is some miscommunication.
>
> We have been waiting for permission to commit to repo for a long time,
> after quite some applications. None of the members in our team have
> received accounts to commit, including myself. My previous student had
> permission, but he graduated. We reported.
>
> As a matter of fact, the CMDA team has developed project website, also
> we
> have set up various ways to publish our code, in github as well as
> dockerhub.
>
> We hope mentors could give us more advice.
>
> Thanks a lot.
>
> Best regards,
> Jia
>
> On Tue, Jan 24, 2017 at 7:01 PM, John D. Ament <jo...@apache.org>
> wrote:
>
> > Dear CMDA Podling,
> >
> > Last summer, a discussion started to retire the CMDA podling. A
> vote was
> > started shortly after and it was decided to give more time to see
> how the
> > podling grows. Unfortunately at this point, public discussions
> around the
> > podling have ceased. There is still no website, no releases. The
> last
> > commit to the repo is still November 2015.
> >
> > At this point, the only path forward I believe is retirement of the
> > podling.
> >
> > John
> >
>
>
>
>
Re: [DISCUSS] Retire the CMDA Podling
Posted by Chris Mattmann <ma...@apache.org>.
Hi Jia, and community,
The basic situation we have here is:
1. The CMDA podling doesn’t send email to the lists. There are
0 new threads started by the PPMC in months, and 0 communication other
than report reminders (and late reports), and questions about the podling’s
status: https://lists.apache.org/list.html?dev@cmda.apache.org
2. Communication and work on CMDA are occurring, just not at Apache.
Regardless of the account requests (which I had a spreadsheet early on,
here, and asked the team to track where they were with submitting and the process which
they never updated), the podling has not met the minimum bar for being an open and transparent
community despite many threads regarding this. In addition, due to my own limited time
for mentorship and the limited time of other mentors there was difficulty in actively
monitoring this and overall I believe there was the hope that somehow this would be
figured out and corrected.
I am +1 for John, because of this, to start and continue the Retirement discussion.
We tried, and this isn’t a repudiation of the project by any means. It’s simply a
recognition the experiment here at Apache didn’t work out, and it’s the
correct thing to do for both sides.
Sincerely,
Chris
On 1/24/17, 8:55 PM, "Jia Zhang" <ji...@sv.cmu.edu> wrote:
Dear John:
Happy New Year!
I believe there is some miscommunication.
We have been waiting for permission to commit to repo for a long time,
after quite some applications. None of the members in our team have
received accounts to commit, including myself. My previous student had
permission, but he graduated. We reported.
As a matter of fact, the CMDA team has developed project website, also we
have set up various ways to publish our code, in github as well as
dockerhub.
We hope mentors could give us more advice.
Thanks a lot.
Best regards,
Jia
On Tue, Jan 24, 2017 at 7:01 PM, John D. Ament <jo...@apache.org>
wrote:
> Dear CMDA Podling,
>
> Last summer, a discussion started to retire the CMDA podling. A vote was
> started shortly after and it was decided to give more time to see how the
> podling grows. Unfortunately at this point, public discussions around the
> podling have ceased. There is still no website, no releases. The last
> commit to the repo is still November 2015.
>
> At this point, the only path forward I believe is retirement of the
> podling.
>
> John
>
Re: [DISCUSS] Retire the CMDA Podling
Posted by Jia Zhang <ji...@sv.cmu.edu>.
Dear John:
Happy New Year!
I believe there is some miscommunication.
We have been waiting for permission to commit to repo for a long time,
after quite some applications. None of the members in our team have
received accounts to commit, including myself. My previous student had
permission, but he graduated. We reported.
As a matter of fact, the CMDA team has developed project website, also we
have set up various ways to publish our code, in github as well as
dockerhub.
We hope mentors could give us more advice.
Thanks a lot.
Best regards,
Jia
On Tue, Jan 24, 2017 at 7:01 PM, John D. Ament <jo...@apache.org>
wrote:
> Dear CMDA Podling,
>
> Last summer, a discussion started to retire the CMDA podling. A vote was
> started shortly after and it was decided to give more time to see how the
> podling grows. Unfortunately at this point, public discussions around the
> podling have ceased. There is still no website, no releases. The last
> commit to the repo is still November 2015.
>
> At this point, the only path forward I believe is retirement of the
> podling.
>
> John
>