-
Notifications
You must be signed in to change notification settings - Fork 123
Anyone interested in a hard fork? #338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can I become a maintainer? |
Hi folks - maintenance is on. There have been some small changes to the release process. We're in the process of adding features like bulk delete, and aggregations as we speak. Part of the explicit reason for the delay is that we've brought on a PM (@thomascaudron) and asked him to help prioritize things so that we work on the right things - this is especially true as GitHub issues doesn't reflect a complete list of asks. I'd ask that we maintain any and all feedback we have for all OM clients in these issues, so that @thomascaudron can help us out! On the plus side, there's nothing we love more than issues/feature requests, and pull requests! It definitely helps us meet the needs, and embrace the community, while we work to build a great client. |
Closing this issue because it is still an active project. At first, i thought it was abandoned! Ma bad! Anyways, hoping to see a new release soon. |
@wiseaidev I'll try and look today. Saw the six comment previously and immediately ❤️ Baby steps my friend! Ninja edit: And ignore me... @dvora-h is so much faster at this than I am :D |
Uh oh!
There was an error while loading. Please reload this page.
Hey everyone. Since this project is not actively maintained anymore, the last release was around 3 months ago, and I am thinking to release a new package/version based on a fork I am currently working on that includes all the patches, additional features, docs... Is anyone interested? Is it ok @simonprickett @ everyone to do so? How about licensing? Do i need to release it under the MIT license?
The text was updated successfully, but these errors were encountered: