Hi,
> Yes, exactly. Thanks.
And done.
Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
> On 8 May 2019, at 10:13, Justin Mclean wrote:
>
> Hi,
>
>> I can see it from here, but I was unable to log in. Tried a password reset,
>> whereupon I'm no longer permitted even to view the report on the browser
>> that's logged in!
>
> I assume you were going to sign off PageSpeed? It
Hi,
> Stop sending me your bogus ass shit!!
As requested you have been unsubscribed from this list.
Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail:
Stop sending me your bogus ass shit!!
On Tue, May 7, 2019, 6:50 PM Nick Kew
> > On 5 May 2019, at 23:21, Justin Mclean wrote:
> >
> > 1. https://cwiki.apache.org/confluence/display/INCUBATOR/May2019
>
> Anyone else having trouble with that?
>
> I can see it from here, but I was unable to log
For someone with ptsd!!! Do u want some more?
On Tue, May 7, 2019, 6:50 PM Nick Kew
> > On 5 May 2019, at 23:21, Justin Mclean wrote:
> >
> > 1. https://cwiki.apache.org/confluence/display/INCUBATOR/May2019
>
> Anyone else having trouble with that?
>
> I can see it from here, but I was unable
Hi,
> I can see it from here, but I was unable to log in. Tried a password reset,
> whereupon I'm no longer permitted even to view the report on the browser
> that's logged in!
I assume you were going to sign off PageSpeed? It currently has no signs off
and will be asked to report next month
Sent from my iPhone
> On May 7, 2019, at 4:52 PM, Kevin A. McGrail wrote:
>
> On 5/7/2019 7:50 PM, Nick Kew wrote:
>>> On 5 May 2019, at 23:21, Justin Mclean wrote:
>>>
>>> 1. https://cwiki.apache.org/confluence/display/INCUBATOR/May2019
>> Anyone else having trouble with that?
>>
>> I
On 5/7/2019 7:50 PM, Nick Kew wrote:
>> On 5 May 2019, at 23:21, Justin Mclean wrote:
>>
>> 1. https://cwiki.apache.org/confluence/display/INCUBATOR/May2019
> Anyone else having trouble with that?
>
> I can see it from here, but I was unable to log in. Tried a password reset,
> whereupon I'm no
On Tuesday, May 7, 2019, Dave Fisher wrote:
> Hi -
>
> It seems that the report has been finalized. I had a comment in response
> to Justin’s notes regarding CDN testing for MxNet and ECharts.
>
> A third party provider is being used for these Anycast CDNs. Nothing to
> file for the ASF.
>
>
Hi -
It seems that the report has been finalized. I had a comment in response to
Justin’s notes regarding CDN testing for MxNet and ECharts.
A third party provider is being used for these Anycast CDNs. Nothing to file
for the ASF.
Regards,
Dave
> On May 5, 2019, at 3:21 PM, Justin Mclean
Hi,
> Though I don't like implying that IPMC members are better than
> others...IMO the core problem is "uninformed people" or something like
> that.
Yep that seems a much better way of putting it, thanks for the input.
Justin
Hi,
On Tue, Apr 9, 2019 at 12:27 PM Justin Mclean wrote:
> ...I actually when though the mailing list for the last 6 months and checked
> what
> over 100 people had commented on one by one and reported back here. There was
> a clear
> correlation between those on the IPMC and those who are
Hi,
Sorry I was referring to the second part of your email not the first. it seems
you may of missed that bit of analysis. There is certainly some of what you say
but the majority of IPMC members, even those who are not that involved are
helpful and provide useful comments. The non-IPMC
Hi,
> I agree that drive-by comments are sometimes a problem here but I
> don't think they necessarily correlate with people being on the IPMC
> or not.
Like this discussion perhaps? :-) I actually when though the mailing list for
the last 6 months and checked what over 100 people had commented
+1, I like that formulation.
On 2019/04/09 09:26:00, Bertrand Delacretaz wrote:
> Hi,
>
> On Tue, Apr 9, 2019 at 10:43 AM Julian Feinauer wrote:
> > ...If its these "drive-by comments" that are annoying then I would name
> > that so, e.g. "What
> > seems less helpful in some cases is
Hi,
On Tue, Apr 9, 2019 at 10:43 AM Julian Feinauer wrote:
> ...If its these "drive-by comments" that are annoying then I would name that
> so, e.g. "What
> seems less helpful in some cases is involvement of non-IPMC members which drop
> comments and leave the discussion then
I agree that
Hi,
thanks for your clarification. I can only speak for myself and I try to involve
in discussions where I think I can be helpful or where I have a strong opinion
(usually from the podling perspective).
But, of course, I do not want to disturb things or annoy people on these lists,
so I was a
Hi,
> The last sentence indicates that non-IPMC members should not involve on this
> list? Is this the case?
Well we can’t stop them from being involved, and nor IMO should we, it is a
public list after all. And most of the time they can be useful and helpful,
it's just in some cases they
Hi Justin,
thanks for the report. I agree with all thats listed there, but theres one
passage which I dont understand or which makes me think... it is:
Having a smaller IPMC was discussed, it was suggested that anyone not
signed up to the private list be removed from the IPMC. This was looked
Hi,
> If the non-approved artifact is not advertised on the download page and is
> made available to the development community on request then we are good.
Well I think so, but I’m sure that release policy does and infra doesn’t seem
to allow it on docker hub, but perhaps they do “unofficial”
Sent from my iPhone
> On Feb 7, 2019, at 6:51 PM, Justin Mclean wrote:
>
> Hi,
>
> Give the response from intro on use of docker. it would seem that this is not
> actually allowed.
>
>> Nightly builds for project-internal use clearly marked as "snapshot" or
>> "prerelease" (or similar)
Hi,
> Give the response from intro on use of docker. it would seem that this is not
> actually allowed.
"response from INFRA" sorry.
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional
Hi,
Give the response from intro on use of docker. it would seem that this is not
actually allowed.
> Nightly builds for project-internal use clearly marked as "snapshot" or
> "prerelease" (or similar) can be made available to project contributors. If
> in doubt please ask your mentors or on
Hi -
> On Feb 7, 2019, at 3:41 PM, Justin Mclean wrote:
>
> Hi,
>
>> I respectfully request that you edit the following to make it less alarming
>> and remove any implication that the IPMC cannot handle our duties.
>
> I don’t read that implication there, this is quite factual all of the
Hi,
> I respectfully request that you edit the following to make it less alarming
> and remove any implication that the IPMC cannot handle our duties.
I don’t read that implication there, this is quite factual all of the project
had issues with unapproved releases that had gone unnoticed. I’ll
concerns,
but it is in limbo …
Regards,
Dave
> On Feb 7, 2019, at 12:38 AM, Justin Mclean wrote:
>
> Sorry I meant to send this to the list but only Dave got it.
>
>> Begin forwarded message:
>>
>> From: Justin Mclean
>> Subject: Re: Draft incubator rep
HI,
> "A reminder to all incubating projects and mentors that all releases
> and distributions advertised to the general public need to be approved by
> the PPMC and IPMC. This includes docker, github, PyPi, npm and any
> other platform for publishing releases, and also covers release candidates.
Cool. I think we've generated some consensus, even if we haven't answered
every question. To summarize, I'd like to change this paragraph of the
report:
"Again a reminder to all incubating projects and mentors that all releases
made available to the general public need to be approved by the
> On Feb 5, 2019, at 10:27 AM, Kevin A. McGrail wrote:
>
> On 2/5/2019 6:27 AM, Justin Mclean wrote:
>> Hi,
>>
As long as these are not available to the general public all is fine. [1]
>>> s/available/advertised/
>> Thanks that’s a better way of putting it. Obviously any published
On 2/5/2019 6:27 AM, Justin Mclean wrote:
> Hi,
>
>>> As long as these are not available to the general public all is fine. [1]
>> s/available/advertised/
> Thanks that’s a better way of putting it. Obviously any published artefact is
> available to the general public if and when they discover
Hi,
>> As long as these are not available to the general public all is fine. [1]
>
> s/available/advertised/
Thanks that’s a better way of putting it. Obviously any published artefact is
available to the general public if and when they discover it.
What’s important is that it’s not the
On 05/02/2019 10:23, Justin Mclean wrote:
> Hi,
>
>> We need a formulation which enables pre-release QA by non-coding
>> contributors. I've given my attempt at formulating it. Please give your
>> take on how to accomplish this.
>
> As long as these are not available to the general public all
Hi,
> That statement would also forbid maven snapshots. Something which many
> projects (TLPS too) offer. Is that the intention?
They are fine as you need to explicitly do something to use them, i.e. they are
not the default and the user understands that by using snapshots they are using
That statement would also forbid maven snapshots. Something which many
projects (TLPS too) offer. Is that the intention?
It’s important to me that when we forbid something that projects are doing
for valid reasons that we offer an alternative within the same statement.
I’ve offered a potential
Hi,
> We need a formulation which enables pre-release QA by non-coding
> contributors. I've given my attempt at formulating it. Please give your
> take on how to accomplish this.
As long as these are not available to the general public all is fine. [1]
Thanks,
Justin
1.
Hi Justin,
We need a formulation which enables pre-release QA by non-coding
contributors. I've given my attempt at formulating it. Please give your
take on how to accomplish this.
Best Regards,
Myrle
On Mon, Feb 4, 2019 at 10:01 PM Justin Mclean
wrote:
> Hi,
>
> > This does *not* include
Hi,
> This does *not* include nightly builds, or other project *internal* artifacts
> used for quality control and experimentation.”
Actually it does apply and those builds can’t be offered directly to the
general public, but each of the platforms has mechanisms for doing that.
For instance,
Hi Justin,
Everything looks good. Thank you!
By the way, I've noticed that some podling communities have been less
active since last week. The lunar new year day, tomorrow, might have
affected them, especially where most committers are working in Korea
or China. That can't be an excuse though.
Hi Justin,
This looks good.
in your general notice about releases, please include a note about nightly
builds, and any other non-releases which communities can make.
In other words, after: "This includes docker, githubb, PyPi, npm and any
other platform for
publishing releases, and also covers
Hi,
You can edit it in whimsy.
Thanks,
Justin
On Fri, 11 Jan 2019, 08:50 Myrle Krantz Hey Justin,
>
> I just signed off weex... and then realized I was signing off on a report
> that was already submitted. Sorry about that.
>
> Best Regards,
> Myrle
>
> On Mon, Jan 7, 2019 at 8:55 AM Justin
Hey Justin,
I just signed off weex... and then realized I was signing off on a report
that was already submitted. Sorry about that.
Best Regards,
Myrle
On Mon, Jan 7, 2019 at 8:55 AM Justin Mclean wrote:
> Hi,
>
> Currently there's a couple of projects don’t have any sign offs. While we
>
Hi,
Currently there's a couple of projects don’t have any sign offs. While we have
more than a day to go please don't leave it too late. Just a friendly reminder
any project that doesn't get any sign-off will be asked to report next month
and the board likes to see more than one sign off.
I am on a cell phone most of the day today, but i can check in the evening.
If anyone bit me to it, there is a copy of the report on the marvin dev
list.
On Tue, Oct 2, 2018 at 05:17 John D. Ament wrote:
> There's a conflict in the Marvin AI report, not sure which sections to fix
> though.
>
>
There's a conflict in the Marvin AI report, not sure which sections to fix
though.
On Tue, Oct 2, 2018, 06:40 Justin Mclean wrote:
> Hi,
>
> I’m still waiting for a few podlings to submit their reports but have made
> a draft incubator report. [1] Feedback, suggested changes, spelling or
>
Hi,
The report has been submitted.
In the end one two podling didn’t report (Gearpump and Milagro) and two reports
didn’t have any sign offs (OpenWhisk and Warble).
Thanks,
Justin
Hi,
I’ve updated the draft incubator report here. [1].
Currently we are missing reports from 3 podlings; Gearpump, Milagro and
OpenWhsk, and a number of report sign offs.
If you are a mentor of a project please read the report, sign off and make any
comments you think are needed before
Hi,
> HAWK graduated to TLP.
That should be HAWQ - thank you auto correct.
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
47 matches
Mail list logo
