Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: [Original edit by KevinMcGrail] More policy polishing re: other dev's sandboxes

...

Editing another developer's sandbox rules is generally frowned upon. However, there are instances where this is necessary and permitted:

  1. Individual developers may allow more access to files in their sandbox by adding comments to the beginning of the file.

2. If content in the sandbox has However, if the rules have been promoted into the core codebase or rules, it is treated like any other portion of the code.

3. If a developer's sandbox has had no changes for more than 6 months, it may be considered abandoned. After sending an email to the original developer, if rules and no replies are received for 2 weeks from the original developer, updates can be made by other developers. It Note, it is still best practice to notify the original developer that that you're making the change . The and the revision control comments for the update should also clearly state that the rule was updated by another developer with the reason for the update.

4. In the case of a any problem that is considered time-sensitive , a bug with a and not covered above, any patch with votes to commit following RTC, i.e. requiring three votes and no vetoes before committing, can be immediately applied.

...