Merge branch 'master' into fancypodcast

[git.ikiwiki.info.git] / doc / todo / fancypodcast.mdwn

diff --git a/doc/todo/fancypodcast.mdwn b/doc/todo/fancypodcast.mdwn
index 258538ff96fadcb543ea755a1c8242044a22ed76..d1697cbaa370c7f39a094ae8af4bdd601a548bcb 100644 (file)
--- a/doc/todo/fancypodcast.mdwn
+++ b/doc/todo/fancypodcast.mdwn
@@ -19,6 +19,7 @@ also have lots more metadata.
 ## Implementation
 
 [[!template id=gitbranch branch=schmonz/fancypodcast author="[[schmonz]]"]]
 ## Implementation
 
 [[!template id=gitbranch branch=schmonz/fancypodcast author="[[schmonz]]"]]

+[[!tag patch]]

 
 ### Completed
 
 
 ### Completed
 


@@ -35,26 +36,47 @@ also have lots more metadata.
 * Match feature-for-feature with
   [tru_podcast](http://www.rainskit.com/blog/542/tru_podcast-a-podcasting-plugin-for-textpattern)
   (what [[schmonz]] will be migrating from).
 * Match feature-for-feature with
   [tru_podcast](http://www.rainskit.com/blog/542/tru_podcast-a-podcasting-plugin-for-textpattern)
   (what [[schmonz]] will be migrating from).

+* Enrich [feed metadata](http://cyber.law.harvard.edu/rss/rss.html)
+  by catching up `rsspage.tmpl` to `atompage.tmpl`.
+* Subscribe to a fancy feed in some common podcatchers and verify
+  display details against a reference podcast.
+* Verify that the feeds validate.

 
 ### Must-have (for [[schmonz]], anyway)
 
 
 ### Must-have (for [[schmonz]], anyway)
 

-* Enrich [podcast feed metadata](http://cyber.law.harvard.edu/rss/rss.html)
-  (some of which is
-  [iTunes-specific](https://www.apple.com/itunes/podcasts/specs.html),
-  though I'm not aware of it causing any problems for other
-  podcatchers, and in fact some of them may also use it).
-* Subscribe to a fancy feed in some common podcatchers and verify
-  display details against a reference podcast.

 * Think carefully about...
     * UTF-8.
     * Other templates with `CONTENT` and whether they want to learn
       about `ENCLOSURE` (maybe `aggregatepost.tmpl`?).
     * Whether [[tips/howto avoid flooding aggregators]] suffices for
       migrating a fancy podcast into ikiwiki.
 * Think carefully about...
     * UTF-8.
     * Other templates with `CONTENT` and whether they want to learn
       about `ENCLOSURE` (maybe `aggregatepost.tmpl`?).
     * Whether [[tips/howto avoid flooding aggregators]] suffices for
       migrating a fancy podcast into ikiwiki.

-* Verify that the feeds validate.

 * Verify that _all_ the tests pass (not just my new ones).
 
 * Verify that _all_ the tests pass (not just my new ones).
 

-### Nice-to-have
+-----
+
+## Future improvements
+
+### iTunes fancy podcasting
+
+* [iTunes-specific tags](https://www.apple.com/itunes/podcasts/specs.html)
+  appear to be RSS-only
+    * If they work in Atom, teach `inline` to optionally iTunesify RSS/Atom.
+    * Else, add `itunes` as a third kind of feed (RSS plus more stuff).
+* Notable tags for feeds:
+    * `itunes:subtitle`
+    * `itunes:author`
+    * `itunes:summary` (same as `description`)
+    * `itunes:owner` (includes `itunes:name` and `itunes:email`)
+    * `itunes:image href=''`
+    * `itunes:publisher`
+    * `itunes:category text=''` (can contain subcategories)
+    * `itunes:keywords`
+* Notable tags for entries:
+    * `itunes:duration`
+        * use `Audio::TagLib` if present and applicable
+        * fall back to `ffprobe`
+
+### Other ideas

 
 * Let the enclosure's MIME type be specified, in case someone ever
   needs to disagree with `File::MimeInfo`.
 
 * Let the enclosure's MIME type be specified, in case someone ever
   needs to disagree with `File::MimeInfo`.


@@ -82,7 +104,3 @@ Episode author     |(./)      |(./)       |(./)        |(./)
 Episode description|(./)      |(./)       |(./)        |
 Episode enclosure  |(./)      |(./)       |(./)        |(./)
 """]]
 Episode description|(./)      |(./)       |(./)        |
 Episode enclosure  |(./)      |(./)       |(./)        |(./)
 """]]

-
-Notes:
-
-* RSS appears to be strongly preferred over Atom for podcasting.