On 07/12/2018 18:31, Rich Bowen wrote:
> I have, over the last few days, seen several of our project communities
> use their private list for discussions that were not, in anyway,
> sensitive. I have called them out on this, but, in each case, my message
> has been utterly ignored.
Wearing my b
On 12/7/18 12:08 PM, Shane Curcuru wrote:
> Bertrand Delacretaz wrote on 12/7/18 10:14 AM:
>> Hi,
>>
>> On Fri, Dec 7, 2018 at 3:53 PM Jay Vyas wrote:
>>> ...At the CNCF, I’ve noticed that almost all decisions are made in hangouts
>>> and in GitHub issues, and proposals..
>>
>> I think this is
Bertrand Delacretaz wrote on 12/7/18 10:14 AM:
> Hi,
>
> On Fri, Dec 7, 2018 at 3:53 PM Jay Vyas wrote:
>> ...At the CNCF, I’ve noticed that almost all decisions are made in hangouts
>> and in GitHub issues, and proposals..
>
> I think this is exactly how Apache projects are supposed to operate
[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]
Hello Apache projects,
I am writing to you because you may have git repositories on the
git-wip-us server, which is slated to be decommissioned in the coming
mon
Hi,
On Fri, Dec 7, 2018 at 3:53 PM Jay Vyas wrote:
> ...At the CNCF, I’ve noticed that almost all decisions are made in hangouts
> and in GitHub issues, and proposals..
I think this is exactly how Apache projects are supposed to operate:
*all* discussions and decisions in public places unless t
At the CNCF, I’ve noticed that almost all decisions are made in hangouts and in
GitHub issues, and proposals. It definitely is a model that can work.
Not saying we should copy them, but just noting that there’s more then one way
to skin a cat, and there aren’t any right answers here.
> On Dec
On Fri, 7 Dec 2018 at 13:37, Bertrand Delacretaz wrote:
>
> Hi,
>
> On Fri, Dec 7, 2018 at 2:19 PM Daniel Gruno wrote:
> > ...To me, the question isn't so much about ditching private lists, but
> > rather having a separate public management list for PMCSs, and keep a
> > private list for private
Hi,
On Fri, Dec 7, 2018 at 2:19 PM Daniel Gruno wrote:
> ...To me, the question isn't so much about ditching private lists, but
> rather having a separate public management list for PMCSs, and keep a
> private list for private issues...
So for project foo you'd have
dev@foo.a.o : public
pmc
On 12/7/18 2:16 PM, Bertrand Delacretaz wrote:
On Fri, Dec 7, 2018 at 11:51 AM sebb wrote:
On Thu, 6 Dec 2018 at 13:05, Jay Vyas wrote:
..Agree / propose: remove all private communication.
I don't think that is feasible.
There are some discussions that must happen in private...
+1, if we w
On Fri, Dec 7, 2018 at 11:51 AM sebb wrote:
> On Thu, 6 Dec 2018 at 13:05, Jay Vyas wrote:
> > ..Agree / propose: remove all private communication.
> I don't think that is feasible.
> There are some discussions that must happen in private...
+1, if we wouldn't have private lists people would use
On Thu, 6 Dec 2018 at 13:05, Jay Vyas wrote:
>
> Agree / propose: remove all private communication.
I don't think that is feasible.
There are some discussions that must happen in private.
For example, reports of security issues and personnel discussions.
> Other foundations are becoming more ope
11 matches
Mail list logo
