> > > My suggestion is in team Mame/Mess dev should divide two parts: one part for Mame > > > work,the other is for Mess > > > > A lot of the code is used in both, how would that work? > Can these change help the emulation work for Mame/Mess,or these changes can help > improve those games in not working list for Mame/Mess?
The MAME project itself is very much merged right now and will not be splitting up. The codebase for MESS was merged into MAME's active codebase for nearly 2 years now as well as the Developer pool. "Devs" are real people with real lives and will work towards improving the project when spare time and/or desire hits them.
What you are suggesting seems to me you want to be able to arbitrarily assign a developer to a certain project or task, creating checklists, enforcing timetables for completion and otherwise require Devs to "xxx amount of work per xxx" schedules. People tend forget this is purely a project built on volunteer effort and not a business or a other entity which is required to appease stockholders, upper management or end users.
As much as we all want sound in this game, proper graphics in that game, or even a game to be playable, this is the wrong way to approach it.
|