You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@iotdb.apache.org by jm...@apache.org on 2019/06/01 00:38:32 UTC
Podling Report Reminder - June 2019
Dear podling,
This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.
The board meeting is scheduled for Wed, 19 June 2019, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, June 05).
Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.
Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.
Thanks,
The Apache Incubator PMC
Submitting your Report
----------------------
Your report should contain the following:
* Your project name
* A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
* A list of the three most important issues to address in the move
towards graduation.
* Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
* How has the community developed since the last report
* How has the project developed since the last report.
* How does the podling rate their own maturity.
This should be appended to the Incubator Wiki page at:
https://cwiki.apache.org/confluence/display/INCUBATOR/June2019
Note: This is manually populated. You may need to wait a little before
this page is created from a template.
Note: The format of the report has changed to use markdown.
Mentors
-------
Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.
Incubator PMC
Re: Podling Report Reminder - June 2019
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> I submitted the report just now.
I’m not seeing it here:
https://cwiki.apache.org/confluence/display/INCUBATOR/June2019
Thanks,
Justin
Re: Podling Report Reminder - June 2019
Posted by Xiangdong Huang <sa...@gmail.com>.
Hi,
I submitted the report just now.
Besides, I add more detailed info:
### How has the project developed since the last report?
1. IoTDB is more stable than before. Now it works well on a VM provided
by Apache (iotdb-vm.apache.org).
2. A distributed version is almost done (in the `cluster branch`).
3. In the last 3 months, we opened 78 JIRA issues and resolved/closed 40
JIRA
issues.
Created Resolved
Mar 2019 42 26
Apr 2019 15 6
May 2019 21 8
4. In the last 3 months, we merged/closed 107 PRs in Github (seen at Jun 4)
-----------------------------------
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Justin Mclean <ju...@me.com> 于2019年6月3日周一 下午5:59写道：
> Hi,
>
> OK I leave it here for a few days for any feedback and then submit it.
>
> Unless one of the PPMC members wold like to submit it here first, [1]
>
> Thanks,
> Justin
>
> 1. https://cwiki.apache.org/confluence/display/INCUBATOR/June2019
>
Re: Podling Report Reminder - June 2019
Posted by Justin Mclean <ju...@me.com>.
Hi,
OK I leave it here for a few days for any feedback and then submit it.
Unless one of the PPMC members wold like to submit it here first, [1]
Thanks,
Justin
1. https://cwiki.apache.org/confluence/display/INCUBATOR/June2019
Re: Podling Report Reminder - June 2019
Posted by Xiangdong Huang <sa...@gmail.com>.
Hi,
the new report is attached,
IoTDB is a data store for managing large amounts of time series data such
as timestamped data from IoT sensors in industrial applications.
IoTDB has been incubating since 2018-11-18.
1. Three most important unfinished issues to address before graduating:
- Learn to how to release a formal version;
- Declare a clear release roadmap;
- Attract more contributors joining the community.
2. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- No
3. How has the community developed since the last report?
- We can find that IoTDB is becoming a new choice when users need a time
series database.
New users from UCI (IoTDB-104), Sangfor Inc., University of Liverpool
(IoTDB-94) etc. are testing and proposing issues for IoTDB.
4. How has the project developed since the last report?
- IoTDB is more stable than before. Now it works well on a VM provided by
Apache (iotdb-vm.apache.org).
- A distributed version is almost done (in the `cluster branch`)
5. How would you assess the podling's maturity? Please feel free to add
your own commentary.
[ ] Initial setup
[x] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
- N/A
When were the last committers or PPMC members elected?
- N/A
Have your mentors been helpful?
- Yes
Have your mentors been helpful and responsive or are things falling through
the cracks? In the latter case, please list any open issues that need to be
addressed.
- They are helpful.
Signed-off-by:
(iotdb) Justin Mclean Comments:
(iotdb) Christofer Dutz Comments:
(iotdb) Willem Ning Jiang Comments:
(iotdb) Kevin A. McGrail Comments:
-----------------------------------
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Justin Mclean <ju...@classsoftware.com> 于2019年6月2日周日 上午10:24写道：
> Hi,
>
> > IoTDB is a data store for managing large amounts of time series data such
> > as timestamped data from IoT sensors in industrial applications.
> > IoTDB has been incubating since 2018-11-18.
> >
> > 1. Three most important unfinished issues to address before graduating:
> > - memory controlling problem: JIRA IOTDB-84/87 (they are correlative),
> > - distributed version: JIRA IOTDB-68
> > - (not a JIRA issue): learn to how to release a formal version, and
> declare
> > a clear release roadmap.
>
> These should not be technical reasons but steps along the way of becoming
> a top level apache project. At this point they probably need to be along
> the lines of make a first ASF release (as your note) and grow you community.
>
> Thanks,
> Justin
>
>
Re: Podling Report Reminder - June 2019
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> IoTDB is a data store for managing large amounts of time series data such
> as timestamped data from IoT sensors in industrial applications.
> IoTDB has been incubating since 2018-11-18.
>
> 1. Three most important unfinished issues to address before graduating:
> - memory controlling problem: JIRA IOTDB-84/87 (they are correlative),
> - distributed version: JIRA IOTDB-68
> - (not a JIRA issue): learn to how to release a formal version, and declare
> a clear release roadmap.
These should not be technical reasons but steps along the way of becoming a top level apache project. At this point they probably need to be along the lines of make a first ASF release (as your note) and grow you community.
Thanks,
Justin
Re: Podling Report Reminder - June 2019
Posted by Xiangdong Huang <sa...@gmail.com>.
Hi,
I prepare the draft about the podling report of IoTDB.
For the first question, "Three most important unfinished issues to address
before graduating", I think they are:
- memory controlling problem: JIRA IOTDB-84/87 (they are correlative),
- distributed version: JIRA IOTDB-68
- (not a JIRA issue): learn to how to release a formal version, and declare
a clear release roadmap.
Detailed Report:
IoTDB is a data store for managing large amounts of time series data such
as timestamped data from IoT sensors in industrial applications.
IoTDB has been incubating since 2018-11-18.
1. Three most important unfinished issues to address before graduating:
- memory controlling problem: JIRA IOTDB-84/87 (they are correlative),
- distributed version: JIRA IOTDB-68
- (not a JIRA issue): learn to how to release a formal version, and declare
a clear release roadmap.
2. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- No
3. How has the community developed since the last report?
- We can find that IoTDB is becoming a new choice when users need a time
series database.
New users from UCI (IoTDB-104), Sangfor Inc., University of Liverpool
(IoTDB-94) etc. are testing and proposing issues for IoTDB.
4. How has the project developed since the last report?
- IoTDB is more stable than before. Now it works well on a VM provided by
Apache (iotdb-vm.apache.org).
- A distributed version is almost done (in the `cluster branch`)
5. How would you assess the podling's maturity? Please feel free to add
your own commentary.
[ ] Initial setup
[x] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
- N/A
When were the last committers or PPMC members elected?
- N/A
Have your mentors been helpful?
- Yes
Have your mentors been helpful and responsive or are things falling through
the cracks? In the latter case, please list any open issues that need to be
addressed.
- They are helpful.
Signed-off-by:
(iotdb) Justin Mclean Comments:
(iotdb) Christofer Dutz Comments:
(iotdb) Willem Ning Jiang Comments:
(iotdb) Kevin A. McGrail Comments:
-----------------------------------
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
<jm...@apache.org> 于2019年6月1日周六 上午8:38写道：
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 19 June 2019, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, June 05).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> ----------------------
>
> Your report should contain the following:
>
> * Your project name
> * A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> * A list of the three most important issues to address in the move
> towards graduation.
> * Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> * How has the community developed since the last report
> * How has the project developed since the last report.
> * How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/June2019
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Note: The format of the report has changed to use markdown.
>
> Mentors
> -------
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>