slangasek says this can just be done on ubuntu-release, nevermind then :)
|Deletions are marked like this.||Additions are marked like this.|
|Line 15:||Line 15:|
|* ''ACTION:'' bashfulrobot / fossfreedom - review and discuss Ubuntu Budgie LTS proposal. Current draft located at https://wiki.ubuntu.com/UbuntuBudgie/18.04/LTS-Proposal|
If you have a question to raise with the Board, you can reach the Technical Board members directly by e-mailing email@example.com. They may decide that your issue should be discussed at the next meeting, in which case they will add it to this page.
The meeting schedule is available on the fridge calendar. We meet in channel #ubuntu-meeting-2 on chat.freenode.net.
The next meeting is set for 2017-12-19, 20:00 London time. chair: infinity, backup: kees The agenda will include the following:
- Action review:
ACTION: infinity to ask maas team to prepare SRU exception policy à la CurtinUpdates
ACTION: infinity to play with seed/maint-check changes on dogfood to build a new xenial release pocket for support length auditing (ETA: 16.04.3 release)
ACTION: slangasek to investigate getting tagged ubuntu-community bugs automatically forwarded to technical-board, and if not feasible, fall back to DMB sending signed emails to list for ACL requests
ACTION: bashfulrobot / fossfreedom - review and discuss Ubuntu Budgie LTS proposal. Current draft located at https://wiki.ubuntu.com/UbuntuBudgie/18.04/LTS-Proposal
- [Add new agenda items above this line - include your name]
Scan the mailing list archive for anything we missed (standing item)
Check up on community bugs (standing item)
Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)
Logs from previous meetings may be found at http://irclogs.ubuntu.com/ or http://ubottu.com/meetingology/logs/ubuntu-meeting-2/. Logs from older meetings are available via MootBot.