[sakai2-tcc] VOTE: Proposal to include Antisamy in 2.9.2

Jean-Francois Leveque jean-francois.leveque at upmc.fr
Wed Apr 3 05:26:58 PDT 2013


0
I would really like to know who will enable it, with which settings, and 
when.

J-F

On 02/04/2013 20:58, Aaron Zeckoski wrote:
> 0
> Should definitely be included and I think it should be on by default
> to close the security holes for users without SCA support (as I
> understand it, all the major SCAs will be using it so those users are
> safe but the independent groups are stuck unless they happen to know
> better and enable it).
>
> -AZ
>
> On Tue, Apr 2, 2013 at 2:05 PM, May, Megan Marie<mmmay at indiana.edu>  wrote:
>> PROPOSAL
>>
>> Inclusion of Anitsamy as a replacement of formattedtext in 2.9.2.  The
>> change will be disabled OOTB and summaries of low and high AntiSamy policies
>> will be provided in ‘plain speak.’
>>
>>
>>
>> Once there is positive production experience, Antisamy will be the default
>> in subsequent releases (ie 2.9.3).
>>
>>
>>
>> Changes to maintenance branches normally follow the maintenance branch merge
>> policy [1] and given the deviation from stated policy, a formal vote is
>> being called.
>>
>>
>>
>> Voting is now OPEN until 23:59 UTC on Friday, 5 April 2013.
>>
>>
>>
>> As a reminder, this is a public, on-list vote with a "+1" signifying
>> approval. Per our governance documents, a -1 vote must be accompanied by a
>> detailed explanation. A single -1 vote based on a material objection will
>> block action. However, -1 blocking votes can be overridden by a 2/3 majority
>> roll call vote of active TCC members.
>>
>>
>>
>> Thanks,
>>
>> Megan
>>
>>
>>
>> Megan May
>>
>> TCC Chair
>>
>>
>>
>> [1]
>> https://confluence.sakaiproject.org/display/TCC/Maintenance+Branch+Merge+Policy


More information about the sakai2-tcc mailing list