Re: Podling Tubemq Report Reminder - January 2020

[Justin Mclean <jm...@apache.org>]

Hi,
Just a friendly reminder that this report is due today, is anyone working on it?
Thanks,
Justin

Re: Podling Tubemq Report Reminder - January 2020

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> For the first time, report get missing is because we haven't setup dev
> list ready so PPMCs hasn't been notified - I believe IPMCs also not get
> notified for some reason. So I think this should be the first time that
> counts - because most of PPMCs were on vacation due to holidays.

The podling has had ample notice. The mentors should be following the incubator general list and be reading the IPMC report. The mentors should know that a podling needs to report monthly for the first 3 months. I personally reached out to the projects mentors asking for an explanation a month ago. Questions about this project have gone unanswered on the incubator general list. This issue has been mentioned in two IPMC reports now. What more needs to be done before the podling or it’s mentors takes notice?  During setup the podling still has to report, even if that’s to explain why things have not been setup yet.

Thanks,
Justin

Re: Podling Tubemq Report Reminder - January 2020

[俊平堵 <ju...@apache.org>]

Agree. TubeMQ PPMC team should be aware of this - only
discussions/decisions made on JIRA or dev list are accepted in apache way.

Thanks,

Junping

Justin Mclean <jm...@apache.org> 于2020年1月2日周四 下午2:32写道：

> Hi,
>
> > I have pinged the team and they should reply soon.
>
> How and where is this off list communication happening? This has been
> asked several times and no answer has been supplied. Has it been made clear
> to the project that communication and decisions needs to happen on this
> mailing list? I understand it may take time to move towards that, but the
> project needs to show signs of doing so, more so than they currently have,
> otherwise they may need to explain to the IPMC why they should be an
> incubating project.
>
> Without communication on this list the mentors and the IPMC can't help the
> project. Without communication on this list this project going to find it
> hard to grow it's community. Without communication on this list the project
> will not graduate.
>
> Thanks,
> Justin
>

Re: Podling Tubemq Report Reminder - January 2020

[Justin Mclean <jm...@apache.org>]

Hi,

> I have pinged the team and they should reply soon.

How and where is this off list communication happening? This has been asked several times and no answer has been supplied. Has it been made clear to the project that communication and decisions needs to happen on this mailing list? I understand it may take time to move towards that, but the project needs to show signs of doing so, more so than they currently have, otherwise they may need to explain to the IPMC why they should be an incubating project.

Without communication on this list the mentors and the IPMC can't help the project. Without communication on this list this project going to find it hard to grow it's community. Without communication on this list the project will not graduate.

Thanks,
Justin

Re: Podling Tubemq Report Reminder - January 2020

[俊平堵 <ju...@apache.org>]

Hi Justin,
     For the first time, report get missing is because we haven't setup dev
list ready so PPMCs hasn't been notified - I believe IPMCs also not get
notified for some reason. So I think this should be the first time that
counts - because most of PPMCs were on vacation due to holidays. I have
pinged the team and they should reply soon.

Thanks,

Junping

Justin Mclean <jm...@apache.org> 于2020年1月2日周四 上午10:05写道：

> Hi,
>
> This is the second report in a row the project has missed, one missed
> report is OK, two are cause for concern, three and you may be kicked out of
> the Incubator. I can see that you are still moving resources to the
> incubator and start up here has been slow. You need to provide the IPMC
> with oversight to how the project is going and what issues it is facing and
> still need to submit reports in the start up phase.
>
> It seems to me that some of your mentors are missing, if this is the case
> please mention this in your report. I've reached out to them (on the
> private list) and if they don't reply they will be removed and other
> mentors found to replace them.
>
> I suggest you discuss on this list what is need to move the project over,
> I'm not seeing a lot of communication on these lists, and it seems that
> some communication is currently occurring elsewhere. Please fix this.
>
> Thanks,
> Justin
>

Re: Podling Tubemq Report Reminder - January 2020

[Saisai Shao <sa...@gmail.com>]

I've updated some parts of the report, please help to review, thanks!

Besides, we will follow the Apache way to bring out all the discussions on
the mail list, thanks for your guidance.

Thanks
Saisai


Saisai Shao <sa...@gmail.com> 于2020年1月3日周五 上午11:27写道：

> Thanks Justin for your reply, I will amend the report soon.
>
> Best regards,
> Saisai
>
> Justin Mclean <jm...@apache.org> 于2020年1月3日周五 上午7:03写道：
>
>> Hi,
>>
>> Thanks for submitting the  report but it will not be accepted in it's
>> currently form as it doesn't accurately reflect the current podlings state
>> and what it needs to do. Next time I suggest you work on the report in the
>> open before the due date.
>>
>> You have user the three most important unfinished issues to address
>> before graduating:
>> 1. Grow the community to involve more contributors and increase the
>> diversity.
>> 2. Polish the code and document to satisfy the Apache way.
>> 3. Publish the Apache release.
>>
>> There are far more serious matters that need to be sorted out before
>> those are addressed. Number one being moving conversation to this mailing
>> list.
>>
>> Under "Are there any issues that the IPMC or ASF Board need to be aware
>> of?" you have said "No" this is incorrect.
>>
>> Under "How has the community developed since the last report?" you
>> mention PRs and commits but the repos have not moved to the ASF yet so how
>> is this possible?
>>
>> User "How has the project developed since the last report?" you mention
>> working on the first release and website. I see no conversation of this on
>> list or any work towards those gaols. http://tubemq.apache.org currently
>> gives 404 not found.
>>
>> Please rewrite the report to accurately reflect where the podling
>> currently is and what issues it faces.
>>
>> Thanks,
>> Justin
>>
>>
>>
>>
>>
>>

