The Tech Committee meetings documentation must follow the format of the Tech Committee Log Entry Template
ℹ️ See here for all Tech Committee tasks
TBD in in the first 5 min of the meeting
- add new entry for next meeting from template
- tasks to review
- pull requests to process
- feature requests and issues to process
- Varia: further points raised by Tech Committee members
- ...
- ...
- review log entry together, approve and post
After the meeting, create and link tasks and update the entry
Tasks are added during the meeting to the log entry of the next meeting. After the meeting, the task is added to the django CMS management board as an issue and linked here.
- respond to open merge requests on the core
- create a definition of what changes are required in v4 to switch community efforts to v4 and abandon v3
The Tech Committee decides what to do with them, thereafter a task is created to process them.
- PR 1
- ...
The Tech Committee decides what to do with them, thereafter a task is created to process them.
- ...
- ...
Any other decisions taken during the meeting are documented here, since all decisions must be actionable, a task must be created from it.
- ...
- ...
TBD in in the first 5 min of the meeting
- add new entry for next meeting from template
- tasks to review
- pull requests to process
- feature requests and issues to process
- Varia: further points raised by Tech Committee members
- RFP / Feature request process: Propose to use discourse and discourse voting plugin - this would completely replace the Fider setup
- all feature requests that are posted as issues on the respective repositories would be tagged as feature requests, a discourse topic would be opened and the link referenced in the issue, the issue would be tentatively closed in the repo, and a discussion period would start on discourse, in which everyone would participate, including members of the tech committee. The tech committee then would review the results from the discussion period and would then either discard or accept into the roadmap.
- RFP / Feature request process: Propose to use discourse and discourse voting plugin - this would completely replace the Fider setup
- review log entry together, approve and post
After the meeting, create and link tasks and update the entry
- respond to open merge requests on the core - postponed
- create a definition of what changes are required in v4 to switch community efforts to v4 and abandon v3 - postponed
- This is for the moment handled via the pending cleanup task
- We will postpone issue mgmt to after we've cleaned up the pending PRs.
- we will set up Discourse with a voting plugin for feature voting
- we will abandon the idea to use fider since Discourse can do that well via feature voting plugin
- moving meeting back to 14:00 because Divio team members already have weekly meetings at 15:00
- Mario to create the markdown structure of the wiki on wiki github repo
- we want to gather feedback for all open PRs from all TC members and the PR creator, to either close, fix or reassign PRs
- wiki format is approved and will be used from now on
- move gitlab board to new github project board for dCA activities
- Mario to create the markdown structure of the wiki on wiki github repo
- review https://github.com/divio/django-cms/pulls and propose the easy ones to merge for 3.8
- get free slack account for django CMS Association
- create a definition of what changes are required in v4 to switch community efforts to v4 and abandon v3.
- Andrew to look at two pending PRs on django CMS core