Differences between revisions 2 and 3
Revision 2 as of 2016-09-23 09:04:44
Size: 1279
Editor: KaiJaeger
Comment:
Revision 3 as of 2017-08-24 07:16:25
Size: 1292
Editor: KaiJaeger
Comment:
Deletions are marked like this. Additions are marked like this.
Line 18: Line 18:
 * Run the test cases. (For all APLTree sub-projects that means execute `#.TestCases.RunDebug 0`). You are not expected to check in without all tests passing, and covering all new methods/features by new/additonal test cases.  * Run the test cases. (For all APLTree sub-projects that means execute `#._{ProjectName}.TestCases.RunDebug 0`). You are not expected to check in without all tests passing, and covering all new methods/features by new/additonal test cases.
Line 20: Line 20:
 * Optionally write an email to kai@aplteam.com and explain your idea/changes. Note that it might not be a bad idea to do this first.

Your changes / additions will then be checked and either discussed or incorporated.
 * Optionally write an email to kai@aplteam.com and explain your idea/changes. (Note that it might not be a bad idea to do this first) Your changes / additions will then be checked and either discussed or incorporated.

How to contribute to an APLTree project

There are two very different ways for how you can contribute to any APLTree project:

  • Use the GitHub repository of the APLTree project in question.

  • Use acre, PhilLast's excellent source code management system used for the APLTree project.

While the latter gives you more opportunities, the former is easier to start with, so here we explain just this route.

The sole purpose of the APLTree-related GitHub repositories at https://github.com/aplwiki/ is to make contributions as easy as possible.

Perform the following steps:

  • Clone the repository.
  • Load the workspace.
  • Make your changes.
  • Save the workspace.
  • Run the test cases. (For all APLTree sub-projects that means execute #._{ProjectName}.TestCases.RunDebug 0). You are not expected to check in without all tests passing, and covering all new methods/features by new/additonal test cases.

  • Initiate a pull request.
  • Optionally write an email to kai@aplteam.com and explain your idea/changes. (Note that it might not be a bad idea to do this first) Your changes / additions will then be checked and either discussed or incorporated.

For advice how to use acre in order to contribute to an APLTree project see TheAPLTreeProjectAndAcre.

HowToContributeToTheAPLTreeProject (last edited 2017-08-24 07:16:25 by KaiJaeger)