-
Notifications
You must be signed in to change notification settings - Fork 233
Is this project still alive? #2149
Comments
@yarbelk - Unfortunately this project is not active, anymore. |
While we are not able to actively contribute to Pilosa at this time, please ask any questions in the slack support channel and we will be glad to help. We plan on resuming contributing to Pilosa sometime next year. |
what happened about this project? technical or business problems? |
See FeatureBaseDB/featurebase#2149 (comment) Closes #95805. Signed-off-by: Sean Molenaar <1484494+SMillerDev@users.noreply.github.com> Signed-off-by: BrewTestBot <1589480+BrewTestBot@users.noreply.github.com>
@yarbelk @ovasty @kuba-- We are open sourcing what the team has built from Pilosa. Please feel free to reach out with any questions you have. |
We're also available on Discord: https://discord.gg/PFyCFYw4gN |
Yay! I can start using this for things :) |
@yarbelk oh? What are you building over there? |
It's been a month, we're up and running. |
For bugs, please provide the following:
What's going wrong?
Not seeing activity for many months in github
What was expected?
see bugfixes etc.
Steps to reproduce the behavior
look at github
Information about your environment (OS/architecture, CPU, RAM, cluster/solo, configuration, etc.)
NA
For feature requests, please provide the following:
Description
Success criteria (What criteria will consider this ticket closeable?)
Update on status of pilosa
The text was updated successfully, but these errors were encountered: