#323 Web Assets
Closed: Fixed None Opened 6 years ago by patches.

I have a few related drafts for you all:

The first two obviously go together. As for the last one, we want to make sure the metadata in font files is accurate going forward, now that they can be used as web fonts. We're going to clean up the ones we have now for F20, but the guideline will ensure their correct in the future.

For more information, see:
the F20 Change outlining the engineering component
the packaging list discussion
* the devel list discussion

Many changes have already been made in response to feedback from these discussion, including feedback from the httpd maintainer, people involved with fonts, FESCo, and others.

Thanks!


This is going to take a while to hash through, and it would be very helpful if you could attend our discussion meeting on IRC. We plan to reserve our August 15th meeting for the drafts in this ticket. That meeting happens at 1600 UTC in #fedora-meeting-1 on irc.freenode.net.

I'll try and be there. In the meantime, I went ahead and answered some of the questions raised in today's meeting if that helps save some time:

https://lists.fedoraproject.org/pipermail/packaging/2013-August/009388.html

FPC and tchol discussed these drafts and made minor updates to the language at today's meeting. We also removed the exception for prebuilt flash files.

Proposal: Accept all three of the web asset related guidelines. We'll be waiting for an update that takes care of the name of the javascript directory exported to web servers.

(+1:5, 0:0, -1:0)

racor voted late. So the vote ended up being: (+1:6, 0:0, -1:0)

Related to the flash discussion we had, we should modify the list of extensions here:

https://fedoraproject.org/wiki/Packaging:Guidelines#No_inclusion_of_pre-built_binaries_or_libraries

to mention *.swf

Okay, all of these have been added to the guidelines now.

Announcement:

Guidelines for shared web assets including browser-side javascript have been added. These finally add rules for unbundling javascript libraries from web applications as well as shared css libraries, icons, and other files. Although a lot of work over many releases is anticipated from this, an effort has been made to cut out some of the work by allowing a static-library like arrangement for JavaScript libraries. Two related areas were clarified as part of this: pre-compiled shockwave flash files count as pre-compiled binaries and are not allowed (compile flash resources from source with an open source flash toolchain or patch them out of the package). Font files need to have proper licensing informaiton in their metadata. The following pages contain the updated guidelines:

After reading patches' reply in the flash bundling thread about the intention of the static library-style packaging section, I think we better modify the announcement in case we tighten up the wording in the future. New announcement text:

Guidelines for shared web assets including browser-side javascript have been added. These finally add rules for unbundling javascript libraries from web applications as well as shared css libraries, icons, and other files. Two related areas were clarified as part of this: pre-compiled shockwave flash files count as pre-compiled binaries and are not allowed (compile flash resources from source with an open source flash toolchain or patch them out of the package). Font files need to have proper licensing informaiton in their metadata. The following pages contain the updated guidelines:

Login to comment on this ticket.

Metadata