New Issue Resolution Process

Steps (http://trellislms.org/wiki/DeveloperGuide):

1. Issue is identified: Anyone can identify an issue whether it be a
bug, a tweak, or a new feature.

2. Identifier analyzes and reports the issue: Once the issue is
identified, the person who identified the issue must collect as much
information as possible to submit a complete report in the tracker.

3. Issue is confirmed: Once the issue is reported, a lead developer will
review the report and confirm the issue if it is valid, adding any
useful information to the report.

4. Issue is discussed: If the issue is not a straightforward bug fix,
the issue will be discussed by the developers to determine an
appropriate solution.

5. Issue is assigned to a developer: Based on the urgency of the issue,
a lead developer will decide when and to whom to assign the issue.

6. Developer makes changes to development repository: Once a developer
has been assigned to an issue, the developer will make the necessary
changes to the development repository and test the changes. After the
developer is satisfied with the changes, the developer will notify the
maintainer by sending a reminder from the issue tracker. The reminder
should include any information which will help the maintainer understand
the changes.

7. Changes are reviewed by the maintainer: The maintainer will review
the changes and determine if the changes have resolved the issue and
ensure that it conforms with the coding standards. If more work is
needed, the maintainer will inform the developer by adding notes to the
report. This process will repeat until the maintainer determines the
changes are complete.

8. Changes are merged with the main repository: The maintainer will then
merge the developer's changes to the main Trellis repository including a
message summarizing the changes applied.

9. Issue is resolved: The maintainer will then update the report to show
a resolution has been committed.

------------------------------------------------------------------------

Roles:
Shaddy Zeineddine: maintainer, lead developer, developer, reporter
James Carlos: lead developer, developer, reporter
Henry Lim: developer, reporter
Carlos Santos: developer, reporter
Everyone else: reporter, (and possibly contributor)

------------------------------------------------------------------------

The new process, as outlined above, is now in effect. This process was
implemented to achieve the following goals:

- maintain a detailed changelog
- document issues
- maintain high level of quality
- maintain minimal overhead
- facilitate collaborative development
- facilitate versioning and regular releases

The process will be under continuous review, and changes may be made in
order to better reach our goals.

Please remember to include the issue number in your commit messages so
that it will be attached to the issues. The accepted formats are as follows:

issue#23
issue #23

It is not case sensitive and it can appear anywhere in the message.
Thank you.

Shaddy