All the best in your Apache journey!
Regards,
Dave
Sent from my iPhone
> On Sep 13, 2019, at 7:22 PM, Adina Crainiceanu wrote:
>
> The vote to recommend Apache Rya graduation to Top Level Project resolution
> to the board has passed with:
>
> 9 binding +1 votes:
>
> Billie Rinaldi
> Josh
12, 2019, at 6:42 AM, Dave Fisher wrote:
>
> Inline
>
> Sent from my iPhone
>
>> On Sep 12, 2019, at 3:18 AM, SHUANG SU wrote:
>>
>> Justin & Furkan, thank you for the detailed check!
>>
>> There is a relevant build instruction in
>> h
Inline
Sent from my iPhone
> On Sep 12, 2019, at 3:18 AM, SHUANG SU wrote:
>
> Justin & Furkan, thank you for the detailed check!
>
> There is a relevant build instruction in
> https://echarts.apache.org/en/tutorial.html#Create%20Custom%20Build%20of%20ECharts
> and the link is listed in
gt; Since the build was broken I'm not sure what I'm looking at right now
> unfortunately.
>
>> On Tue, Sep 10, 2019, 21:20 Dave Fisher wrote:
>>
>> Look at incubator.apache.org/clutch/tamaya.html
>>
>> Sent from my iPhone
>>
>>> On Sep 10, 201
planning to handle projects like Tamaya with
> multiple git repos? I put a link to the query on github that shows you all
> of their repos.
>
> John
>
>> On Tue, Sep 10, 2019 at 8:32 PM Dave Fisher wrote:
>>
>> Hi -
>>
>> All fixed.
>>
>&
training: urlWww=http://training.incubator.apache.org/
> tuweni: urlWww=http://tuweni.apache.org/
> tvm: urlWww=http://tvm.incubator.apache.org/
> weex: urlWww=http://weex.incubator.apache.org/
> ```
>
> - Sijie
>
> On Tue, Sep 10, 2019 at 4:13 PM Dave Fisher wrote:
&g
Hi -
Thanks for fixing the problem with Rya’s status page.
I’m not sure what is happening with this error. It works on python 3.7.3 but
not on the build bot.
If at ACNA and will talk directly with Infra and/or figure out whatever the
error is.
Thanks,
Dave
> On Sep 10, 2019, at 3:29 PM,
Carrying over +1 (binding)
Sent from my iPhone
> On Sep 5, 2019, at 9:37 PM, Antoine Toulme wrote:
>
> Hi all,
> The Tuweni community voted on and has approved a proposal to release Apache
> Tuweni 0.8.2.
>
> Pursuant to the Releases section of the Incubation Policy and we would now
> like
HI
> On Sep 5, 2019, at 11:25 AM, Nygard, Carl J wrote:
> Hi,
>
>>> Cengage wishes to donate the code to Apache, but is unable to do so until
>>> the project is accepted as an Incubator project.
>
>> Could you expand a little on why is that?
>
> Perhaps it is an issue of understanding the
> On Sep 4, 2019, at 3:50 PM, Justin Mclean wrote:
>
> Hi,
>
> Thursday morning here and still to report are:
> Amaterasu*
> Hivemall
> Iceberg
> Marvin-AI
> Omid**
> SINGA
> Superset
> Tamaya*
> Taverna
> Tephra
> Warble
Warble just reported….
>
> * did not report last month.
>
> A
Hi -
I see the discussion that an SGA is not needed about 4/2/2015. [1]
I don’t necessarily see the there was a conclusion to that discussion on
private@singa. I certainly don’t see anything related to Singapore in the
grants index in the foundation records. There are plenty of other sgas
Hi -
As one of the mentors to Daffodil I hope to be there. FYI - The only thing that
prevents Daffodil’s graduation is community growth. This is not a criticism of
the podling. They are attempting to grow the community. This really fills an
important capability of applying schemas to any file
The Jenkins jobs that update the incubator projects and project status pages
run every 24 hours at end of day at roughly 19:00 PDT.
Regards,
Dave
Sent from my iPhone
> On Aug 30, 2019, at 2:18 AM, Sheng Wu wrote:
>
> I am just curious whether this is manual way :)
>
> Sheng Wu 吴晟
>
>
Hi -
Sorry for my top post, but I have some observations about your “guide”.
(1) It is more a mentoring FAQ than a guide.
(2) You are listing symptoms / policy violations.
(3) It would be better to discuss what community problem is causing the
particular issue instead of putting the blame on
You have enough IPMC votes from your mentors.
I think you are good.
Sent from my iPhone
> On Aug 19, 2019, at 7:36 PM, Joshua Poore wrote:
>
> Hi Folks—
>
> Just a reminder to VOTE on Apache Flagon UserALE.js (Incubating) v2.0.2.
>
> We’ve passed the VOTE on dev@, still looking for a few
; according to ASF Committer list[1], he has been a member of IPMC
>
>
> [1] http://people.apache.org/phonebook.html?uid=djkevincr
>
> Sheng Wu 吴晟
>
> Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> Twitter, wusheng1108
>
>
> Dave Fisher 于2
Kevin,
Since you a member all you need do to join the IPMC is to send an email to
private@ requesting to be added.
Regards,
Dave
> On Aug 18, 2019, at 3:42 AM, Kevin Ratnasekera wrote:
>
> Hi Sheng,
>
> If there is space and help is needed, I am interested in mentoring the
> project. Even
Hi -
Feel free to submit a PR to
https://github.com/apache/incubator/blob/master/pages/guides/podling_sourcecontrol.ad
Regards,
Dave
> On Aug 15, 2019, at 12:50 PM, Marco de Abreu wrote:
>
> Hi,
>
> I stumbled across this [1] guide and noticed that the link [2] is broken.
> The correct one
> On Aug 14, 2019, at 3:59 AM, Greg Stein wrote:
>
> On Mon, Aug 12, 2019, 22:31 David Nalley wrote:
>> ...
>
>> Greg - I propose that you, Ross (sorry for volunteering you), and I
>> pick an incubating project in need of mentor attention and make this
>> as streamlined as we can. Let's
>>
>> Q: Does the IPMC want to produce non-ASF releases?
My answer is yes! I want podlings to be on a path towards graduation! I
recognize multiple requirements. The path may differ for each podling. I’m the
end there are two outcomes!
Thanks Greg!
Regards,
Dave
>>
>> -g
>
>
>
Sent from my iPhone
> On Aug 13, 2019, at 9:32 PM, Greg Stein wrote:
>
> On Tue, Aug 13, 2019 at 8:17 PM Justin Mclean
> wrote:
>
>> Hi,
>>
>>> Hoops constructed by the IPMC. Like a secondary release vote on general@
>>
>> This is because of ASF bylaws i.e only PMC votes are binding on
that change?
>
> Every other change is peripheral.
>
>
>
> On Tue, Aug 13, 2019 at 8:37 AM Dave Fisher wrote:
>
>>
>>
>>> On Aug 12, 2019, at 1:34 PM, Ted Dunning wrote:
>>>
>>> On Mon, Aug 12, 2019 at 11:10 AM Da
> On Aug 12, 2019, at 1:34 PM, Ted Dunning wrote:
>
> On Mon, Aug 12, 2019 at 11:10 AM Dave Fisher <mailto:w...@apache.org>> wrote:
>
>>
>>
>>> On Aug 12, 2019, at 10:02 AM, Ted Dunning wrote:
>>>
>>> On Mon, Aug 12, 2019 at 9:
+1 (binding)
Regarding: QU30: See https://www.apache.org/security/ and
https://www.apache.org/security/committers.html
https://druid.apache.org/druid-powered is impressive.
Regards,
Dave
> On Aug 13, 2019, at 12:03 AM, Gian Merlino wrote:
>
> The Apache Druid community has recently
Sent from my iPhone
> On Aug 13, 2019, at 2:39 AM, Justin Mclean wrote:
>
> HI,
>
> I think there's a couple of misconceptions in this thread. First off
> currently you can join the IPMC two ways by being an ASF member and asking to
> join, the other by being voted in. On average the
Hi -
I’ve been following as a member of the brand committee and have no concern
about Druid graduation at this time.
Regards,
Dave
Sent from my iPhone
> On Aug 12, 2019, at 10:12 PM, Gian Merlino wrote:
>
> FYI- we gave the board a heads up too and received generally positive
> feedback. I
> On Aug 12, 2019, at 4:29 PM, Greg Stein wrote:
>
> On Mon, Aug 12, 2019 at 5:26 PM Justin Mclean
> wrote:
>
>> Hi,
>>
>>> I will also note that if the IPMC switches to *voting* Members into the
>>> IPMC, that the Apache Member will be observing that vote take place on
>>> private@
> On Aug 12, 2019, at 10:02 AM, Ted Dunning wrote:
>
> On Mon, Aug 12, 2019 at 9:24 AM Jim Jagielski wrote:
>
>>
>>
>>> On Aug 12, 2019, at 10:44 AM, Ted Dunning wrote:
>> ...
"The Apache Podling Foo has voted on releasing Foo 1.2.2 (url and
pointers here). We have 3 (or more)
Hi -
> On Aug 12, 2019, at 6:41 AM, Matt Sicker wrote:
>
> This observer IPMC role sounds interesting. That would make it less
> intimidating for people who can help verify a generic release but are
> unfamiliar with the domain itself.
We currently have Shepherds to look into podlings at
Hi -
> On Aug 12, 2019, at 8:44 AM, Julian Feinauer
> wrote:
>
> Hi Ted,
>
> dont get me wrong, I'm rather new to the ASF, the incubator and especially
> the IPMC. So my perspective might be different. But, I understand the
> frustration that some may have and I leant that there have been
> On Aug 12, 2019, at 9:24 AM, Jim Jagielski wrote:
>
>
>
>> On Aug 12, 2019, at 10:44 AM, Ted Dunning wrote:
>>
>> On Mon, Aug 12, 2019 at 5:20 AM Jim Jagielski wrote:
>>
>>> ...
>>> This does NOT mean that the IPMC should be gatekeepers though... Just as
>>> PMC chairs are the "eyes
Hi Furkan,
The clutch is looking at the Podling’s status xml and for DLab there is an
incorrect id attribute for the tracker url:
Change:
https://issues.apache.org/jira/projects/DLAB/;>https://issues.apache.org/jira/projects/DLAB/
To:
Hi Justin,
A couple of suggested edits to the responsibilities:
- Welcoming new Podlings to become part of the Apache Software Foundation (ASF).
- Guiding Podlings to govern and grow their communities according to *the
Apache Way*, the ASF's philosophy and guidelines for collaborative
have one vote in. We request
> the Incubator PMC members to review and vote on this incubator
> release.
>
> The results of the Release Candidate 3 votes are below:
>
> - Binded Approvals: 1
>
> * Dave Fisher
>
> - Vote Thread
>
> https://mail-archives.apac
Thank you Bertrand.
Regards,
Dave
> On Jul 22, 2019, at 7:18 AM, bdelacre...@apache.org wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> bdelacretaz pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/incubator.git
>
>
> The
Only VPs of TLPs need to subscribe.
Sent from my iPhone
> On Jul 21, 2019, at 9:37 AM, Tom Barber wrote:
>
> Hello
>
> Quick protocol question as the board isn’t fit for purpose and I’m fed up
> of it clogging up my inbox. Do incubating project chairs for incubating
> projects have to be
> On Jul 1, 2019, at 1:30 AM, Bertrand Delacretaz
> wrote:
>
> Hi,
>
>> On Sun, Jun 30, 2019 at 1:39 AM Justin Mclean
>> wrote:
>> ...I put up suggested text changes for an incubator disclaimer here [1]...
>
> Basically just adding this, right?
>
>> Some of the project releases may not
Sent from my iPhone
> On Jul 12, 2019, at 7:32 PM, Justin Mclean wrote:
>
> HI,
>
>> +1 if as discussed earlier we enhance both disclaimers to include a link to
>> the podling status page where the podling will provide the most up to date
>> details.
>
> I think the text needs to refer
+1 if as discussed earlier we enhance both disclaimers to include a link to the
podling status page where the podling will provide the most up to date details.
We can discuss a new Git based status page in a separate thread. I’d like to
change from the xml/secret yaml files in svn to a straight
in git with v2.4.0-rc1.
>
> For reference, here is a list of all closed JIRAs tagged with 2.4.0:
>
> https://s.apache.org/daffodil-issues-2.4.0
>
> For a summary of the changes in this release, see:
>
> https://daffodil.apache.org/releases/2.4.0/
>
> One +1 (binding
+1 (binding)
I’ve reviewed the Maturity Model, recent activity, and the large number of
repositories(51) vs. released artifacts (21) [1][2]
I wanted to note two things:
- In looking at contributing [2] I notice that there is a higher bar than many
projects in requiring an ICLA. Given the large
Various podlings including tuweni have had to handle downloading gradle
separately. It’s not unusual and not really a source code issue where the
correct boundary is drawn.
Regards,
Dave
Sent from my iPhone
> On Jul 5, 2019, at 8:42 PM, Rodric Rabbah wrote:
>
> We’ll sort it out I opened an
Sent from my iPhone
> On Jul 3, 2019, at 3:59 PM, Daniel Shahaf wrote:
>
> Alex Harui wrote on Wed, 03 Jul 2019 21:35 +:
>> Re-rolling required re-GPG-signing, new hashes, etc.
>
> Yes, I know how re-rolling works. I've RM'd things before. I still think
> in-band is better.
It
Sent from my iPhone
> On Jul 3, 2019, at 2:53 PM, Roman Shaposhnik wrote:
>
>> On Wed, Jul 3, 2019 at 2:13 PM Jim Jagielski wrote:
>>
>>
>>
On Jul 3, 2019, at 5:06 PM, Roman Shaposhnik wrote:
1. Podlings, and PPMC members, to enjoy the legal protection of the
> On Jul 3, 2019, at 12:32 PM, Roman Shaposhnik wrote:
>
> On Wed, Jul 3, 2019 at 12:29 PM Dave Fisher wrote:
>>
>>
>>
>>> On Jul 3, 2019, at 12:24 PM, Roman Shaposhnik wrote:
>>>
>>> On Wed, Jul 3, 2019 at 12:17 PM Dave Fisher wrot
> On Jul 3, 2019, at 12:24 PM, Roman Shaposhnik wrote:
>
> On Wed, Jul 3, 2019 at 12:17 PM Dave Fisher wrote:
>>> On Jul 3, 2019, at 11:50 AM, Roman Shaposhnik wrote:
>>>
>>> On Tue, Jul 2, 2019 at 10:28 AM Dave Fisher wrote:
>>>>
+1.
> On Jul 3, 2019, at 11:49 AM, Daniel Shahaf wrote:
>
> Guys, aren't you forgetting something? The VP is to sign the Board
> report. Everything else that Justin is doing he's doing as a rank and
> file Incubator committer. If you disagree with Justin, that's one
> thing, but his being
> On Jul 3, 2019, at 12:16 PM, Dave Fisher wrote:
>
>
>
>> On Jul 3, 2019, at 11:50 AM, Roman Shaposhnik wrote:
>>
>> On Tue, Jul 2, 2019 at 10:28 AM Dave Fisher wrote:
>>>
>>> Hi -
>>>
>>>> On Jul 1, 2019, at 1:30 A
> On Jul 3, 2019, at 11:50 AM, Roman Shaposhnik wrote:
>
> On Tue, Jul 2, 2019 at 10:28 AM Dave Fisher wrote:
>>
>> Hi -
>>
>>> On Jul 1, 2019, at 1:30 AM, Bertrand Delacretaz
>>> wrote:
>>>
>>> Hi,
>>>
>>
All we need is a simple pivot back. This is the closest, easiest path.
Prioritize and ease the acceptance of the Apache Way.
Our current Disclaimer is enough. If governing in the way then the path to a
PMC is eased.
We need to assure that the lessons from all versions of the Incubator are
Hi -
To me you have two parts. One fits Apache and the other would need to be
outside.
(1) Open Source Software which is the library, service and CLI tools. This is
something that an Apache Community could grow around and be governed in the
Apache Way. This part can be incubated.
(2) Open
Hi -
> On Jul 1, 2019, at 1:30 AM, Bertrand Delacretaz
> wrote:
>
> Hi,
>
> On Sun, Jun 30, 2019 at 1:39 AM Justin Mclean
> wrote:
>> ...I put up suggested text changes for an incubator disclaimer here [1]...
>
> Basically just adding this, right?
>
>> Some of the project
Hi -
LGTM!
Some comments inline:
> On Jul 2, 2019, at 8:42 AM, David P Grove wrote:
>
> Justin Mclean wrote on 07/02/2019 05:53:06 AM:
>>
>> There were a couple of minor issue around branding. communication
>> and releases brought up in the discussion on graduation, I believe
>> most (if
You have your 3 +1 Votes!
We can discuss messaging on dev@tuweni
> On Jun 27, 2019, at 2:04 PM, Antoine Toulme wrote:
>
> I’m not quite sure what to do. If I don’t hear by tomorrow I’ll close this
> vote as passing.
>
>> On Jun 27, 2019, at 10:42 AM, Greg Stein wrote:
>>
>> On Thu, Jun 27,
[
https://issues.apache.org/jira/browse/INCUBATOR-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874279#comment-16874279
]
Dave Fisher commented on INCUBATOR-240:
---
Lee, This should be an INFRA JIRA issue. Also
Sent from my iPhone
> On Jun 26, 2019, at 6:17 AM, Justin Mclean wrote:
>
> Hi,
>
>> Going only by past experiences in the incubator, my understanding is that a
>> graduation blocking issue is not something that necessarily blocks a
>> podling release.
>
> And I was not stating that, nor
+1 (binding) carried over from dev@tuweni Vote.
Regards,
Dave
Sent from my iPhone
> On Jun 24, 2019, at 6:39 AM, Jim Jagielski wrote:
>
> +1 (binding) - carried over from PPMC vote
>
>> On Jun 24, 2019, at 6:03 AM, Antoine Toulme wrote:
>>
>> Hi all,
>> The Tuweni community voted on and
Thanks Roman!
+1 to the 2nd camp!
Regards,
Dave
Sent from my iPhone
> On Jun 23, 2019, at 8:25 PM, Roman Shaposhnik wrote:
>
>> On Sat, Jun 22, 2019 at 3:31 PM Rich Bowen wrote:
>>
>> A couple of thoughts:
>
> And a couple of thoughts on top of that.
>
>> Podlings are not permitted to
I find TVM concentrating on moving their community to Apache first to be very
refreshing. I think that may allow an eyes wide open approach to Apache
governance.
I think a soft approach to policy compliance will yield better, happier Apache
communities.
The Incubator should celebrate the
> On Jun 19, 2019, at 10:28 AM, Bertrand Delacretaz
> wrote:
>
> On Wed, Jun 19, 2019 at 7:14 PM Ted Dunning wrote:
>> ...This vote is *confirming* that
>> nobody has objections (of any form) to Zipkin leaving and control of the
>> git repos being transferred...
>
> I agree and this means
on (1), when (3) via (2) is IMO
more important.
Maybe we need to reorder our curriculum?
Regards,
Dave
> On Jun 19, 2019, at 8:39 AM, Dave Fisher wrote:
>
> Hi Justin,
>
> You are certainly correct about this. I’ve been learning to cook the last few
> years and have a c
Hi Justin,
You are certainly correct about this. I’ve been learning to cook the last few
years and have a cupboard full of recipes to follow.
I made a directory in the incubator git for us all to share our tools and
recipes in the hopes that they are useful.
Hi -
I agree with Greg and Bertrand to focusing on the Incubator's service
orientation. And have written in other threads that we should update our
documentation.
A podling exit needs to be visible to the Incubator here on general@. (Jim’s
clear trail)
(1) In order to maintain a record about
Hi David and Greg,
> On Jun 18, 2019, at 5:39 PM, Justin Mclean wrote:
>
> HI,
>
> +1 (binding)
>
> I hope the podling has better success outside the ASF.
>
> BTW in all previous cases of podlings exiting I could find, a vote was taken
> (see below links and there’s more I’ve not listed).
mire projects like Maven or
>> TomEE and to want and aim to be like them, regardless of the contortions
>> required to get there.
>>
>> Gj
>>
>>
>> On Thu, 13 Jun 2019 at 21:10, Dave Fisher wrote:
>>
>>> Hi -
>>>
>>> Here are some
Apologies for replying twice in a row to the thread.
> On Jun 18, 2019, at 10:32 AM, Ted Dunning wrote:
>
> Alex, Jim, Bertrand,
>
> This discussion is re-inventing a discussion that has been had before. At
> one time, the incubator tried to present principles to incoming podling
> (albeit not
> On Jun 18, 2019, at 4:42 AM, Bertrand Delacretaz
> wrote:
>
> On Tue, Jun 18, 2019 at 1:18 PM Jim Jagielski wrote:
>> ...prepping the existing community regarding what "moving to the ASF means"
>> is the job of the Champion, no?...
>
> I agree but it has to be based on written docs, not
+1 Agree. Best of luck to the OpenZipkin community going forward.
(Please make sure that RO clones of the repositories are kept by Infra for the
record.)
Regards,
Dave
Sent from my iPhone
> On Jun 17, 2019, at 6:21 PM, Sheng Wu wrote:
>
> Hi
>
> This is a call for official vote of Zipkin
Hi -
A retirement VOTE on general@ is required. [1] This is the last formality
required. Incubation is not for every project.
Then follow [2] as much as possible, but with the exception of transferring the
repositories back to OpenZipken. In addition the IPMC will request that INFRA
make
gt;> Spread out pretty thin with all the things I do for the ASF) to deal
>>> with rebellious podlings.
>>>>
>>>> Chris
>>>>
>>>>
>>>>
>>>>
>>>> Perhaps creating a training session as part of the trainin
Hi Greg,
I agree. A pragmatic, incremental, trust in a community’s best intentions is
all we should ask.
To me the minimum requirements are:
(1) License is AL v2.
(2) Disclaimer is standard. I don’t want it to vary because then we’ll discuss
correctness.
(3) Signature.
(4) Checksum.
The rest
Hi -
> On Jun 14, 2019, at 5:08 AM, York Shen wrote:
>
> It depends on the definition of optional dependency. Weex targets iOS,
> Android and Browser environment and Webkit header files and shared library
> are only bundled for Android environment. As for other environments, the OS
> or
Hi Merle,
A footnote on your list below.
Sent from my iPhone
> On Jun 14, 2019, at 2:39 AM, Myrle Krantz wrote:
>
> I feel like the answers provided here up till now are too simple. I
> believe we have projects at Apache which seem to be using, or have used
> Webkit: (
>
Hi -
Here are some thoughts I have to improving Incubation. These are not really
new, but I think we should discuss where and how best to apply these.
(1) Champions need to very clear that the ASF expects Community decisions not
BDFLs. Burnout is one factor to highlight why community is
Hi -
The ASF expects that PMCs will watch out for their project and product brands.
The VP, Brand and their committee are available to help with advice and also
trademark registrations via the tradema...@apache.org mailing list.
My only concern with the README.md files in some Github project
Hi -
This is very interesting. I’m going to be digging into it.
Regards,
Dave
> On Jun 8, 2019, at 8:09 PM, Justin Mclean wrote:
>
> Hi,
>
> Please keep the discussion here and not in the vote thread,
>
> Even if not voting, mentors and IPMC members may want to talk a look at the
>
Top Post.
(1) We are losing track of the goal. The goal is to make it easier for
incubating projects to begin to follow Foundation Release and Distribution
Policies on their path to adopting the Apache Way, building a Community and
graduating to become a TLP project. I think the IPMC has
I have a question below.
Sent from my iPhone
> On Jun 7, 2019, at 6:37 PM, Rodric Rabbah wrote:
>
> The PMC has individuals from 6 unrelated companies. I think committers add
> another 2 unrelated companies/entities. We expect to welcome new committers
> after graduation.
>
> -r
>
>> On
FYI - On the Doris Dev list I’ve asked some questions about third party
dependencies to clarify what is required vs. optional.
I’ll note that there are some archives included in the release which are
related to test cases.
Under my opinion of what’s permissible on a first release I would
[
https://issues.apache.org/jira/browse/INCUBATOR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Fisher resolved INCUBATOR-238.
---
Resolution: Fixed
The project xml files are processed and staged into git once a day from
Kevin and Justin,
This is spot on.
Disclaimer, signatures/checksums, Apache license, and a start to notes are the
minimum.
Acceptance of issues to fix is also a requirement.
Full compliance with Apache Release and Distribution Policies are some of our
agreed Incubation requirements for
Apologies for the delay.
-1 (binding)
Policy violations:
The missing DISCLAIMER in the source release is a blocker.
Please move https://dist.apache.org/repos/dist/dev/tuweni to
https://dist.apache.org/repos/dist/dev/incubator/tuweni for the next candidate.
I checked the signatures and
ntly, the thing to fix is not the release
> cadence.
>
> This project is overdue to graduate; that, not the release cadence, is why
> mentors are a bit burned out.
>
> Julian
>
>
>> On May 21, 2019, at 6:05 PM, Dave Fisher wrote:
>>
>> I noticed a 0
I noticed a 0 vote by a PPMC member saying the cadence is too frequent for a
database product and thinking it may impact perceived stability.
Just a data point.
Regards,
Dave
Sent from my iPhone
> On May 21, 2019, at 5:36 PM, Julian Hyde wrote:
>
> No.
>
> In my defense, Druid has produced
Hi Justin,
Please remove Dubbo since it graduated.
Regards,
Dave
Sent from my iPhone
> On May 21, 2019, at 4:57 PM, Dave Fisher wrote:
>
> Hi Justin,
>
> You gave me four to shepherd again and missed Drew.
>
> Thanks,
> Dave
>
>> On May 21, 2019,
Hi Justin,
You gave me four to shepherd again and missed Drew.
Thanks,
Dave
> On May 21, 2019, at 4:49 PM, Justin Mclean wrote:
>
> Hi,
>
> It been suggested we use markdown for the incubator reports. I modified the
> this months report [1] to have:
> - a table of contents
> - headings
> -
Hi -
I think that we are mixing together a few events in a podling's lifecycle.
Since I published a plan to update the status process and am just about to
implement I think we should discuss events in a modern way since much of the
language is a decade or more old and we are each trying to
> On May 13, 2019, at 2:23 PM, Kenneth Knowles wrote:
>
> Thanks for the detailed steps.
>
> (2) SGAs are typically needed when the project code is donated by a
>> company, these go to secretary@. A CCLA might substitute for that, but
>> that is up to legal-discuss@apache. Once the IP is
Hi Kenneth,
I’m sorry about the state of documentation.
Let’s separate the ICLA requirement from the SGA question.
(1) Each initial committer / PPMC member needs to have an ICLA on file with
secretary@apache before their account is created. The mentors are responsible
for tracking this and
Hi Rich,
It has been disappointing that no progress has been made for so long.
Do we need one more shot at mentoring or is it time to retire?
Regards,
Dave
Sent from my iPhone
> On May 13, 2019, at 10:33 AM, Rich Bowen wrote:
>
> Hi, folks.
>
> I'm not sure who to direct this to.
>
> The
Hi -
The subject came up in another list and I thought I would share the current
state of editing of pooling status pages.
I am currently working on improvements from within Whimsy, but since these are
not done and I cannot predict when the work will be finished here you go:
See:
Hi -
I would discuss this with Apache Infra. Either:
join https://the-asf.slack.com - #asfinfra, or
subscribe to us...@infra.apache.org and send an email.
Regards,
Dave
> On May 10, 2019, at 12:08 PM, leerho wrote:
>
> I am in the process of trying to move code from our current GitHub
>
Hi -
A few points about the Apache Software Foundation and Incubation.
(1) Projects work best when they bring in both a small community of developers
and a codebase.
(2) Projects learn the Apache Way of project governance which includes
releasing under the Apache License.
Until you do have a
a good avenue to pursue instead of rolling our own. They
>> handle fundraising's moderation, for example as well as trademarks.
>>
>> Email mod-priv...@gsuite.cloud.apache.org if interested.
>>
>> I think we could create a moderation PMC and try and centralize this
&
Hi -
It looks like we need two or three new volunteers to help moderate this mailing
list. Many of the five moderators are not very active in the incubator at this
time.
(I’d volunteer, but I’m currently moderating some 22 lists…)
Regards,
Dave
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
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
+1 (binding)
> On Apr 30, 2019, at 6:44 PM, Huxing Zhang wrote:
>
> Hi All,
>
> After discussion in the Apache Dubbo community on the dev mailing
> list[1], choosing PMC chair[2], forming the PMC members[3], completing
> the maturity model[4], discussing the resolution proposal[5], and
>
Hi -
The gitbox directory at http://gitbox.apache.org/repositories.json stopped
providing a commit count on April 26 or 27.
I’ve commented this out. Everything should be back to normal now without that
information on the clutch analysis pages.
Regards,
Dave
> On May 1, 2019, at 6:34 AM, sebb
Hi Justin,
I’ll take a look. It may be tomorrow.
Regards,
Dave
Sent from my iPhone
> On Apr 30, 2019, at 6:47 PM, Justin Mclean wrote:
>
> Hi,
>
> JFYI The clutch report is currently failing right at the end, not sure what
> the issue is.
>
> FINAL: current: 50
> FINAL: date: Wed May 1
401 - 500 of 1155 matches
Mail list logo
