ARK new users engaging
Closed this issue · 6 comments
As for engaging new people to project
- Firstly, ARK needs to get rid of problems, that not allowed to try it just doing simple things with a guide and get working results(so we need client-server examples). It is even more important than overall quality when the project still is not popular enough. For ex., If ARK has Linux support, a user must have an opportunity to start without needing to generate files on windows and need to rename binaries after compiling. Minimum, we need to suggest a temporary alternative until we add full support.
- Secondly, we need to split the audience to users and developers who can help us with the server. Users want new functionality and code stability; they don’t want to see their code broken after server update. Developers need clear workflow and transparent policies. All of them wants Informative guides, of how to work with ARK. Until the project becomes sufficiently stable, the framework needs more developers to help than users.
- Article with comparison with other server solutions so that engineers could better understand for what task do they need ARK and maybe article that shows ARK performance
- Guides and code comments should be preferably in English to extend audience
-Newbie guides, even maybe ARK should have “Fast start video guide.” - Also, in my opinion, issues list and next version iteration plan should be opened for anyone. There should be a list of tasks that others can do to improve the project, the opportunity to offer their improvements. But it can’t be allowed to commit any upgrades to any nearest version because of quality and backward compatibility issues.
- ARK needs well-organized GIT development workflow. A server is a critical part of multiplayer game and developers who want to use it are interested in its stability. So they will use it if there will not be significant issues, server crashes, etc. I think ARK needs different workflow(for better quality control, for ex. for having stabilization period during which features commits are not allowed to branch, only bugfixes)
We can use this one: https://nvie.com/posts/a-successful-git-branching-model/
3.Need to develop community and encourage discussion actively. So ARK need a place, where the community will communicate(for ex. forum)
4. Also, let's discuss the target audience for the project. I think that now ARK is somewhat tricky for indie developers and they don’t need all scalability features. We can attract their attention later with fast development and cheap maintain(by solving deploying issues, adding cloud features - use a cheap server, but on overload there can be autoscale on cloud and e.t.c.), but now, in my opinion, ARK is fitting for professional teams, but not indie.
This document only invites for discussion, so please add comments.
We will think about your suggestion and figure out a better way to improve all these points.
Good job, thank you.
Also, I like the name ArkGame and logo, but it is entirely impossible to find it in search engines because All pages are occupied by a survival game with the name "ARK" and by its servers. It is worth thinking what to do with it.
@ascherbakhov I'll plan to merge another OS project and will change a new name. If you have any new names, welcome to give a suggestion.
Cool! What project do you want to merge? NoahGameFrame?
@ascherbakhov Not this project, it's PSS and a friend who tries to develop a mini program in WeChat. We plan to improve ARK by using some new ideas. We are still discussing it.
@ascherbakhov
Hi, I have added document website by using gh-pages, will finish the contents. maybe you can continue doc translation in branch gh-pages. https://docs.arkgame.net