Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 286931016D for ; Tue, 23 Jul 2013 13:42:18 +0000 (UTC) Received: (qmail 60694 invoked by uid 500); 23 Jul 2013 13:42:18 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 60651 invoked by uid 500); 23 Jul 2013 13:42:17 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 60643 invoked by uid 99); 23 Jul 2013 13:42:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jul 2013 13:42:16 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jul 2013 13:42:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:In-Reply-To:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=0eH7gWCFOSK1/OJ1j9jHr3RQKx+XzikgvH2ijxtANH8=; b=rcAkBwRvuJbXS09aeyn0YGvqfVJ23458PKi596UOxXutIpDfv8Z1QKqQbLCB/xKEmO6aIoMSLhiXYM7lK920IvqD2Zd46AYEYAe4toSNLJjyyoINIxfxiTwCY59+ws+IwtMi3olPqJXpMRVdJp1LM01ET+pea6rvT3I2u42Hdm0=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-3.v29.ch3.sourceforge.com) by sfs-alluradaemon-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1V1cqb-0008SE-Sh for allura-dev@incubator.apache.org; Tue, 23 Jul 2013 13:41:49 +0000 Content-Type: multipart/related; boundary="===============0972656486454103853==" MIME-Version: 1.0 To: "[allura:tickets] " <6392@tickets.allura.p.re.sf.net> From: "Dave Brondsema" Reply-To: "[allura:tickets] " <6392@tickets.allura.p.re.sf.net> Subject: [allura:tickets] Re: #6392 Per tool user bans Message-ID:

In-Reply-To: <68f4f5ac41f8fb1b9b2dd4db210c992f7c265b65.tickets@allura.p.sourceforge.net> Date: Tue, 23 Jul 2013 13:41:49 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============0972656486454103853== Content-Type: multipart/alternative; boundary="===============2822967353388806138==" MIME-Version: 1.0 --===============2822967353388806138== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit If using DENY in the existing ACL system works (and I hope it does) then I think it should be on the existing permission page and associated with an individual permission (e.g. "post"). I've attached a possibility. When you click on it, we'll need a username field and a place for a note, so a modal dialog might be best. We also need to list existing blocked users. Perhaps those could be listed in the modal dialog too. --- ** [tickets:#6392] Per tool user bans** **Status:** open **Labels:** support p3 42cc **Created:** Tue Jun 25, 2013 02:05 PM UTC by Chris Tsai **Last Updated:** Tue Jul 23, 2013 08:13 AM UTC **Owner:** nobody It should be possible to ban users from posting to individual tools, in case of spam, abuse, etc. There should also be a spot to indicate the reason when banning. These bans should be collected in a site or neighborhood wide admin page so we can review these periodically in case we want to remove/disable that account site wide. --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============2822967353388806138== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

If using DENY in the existing ACL system works (and I hope it does) then I think it should be on the existing permission page and associated with an individual permission (e.g. "post"). I've attached a possibility. When you click on it, we'll need a username field and a place for a note, so a modal dialog might be best. We also need to list existing blocked users. Perhaps those could be listed in the modal dialog too.


[tickets:#6392] Per tool user bans

Status: open
Labels: support p3 42cc
Created: Tue Jun 25, 2013 02:05 PM UTC by Chris Tsai
Last Updated: Tue Jul 23, 2013 08:13 AM UTC
Owner: nobody

It should be possible to ban users from posting to individual tools, in case of spam, abuse, etc. There should also be a spot to indicate the reason when banning.

These bans should be collected in a site or neighborhood wide admin page so we can review these periodically in case we want to remove/disable that account site wide.


Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============2822967353388806138==-- --===============0972656486454103853==--