Openkore community, we need to talk.
Posted: 13 Mar 2012, 12:16
Too long; dint read: You, the community needs to step up to get involved or else this project will die a slow tragic death.
The story of a problematic relationship being dragged along its limping feet because the two parties in it refuses to acknowledge the problem in front of them in hopes that maintaining the illusion of normalcy can make the problem disappear is a tragedy waiting to happen. We are all too familiar but this is what openkore's situation is.
The truth is that it is neither new and sadly is not just a phase but has become a fact of life for Openkore 3 years now. Openkore at the moment has about 5 active devs (none of whom who plays the game) and even less moderators (maybe 3). Posts from newly registered users someone takes weeks to approve. At one point was in months. The idea was to reduce newbie questions from flooding the forum but it was not a real solution as it was just fixing the symptom. In reality it was worse as without proper manpower (hey we have real life too) to moderate (which by the way is a shitty job that not many wants to do) even good post gets ignored and that damages the health of the project more than it solves problems. And yet that is only part of the problem. You may ask why not recruit more mods? But where from?
Look around the support forums and you will see large number of questions being unanswered. The community is supposed to help itself, not just the job of the mods, admins or developers. A lot of original posters do not even reply back. I get the feeling that after correct direction was provided (say to obtain server info)no shit was given. The same question reappears 3 days later.
Then there is the obsession with macros. It is probably the most active section yet it still falls prey to the same issue as the support section but that is however not the main issue. The obsession means many features (some which can be considered core or important functions) gets solved in a half assed way while a true solution (through the main codebase and plugins) get ignored while it. Macros were designed for simple workarounds and have massive limitations (eg: macros break when disconnects happen) when dealing with complex requirements. Plugins are supposed to resolve that need yet the plugin archive is awfully sparse and woefully outdated.
Which comes to the final and worst problem - leeches. Our attitude towards leeches has always to demonize them because they do not give back to the community but the expectation for all users to come back and contribute is silly and unrealistic. Yet, there should be more than a mere handful of people who maintain the project for such a large userbase. I feel that a large part of the skilled userbase refuse to contribute back for fear of losing their edge in the game and it is selfish. Often you see posts which states "problem solved" and nothing else or worse brags about the solution with an emoticon at the end of the post. This attitude is what lead us here in the first place and if it continues the project can die at a whim's notice. The devs do not even play, do you understand the implication? Given enough frustration, they can just don't care and that will be the end of openkore. Have fun trying to make anything work when things break (as if openkore isn't breaking down as it is).
I would like to point out to the zenny sellers; look, you guys are very skilled users probably with deeply intricate setups. You know openkore and you have utilized it to your benefit, monetary benefit and probably not just pocket change either. It is time you give back because you have the most to lose.
I am surprised the project survived this long. We are maintaining a software that is running at the minimum it requires to work and many other non critical components are left breaking down (tables for renewal for example) and we are helpless to resolve it. It's time to step up because the alternative is openkore dying before RO. Maybe this is how it is, it is the life story of many open source projects. Prove me wrong though.
The story of a problematic relationship being dragged along its limping feet because the two parties in it refuses to acknowledge the problem in front of them in hopes that maintaining the illusion of normalcy can make the problem disappear is a tragedy waiting to happen. We are all too familiar but this is what openkore's situation is.
The truth is that it is neither new and sadly is not just a phase but has become a fact of life for Openkore 3 years now. Openkore at the moment has about 5 active devs (none of whom who plays the game) and even less moderators (maybe 3). Posts from newly registered users someone takes weeks to approve. At one point was in months. The idea was to reduce newbie questions from flooding the forum but it was not a real solution as it was just fixing the symptom. In reality it was worse as without proper manpower (hey we have real life too) to moderate (which by the way is a shitty job that not many wants to do) even good post gets ignored and that damages the health of the project more than it solves problems. And yet that is only part of the problem. You may ask why not recruit more mods? But where from?
Look around the support forums and you will see large number of questions being unanswered. The community is supposed to help itself, not just the job of the mods, admins or developers. A lot of original posters do not even reply back. I get the feeling that after correct direction was provided (say to obtain server info)no shit was given. The same question reappears 3 days later.
Then there is the obsession with macros. It is probably the most active section yet it still falls prey to the same issue as the support section but that is however not the main issue. The obsession means many features (some which can be considered core or important functions) gets solved in a half assed way while a true solution (through the main codebase and plugins) get ignored while it. Macros were designed for simple workarounds and have massive limitations (eg: macros break when disconnects happen) when dealing with complex requirements. Plugins are supposed to resolve that need yet the plugin archive is awfully sparse and woefully outdated.
Which comes to the final and worst problem - leeches. Our attitude towards leeches has always to demonize them because they do not give back to the community but the expectation for all users to come back and contribute is silly and unrealistic. Yet, there should be more than a mere handful of people who maintain the project for such a large userbase. I feel that a large part of the skilled userbase refuse to contribute back for fear of losing their edge in the game and it is selfish. Often you see posts which states "problem solved" and nothing else or worse brags about the solution with an emoticon at the end of the post. This attitude is what lead us here in the first place and if it continues the project can die at a whim's notice. The devs do not even play, do you understand the implication? Given enough frustration, they can just don't care and that will be the end of openkore. Have fun trying to make anything work when things break (as if openkore isn't breaking down as it is).
I would like to point out to the zenny sellers; look, you guys are very skilled users probably with deeply intricate setups. You know openkore and you have utilized it to your benefit, monetary benefit and probably not just pocket change either. It is time you give back because you have the most to lose.
I am surprised the project survived this long. We are maintaining a software that is running at the minimum it requires to work and many other non critical components are left breaking down (tables for renewal for example) and we are helpless to resolve it. It's time to step up because the alternative is openkore dying before RO. Maybe this is how it is, it is the life story of many open source projects. Prove me wrong though.