TechnicalBoardAgenda
|
Size: 4324
Comment: new release dates; certification exceptions; uploads via upstream
|
Size: 2263
Comment: Post-meeting update
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = TechnicalBoardAgenda = | This page records the Agenda for the next meeting of the [[TechnicalBoard|Ubuntu Technical Board]]. Please see the [[https://www.ubuntu.com/about/about-ubuntu/governance|Ubuntu Governance]] page for details on participation. |
| Line 3: | Line 3: |
| ## =================Please add items at the bottom of the page! ============================== | If you have a question to raise with the Board, you can reach the Technical Board members directly by e-mailing technical-board@lists.ubuntu.com. They may decide that your issue should be discussed at the next meeting, in which case they will add it to this page. |
| Line 5: | Line 5: |
| Please use this page to add items for the Agenda of the Ubuntu Technical Board. Please see the [http://www.ubuntulinux.org/community/processes/governance Ubuntu Governance] page for details on participation. | The meeting schedule is available on the [[https://wiki.ubuntu.com/Fridge/Calendar|fridge calendar]]. We meet in channel '''#ubuntu-meeting''' on [[https://libera.chat/|Libera.Chat]]. |
| Line 7: | Line 7: |
| The next meeting of the Board will be on: | The next meeting is set for 2024-04-09, 20:00 London time. chair: seb128, backup: vorlon. |
| Line 9: | Line 9: |
| {{{2006-03-14 at 2000UTC}}} | The agenda will include the following: |
| Line 11: | Line 11: |
| in channel '''#ubuntu-meeting''' on chat.freenode.net. The agenda will include the following: | * Apologies: * Action review: * ''ACTION:'' rbasak to update third party repo draft with outcomes from our recent out-of-band meeting (rbasak, 20:04) * ''ACTION:'' rbasak to open wider discussion on third-party repo policy (rbasak, 20:04) * ''ACTION:'' rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification (rbasak, 20:05) * ''ACTION:'' vorlon to look into scripting for packages in flavor-specific overlays (rbasak, 20:05) * ''ACTION:'' seb128 to continue working with SRU, AA, Release, Backporters and Security teams to document their membership process and link to it from https://wiki.ubuntu.com/TechnicalBoard#Team_Delegations (rbasak, 20:05) * Scan the [[https://lists.ubuntu.com/archives/technical-board/|mailing list archive]] for anything we missed (standing item) * Check up on [[https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard|community bugs]] and [[https://bugs.launchpad.net/techboard|techboard bugs]] (standing item) * Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members) * AOB |
| Line 13: | Line 24: |
| ## Permanent agenda items ## * Review [https://launchpad.net/people/ubuntu-core-dev/+members core developer candidates] * Review [https://launchpad.net/people/ubuntu-dev/+members developer candidates] ## ========================= Add your agenda items under this line, INCLUDE YOUR NAME and plan to ATTEND THE MEETING ================== * PaulSladen: I was granted main upload at TB in January 2005... but didn't use it owing to not producing usplash in the required timeframe. Since January 2006 I've actually been motivated to do sensible amount of Ubuntu related-work and I'm finding it frustrating, particularly relating to one-liner fixes where the overhead of multiple updates via the bugtracker is largest. Sorry I missed the previous 2006-02-28 meeting (owing to meeting Crispin about AppArmour and integration with Ubuntu...). * http://people.ubuntu.com/~fabbione/irclogs/archived/2005-01/ubuntu-meeting-2005-01-18.html | grep -A20 ^06:48.*sladen * ColinWatson: Should we produce new installer and CD images for this [http://www.ubuntu.com/usn/usn-262-1 serious installer vulnerability]? At present, users installing Breezy must make sure to upgrade from -security before adding any other local users, which I think will result in a number of vulnerable systems in practice. On the other hand, it's not as if we can rev shipit CDs at this point. * Mark's ''Proposal for additional QA and localisation time on Dapper'', if this happens, TB needs to break down the extra time on different schedule freezes(?) * http://lists.ubuntu.com/archives/ubuntu-devel-announce/2006-March/000094.html * From morning meeting: ''<Seveas@> how about making an almost-there release apri 20 and call for wide testing?'' * PaulSladen: If there is a 6week hold, of which one of the mentioned aims is vendor Certification, does this allow the import of new code? The example I have in hand is that Linux Emporium (who sell pre-installed ThinkPads in the UK) report needing newer 'madwifi-ng' to support the Lenovo ThinkPad Z60*'s newer atheros chip. They also want i810 rotation code for support of the IBM ThinkPad X41Tablet fully (support in FD.org CVS since the new year). Whilst the atheros support is fairly clearly "it doen't work so it's a bug", the xrandr support is closer to a feature request. Should exceptions be requested to allow certification requested by vendors? * PaulSladen: Syncs from external repositories. I've noticed a few people doing fake uploads of duplicate packages into order to speed up the development cycle. The benefits for/against uploading to Ubuntu or Upstream (eg. Debian) and then syncing back are: * To Ubuntu: * '''+''' Faster turn-around time (eg. 1hour to downloadable package) for users, something Ubuntu excels at. * '''-''' Each Ubuntu upload introduces a delta against upstream, something Ubuntu is trying not to do. * Via Upstream and then back: * '''+''' Encourages the notion that feeding-back to upstream is important * '''-''' May slow down the development cycle and can cause continued filing of duplicate bug-reports * Since anyone with upload priviliges can in theory perform an upload with an arbitrary higher version number, is simultantious uploading of identical packages to both archives (a) a good compromise (b) that should be encouraged (c) does launchpad cope with still seeing it as an import? ''Simple import: eg. Subject to UVF exception granted, identical maintainers, current patches being dropped, et al'' ## ======================== Add your agenda items above this line, INCLUDE YOUR NAME and plan to ATTEND THE MEETING =================== ## More permanent agenda items ## * Other business * Update the agenda for the next meeting |
Logs from previous meetings may be found at [[http://irclogs.ubuntu.com/]] or [[http://ubottu.com/meetingology/logs/ubuntu-meeting-2/]] or [[https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/]]. Logs from older meetings are available via [[ScribesTeam/MootBot|MootBot]]. |
This page records the Agenda for the next meeting of the Ubuntu Technical Board. Please see the Ubuntu Governance page for details on participation.
If you have a question to raise with the Board, you can reach the Technical Board members directly by e-mailing technical-board@lists.ubuntu.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 on Libera.Chat.
The next meeting is set for 2024-04-09, 20:00 London time. chair: seb128, backup: vorlon.
The agenda will include the following:
- Apologies:
- Action review:
ACTION: rbasak to update third party repo draft with outcomes from our recent out-of-band meeting (rbasak, 20:04)
ACTION: rbasak to open wider discussion on third-party repo policy (rbasak, 20:04)
ACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification (rbasak, 20:05)
ACTION: vorlon to look into scripting for packages in flavor-specific overlays (rbasak, 20:05)
ACTION: seb128 to continue working with SRU, AA, Release, Backporters and Security teams to document their membership process and link to it from https://wiki.ubuntu.com/TechnicalBoard#Team_Delegations (rbasak, 20:05)
Scan the mailing list archive for anything we missed (standing item)
Check up on community bugs and techboard bugs
(standing item)
Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)
- AOB
Logs from previous meetings may be found at http://irclogs.ubuntu.com/ or http://ubottu.com/meetingology/logs/ubuntu-meeting-2/ or https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/. Logs from older meetings are available via MootBot.
TechnicalBoardAgenda (last edited 2024-04-23 19:10:37 by seb128)