On Sep 11, 2010, at 4:50 AM, Nathan Kinsinger wrote: > If he does agree to hand it over to someone else I'm pretty sure it's > possible to change over the code signing key, it would just require one last > release signed by him. However he has mentioned that he wanted to keep > control of the sparkle feed.
Another option would be to make a "paid" update on Pieter's Sparkle feed (may require merging some changes from my Sparkle branch -- not sure whether Andy merged them over yet). A "paid" update is an update with a version number but no enclosure, and will show HTML and provide a "Learn More..." link (so it doesn't really involve any pay). That way, people who have Pieter's version would be notified of a new site with a "cold" update via Sparkle, but would have to manually move to the new version and visit the new website. Just a thought, particularly if Pieter wanted out and transferring the signature would be an issue of some sort. Though I guess this is just the Sparkle-specific DSA key, so it prolly isn't. Cheers, -- Uli Kusterer "The Witnesses of TeachText are everywhere..."
