-
Notifications
You must be signed in to change notification settings - Fork 442
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
I want to continue the project as a new repo #601
Comments
If you like to create, say, a 2.0 version, then I think it would be beneficial to keep it in this repo. That said, feel free to start a fork, and maybe eventually open a PR to get it merged to the main repo. But beware, creating a library might not be that hard, but maintaining is no trivial task by any means. And you wouldn't be the first to attempt to give this library a new, without success. I've done a lot of work on this project, but I didn't want to move solely on my own, which caused development to get stuck on waiting for reviews. |
Hi @koenpun, I did not fork this repo. I cloned and uploaded it in my github account. So, I got all commits, but here is no issues, no PR. I am building an MVC framework (https://github.com/iceboxphp) and using ActiveRecord in my project.
|
It looks like, this project is inactive for more than 1 year. I really like this library, very straight forward, minimal features. Only missing part is the migration. I am not here to argue about anything.
What I want to do is, I want to continue the project as a new repo in github.
Is anybody here to help me to make decision.
Is version 1.2.0 (latest version) is stable enough to use in large scale application? I mean, can there be any known security issue?
Do I need to change directory structure? suppose, I convert to psr-4. Is current directory structure will reduce performance?
Please share what you think. Thanks.
The text was updated successfully, but these errors were encountered: