deepThought
New member
Hello guys, I'm new on the forum (will take time to present myself a bit later).
As a dev, I'm pretty used to manage my software with versionning tools like GIT.
Since I see lots of fixes/mods here and there on the forum, I think it'd be great to provide each engine/module it's own repository on github so everyone could fork those modules, share their fixes/enhancements, submit pull requests and issues.
Honestly, I don't get why it's not done already (unless I missed it somewhere) since this kind of tool is so useful once you get used to it, you can access the log of each commit, export the repo in a zip file (useful since in 4.0.12 you can import/export zip files), branch the software into dev/alternate branches which gives you the ability to merge the modifications into the distributed branch (master) without breaking anything or even roll back in case of any mistake.
Since the modules could already be downloaded freely, I don't see any reason why not to share them on github or any gitlab out there.
Well, I hope you get the point, like that, the dev team could focus more on the NESm app and the community could debug/upgrade most of the different modules at the same time.
I'm pretty sure there are some asm gurus hiding somewhere nearby eager to share their knowledge in an easier way than posting code which will get lost in old forum posts.
Anyway guys, that my suggestion, do not hesitate to ask for help or more details about GIT, it seems like @cornphillips is also used to work with GIT so I'm sure him, me or somebody else will be glad to answer your questions. With all the details (github account, files hierarchy, some things I don't have in mind atm) it could be done in a few minutes, so I'll be glad to do it for you if needed.
As a dev, I'm pretty used to manage my software with versionning tools like GIT.
Since I see lots of fixes/mods here and there on the forum, I think it'd be great to provide each engine/module it's own repository on github so everyone could fork those modules, share their fixes/enhancements, submit pull requests and issues.
Honestly, I don't get why it's not done already (unless I missed it somewhere) since this kind of tool is so useful once you get used to it, you can access the log of each commit, export the repo in a zip file (useful since in 4.0.12 you can import/export zip files), branch the software into dev/alternate branches which gives you the ability to merge the modifications into the distributed branch (master) without breaking anything or even roll back in case of any mistake.
Since the modules could already be downloaded freely, I don't see any reason why not to share them on github or any gitlab out there.
Well, I hope you get the point, like that, the dev team could focus more on the NESm app and the community could debug/upgrade most of the different modules at the same time.
I'm pretty sure there are some asm gurus hiding somewhere nearby eager to share their knowledge in an easier way than posting code which will get lost in old forum posts.
Anyway guys, that my suggestion, do not hesitate to ask for help or more details about GIT, it seems like @cornphillips is also used to work with GIT so I'm sure him, me or somebody else will be glad to answer your questions. With all the details (github account, files hierarchy, some things I don't have in mind atm) it could be done in a few minutes, so I'll be glad to do it for you if needed.