i'd like to know the status of this project. It hasn't seen an update in almost a year. Pull requests are piling up with features that are very much needed and wanted by the community.
@praeclarum any thoughts?
It's called OPEN SOURCE. Which means absolutely no reliability. The maintainer can sign out from it with no excuses needed.
Sad but this is the reality.
I'd definitely contribute with some $ if the maintainer asks for it.
Unfortunately he didn't setup any way to contribute yet.
I wish it becomes a standard for open source to ask for $ contribution when the creatormaintainer really wishes to maintain his work ONLY IF there's enough $.
Otherwise, with no such contribution plan setup, this really means the creator has no intention of contributing. And this kind of work needs to be seen with caution.
Ona can always fork an open source project and carry on. If there are people interested in this, we can setup a new one.
@opcodewriter i'd like to extend your point though, since this is open source, the creator/maintainer must let others "maintain" this and make others accept pull requests on his stead, since open source SHOULD be about the community building a better product. but sad that this is still the way open source is perceived. always on the brink of obsolescence.
@superyetkin I think we can say, there is a pretty big number of people interested in this project as seen in the issues tracker and pull requests. the challenge will be to herd these developers to another fork and make them feel assured that this will be maintained much better.
If anyone is interested, I have a new repo that targets Sqlite and is cross platform ( .NetStandard 2.0). It is in the early stages of development, but I believe provides the features of this inactive repo. Entities.Sqlite.
If there is an active owner to this repo, please feel free to delete this comment. I only want to offer an alternative if this repo is inactive.
If anyone is interested, I have a new repo that targets Sqlite and is cross platform ( .NetStandard 2.0). It is in the early stages of development, but I believe provides the features of this inactive repo. Entities.Sqlite.
This is actually not completely true. To name only a few:
dynamic which is a no-go if you are targetting iOSWould you be keen on including these constraints?
@Weldryn I don't want to hijack this repo! I thank-you for your input and have created the following issues:
achilles-software/entities.sqlite#7 and achilles-software/entities.sqlite#8
Thank you for your concern over this repo.
Most helpful comment
If anyone is interested, I have a new repo that targets Sqlite and is cross platform ( .NetStandard 2.0). It is in the early stages of development, but I believe provides the features of this inactive repo. Entities.Sqlite.
If there is an active owner to this repo, please feel free to delete this comment. I only want to offer an alternative if this repo is inactive.