This repository maintain a list of all the proposals for improving the Toronto JS (TJS) community. This is a place to discuss and collaborate on the future of the Toronto JS community.
A proposal follows the model of an RFC (Request for Comments). It is a document that describes a new feature or change to some part of the TJS community. It should provide a concise and clear explanation of the proposed change, and should include the motivation for the change and the benefits of the change.
- Create an issue in this repository with the title of your proposal, prefixed with
[PROPOSAL] -. This issue will automatically load the issue template for proposals. You just need to fill in the details. - Tag the organizers using the
@torontojs/organizershandle. - Once the proposal is submitted, the organizers will review and give feedback on the proposal.
- One of the organizers will be assigned as the champion for the proposal. The champion will be responsible for helping with the bureaucratic process and to move to the next steps. They are also responsible to keep the proposal updated and to answer any questions that may arise.
- If needed, create a repository with the proposal and link it to the issue.
- The proposal will be approved or rejected by the organizers. If approved, the champion will be responsible for following up on the proposal implementation.
If you have an idea that do not fit into a proposal, we also have an ideas board where you can add new ones here: https://github.com/orgs/torontojs/projects/3
| Proposal | Champion | Status |
|---|---|---|
| Newsletter and Blog Integration | @dreymoreau / @madcampos | Work in progress |
| Cross-post our events on our website! | @dxnn | In review |
| Investigation of communication platforms and moving off of Slack | --- | On Hold |
| Volunteer Management System (VMS) software | @GingerKiwi | Work in progress |
| Moving volunteer info to volunteer.torontojs.com | @GingerKiwi | Work in progress |