RomRaider

I personally don't have the time to do much except minor bugfixing and it sounds like most people will be in the same boat. Wife, kid, full-time job and 2 on the side contracting jobs already keep me more than busy enough. I will try to look at the 3D, stuff if I can get the time!

I do agree that now is the time to finish the major overhaul which gives us the base we need to proceed into the future.

The current code works well with it's given feature set and should be branched into maintenance mode. I'd be willing to take that over, but for new stuff I just don't have the bandwidth.

I personally don't care for the everyone has their specific job title thing. If someone sees an area they can help in, they should jump right in. Let anyone wear whatever hat they want.

In the end, let the code speak for itself!

I was speaking more along the lines of as the project gets large (more ECU support, etc) about the titles/organization and stuff as the amount of work could start to grow exponentially. I have been in several startups where this happens and without a sound way to divide up roles and tasks, things fall apart. Anyway, the project is not that big yet and it might never get that big. I prolly just have big dreams.

It sounds like there are just a few things to wrap up and it still is managed pretty well. Lack of time is definitely an issue with any open source project, and having some modularity starts with a managment strategy and dividing up specific tasks/roles. This can probably just be revisitted when we all have some time to complete our given tasks. By that time, ramtune and all the neat features should be close to completion. Seems like we are just churning here (in this thread) and what is in place right now will work for the time being.

So Ima get back to work. I keep browsing the flashing code from time to time until I have the time to sit down and start stripping it apart.

-Gabe

We could simplify RamTune a bit making it easier to develop on the RomRaider side. Instead of allowing the user to select profiles of any combinations of 20 maps, we could just have, say, 4 set of pre-chosen maps that the user has to choose from. They would have to flash the rom if they switched from one set to another. The rom code would be virtually the same and it would still allow for map switching. It would just be that RomRaider wouldn't have to deal with the interface necessary to create/edit/transfer profiles and the associated headaches with a dynamic assortment of tables. Since the 32bit ecus don't have an issue with ram, this is likely how we would do it anyway for those ecus as well. Therefore, if we do this for the 16bit ecus, it will at least be consistent.

Good idea, Merchgod, I like it.