On 02.01.2015 11:36, Stian Soiland-Reyes wrote:
> Apache Commons has already given write access to *all* ASF committers
So did Subversion, quite a while ago.
If you get rogue commits from someone, the solution is not extra tooling
but community management. Even more so in the case of the Incubato
Thank you Roman and IPMC members!
On Wed, Dec 31, 2014 at 6:09 AM, Roman Shaposhnik wrote:
> Hi!
>
> sorry for not sending this out sooner -- holidays got
> the best of me ;-)
>
> I am really happy to welcome an ASF member
> Hyunsik Choi, who has recently voluteered to
> join the Incubator PMC!
On 04/01/2015 Mark Struberg wrote:
I know many projects (TLP) which discuss/draft the report in private
and only later make it public.
OpenOffice, both as podling and TLP, has done the opposite (which I
assume is the norm): report is discussed on the dev list, stored on a
wiki page and the pr
There are occasionally items that appear in board reports enclosed in
, which concern behavior of project members, legal issues,
not-yet-publicized security exploits, and the like, which should
probably remain private. This is the exception, rather than the norm.
Everything else should be publi
Imnsho, that is a poor practice.
Sent from my iPhone
> On Jan 4, 2015, at 7:18 AM, Mark Struberg wrote:
>
> I know many projects (TLP) which discuss/draft the report in private and only
> later make it public.
>
> LieGrue,
> strub
>
>
>
>
>
>>> On Sunday, 4 January 2015, 16:10, Alan Cabr
I know many projects (TLP) which discuss/draft the report in private and only
later make it public.
LieGrue,
strub
> On Sunday, 4 January 2015, 16:10, Alan Cabrera wrote:
> > Board reports are always public, as are a project's/podling's
> discussions about what should go in their report.
>
Board reports are always public, as are a project's/podling's discussions about
what should go in their report.
It's the mentors job to clear up any confusion there may be for a podling
writing its first report.
Sent from my iPhone
> On Jan 4, 2015, at 5:25 AM, John D. Ament wrote:
>
> Hi al
On Sunday, January 4, 2015, John D. Ament wrote:
> Hi all,
>
> Just wondering, should we tell podlings that a board report is considered
> public while in draft and can be discussed on their dev list, or its
> private and should be discussed on their private list?
clearly public, the report is
Hi all,
Just wondering, should we tell podlings that a board report is considered
public while in draft and can be discussed on their dev list, or its
private and should be discussed on their private list?
I had always assumed public, but could hear someone say its private.
John
