-
Notifications
You must be signed in to change notification settings - Fork 188
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
Dead / Stagnant Project #936
Comments
Maybe you are not aware but I am a direct communication with the developer, who have their own private repository. They openly admit the project is dead. I'm just attempting to get them to admit it publicly. The company was restructured and bought out and no longer maintains this software publicly. I have a very novel idea, and it involves others, not policing one another for valid issues or discussion topics. |
Ya, the maintainers have been silent for a long time
|
This is very sad to hear. I'd been trying to contact people I know then too and I was getting concerned about the radio silence. Seeing people at different companies via LinkedIN was another clue. Add in the corporate website being down and yea, it's time to do the right thing and tell people its dead. Guess I'll migrate to MooseFS.. |
Their website is back up again: |
Nothingburger. The site has pretty much always been up for years. The company went private and may have ported the codebase as a proprietary software stack. This means that unless other programers maintain the existing code it's essentially a dead project from a development perspective. I wouldn't except future features or bug fixes. |
Anon,
Yea, I figured that and didn't respond earlier. Since folks stopped
responding to me in fall of 2023, I had been very concerned so this was the
final nail in the coffin. Since this post, we've been draining our cluster
so we can move.
Honestly, this is a sad ending after what LizardFS has previously
overcome. I had been using and promoting it for years but it is really
time for them to announce what is going on so everyone can migrate.
…On Fri, May 3, 2024 at 4:19 PM anon314159 ***@***.***> wrote:
Their website is back up again: https://www.saashub.com/lizardfs-status
Nothingburger. The site has pretty much always been up for years. The
company went private and may have ported the codebase as a proprietary
software stack. This means that unless other programers maintain the
existing code it's essentially a dead project from a development
perspective. I wouldn't except future features or bug fixes.
—
Reply to this email directly, view it on GitHub
<#936 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFY3WZWSHRZ36JDUM5NPZDLZAPWMNAVCNFSM6AAAAABBZ35JTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJTG4YDMMRXG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hello,
I have been considering migrating from GlusterFS to LizardFS for a variety of reasons. I digress, I already started migrating some of my company's high valid data to MooseFS CE since replication is acceptable but would like to utilize the erasure codes capabilities not found in MFS's CE, henceforth LizardFS. But upon further research it seems like this project is completely dead/stale. If this is the case the maintainers really should come out and admit this publicly.
The text was updated successfully, but these errors were encountered: