MagicWall
Veteran OT User
- Joined
- Oct 12, 2008
- Messages
- 124
- Solutions
- 6
- Reaction score
- 344
New year, new aims, but...
From time when @edubart don't may maintain OTClient github repo (Nov 4, 2017), project was stopped significantely.
[RFC] Project needs a new maintainer · Issue #886 · edubart/otclient
I think that is serious problem for OTClient community and future of this project, so maybe we need to discuss this problem.
Now we have a lot of open pull request, fixed issues waiting to close and not even one project boards.
Statistics from previous year (2018):
Probably contributors want add more pull request but:
From time when @edubart don't may maintain OTClient github repo (Nov 4, 2017), project was stopped significantely.
[RFC] Project needs a new maintainer · Issue #886 · edubart/otclient
I think that is serious problem for OTClient community and future of this project, so maybe we need to discuss this problem.
Now we have a lot of open pull request, fixed issues waiting to close and not even one project boards.
Statistics from previous year (2018):
- Added 6 commits.
- Added 44 lines of code.
- Delete 15 lines of code.
- 22 Pull Request (6 accepted, 14 waiting, 2 closed by authors).
- 49 Issues (35 open, 14 closed).
Probably contributors want add more pull request but:
- Pull request code conflicts.
- High conflict risk if we want to add new C++ -> Lua feature (client and framework -> luafunctions).
- No possibility adding fork from fork (make impossible to add pull request and further work on it).