www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-8767) Create error-proof, predefined podling mailing creation
Date Tue, 02 Dec 2014 17:03:13 GMT

    [ https://issues.apache.org/jira/browse/INFRA-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231748#comment-14231748
] 

Sebb commented on INFRA-8767:
-----------------------------

+1

Discussions I have seen on the Incubator list generally say that podlings should not have
user lists, as the focus should be on growing the dev community.
Having a separate user list tends to fragment the community at a critical stage.

Bigger/busier podlings might need a separate issues list; maybe that should be an option.

> Create error-proof, predefined podling mailing creation 
> --------------------------------------------------------
>
>                 Key: INFRA-8767
>                 URL: https://issues.apache.org/jira/browse/INFRA-8767
>             Project: Infrastructure
>          Issue Type: Planned Work
>          Components: Whimsy
>            Reporter: David Nalley
>
> We have a number of instances where people submit mlreq requests that errantly requests
public lists to be private.
> We know that most projects are going to have the following lists:
> private@
> dev@
> commits@
> Alternately we could have a boolean option to allow projects that desire users@ lists.

> Essentially, the current incubator form asks too many questions of the users.
> Let's streamline that, and make it trivial to get going.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message