<commit_before>=======================
Subversion repositories
=======================

Repository
------------
The subversion repository for the project is set up as follows:

* URL: svn://svn.code.sf.net/p/chapel/code
         branches/
           collaborations/     -- used for external collaborators
           release/            -- used to capture release branches
         tags/                 -- used to tag releases
         third-party-norelease -- third party code not yet intended for release
         trunk/                -- our main development branch ($CHPL_HOME)

* Anyone can read the repository.

* To commit to the repository, you need a SourceForge account and
  permissions granted by a Chapel administrator.  If you are not a
  Cray employee, a contributor's agreement is required to obtain
  commit privileges.  Different versions of the form exist for
  students and government employees.  The forms can be found in
  $CHPL_HOME/doc/developer/contributorAgreements

* Most external collaborations of any scope will be encouraged to work
  in a project-specific branch in the branches/collaborations/ space.


External Contributor Notes
--------------------------
In general, external contributors should work using the following
guidelines, which are designed to protect the core Chapel team's
ability to make forward progress and meet their contractual
requirements:

* Recall that commits to subversion are extremely difficult to remove
  from the source tree's history, so be very careful not to commit
  anything that you will regret later.

* Please avoid committing third-party source code to any part of the
  repository without clearing it with a member of the core Chapel
  team.

* Commit changes to your branch as often as you find worthwhile; when
  committing merges of trunk/ into your branch, please try to minimize
  the number of commits required in order to avoid creating too much
  noise for developers or users who may be tracking the commits
  through email or RSS feeds.

* Most commits to trunk/ should be done with someone on the main
  development team in the loop in order to avoid stepping on toes.  If
  you have changes in your branch that you believe are ready and
  worthwhile to migrate to trunk, please work with someone on the main
  development team to review the changes and approve their inclusion.

* Adding new tests or future tests to trunk/test can generally be done
  without prior approval; just be sure that the tests work well within
  the testing system and that they are sorted into a reasonable
  location in the test hierarchy.

* Other improvements, such as fixes to the documentation or vim/emacs
  highlighting modes, are also valued.  Minor changes can be committed
  to trunk/ without review; more major changes should get approval
  from the core team as with code changes.<commit_msg>Minor refresh to Subversion best practices file.<commit_after>=======================
Subversion repositories
=======================

Repository
------------
The subversion repository for the project is set up as follows:

* URL: svn://svn.code.sf.net/p/chapel/code
         branches/
           collaborations/      -- used for external collaborators
           release/             -- used to capture release branches
         tags/                  -- used to tag releases
         third-party-norelease/ -- third party code not intended for release
         trunk/                 -- our main development branch ($CHPL_HOME)

* Anyone can read the repository.

* To commit to the repository, you need a SourceForge account and
  permissions granted by a Chapel administrator.  If you are not a
  Cray employee, a contributor's agreement is required to obtain
  commit privileges.  Different versions of the form exist for
  students and government employees.  The forms can be found in
  $CHPL_HOME/doc/developer/contributorAgreements

* Most external collaborations of any scope will be encouraged to work
  in a project-specific branch in the branches/collaborations/ space.


Contributor Notes
-----------------

In general, contributors should work using the following guidelines,
which are designed to protect the broad Chapel team's ability to make
forward progress:

* Recall that commits to subversion are extremely difficult to remove
  from the source tree's history, so be very careful not to commit
  anything that you might regret later (e.g., sensitive code, code
  owned by anyone other than yourself).

* Apropos of the above, please avoid committing third-party source
  code to any part of the repository without clearing it with a member
  of the core Chapel team.

* Commit changes to your branch as often as you find worthwhile.

* Any non-test commits to code or documentation to trunk/ should go
  through a pre-commit review with someone on the core development
  team.  Adding new tests or future tests to trunk/test can generally
  be done without a review; just be sure that the tests work well
  within the testing system and that they are sorted into a reasonable
  location in the test hierarchy.

* Experienced developers may make minor fixes to code or documentation
  without review, but the changes should generally be quite minor and
  innocuous in scope.
{'fraction_non_alphanumeric': 0.06289188675660269, 'fraction_numerical': 0.0, 'mean_word_length': 3.2315112540192925, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2967461', 'n_tokens_mistral': 1232, 'n_tokens_neox': 1178, 'n_words': 710}