Dear Mnemonic PMC/Dev

We have had several releases done since our last reboot, and
recruited several new committers and PMC who would like to help us to build
Mnemonic a better project. As we enter the second half of this year, I want
to share some personal opinions and get your feedback for our next steps
ahead.

Our release iterations have been stuck at 0.1x for a while, partially
because our project slept for a while and lost momentum. To keep our
project growth and maintain a healthy momentum, we need to have a roadmap
to remind us, and show to our dev and potential users our next step.

Some suggestions are as follows
1. *Increase community engagement* by reducing the deployment dependencies
and improving *DOCUMENTATION*/use cases/examples*.* Those will
significantly lower the bar for any people who are curious about our
project and would like to give it a try or contribute to our project
2. *Build egosystem.* We currently have Hadoop and Spark support plugins in
our projects, which is a very good start. We plan to add more support for
other popular frameworks such as Flink, Redis, etc. I also suggest
splitting those third-party plugins out from our main projects, and
maintain each plugin separately in the form of sub-project to avoid growing
mnemonic too large and intimidating potential users and customers.
3. *Evolve along with the industrial needs and add new features.* Our
project started as a framework for storage backend services, but that
doesn't exclude us from adding other features to enrich its
functionalities. For example, data security has been getting much attention
in recent years. As a storage service, it is very natural we add security
features to guard stored data at our framework level, making Mnemonic more
competitive compared with similar project/product

Just my two cents, please also share your thoughts, suggestions and
comments. Based on your feedback, together we can make a roadmap and plan
for our v1.x release targeting early 2022.

Best Regards

Yanhui

Reply via email to