Adding meeting keyword to add to next scheduled meeting.

This is in reference to the linking static libraries guidelines:
https://fedoraproject.org/wiki/Packaging:Guidelines#Staticly_Linking_Executables

Note that creating the -static package doesn't need FESCo approval. Linking to the static library when a dynamic library is also available does.

yaboot looks to have a valid reason for linking statically to me.

As I'm not going to be at the meeting, commenting here - I'm fine with linking yaboot statically against e2fsprogs. Is it going to need it for btrfsprogs, et. al. as well?

This static linking exception for yaboot was approved.

Toshio: Can you add it to the exceptions list?

Looks like we don't have an exception list for this (permission to link a program statically) atm. We do need to document it so we don't get bugs later on that we can't easily point people to the exceptions for. For now, I've added it here:

https://fedoraproject.org/wiki/Packaging:Guidelines#Programs_which_don.27t_need_to_notify_FESCo

We may want to move that list somewhere else later (maybe even out of the Packaging: namespace). The exception granting for using static libraries isn't supposed to have as stringent requirements as bundling libraries so I'm not sure what we want to do long term.

Sounds good. Thanks!