Quote:
fork (http://www.webopedia.com/TERM/f/fork.html)
To split source code into different development directions. Forking leads to the development of different versions of a program. Forking often occurs when the development of a piece of open source code has reached an impasse. The project is forked so that the code can be developed independently in different ways with different results.
|
Had to look it up since I wasn't really sure exactly what a "fork" was. And I guess for me to fully understand what this means, I had to look up the true meaning to what the word "impass" means (
http://en.wikipedia.org/wiki/Impasse); in short, it's like a stalemate in a chess game, for whatever reason - in our case, we are at an "impass", due to simple lack of comunication.
I guess already there has been a "fork", when the original dev(s) were booted out, for whatever reasons. If the original Devs decide to continue their direction, then they will rightfully hold the original source, and what we have now is a fork? How about the databases: should they be considered as part of the "source" , and if so, where is the original database that should have been what we all worked on?
Quote:
Originally Posted by TheLieka
I'd prefer to see an attempt at reconciling the current communication issues before someone jumps the gun and forks the project. I don't think it will help anyone to split EQEmu into distinctive factions. All it would take is reopening these closed communication channels to get things back on track, but again, it's up to the devs to step in here and post their thoughts.
|