The Great Module Audit and Merge-athon v2.0! #3737
Edit: More details added for maturity levels, rules for our Merge-athon added - win prizes!
With GSOC ending and us having merged a lot of fundamental / API breaking things lately I'd like for us to do a round of module testing to catch our breath and make sure all the things are working - or at least compiling and running :-)
The zip I prepared earlier for this September's playtest is http://jenkins.terasology.org/job/DistroOmega/1056/artifact/distros/omega/build/distributions/TerasologyOmega.zip and can be used for testing the before-case as lots of modules will will have broken since, possibly subtly (most/all will compile, some/most will run, a few/some will work fine)
Read on for more details and join us on Discord: https://discord.gg/terasology
Maturity levels in summary:
I've only included the modules in the stable lineup for now but we might want to add a few more we want to focus attention on. For instance FlexibleMovement has been identified as high potential, but may not even compile just yet.
In some cases (like JS) it'll be hard to determine which module should count as working or not, but ... apply best judgement.
Good First Issue / Hacktoberfest
Testing modules and making small fixes is generally easy. You just need a workspace (see https://github.com/MovingBlocks/Terasology/wiki/Dev-Setup) then
Study the module some to figure out what it is actually meant to do so you can look at checkbox 3 and 4. Some modules have wikis, or even test plans. You can use the
For PRs (needed for Hactoberfest) you will actually need to find something broken and then fix it with a PR to the associated module repo :-)
Try to coordinate on our Discord just to avoid duplicate work and to ask questions. If you can't check the boxes directly here or need a whole bunch checked then also ask on Discord. And have fun!
For making a good PR see the template that should populate when you open a PR and https://github.com/MovingBlocks/Terasology/wiki/How-to-Work-on-a-PR-Efficiently
As an attempt to hurry along merging any outstanding work before checking the boxes below we will award $100 Amazon gift cards to the top 10 helpful contributors who put in work for testing and merging all the things. Note that this is also an experiment in gamifying contributions so expect the rules to change during the live period of October 5th-19th
We'll keep a private leaderboard and may extend the contest (after guaranteeing the top 10 as of October 19th), increase the number of gift cards, or add value to those going to particularly helpful contributors :-)
To get your points please ask on Discord and link to your work. Please be patient as it may be a little while before everything gets processed and responded to, but we'll get it!
SimpleLiquids (note: moved to our org archive, may need to reflect here and elsewhere)
The text was updated successfully, but these errors were encountered:
Dig around in our project documentation for more, like starting with https://github.com/MovingBlocks/Terasology/wiki/Dev-Setup and hop on our Discord to ask further questions if needed! https://discord.gg/terasology
Thanks @monique1087 , Contributing is very easy , just fork the repo then clone it into your local machine, create a branch and make commit changes then push them to the github, remember your original repository should be updated for pull request to be successful. Any help please am here to help you thanks. Am sorry for late reply…
On Sun, Oct 6, 2019 at 8:55 AM monique1087 ***@***.***> wrote: Hello! My name is Monique and I want to contribute. How could I proceed? Have a nice day! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3737?email_source=notifications&email_token=ALOKS6BLU5DDBHYRCQ7X5PLQNIC5NA5CNFSM4IURDU32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAONJEI#issuecomment-538760337>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALOKS6HJY4WQSG2VRVB2FWTQNIC5NANCNFSM4IURDU3Q> .
Update: All modules have been built (or fail to build) in the new Jenkins' mega module build job. I've checked off most of them with a few remaining that need a closer look. They're either failing for legitimate compile issues (like Alchemy seemingly is) or possibly need some more poking in Jenkins.
The failing modules of interest as of right now are: