Hi Yanhui, Thanks for initiating this topic and proposing the suggestions! It would definitely be helpful to have a mid/long term plan. I fully agree with suggestion 1 to improve the project to be more accessible to a broader range of developers. Frankly the project already has plenty of use cases and some documents. We could review what's missing in the next meeting and make a plan to complement the missing pieces, if any. In addition, a fully automated CI/CD pipeline could be considered to get the project production ready, as well as to facilitate future plugin development. I personally think this project is very close to v1.0 but would like to hear everyone's feedback.
Suggestions 2 and 3 are going to extend the features of the project. I would love to brainstorm ideas and put them in our roadmap. Also they could be features in v1.x versions so they don't gate the release of v1.0. Again, thanks for bringing up the discussion! Best, Li On Fri, Jul 23, 2021 at 7:11 AM Yanhui Zhao <[email protected]> wrote: > 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 > > >
