ZaKaX read your PMs.
momo61 i will not delete your posts on this topic, but stop it, if you dont then i will remove them all.
Keep your personal matters out of this forum from now on, i know you hate each other so fight over MSN or Email or whatever you want but OUT OF THIS FORUM, this goes for both of you.
Lets go by parts, lets start about the L2j Hierarchy
As in any project we need some organization to keep certain order in our work, i tried to simplify the way of how this order is stablished, maybe on a future i would have time to put the duties and responsabilities of each team in L2j, as you can see this hierarchy has two branches, the ones with Developers and the one with the Community, your vision of coaching a whole community is really impresive, but you need to stick to the reality, you cant really coach more than 14.000 users people efficiently, even if this amount doesnt reflect the current active L2j users, lets talk about 1.000 users to keep it small, is still hard to do, i have studied management and organization procedures in the college, and they all recommend that you need to divide in smaller groups the amount of people to manage, because you will be overflowed by them, is better to coach properly an small amount of people than coaching badly a big amount since you cant really focus on all of them at the same time, how come you can keep an eye on 1.000 users and follow them individually to see where they do wrong or they do right? is almost impossible to dont say that isnt possible.
Here is where it borns the Advanced Users idea, if you have read the first post, the goal of this group are:
- Providing Quality Support to other Community Members through forums.
- Testing 0-day patches
- Testing New Features before being commited to the SVN
- Testing New Releases during Closed Development
- Providing Retail Gameplay Information
- Providing feedback about our work and the Community.
- Idleing on IRC with us
- Becoming Wiki Editors
- Getting involved in team decissions.
Managing the community as a whole is really hard to accomplish, maybe with a smaller community it would be possible but when you exceed an amount of people in this community is starts to get "difficult" when *fork* you have a limited number of people working on it, and is easyer to get in touch with everyone that way, but with BIG things, you need BIG ideas and BIG decisions.
About DrLecter rare sights i have to say that he is on the process of retirement, he has done a great job over the years, with more than 1.200 commits since 2005 but once in a time you find that you have to work to live, be with your wife and childrens so time is limited to develop and contribute, anyways he tries to find free time and reads the Dev Private forums to give his throughs about the current discussions and ideas, his experience as developer and project leader is really valuable for us the "new" Inner Circle members, we can say pretty much about the rest of the Project Leaders as (Dalrond and Julian) they are still around teaching and coaching us mostly on IRC, but not actively developing so they will step down from their position in the next weeks and another one will take their chair.
You are badly wrong by saying that, with limited amount of time tries to keep up with the current private discussions and projects inside the Private Dev area and the IRC dev channel, i think that all the L2j Team members value a lot the effort that DrLecter makes to stay with us either than just "disappearing" from the scene. If you really need to get in contact with DrLecter i suggest you to write down a PM, of course, try to dont waste his time with stuff that you could manage to solve with the rest of us.theone wrote:I think this is very ego-centric on his part... no one is so "high and mighty" that he is above saying "hi" or "thank you" to the people who help his project on a daily basis. From my point of vue, it looks as if he thinks that all the contributors on his forum are "lower life forms" and that he'll talk only to the select few who he chooses to be part of his team. In other words BigBoss, please mind your own business if you're going to talk through your [I think I cant say this word here...].
I dont want to make any biased comment about this, but since you cant prove what are you saying because your project is private and closed source, there is no way to check this. And the word "create" is wrong in your argument since you "modified" an already existing project like L2j and i really doubt that you have modified more than the 10% of the code (about 90k lines of code) anyways you are always welcome to keep contributing pieces of code to our project, you are also an experienced and great developer that knows his kung-fu. If you think that you can make your code public then we may look at it and see where we can improve L2j with your modifications, or you could commit those modifications to our forums.theone wrote:With a team about 1/2 the size of your "official team" we managed to create an emulator much more complete and much more efficient than L2J
You can ask to ANY of the L2j Team members and they will say that everyone has voice and rights, they are all equal to us as developers, they are the group of people that we trust, feel free to ask any developer, some of them have made mistakes and they were pardoned because they learned their lesson, have you ever seen a notice saying "XYZ has been kicked from the L2j Team" here in L2j we learn from each other and we like to be who we are, we do not force anyone to stay or to leave, if something was "forbidden" to be commited (by Senior Devs) it was mostly because it didnt fulfiled our coding guidelines, mostly custom stuff and badly programmed contributions.theone wrote:you know why? because we consider our members as all equals! everyone has a voice, everyone has a right to make mistakes as long as he/she learns from them, everyone learns from everyone else.
That is what we try to accomplish with the recent changes and future ones.theone wrote:It's not by doing everything important behind closed doors that you'll better your project, but by opening yourself up to the community, because they are the future of your project, not you or your team, the community as a whole is the future of L2J.