Concept Introduction
Recently, I asked a wise friend a question about the state of the Conquer Online development community. He gave me insight to a major shortfall in the community: our ability to cleanly share code snippets and debug code. With the current source variations, code cannot be shared between projects. Debugging and programming new features for Conquer Online servers are difficult, as the bases of most sources are different and poorly designed. There is a strong need for standardization: one open-source library that consists of interfaces and reusable modules, designed by a skilled team of programmers and designers. Once established, all servers must implement the standardization library. Although I cannot enforce this rule in this community, I can in another and would like to invite Elitepvpers in the standardization effort. By doing so, programmers will be able to share code that "can be seamlessly integrated between different projects". Bugs would be easier to isolate and fix, and sources would scale a lot faster and more effectively.
How does Standardization Work?
Standardization doesn't just include the rules and standards for software development; it includes the people and the process of creating and using the standards. Standards must be approved of by the community implementing the standards; therefore, in order for this project to succeed, the community must work together towards the standardization effort. We need both designers and programmers: people working in source control on the standardization library, and people working on sources that implement the library and provide feedback.
Project Roles
This project is very much a software engineering project. It's a large project by a team of programmers; therefore, we need to give ourselves roles and responsibilities to managing the project. As an experienced project manager and project owner, I would like to offer my services in managing the project roles and contributing to the design of the library. Below is a list of the roles I would like to see filled (multiple people per role).
Project Owner: manages the requirements of the entire project, the communication between teams, and release through source control.
Project Managers: manages modules in the project, the requirements and timeline of developing those modules, and communication between team members.
Software Engineers: works with the managers to develop modules that meet the need of the community.
Test Engineers: works with the managers and programmers to specify the needs of the community and test modules in development.
Getting Involved
Interested in supporting the project? Let me know below. The more support we have and more roles we have filled, the better we can make this community and turn it around. If I see enough support for a project like this, I'll create the project and forums for standardization, and start bringing the developers together. Also, if you could fill out the poll above, I would love to see your feedback. Thank you for your interest and support.
Recently, I asked a wise friend a question about the state of the Conquer Online development community. He gave me insight to a major shortfall in the community: our ability to cleanly share code snippets and debug code. With the current source variations, code cannot be shared between projects. Debugging and programming new features for Conquer Online servers are difficult, as the bases of most sources are different and poorly designed. There is a strong need for standardization: one open-source library that consists of interfaces and reusable modules, designed by a skilled team of programmers and designers. Once established, all servers must implement the standardization library. Although I cannot enforce this rule in this community, I can in another and would like to invite Elitepvpers in the standardization effort. By doing so, programmers will be able to share code that "can be seamlessly integrated between different projects". Bugs would be easier to isolate and fix, and sources would scale a lot faster and more effectively.
How does Standardization Work?
Standardization doesn't just include the rules and standards for software development; it includes the people and the process of creating and using the standards. Standards must be approved of by the community implementing the standards; therefore, in order for this project to succeed, the community must work together towards the standardization effort. We need both designers and programmers: people working in source control on the standardization library, and people working on sources that implement the library and provide feedback.
Project Roles
This project is very much a software engineering project. It's a large project by a team of programmers; therefore, we need to give ourselves roles and responsibilities to managing the project. As an experienced project manager and project owner, I would like to offer my services in managing the project roles and contributing to the design of the library. Below is a list of the roles I would like to see filled (multiple people per role).
Project Owner: manages the requirements of the entire project, the communication between teams, and release through source control.
Project Managers: manages modules in the project, the requirements and timeline of developing those modules, and communication between team members.
Software Engineers: works with the managers to develop modules that meet the need of the community.
Test Engineers: works with the managers and programmers to specify the needs of the community and test modules in development.
Getting Involved
Interested in supporting the project? Let me know below. The more support we have and more roles we have filled, the better we can make this community and turn it around. If I see enough support for a project like this, I'll create the project and forums for standardization, and start bringing the developers together. Also, if you could fill out the poll above, I would love to see your feedback. Thank you for your interest and support.
