Consent / upgrades

[Cantor, Scott]

On 11/17/14, 8:24 PM, "Tom Scavo" <trscavo at gmail.com> wrote:

>On Mon, Nov 17, 2014 at 3:14 PM, David Langenberg <davel at uchicago.edu> 
>wrote:
>> The default on new-installs should definitely be on, but for upgrades, 
>>I'd
>> rather see it behave as v2 does today (no consent).
>
>I certainly understand your (deployer-centric) PoV but from a
>federation perspective, the game-changing potential of consent is
>diminished if it ships with default = off.

I've been trying to avoid using properties for this particular toggle 
because of how this gets configured, but I'll see, maybe we can come up 
with something that lets us prompt for it at upgrade time.

-- Scott