Hi Mnemonic Contributors and PMCs I have prepared the following report for your review. it will be submitted before Nov.11, Please don’t hesitate to hit reply with any questions. =====================
Description: Apache Mnemonic is an open-source Java library for durable object-oriented programming on hybrid storage-class memory(e.g. NVM) space. It comes up with durable object model (DOM) and durable computing model(DCM) and takes full advantages of storage-class memory to simplify the code complexity, avoid SerDe/(Un)Marshal, mitigate caching for constructing next generation computing platforms. Mnemonic makes the storing and transmitting of massive linked objects graphs simpler and more efficient. The performance tuning could also be mostly converged to a single point of tuning place if based on Mnemonic to process and analyze linked objects. The programmer is able to focus on the durable object oriented business logic instead of worrying about how to normalize/join, SerDe(un)marshal, cache and store their linked business objects with arbitrary complexity. Issues: There is a roll call to decide to retire this project, but it has been supported by several contributors, so we decided to reboot it. Activity: In this period of reporting, 5 of tickets have been created and 3 resolved, basically, we are working on migrating Maven build to Gradle for efficiency and flexibility. There is a roll call to decide whether to retire this project and we conclude to reboot. We have come up with a HL community plan as follows. Project goal: To deliver a pre-product durable object model library that is working along with abstract software layers of hybrid memory and high performance storage, e.g. PMem, FS, KV Store at the end of next year (2021). Project core values: • Unified durable object model • Reduced burden of SerDe process Project objectives 1) A stable and efficient CI system 2) An improved documentation and website ◦ Highlight core values ◦ Usage guide ◦ Performance benchmark 3) Verified code quality and testing ◦ Unified interfaces ◦ Quality test cases ◦ Building system / CI ◦ Release process 4) Adding Redis as one of back-ends of durable object 5) Supporting JDK14 ◦ Leveraging an incubating feature of non-volatile mapped byte buffers Project Milestones 1) Dec. 2020, Gradle migration (v0.14.0) 2) May. 2020, Improved code quality (v0.15.0) 3) Jul. 2021, Redis backend and document/website (v0.16.0) 4) Dec. 2021, JDK15 support (v0.17.0) Project Communication 1) Biweely meeting ◦ community activity ◦ bug fixes and features ◦ feedback and improvement 2) Event based release meeting ◦ scope and objectives ◦ version release ◦ release process 3) Maillist, Jira, PR based discussion ◦ technical topics ◦ PR reviews, feedback 4) Management meeting on demand ◦ planning, road-map, growth ◦ goals alignment ◦ mentoring, training, events ◦ process improvement ◦ financial/budget advice We decided to keep current PMC unless explicitly requested. we don't expect to complete Gradle building before next project reporting (Nov.11). we expect a new minor release at the end of this year. Health Report: After reboot, we have 3 more new PMCs, they like to manage this project together, we have held 2 conference calls during this report period. There are plans, actions and roles that have been fully discussed and defined. PMC Changes: - Currently 14 PMC members. - 3 PMC joined in Oct. 2020. Committer Base Changes: - Currently 19 committers (corrected according to whimsy). - 3 same committers joined in Oct. 2020. Releases: - Last release was v0.12.0 on Sep. 04 2018 - Still active development on next major version (0.13) ===================== Sincerely Gary