Re: Podling Tubemq Report Reminder - January 2020

[Saisai Shao <sa...@gmail.com>]

Thanks Justin for your reply, I will amend the report soon.

Best regards,
Saisai

Justin Mclean <jm...@apache.org> 于2020年1月3日周五 上午7:03写道：

> Hi,
>
> Thanks for submitting the  report but it will not be accepted in it's
> currently form as it doesn't accurately reflect the current podlings state
> and what it needs to do. Next time I suggest you work on the report in the
> open before the due date.
>
> You have user the three most important unfinished issues to address before
> graduating:
> 1. Grow the community to involve more contributors and increase the
> diversity.
> 2. Polish the code and document to satisfy the Apache way.
> 3. Publish the Apache release.
>
> There are far more serious matters that need to be sorted out before those
> are addressed. Number one being moving conversation to this mailing list.
>
> Under "Are there any issues that the IPMC or ASF Board need to be aware
> of?" you have said "No" this is incorrect.
>
> Under "How has the community developed since the last report?" you mention
> PRs and commits but the repos have not moved to the ASF yet so how is this
> possible?
>
> User "How has the project developed since the last report?" you mention
> working on the first release and website. I see no conversation of this on
> list or any work towards those gaols. http://tubemq.apache.org currently
> gives 404 not found.
>
> Please rewrite the report to accurately reflect where the podling
> currently is and what issues it faces.
>
> Thanks,
> Justin
>
>
>
>
>
>

Re: Podling Tubemq Report Reminder - January 2020

[Justin Mclean <jm...@apache.org>]

Hi,

Thanks for submitting the  report but it will not be accepted in it's currently form as it doesn't accurately reflect the current podlings state and what it needs to do. Next time I suggest you work on the report in the open before the due date.

You have user the three most important unfinished issues to address before graduating:
1. Grow the community to involve more contributors and increase the diversity.
2. Polish the code and document to satisfy the Apache way.
3. Publish the Apache release.

There are far more serious matters that need to be sorted out before those are addressed. Number one being moving conversation to this mailing list.

Under "Are there any issues that the IPMC or ASF Board need to be aware of?" you have said "No" this is incorrect.

Under "How has the community developed since the last report?" you mention PRs and commits but the repos have not moved to the ASF yet so how is this possible?

User "How has the project developed since the last report?" you mention working on the first release and website. I see no conversation of this on list or any work towards those gaols. http://tubemq.apache.org currently gives 404 not found.

Please rewrite the report to accurately reflect where the podling currently is and what issues it faces.

Thanks,
Justin

Re: Podling Tubemq Report Reminder - January 2020

[Saisai Shao <sa...@gmail.com>]

Hi Justin,

Sorry about the late reply, we will work on this today. Thanks a lot for
your reminder.

Best regards,
Saisai

Justin Mclean <jm...@apache.org> 于2020年1月2日周四 上午10:05写道：

> Hi,
>
> This is the second report in a row the project has missed, one missed
> report is OK, two are cause for concern, three and you may be kicked out of
> the Incubator. I can see that you are still moving resources to the
> incubator and start up here has been slow. You need to provide the IPMC
> with oversight to how the project is going and what issues it is facing and
> still need to submit reports in the start up phase.
>
> It seems to me that some of your mentors are missing, if this is the case
> please mention this in your report. I've reached out to them (on the
> private list) and if they don't reply they will be removed and other
> mentors found to replace them.
>
> I suggest you discuss on this list what is need to move the project over,
> I'm not seeing a lot of communication on these lists, and it seems that
> some communication is currently occurring elsewhere. Please fix this.
>
> Thanks,
> Justin
>

Re: Podling Tubemq Report Reminder - January 2020

[Justin Mclean <jm...@apache.org>]

Hi,

This is the second report in a row the project has missed, one missed report is OK, two are cause for concern, three and you may be kicked out of the Incubator. I can see that you are still moving resources to the incubator and start up here has been slow. You need to provide the IPMC with oversight to how the project is going and what issues it is facing and still need to submit reports in the start up phase.

It seems to me that some of your mentors are missing, if this is the case please mention this in your report. I've reached out to them (on the private list) and if they don't reply they will be removed and other mentors found to replace them.

I suggest you discuss on this list what is need to move the project over, I'm not seeing a lot of communication on these lists, and it seems that some communication is currently occurring elsewhere. Please fix this.

Thanks,
Justin