(note: missing next week's meeting, commenting here)

I'm generally +1 to this, but I do note that this feature is effectively dependent on FPC approvals of changes. It also likely needs that approval before any F20 mass rebuild for the affected packages.

Replying to [comment:1 notting]:

(note: missing next week's meeting, commenting here)

I'm generally +1 to this, but I do note that this feature is effectively dependent on FPC approvals of changes.

Yeah, I'm going to file an FPC ticket Really Soon Now. I'm just working on finalizing the font changes I just figured out were needed yesterday. ;-)

It also likely needs that approval before any F20 mass rebuild for the affected packages.

There's nothing to worry about for the mass rebuild. The redhat-rpm-config change doesn't affect any packages that currently exist in the distribution. (It will only help the new ones we want to get in.)

FPC ticket is filed now:
https://fedorahosted.org/fpc/ticket/323

+1 it makes a good sense to me. Finalizing the name of the web assets directory could be done by discussion in FPC.

+1 to the idea, deferring to FPC to figure out the detailed guidelines.

(The name of the web assets directory is a component of the guideline and thus formally up to FPC as well I think; in any case I don't have a well-founded opinion so I wouldn't want to override them.)

+1 because changes were in past approved by FESCo without having guidelines. Please, work on the guidelines with FPC. They should be approved before release of F-20. (It would be better to approve them before doing the changes, but I know it takes time).

+1 blah blah FPC blah blah.

This makes +5, so barring any FESCo member requesting an in-meeting discussion, I believe this is approved.

+1

Given that it's past Change Freeze, and we're still eking out a cross-distro standard for the httpd paths that everyone is (un)happy with, I'm going to retarget that portion of this Change for Fedora 21. Given FESCo and FPC of the broader goals here, I'd still like to land that in Rawhide for F21 as soon as possible, though.

We're still going to make the filesystem infrastructure available in all active Fedora releases, since that will really help with pain points being discussed on devel right now, like tinymce.

Putting off the httpd stuff makes some of the cleanup tasks like the font metadata cleanup not critical for F20, but I'm still going to proceed with them as soon as possible. We'll only force the issue in Rawhide now, but IMHO mismatching licensing metadata is a very good reason to backport to stable releases anyway, so maintainers will still be encouraged to do so.

The Change page has been updated to reflect this:
https://fedoraproject.org/wiki/Changes/Web_Assets#Scope