Hi Chirs, Many thanks for your review of IoTDB. Under all mentors and all contributors' effort, the community is more healthy than before.
If there are no more opinions, I will copy the draft to the wiki page. Best, ----------------------------------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Christofer Dutz <[email protected]> 于2020年5月26日周二 下午3:10写道： > Hi all, > > I think your list of things to do before graduation is the voting issue. > You can't force user feedback and hereby it's tricky to work on it. > Of course you can always have more technical discussions on the list, but > I am already seeing more technical discussion as on some TLPs. > > The GSoC thing is really a pity ... I hope this won't happen again. > > So my gut-feeling tells me you folks are on a very good path. Your release > process seem to be working nicely. > I'm happy with the work the IoTDB podling is doing (from an ASF > perspective). > > Chris > > > > Am 26.05.20, 07:46 schrieb "Xiangdong Huang" <[email protected]>: > > Hi all, > > I finished a draft for the report, pls have a review. > > IoTDB > 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. > > *Q1: Three most important unfinished issues to address before > graduating:* > > - More active PPMC/Committers to join votes in the mailing list; > - More user feedbacks are wanted; > - More technical communications are welcomed to attract more committers > joining the project deeply. > > *Q2: Are there any issues that the IPMC or ASF Board need to be aware > of?* > > We proposed several tasks for GSoc2020, attracted several students > around > the world, and some of them had deep discussions with us on the Jira. > However, because of the permission issue of the community mailing list > for > incubating projects, we missed all the proposals from students and > failed > to join GSoc2020 this year (so no students applied GSoc > unsuccessfully). > More discussion had done on the dev@community mailing list. > Though our mentors helped us a lot, the doc on > http://community.apache.org/gsoc.html may need to be improved for > incubating projects. > > *Q3: How has the community developed since the last report?* > > 1. Suggested by Mentor Christofer, we moved the JIRA notifications to > a new > mailing list notifications@. > After that, there are 609 emails sent by 80 people, divided into 254 > topics > in these 3 months. > > 2. 4 new committers are elected (Dawei Liu, Wangminhao Gou, Yuyuan > Kang, > and XinWang), who come from 3 different companies/organizations. > > 3. A new PPMC is elected (Jincheng Sun). > > 4. Many new contributors joining us. For example, Giorgio Zoppi is > working > for TsFIle/IoTDB C++, Robinet integrated IoTDB with Apache Karaf, Xin > Wang > and Jincheng integrated IoTDB with Flink etc.. > > 5. The website is refactored. > - Now Google Search Engine can index it. > - The website provides a detailed User Guide and some System Designs > both > in English and Chinese. > - Meetup and other talk materials (slides and videos) are shared on the > website. > - More documents to let users joining us （like Code of Conduct, How to > be a > committer, how to release, how to vote new committers, etc..) are > provided > on the website or the wiki. > > 6. Dave Fisher shepherded us and pointed out some issues, and all of > them > are fixed. > > *Q4: How has the project developed since the last report?* > > - Two versions (v0.9.2 and v0.9.3) are released. They are done by two > new > Release Managers from the community. > > - The project keeps active, there are 553 commits submitted by 43 > authors > in these 3 months. (using the gitstats tool to get the result: > `gitstats -c > start_date=2020-03-01 REPO_NAME OUTPUT`) > > - IoTDB is integrated with Apache Karaf and Apache Flink. > > - IoTDB supports MQTT protocol. > > - IoTDB's cluster module is almost done. A PR is submitted. > > > *Q5: How would you assess the podling's maturity?* > *Please feel free to add your own commentary.* > > [ ] Initial setup > [ ] Working towards first release > [ ] Community building > [ ] Nearing graduation > [ ] Other: > > Comment: I think we can choose Community building or Nearing > graduation. > How do you think? > > *Q6: Date of last release:* > 2020-04-13 > > *Q7: When were the last committers or PPMC members elected?* > > 2020-05-18 for the last committer, 2020-05-14 for the last PPMC. > > *Q8: Have your mentors been helpful and responsive?* > > Yes. > > *Q9: Are things falling through the cracks? If so, please list any open > issues that need to be addressed.* > > Q10: I > *s the PPMC managing the podling's brand / trademarks?Are 3rd parties > respecting and correctly using the podlings name and brand? If not what > actions has the PPMC taken to correct this? Has the VP, Brand approved > the > project name?* > > Required Name Search is done. A google search didn’t show any major > branding issues that the PPMC needs to deal with. > > Best, > ----------------------------------- > Xiangdong Huang > School of Software, Tsinghua University > > > Kevin A. McGrail <[email protected]> 于2020年5月24日周日 下午12:12写道： > > > Hi IoTDB PMC, please let me know when a draft report is ready to > review! > > Regards, > > KAM > > -- > > Kevin A. McGrail > > Member, Apache Software Foundation > > Chair Emeritus Apache SpamAssassin Project > > https://www.linkedin.com/in/kmcgrail - 703.798.0171 > > > > > > ---------- Forwarded message --------- > > From: <[email protected]> > > Date: Sat, May 23, 2020 at 12:53 AM > > Subject: Podling Iotdb Report Reminder - June 2020 > > To: <[email protected]> > > > > > > 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, 17 June 2020. > > 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 03). > > > > 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/June2020 > > > > 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 > > > >
