02-06-2016, 08:29 PM
Since the open sourcing of our gamemode last year, we've seen some very cool pull requests from many different people proposing changes to Las Venturas Playground.
As amazing as they are, neither Pawn nor JavaScript are always equally easy, and with about a hundred thousand lines of code it's not always straightfoward to judge the impact of your change at all. Or, at a slightly higher level— does the change compile at all?
In order to make this easier, we're working on a number of projects to make contributing to Las Venturas Playground easier. We've introduced a Code of Conduct that outlines how we'd like to be treated and still have plenty of other ideas on future improvements.
Today, we're introducing continuous integration testing for all pull requests.
What does this mean? Take a look at this pull request. While a more experienced developer will be able to judge that the minor changes will introduce some errors, we've now got an automated tool that will tell you exactly what is wrong with a pull request in case of issues.
This should make it a lot easier to propose changes, and will help us avoid breaking the server on unexpected issues while doing updates.
We'll do a broader post to announce the full suite of changes we have in mind soon. For now, please let me know if you have any further questions!
As amazing as they are, neither Pawn nor JavaScript are always equally easy, and with about a hundred thousand lines of code it's not always straightfoward to judge the impact of your change at all. Or, at a slightly higher level— does the change compile at all?
In order to make this easier, we're working on a number of projects to make contributing to Las Venturas Playground easier. We've introduced a Code of Conduct that outlines how we'd like to be treated and still have plenty of other ideas on future improvements.
Today, we're introducing continuous integration testing for all pull requests.
What does this mean? Take a look at this pull request. While a more experienced developer will be able to judge that the minor changes will introduce some errors, we've now got an automated tool that will tell you exactly what is wrong with a pull request in case of issues.
This should make it a lot easier to propose changes, and will help us avoid breaking the server on unexpected issues while doing updates.
We'll do a broader post to announce the full suite of changes we have in mind soon. For now, please let me know if you have any further questions!