On 24-05-12 01:44, Cory Fields wrote: > On Tue, May 22, 2012 at 4:37 PM, Kevin Goffe<[email protected]> wrote: >> Hi, >> >> I'd just like to ask a question about Cory's statement - >> >> "As a rough draft on policy, i think it suffices to say just this: no >> functionality should be removed and no settings should be lost during >> an automatic skin update, no exceptions." >> >> What if a function or setting can safely be removed due to a change to >> something else (eg skin engine or addon update)? >> >> As the setting would either be obsolete (eg controlled by a boolean >> condition) >> or handled elsewhere (eg setting moved to XBMC or another addon) this would >> ok wouldn't it? >> >> Thanks, >> >> Kev. >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Xbmc-addons mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/xbmc-addons >> > Hey Kevin > > I wasn't meaning to set policy there, rather begin a discussion. So > thanks for keeping it rolling. > > So in your case, I'd say if you remove a setting when an addon is > updated, that's likely reasonable. For ex if there's a weather addon > that supports fetching extra data which your skin shows, and that > addon is updated to provide less data due to a site change, it's > reasonable to assume you skin would update to reflect that. In that > case it wouldn't be removing any functionality, only removing access > to something external that stopped working. I assume that's what you > meant? > > Anyone else care to comment on the policy? >
yes please :) i strongly disagree with the 'no functionality should be removed' rule. to me, it's entirely up to the skinner to develop a skin the way he sees fit. it's his call and nobody else's. if he wants to remove some functionality, for whatever reason, he should be free to do so and not being forced to maintain it against his will for another year or so. don't like the way a skin is heading? np, just rollback or pick another skin. cheers, ronie ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Xbmc-addons mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbmc-addons
