[jira] [Commented] (INCUBATOR-203) Rename Proposals to something else, add more how to get in information

[Dave Fisher (JIRA)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801391#comment-16801391
 ] 

Dave Fisher commented on INCUBATOR-203:
---

Really this can be about updating the Podling Proposal Menu to better separate 
guidance from policy.

> Rename Proposals to something else, add more how to get in information
> --
>
> Key: INCUBATOR-203
> URL: https://issues.apache.org/jira/browse/INCUBATOR-203
> Project: Incubator
>  Issue Type: Improvement
>  Components: guides
>Reporter: John D. Ament
>Assignee: Dave Fisher
>Priority: Major
>
> The current proposal top level menu item is good, but lacks some useful 
> information.  Instead of being called proposals, maybe call it "Becoming an 
> Apache Project" and include some information:
> - Proposal process
> - Update entry to give a higher level how it works
> - Include docs on SGAs, IP Clearance, when each is needed



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Assigned] (INCUBATOR-203) Rename Proposals to something else, add more how to get in information

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher reassigned INCUBATOR-203:
-

Assignee: (was: Dave Fisher)

> Rename Proposals to something else, add more how to get in information
> --
>
> Key: INCUBATOR-203
> URL: https://issues.apache.org/jira/browse/INCUBATOR-203
> Project: Incubator
>  Issue Type: Improvement
>  Components: guides
>Reporter: John D. Ament
>Priority: Major
>
> The current proposal top level menu item is good, but lacks some useful 
> information.  Instead of being called proposals, maybe call it "Becoming an 
> Apache Project" and include some information:
> - Proposal process
> - Update entry to give a higher level how it works
> - Include docs on SGAs, IP Clearance, when each is needed



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Commented] (INCUBATOR-208) Transferring guide needs an editing pass

[Dave Fisher (JIRA)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801388#comment-16801388
 ] 

Dave Fisher commented on INCUBATOR-208:
---

The page needs a pass and the instructions under "Update the Incubator status 
records" needs to be provided. These will likely be on a page that explains how 
to make status file changes.

> Transferring guide needs an editing pass
> 
>
> Key: INCUBATOR-208
> URL: https://issues.apache.org/jira/browse/INCUBATOR-208
> Project: Incubator
>  Issue Type: Bug
>  Components: guides
>Reporter: Jim Apple
>Priority: Major
>
> There are a number of issues with the transferring page:
> "{{noformat}}#foundation/officers/irs-disclosures.txt*{{noformat}" has some 
> odd characters prepended and appended.
> https://incubator.apache.org/guides/transferring.html#notes-status is a 
> missing anchor
> "Final Revision of Podling Incubation Records" has bizarre formatting.
> I suspect these are not the only issues.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Resolved] (INCUBATOR-223) Website build fails with jbake 2.6.2

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher resolved INCUBATOR-223.
---
Resolution: Fixed
  Assignee: Dave Fisher

> Website build fails with jbake 2.6.2
> 
>
> Key: INCUBATOR-223
> URL: https://issues.apache.org/jira/browse/INCUBATOR-223
> Project: Incubator
>  Issue Type: Bug
>  Components: site
>Reporter: Shane Curcuru
>Assignee: Dave Fisher
>Priority: Major
>
> OSX 10.x, jbake 2.6.2 from Homebrew fails to build the website.  Tips from 
> anyone who's built the website locally on Mac appreciated, especially if 
> there are ruby or jbake version limitations.
> jbake seems to parse a number of pages with some complaints, but then dies 
> with:
> 10:12:51.910 INFO org.jbake.app.Crawler - Processing 
> [/Users/curcuru/src/g/incubator/pages/past_podlings.ad]... : new 
> 10:12:52.039 ERROR o.a.internal.JRubyAsciidoctor - org.jruby.RubyNoMethodError
> 10:12:52.041 INFO c.o.orient.core.Orient - Orient Engine is shutting down...
> 10:12:52.043 INFO c.o.orient.core.Orient - - shutdown storage: cache...
> 10:12:52.328 INFO c.o.orient.core.Orient - OrientDB Engine shutdown complete
> An unexpected error occurred: org.jruby.exceptions.RaiseException: 
> (NoMethodError) asciidoctor: FAILED: : Failed to load AsciiDoc 
> document - undefined method `start_with?' for nil:NilClass
> org.asciidoctor.internal.AsciidoctorCoreException: 
> org.jruby.exceptions.RaiseException: (NoMethodError) asciidoctor: FAILED: 
> : Failed to load AsciiDoc document - undefined method `start_with?' 
> for nil:NilClass
>  at 
> org.asciidoctor.internal.JRubyAsciidoctor.render(JRubyAsciidoctor.java:341)
>  at 
> org.asciidoctor.internal.JRubyAsciidoctor.render(JRubyAsciidoctor.java:448)
>  at 
> org.jbake.parser.AsciidoctorEngine.processAsciiDoc(AsciidoctorEngine.java:158)
>  at org.jbake.parser.AsciidoctorEngine.processBody(AsciidoctorEngine.java:152)
>  at org.jbake.parser.MarkupEngine.parse(MarkupEngine.java:118)
>  at org.jbake.app.Parser.processFile(Parser.java:44)
>  at org.jbake.app.Crawler.crawlSourceFile(Crawler.java:193)
>  at org.jbake.app.Crawler.crawl(Crawler.java:112)
>  at org.jbake.app.Crawler.crawl(Crawler.java:65)
>  at org.jbake.app.Oven.bake(Oven.java:137)
>  at org.jbake.launcher.Baker.bake(Baker.java:32)
>  at org.jbake.launcher.Main.run(Main.java:97)
>  at org.jbake.launcher.Main.run(Main.java:83)
>  at org.jbake.launcher.Main.main(Main.java:56)
> Caused by: org.jruby.exceptions.RaiseException: (NoMethodError) asciidoctor: 
> FAILED: : Failed to load AsciiDoc document - undefined method 
> `start_with?' for nil:NilClass
>  at 
> RUBY.parse_section_title(uri:classloader:/gems/asciidoctor-1.5.7.1/lib/asciidoctor/parser.rb:1734)
>  at 
> RUBY.initialize_section(uri:classloader:/gems/asciidoctor-1.5.7.1/lib/asciidoctor/parser.rb:1564)
>  at 
> RUBY.next_section(uri:classloader:/gems/asciidoctor-1.5.7.1/lib/asciidoctor/parser.rb:290)
>  at 
> RUBY.parse(uri:classloader:/gems/asciidoctor-1.5.7.1/lib/asciidoctor/parser.rb:96)
>  at 
> RUBY.parse(uri:classloader:/gems/asciidoctor-1.5.7.1/lib/asciidoctor/document.rb:565)
>  at 
> RUBY.load(uri:classloader:/gems/asciidoctor-1.5.7.1/lib/asciidoctor.rb:1361)
>  at 
> RUBY.convert(uri:classloader:/gems/asciidoctor-1.5.7.1/lib/asciidoctor.rb:1473)
>  at 

Re: INCUBATOR-201 Missing archiver/archives for dev@incubator - is it needed?

[sebb]

On Mon, 25 Mar 2019 at 21:13, Dave Fisher  wrote:
>
> For some reason in 2016, dev@incubator and commits@incubator mailing lists 
> were created.
>
> If you look at these on lists.apache.org there are really not more than a few 
> truly misplaced emails.
>
> By LAZY CONSENSUS in three days I’ll ask INFRA to remove them.

It looks like commits@ is still the destination for some commit mails,
so they need to be directed elsewhere before closure.

I agree that dev@ is redundant; the bounce message should direct
posters to general@

> Regards,
> Dave
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Closed] (INCUBATOR-226) IP Clearance for OpenWhisk Composer

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher closed INCUBATOR-226.
-
Resolution: Fixed

This vote was held and the results recorded

> IP Clearance for OpenWhisk Composer
> ---
>
> Key: INCUBATOR-226
> URL: https://issues.apache.org/jira/browse/INCUBATOR-226
> Project: Incubator
>  Issue Type: Task
>Reporter: Bertrand Delacretaz
>Priority: Major
>
> The donation of that module was discussed in INCUBATOR-222 and the IP 
> clearance form has been created at 
> http://incubator.apache.org/ip-clearance/openwhisk-composer.html but the 
> Incubator PMC vote to accept the IP clearance has not happened.
> [~dgrove] before I start that vote, I have added a note to that IP clearance 
> form stating that "as explained above, a Software Grant is not required, all 
> contributors have an iCLA on file"
> Does that work for you? If yes I'll start the IP clearance vote. Sorry for 
> the delay, this slipped through the cracks after the LEGAL-420 discussions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Closed] (INCUBATOR-225) Missing Link on Incubator Website

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher closed INCUBATOR-225.
-
Resolution: Won't Fix

This page style is being phased out

> Missing Link on Incubator Website
> -
>
> Key: INCUBATOR-225
> URL: https://issues.apache.org/jira/browse/INCUBATOR-225
> Project: Incubator
>  Issue Type: Bug
>  Components: site
>Reporter: Wei Chen
>Priority: Minor
>
> On page: http://incubator.apache.org/projects/ 
> On the left-hand side: 
> in **General** 
> [Incubation Guides|http://incubator.apache.org/guides/index.html] 
> in **Status** 
> [Incubator History|http://incubator.apache.org/history] 
> These 2 pages are missing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Closed] (INCUBATOR-122) Replace all "site-author" to "content" in content/guides/website.xml

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher closed INCUBATOR-122.
-
Resolution: Not A Problem

> Replace all "site-author" to "content" in content/guides/website.xml
> 
>
> Key: INCUBATOR-122
> URL: https://issues.apache.org/jira/browse/INCUBATOR-122
> Project: Incubator
>  Issue Type: Improvement
>  Components: site
>Reporter: Edward J. Yoon
>Priority: Major
>
> I don't know the background why "site-author" direcotry renamed to 
> "content"[1] but shouldn't we change also the text in website.xml?
> 1. http://markmail.org/thread/xehg3nd4xw525kjw



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Closed] (INCUBATOR-116) XML Beans CXX project is in limbo

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher closed INCUBATOR-116.
-
Resolution: Fixed

> XML Beans CXX project is in limbo
> -
>
> Key: INCUBATOR-116
> URL: https://issues.apache.org/jira/browse/INCUBATOR-116
> Project: Incubator
>  Issue Type: Bug
> Environment: 
> http://mail-archives.apache.org/mod_mbox/incubator-general/201108.mbox/%3ccaogo0vbxyrd_tktsgke+bkc8g0pzzpvjxuh7zzylu5wccjf...@mail.gmail.com%3E
>Reporter: Sebb
>Priority: Major
>
> The XML Beans C++ project is in limbo:
> It has a website [1], a status page [2] but is not mentioned in clutch
> [3] or the summary projects page [4] as dormant or retired.
> It still has a RW podling SVN directory [5] but that was last updated in 2007.
> AFAICT the project needs to be retired, and SVN deleted if the copyright 
> issues have not been addressed, otherwise made read-only
> As an initial step, I have made SVN read-only (the access group was empty 
> anyway).
> [1] http://incubator.apache.org/xmlbeanscxx/
> [2] http://incubator.apache.org/projects/xmlbeanscxx.html
> [3] http://incubator.apache.org/clutch.html
> [4] http://incubator.apache.org/projects/index.html
> [5] http://svn.apache.org/repos/asf/incubator/xmlbeanscxx/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Closed] (INCUBATOR-100) document the process for a podling that has decided to go to dormant status

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher closed INCUBATOR-100.
-
Resolution: Fixed

We now have a retirement process. The shortened game links here totally fail.

> document the process for a podling that has decided to go to dormant status
> ---
>
> Key: INCUBATOR-100
> URL: https://issues.apache.org/jira/browse/INCUBATOR-100
> Project: Incubator
>  Issue Type: Task
>  Components: site
>Reporter: David Crossley
>Priority: Major
>
> Document the process.
> Some steps were thoughtfully provided by Leo and Matthieu for TripleSoup:
>  Re: TripleSoup going into dormant mode
>  http://markmail.org/message/kavm65g65x55wqr5



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Closed] (INCUBATOR-77) [IP-GRANT] Local Lucene/Solr Code Dump

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher closed INCUBATOR-77.

Resolution: Fixed

Finished long, long ago.

> [IP-GRANT] Local Lucene/Solr Code Dump
> --
>
> Key: INCUBATOR-77
> URL: https://issues.apache.org/jira/browse/INCUBATOR-77
> Project: Incubator
>  Issue Type: New Feature
> Environment: lucene.apache.org
>Reporter: Ian Holsman
>Priority: Major
> Attachments: locallucene.tgz.asc
>
>
> $ rpm -qf $(which md5sum)
> coreutils-5.97-12.1.el5
> $ md5sum locallucene.tgz
> e470f7dfd963994eebb6c5002f810549  locallucene.tgz



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Closed] (INCUBATOR-99) Clarify how to submit a IP clearance template

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher closed INCUBATOR-99.

Resolution: Unresolved

The process is now clear and this issue is out of date.

> Clarify how to submit a IP clearance template
> -
>
> Key: INCUBATOR-99
> URL: https://issues.apache.org/jira/browse/INCUBATOR-99
> Project: Incubator
>  Issue Type: Improvement
>  Components: site
>Reporter: Antonio Petrelli
>Priority: Major
> Attachments: ip-clearance-template-patch.diff
>
>
> IP clearance can be submitted by a PMC chair or through the post as a JIRA 
> issue. These facts should be clarified.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Closed] (INCUBATOR-65) Branding Guide clarification

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher closed INCUBATOR-65.

Resolution: Implemented

I think that this is already in place - the PRC is no more and there ought to 
be some additional updates to the current page.

> Branding Guide clarification
> 
>
> Key: INCUBATOR-65
> URL: https://issues.apache.org/jira/browse/INCUBATOR-65
> Project: Incubator
>  Issue Type: Improvement
>  Components: site
>Reporter: Xavier Hanin
>Priority: Major
>
> As dicussed on the mailing list recently [1] and [2], I think the branding 
> guide would benefit from some clarification and examples. The second link 
> point to the message with what need some clarification IMO.
> Here is a copy of the message:
> On 5/23/07, Martijn Dashorst  wrote:
> >
> > On 5/22/07, Xavier Hanin  wrote:
> > > Mmm, it's still not completely clear. Is the phrase "However, the
> > > Public Relations Committee MUST review any releases by affiliated
> > > organizations or groups to ensure they comply with these branding
> > > guidelines." referring to press release announcing the podling only,
> > > or to all press releases? Since it seems it's not allowed to issue
> > > press releases announcing the release, I'd think it's for press
> > > releases that reference the podling. And that's what my article will
> > > do, reference the podling.
> >
> > I think the gist is in the term "Press release". I think a press
> > release is something other than an article. A press release is
> > something like "Foo is adopting Apache Ivy in its product line and
> > providing professional support for it." and send it across the wire,
> > i.e. an announcement.
> >
> > This is of course something different than "This is how you manage
> > your Java project dependencies using Apache Ivy, currently undergoing
> > incubation at the Apache Incubator." which is published on
> > theserverside.com and/or infoq. 
> It makes sense, indeed. But I think it would be nice to have something in
> the branding guide more clearly understandable.
> [1] http://www.nabble.com/to-brand-or-not-to-brand--tf3795172.html
> [2] 
> http://www.nabble.com/Branding-Guide-clarification-%28was-Re%3A-to-brand-or-not-to-brand-%29-tf3802984.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Apache DataSketches

[leerho]

I went ahead and performed the following searches based on the list someone
else provided.  Perhaps you can use this?

Note: the term "sketch" commonly refers to an artistic visualization or
drawing.
The use of the term "sketch" in the study of algorithms refer to a synopsis
of some larger set of data where the synopsis is approximate, simplified
(not all the detail), and can be executed quickly.  These properties are
shared with artistic sketches, but there the similarity ends. DataSketches
have nothing to do with visualization at all.

Search results.

https://github.com/search?o=desc=datasketches
returned links are indirect references to our site. or a reference to site
about data art.

https://opensource.google.com/projects/search?q=datasketches
No hits

https://sourceforge.net/directory/os:mac/?q=datasketches
No hits

https://www.openhub.net/p?ref=homepage=datasketches
No hits

https://www.trademarkia.com
No hits: "data sketch", "data sketches", "data-sketch", "data-sketches",
"datasketch", or "datasketches".

https://trademarks.justia.com/search?q=datasketches
No hits: "data sketch", "data sketches", "data-sketch", "data-sketches",
"datasketch", or "datasketches".

http://tmsearch.uspto.gov/
No hits: "data sketch", "data sketches", "data-sketch", "data-sketches",
"datasketch", or "datasketches".

https://www.google.com/search?q=datasketches=datasketches
About 37,600 results most all are indirect references to our site or to
sites about artistic visual renderings of data. Searching for
"datasketches" (with quotes) is a much smaller set (6800) that mostly refer
to our software.

https://en.wikipedia.org/wiki/datasketches
q: "datasketches": No hits
q: "data sketches" One hit: the common data science use of the pair of
words referring to sketching algorithms: "The different techniques can be
classified according to the data sketches they store."

https://stackoverflow.com/search?q=datasketches
2 hits that refer back to our software (Druid-datasketches is our software)
q:data sketches

https://www.linkedin.com/company/datasketches/about/
No hits

https://en.oxforddictionaries.com/search?filter=dictionary=datasketches
No hits

On Mon, Mar 25, 2019 at 1:36 PM Kenneth Knowles  wrote:

> The vote is passed to accept into the incubator. Since there is a cost to
> changing the name once infrastructure is set up, I suggest doing the name
> search immediately. There seemed to be some consensus to try to keep the
> DataSketches name. If there are no objections, I will file a
> PODLINGNAMESEARCH for this.
>
> Kenn
>
> On Tue, Feb 26, 2019 at 3:58 PM Liang Chen 
> wrote:
>
> > Hi Justin
> >
> > You are right, should be "Liang Chen", already updated it.
> >
> > Justin, could you please help to check my right to create new proposal on
> > incubator wiki at :
> > https://wiki.apache.org/incubator/ProjectProposals
> >
> > Regards
> > Liang
> >
> > Justin Mclean wrote
> > > Hi,
> > >
> > >> Currently only IPMC members can be official mentors, of the 3 people
> > >> listed here I believe only Jean-Baptiste Onofré is an IPMC member.
> > >
> > > Sorry, my apologies, Liang Chen is also an IPMC member, (Chen Liang,
> and
> > > presumedly a different person, is a committer but not an IPMC member)
> but
> > > I cannot find Gil Yehuda, do you mind provide a link to the roster for
> > > them or their Apache id?
> > >
> > > Thanks,
> > > Justin
> > > -
> > > To unsubscribe, e-mail:
> >
> > > general-unsubscribe@.apache
> >
> > > For additional commands, e-mail:
> >
> > > general-help@.apache
> >
> >
> >
> >
> >
> > --
> > Sent from: http://apache-incubator-general.996316.n3.nabble.com/
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

[jira] [Commented] (INCUBATOR-54) Define roles and procedures for Incubator PPMC

[Dave Fisher (JIRA)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801171#comment-16801171
 ] 

Dave Fisher commented on INCUBATOR-54:
--

Craig, Is there a reason to keep this issue open?

> Define roles and procedures for Incubator PPMC
> --
>
> Key: INCUBATOR-54
> URL: https://issues.apache.org/jira/browse/INCUBATOR-54
> Project: Incubator
>  Issue Type: Improvement
>  Components: site
>Reporter: Craig L Russell
>Assignee: Craig L Russell
>Priority: Minor
>
> The Incubator PPMCs have responsibility for oversight of podlings but this 
> role is not discussed in the Incubator policy documents.
> This change will define the role, responsibilities, and processes of the 
> PPMCs in incubation. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Closed] (INCUBATOR-34) Clarify Role of Champion And Consolidate Policy [ALTERNATIVE]

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher closed INCUBATOR-34.

Resolution: Duplicate

> Clarify Role of Champion And Consolidate Policy [ALTERNATIVE]
> -
>
> Key: INCUBATOR-34
> URL: https://issues.apache.org/jira/browse/INCUBATOR-34
> Project: Incubator
>  Issue Type: Improvement
>  Components: policy
>Reporter: Robert Burrell Donkin
>Assignee: Robert Burrell Donkin
>Priority: Major
>
> Alternative clarification: only members
> Index: site-author/incubation/Incubation_Policy.xml
> ===
> --- site-author/incubation/Incubation_Policy.xml(revision 423542)
> +++ site-author/incubation/Incubation_Policy.xml(working copy)
> @@ -883,10 +883,14 @@
>
>  Champion
>  
> -A Member of the Apache Software Foundation who supports a 
> Candidate's
> -application for Incubation and who supports and assists the Podling
> -through the Incubation process.
> +The Champion who nominates the proposal SHALL support and assist 
> +the Candidate's application through the Incubation Process. Described in 
> detail 
> +here.
>  
> +The Champion MUST be an
> +  http://www.apache.org/foundation/members.html;>Member
> +of the Foundation.
> +
>
>
>  Sponsor
> Index: site-author/incubation/Roles_and_Responsibilities.xml
> ===
> --- site-author/incubation/Roles_and_Responsibilities.xml   (revision 
> 423542)
> +++ site-author/incubation/Roles_and_Responsibilities.xml   (working copy)
> @@ -123,13 +123,9 @@
>
>  Champion
>  
> -A candidate project shall be sponsored by an
> -
> -  http://www.apache.org/foundation/index.html;>Officer
> -or
> -
> -  http://www.apache.org/foundation/members.html;>Member
> -of the Foundation. The Champion assists the candidate on their
> +A candidate must have a Champion 
> +[definition]. 
> +The Champion assists the candidate on their
>  initial submission to a Sponsor. While private conversations are not
>  generally encouraged within the Apache community, the Champion's
>  relationship with the Candidate should allow for this in order to



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Closed] (INCUBATOR-27) Overhaul the "Check Trademark" process

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher closed INCUBATOR-27.

Resolution: Fixed

This is now more clearly handled by the Brand committee at trademarks AT 
apache.org

> Overhaul the "Check Trademark" process
> --
>
> Key: INCUBATOR-27
> URL: https://issues.apache.org/jira/browse/INCUBATOR-27
> Project: Incubator
>  Issue Type: Task
>Reporter: Matthias Weßendorf
>Priority: Major
>
> Lot's of incubator pages point to nameprotect DOT com for checking the 
> podling name against a registered trademark. For some reasons this is 
> *impossible*. That trademark search engine charges USD for a *research*
> I needs to be checked, howto handle this ?
> -Create an Apache account on that page ?
> -Using United States Patent and Trademark Office website ?
> See also
> http://wiki.apache.org/incubator/Trademarks



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Closed] (INCUBATOR-1) document copyright changes

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher closed INCUBATOR-1.
---
Resolution: Not A Problem

This issue should be considered resolved. This is covered by an SGA which is, 
as I understand it, a license grant. The original owners can retain their 
copyright and the ASF can copyright what is granted to us.

> document copyright changes
> --
>
> Key: INCUBATOR-1
> URL: https://issues.apache.org/jira/browse/INCUBATOR-1
> Project: Incubator
>  Issue Type: Improvement
>  Components: policy
>Reporter: Rodent of Unusual Size
>Priority: Major
>
> there is an issue with files contributed to the asf through the
> incubator.  currently it is unclear how the copyright issue
> should be managed; what gets put into the NOTICE file, what goes
> into each individual file, et cetera.  once this is officially
> sorted out, it needs to be added to the incubator documentation --
> along with a notation about whether the changes should be made
> RTC with review by the board, the incubator, or whom.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Assigned] (INCUBATOR-203) Rename Proposals to something else, add more how to get in information

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher reassigned INCUBATOR-203:
-

Assignee: Dave Fisher

> Rename Proposals to something else, add more how to get in information
> --
>
> Key: INCUBATOR-203
> URL: https://issues.apache.org/jira/browse/INCUBATOR-203
> Project: Incubator
>  Issue Type: Improvement
>  Components: guides
>Reporter: John D. Ament
>Assignee: Dave Fisher
>Priority: Major
>
> The current proposal top level menu item is good, but lacks some useful 
> information.  Instead of being called proposals, maybe call it "Becoming an 
> Apache Project" and include some information:
> - Proposal process
> - Update entry to give a higher level how it works
> - Include docs on SGAs, IP Clearance, when each is needed



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Assigned] (INCUBATOR-202) Graduation steps guide enhancements

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher reassigned INCUBATOR-202:
-

Assignee: Dave Fisher

> Graduation steps guide enhancements
> ---
>
> Key: INCUBATOR-202
> URL: https://issues.apache.org/jira/browse/INCUBATOR-202
> Project: Incubator
>  Issue Type: Improvement
>Reporter: John D. Ament
>Assignee: Dave Fisher
>Priority: Major
>
> Related to this section:
> - Clarify that anyone from the new PMC can create the infra tickets.  This 
> should happen after its clear that the resolution was accepted.
> - Direct users to use Service Desk for ticket creation
> - Most of 3.1 needs to be removed, as TLPs don't have incubator.a.o domains
> - All of 3.2 can be removed
> - Section 6, infra does a move so just create a ticket.
> Sub project specific:
> - Don't require the IPMC to vote, instead use a 72 hour lazy consensus to 
> graduate a podling to a sub-project



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

INCUBATOR-201 Missing archiver/archives for dev@incubator - is it needed?

[Dave Fisher]

For some reason in 2016, dev@incubator and commits@incubator mailing lists were 
created.

If you look at these on lists.apache.org there are really not more than a few 
truly misplaced emails.

By LAZY CONSENSUS in three days I’ll ask INFRA to remove them.

Regards,
Dave
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Commented] (INCUBATOR-201) Missing archiver/archives for dev@incubator - is it needed?

[Dave Fisher (JIRA)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801070#comment-16801070
 ] 

Dave Fisher commented on INCUBATOR-201:
---

Hi -

cvs@ is the equivalent of commits@
general@ is the equivalent of dev@

Do these lists still exist?

Yes, recently some retired podling site have their git directed to commits@
dev@ gets occasional comdev events notifications

> Missing archiver/archives for dev@incubator - is it needed?
> ---
>
> Key: INCUBATOR-201
> URL: https://issues.apache.org/jira/browse/INCUBATOR-201
> Project: Incubator
>  Issue Type: Task
>Reporter: Sebb
>Priority: Major
>
> The dev@incubator mailing list is still active and has 6 messages:
> dev Digest of: get.1_6
> Topics (messages 1 through 6)
> HashPartitioner, strange behavior
> 1 by: Erik Thorson
> 2 by: Erik Thorson
> [ANNOUNCE] CFP open for ApacheCon North America 2016
> 3 by: Rich Bowen
> FOSDEM 2016 - take action by 4th of December 2015
> 4 by: Roman Shaposhnik
> Re: Spawning an Apache Geode Summit - March 9 2016 in Palo Alto, CA
> 5 by: Greg Chase
> ApacheCon Seville CFP closes September 9th
> 6 by: Rich Bowen
> However there does not appear to be an ASF archive for it, and the one on 
> lists.apache.org only contains the latest message [1]
> It should probably be shut down.
> If not, then the archiver needs to be set up.
> Also the missing messages should be retrieved if possible.
> It looks like dev-get recovers the message bodies, but not the headers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Resolved] (INCUBATOR-232) The Release of OpenWhisk 3.19.0-incubating: OpenWhisk Client JS

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher resolved INCUBATOR-232.
---
Resolution: Not A Problem

We don't open issues for VOTE threads

> The Release of OpenWhisk 3.19.0-incubating: OpenWhisk Client JS
> ---
>
> Key: INCUBATOR-232
> URL: https://issues.apache.org/jira/browse/INCUBATOR-232
> Project: Incubator
>  Issue Type: Task
>Reporter: James Thomas
>Priority: Major
>
> The OpenWhisk community is working on its first release 3.19.0-incubating of 
> OpenWhisk Client JS under Apache. An email for VOTE will be sent to the dev 
> mail list of OpenWhisk momentarily, with the title [VOTE] Release Apache 
> OpenWhisk 3.19.0-incubating-rc1: OpenWhisk Client JS.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Closed] (INCUBATOR-219) The release of OpenWhisk 0.9.0-incubating: OpenWhisk deploy kube

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher closed INCUBATOR-219.
-
Resolution: Not A Problem

We don't open issues for release VOTE threads

> The release of OpenWhisk 0.9.0-incubating: OpenWhisk deploy kube
> 
>
> Key: INCUBATOR-219
> URL: https://issues.apache.org/jira/browse/INCUBATOR-219
> Project: Incubator
>  Issue Type: Task
>Reporter: Vincent Hou
>Priority: Major
>
> OpenWhisk community is working on its first release 0.9.0-incubating of 
> OpenWhisk deploy kube under Apache. An email for VOTE will be sent to the dev 
> mail list of OpenWhisk momentarily, with the title [VOTE] Release Apache 
> OpenWhisk 0.9.8-incubating: OpenWhisk deploy kube.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Closed] (INCUBATOR-232) The Release of OpenWhisk 3.19.0-incubating: OpenWhisk Client JS

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher closed INCUBATOR-232.
-

> The Release of OpenWhisk 3.19.0-incubating: OpenWhisk Client JS
> ---
>
> Key: INCUBATOR-232
> URL: https://issues.apache.org/jira/browse/INCUBATOR-232
> Project: Incubator
>  Issue Type: Task
>Reporter: James Thomas
>Priority: Major
>
> The OpenWhisk community is working on its first release 3.19.0-incubating of 
> OpenWhisk Client JS under Apache. An email for VOTE will be sent to the dev 
> mail list of OpenWhisk momentarily, with the title [VOTE] Release Apache 
> OpenWhisk 3.19.0-incubating-rc1: OpenWhisk Client JS.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Resolved] (INCUBATOR-130) Nuvem in limbo

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher resolved INCUBATOR-130.
---
Resolution: Later

INCUBATOR-233 will do a full evaluation of similar scenarios

> Nuvem in limbo
> --
>
> Key: INCUBATOR-130
> URL: https://issues.apache.org/jira/browse/INCUBATOR-130
> Project: Incubator
>  Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> The Nuvem podling appears to be in limbo.
> According to podling.xml it graduated, but the comment says:
> "The podling was voted to become part of Tuscany in Nov 2012 but (as of Aug 
> 2014) nothing has happened."
> The SVN tree still exists.
> Either the graduation should be completed or the podling should be retired.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Created] (INCUBATOR-233) Clean Up Retired Podling Repositories

[Dave Fisher (JIRA)]

Dave Fisher created INCUBATOR-233:
-

 Summary: Clean Up Retired Podling Repositories
 Key: INCUBATOR-233
 URL: https://issues.apache.org/jira/browse/INCUBATOR-233
 Project: Incubator
  Issue Type: Task
Reporter: Dave Fisher


# Confirm policy on when to delete retired podling repositories
# Clean up retired podling SVN repositories
# Clean up retired podling GIT repositories



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Apache DataSketches

[Kenneth Knowles]

The vote is passed to accept into the incubator. Since there is a cost to
changing the name once infrastructure is set up, I suggest doing the name
search immediately. There seemed to be some consensus to try to keep the
DataSketches name. If there are no objections, I will file a
PODLINGNAMESEARCH for this.

Kenn

On Tue, Feb 26, 2019 at 3:58 PM Liang Chen  wrote:

> Hi Justin
>
> You are right, should be "Liang Chen", already updated it.
>
> Justin, could you please help to check my right to create new proposal on
> incubator wiki at :
> https://wiki.apache.org/incubator/ProjectProposals
>
> Regards
> Liang
>
> Justin Mclean wrote
> > Hi,
> >
> >> Currently only IPMC members can be official mentors, of the 3 people
> >> listed here I believe only Jean-Baptiste Onofré is an IPMC member.
> >
> > Sorry, my apologies, Liang Chen is also an IPMC member, (Chen Liang, and
> > presumedly a different person, is a committer but not an IPMC member) but
> > I cannot find Gil Yehuda, do you mind provide a link to the roster for
> > them or their Apache id?
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail:
>
> > general-unsubscribe@.apache
>
> > For additional commands, e-mail:
>
> > general-help@.apache
>
>
>
>
>
> --
> Sent from: http://apache-incubator-general.996316.n3.nabble.com/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[jira] [Comment Edited] (INCUBATOR-231) Cleanup Git-generated Incubator website

[Dave Fisher (JIRA)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16800940#comment-16800940
 ] 

Dave Fisher edited comment on INCUBATOR-231 at 3/25/19 6:06 PM:


[~s...@apache.org]

I've been thinking similarly over the weekend. The clutch2.py scripting should 
be scheduled once a day instead of the git build. The generated files are then 
committed to the incubator.git/trunk/pages/clutch/ directory and that triggers 
the incubator site build.

Clutch takes time due to svn log on the status page content and svn ls on the 
incubator's list areas and once a day is often enough.

If you recommend the git commands I'll give it a try.

 

 


was (Author: wave):
[~s...@apache.org]

I've been thinking similarly over the weekend. The clutch2.py scripting should 
be scheduled once a day prior to the scheduled incubator.git build. The 
generated files are then committed to the incubator.git/trunk/pages/clutch/ 
directory.

Clutch takes time due to svn log on the status page content and svn ls on the 
incubator's list areas and once a day is often enough.

If you recommend the git commands I'll give it a try.

 

 

> Cleanup Git-generated Incubator website
> ---
>
> Key: INCUBATOR-231
> URL: https://issues.apache.org/jira/browse/INCUBATOR-231
> Project: Incubator
>  Issue Type: Task
>Reporter: Bertrand Delacretaz
>Priority: Major
> Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, 
> clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, 
> gitbox.clutch.data.txt, gitbox.svn.diff.txt
>
>
> [http://incubator.apache.org/] is generated from 
> [https://github.com/apache/incubator] but a few things (clutch, project 
> pages) are still maintained under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/]
> We should cleanup and unify for consistency, and there's a number of folders 
> in svn that are not used anymore. Everything should move to Git to avoid 
> confusion.
> Also, a lot of the projects information in the XML files found under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is 
> duplicated in other places, LDAP, podlings websites etc - it would be good to 
> clean that up and simplify those pages to adapt to our current workflows, 
> while preserving history where it makes sense.
> There are also YAML files with yet more duplicated information at 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , 
> not sure if that's used or useful.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website

[Dave Fisher (JIRA)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16800945#comment-16800945
 ] 

Dave Fisher commented on INCUBATOR-231:
---

Regarding the history pages. I've deleted these as the main page at 
[https://projects.apache.org/] has a better version of it. So, one less thing 
for the IPMC to maintain. BTW - the source is {{podlings.xml}}.

> Cleanup Git-generated Incubator website
> ---
>
> Key: INCUBATOR-231
> URL: https://issues.apache.org/jira/browse/INCUBATOR-231
> Project: Incubator
>  Issue Type: Task
>Reporter: Bertrand Delacretaz
>Priority: Major
> Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, 
> clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, 
> gitbox.clutch.data.txt, gitbox.svn.diff.txt
>
>
> [http://incubator.apache.org/] is generated from 
> [https://github.com/apache/incubator] but a few things (clutch, project 
> pages) are still maintained under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/]
> We should cleanup and unify for consistency, and there's a number of folders 
> in svn that are not used anymore. Everything should move to Git to avoid 
> confusion.
> Also, a lot of the projects information in the XML files found under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is 
> duplicated in other places, LDAP, podlings websites etc - it would be good to 
> clean that up and simplify those pages to adapt to our current workflows, 
> while preserving history where it makes sense.
> There are also YAML files with yet more duplicated information at 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , 
> not sure if that's used or useful.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website

[Dave Fisher (JIRA)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16800940#comment-16800940
 ] 

Dave Fisher commented on INCUBATOR-231:
---

[~s...@apache.org]

I've been thinking similarly over the weekend. The clutch2.py scripting should 
be scheduled once a day prior to the scheduled incubator.git build. The 
generated files are then committed to the incubator.git/trunk/pages/clutch/ 
directory.

Clutch takes time due to svn log on the status page content and svn ls on the 
incubator's list areas and once a day is often enough.

If you recommend the git commands I'll give it a try.

 

 

> Cleanup Git-generated Incubator website
> ---
>
> Key: INCUBATOR-231
> URL: https://issues.apache.org/jira/browse/INCUBATOR-231
> Project: Incubator
>  Issue Type: Task
>Reporter: Bertrand Delacretaz
>Priority: Major
> Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, 
> clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, 
> gitbox.clutch.data.txt, gitbox.svn.diff.txt
>
>
> [http://incubator.apache.org/] is generated from 
> [https://github.com/apache/incubator] but a few things (clutch, project 
> pages) are still maintained under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/]
> We should cleanup and unify for consistency, and there's a number of folders 
> in svn that are not used anymore. Everything should move to Git to avoid 
> confusion.
> Also, a lot of the projects information in the XML files found under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is 
> duplicated in other places, LDAP, podlings websites etc - it would be good to 
> clean that up and simplify those pages to adapt to our current workflows, 
> while preserving history where it makes sense.
> There are also YAML files with yet more duplicated information at 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , 
> not sure if that's used or useful.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Incubator wiki being deprecated

[Myrle Krantz]

Hi Dave,

On Mon, Mar 25, 2019 at 6:37 PM Dave Fisher  wrote:

> Does anyone have an objection to doing that migration?
>

I think your proposal is the right one.


> I have some Confluence admin experience and can look into a few of the
> questions around Report pages and Proposal Creation. Anyone else here with
> Confluence Admin experience?
>

Some, but not much.  Mostly adding and removing users from roles...  Let me
know if I can help though.

Best Regards,
Myrle

Re: Incubator wiki being deprecated

[Dave Fisher]

Hi Justin,

Maybe you saw the note earlier today. Bertrand has saved the MoinMoin content 
in the private incubator svn repository.

I think it would be worth while to engage the migration tool without history. 
This will be helpful for these reasons.

(1) We get a copy of everything. I think the Proposals are most important.
(2) We save significantly in the migration since as I understand it each 
version of a page makes one migration and is then diffed. Since we have Reports 
with 100 or more edits that is a significant saving.
(3) The migration tool has trouble with the authors of prior versions anyway.

Does anyone have an objection to doing that migration?

I have some Confluence admin experience and can look into a few of the 
questions around Report pages and Proposal Creation. Anyone else here with 
Confluence Admin experience?

Regards,
Dave

> On Mar 23, 2019, at 6:02 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> If you didn’t know the wiki.apache.org system using Moin software is being 
> decommissioned in May 2019. Currently how incubator reports are being created 
> depend on this system and this will need to change.
> 
> I’ve created an incubator space [1] and we shovel think about mobbing the 
> content over. There’s a self help migration tool, but given the size of the 
> incubator wiki I’m not 100% sure if that’a a good idea to run.
> 
> Thanks,
> Justin
> 
> 1. https://cwiki.apache.org/confluence/display/INCUBATOR
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Cava] Suitable name search - choosing a name

[Antoine Toulme]

I kept messing that one up. Apologies.

> On Mar 25, 2019, at 10:15 AM, Dave Fisher  wrote:
> 
> Hi -
> 
> Correction. VP, Brand approved the name.
> 
> Regards,
> Dave
> 
>> On Mar 25, 2019, at 10:13 AM, Antoine Toulme  wrote:
>> 
>> Legal has approved the name. We are a go with Apache Tuweni.
>> 
>> Thanks to all for helping figure this riddle out, and the many colors we 
>> painted this bike shed together :D
>> 
>> Antoine
>> 
>>> On Mar 22, 2019, at 11:57 AM, Antoine Toulme  wrote:
>>> 
>>> I have filed https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-167 
>>>  for this name.
>>> 
>>> 
 On Mar 22, 2019, at 11:46 AM, Antoine Toulme  wrote:
 
 “Qui ne dit mot consent”. I haven’t heard anyone say no, so this name gets 
 to the next round.
 
 Cheers,
 
 Antoine
 
> On Mar 21, 2019, at 4:56 PM, Antoine Toulme  wrote:
> 
> Any strong objections to Tuweni?
> 
> 
>> On Mar 21, 2019, at 12:04 AM, Antoine Toulme  wrote:
>> 
>> I’m not sure about avac, doesn’t roll off the tongue.
>> 
>> On the theme of “no one”, I found Tuweni (from 
>> https://www.lakotadictionary.org/phpBB3/nldo.php 
>> ).
>> 
>> Would that work?
>> 
>>> On Mar 20, 2019, at 12:02 PM, larry mccay  wrote:
>>> 
>>> Apache Avac ???
>>> 
>>> 
>>> On Wed, Mar 20, 2019 at 7:57 PM Antoine Toulme  
>>> wrote:
>>> 
 There exists an outis open source project.
 
 Maybe we can riff on this name though.
 
> On Mar 20, 2019, at 11:39, Kenneth Knowles  wrote:
> 
> Indeed, http://nemo.apache.org/
> 
> So I looked for similar ideas and came to Outis [2] via [1].
> 
> Kenn
> 
> [1] https://en.wikipedia.org/wiki/Captain_Nemo#Etymology
> [2] https://en.wikipedia.org/wiki/Outis
> 
> On Wed, Mar 20, 2019 at 11:27 AM Anu Engineer 
>  
> wrote:
> 
>> At this point you should call it “Apache Nemo” or literally Apache No
 One
>> (, to indicate we have no affiliations or does not violate any
 trademarks
>> or claims.
>> --Anu
>> 
>> Just kidding, eventually I am sure you will find a good name, -- 
>> that no
>> one else has thought off.
>> 
>> 
>> On 3/20/19, 10:51 AM, "Antoine Toulme"  wrote:
>> 
>> Deep sigh.
>> 
>> OK.
>> 
>>> On Mar 20, 2019, at 9:15 AM, Michael Wall  wrote:
>>> 
>>> I did find this, https://github.com/RainBlock.  Looks like code
>> around
>>> ethereum.  Maybe too close?
>>> 
>>> On Wed, Mar 20, 2019 at 11:59 AM Antoine Toulme 
>>> 
>> wrote:
>>> 
 Yes, you’ve been very flexible, thank you.
 
 Anybody with strong opinions, please chime in.
 
 I’ll start looking for marks around rainblock.
 
> On Mar 20, 2019, at 5:15 AM, Jim Jagielski 
>> wrote:
> 
> Personally, I'm fine w/ anything...
> 
>> On Mar 19, 2019, at 6:53 PM, Antoine Toulme 
 wrote:
>> 
>> I think we will need a made up name, and we likely need a name
>> that is
 rather unambiguous across languages.
>> 
>> Based on our previous proposals, would you be ok with 
>> “RainBlock”?
>> 
>> 
>>> On Mar 19, 2019, at 11:40 AM, Jim Jagielski 
>> wrote:
>>> 
>>> Apache PawPaw
>>> 
 On Mar 19, 2019, at 9:58 AM, Michael Wall 
>> wrote:
 
 Since Cava is the Guava for blockchains, what about sticking
>> with the
 fruit/veggie theme?
 
 Jackfruit
 Jambolan
 Jocote
 Kumquat
 KangKong
 Kabosu
 
 I also saw the word postcava which is the "the inferior vena
>> cava of
 vertebrates higher than fishes" according to
 https://www.merriam-webster.com/dictionary/postcava.  But is
>> seemed
 like a
 name you could use after Cava.
 
 Just brainstorming.
 
 Mike
 
 
 
 On Tue, Mar 19, 2019 at 8:19 AM Jim Jagielski 
 
 wrote:
 
> What is somewhat funny is that the "SkyWalking" podling is on
>> the

Re: [Cava] Suitable name search - choosing a name

[Dave Fisher]

Hi -

Correction. VP, Brand approved the name.

Regards,
Dave

> On Mar 25, 2019, at 10:13 AM, Antoine Toulme  wrote:
> 
> Legal has approved the name. We are a go with Apache Tuweni.
> 
> Thanks to all for helping figure this riddle out, and the many colors we 
> painted this bike shed together :D
> 
> Antoine
> 
>> On Mar 22, 2019, at 11:57 AM, Antoine Toulme  wrote:
>> 
>> I have filed https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-167 
>>  for this name.
>> 
>> 
>>> On Mar 22, 2019, at 11:46 AM, Antoine Toulme  wrote:
>>> 
>>> “Qui ne dit mot consent”. I haven’t heard anyone say no, so this name gets 
>>> to the next round.
>>> 
>>> Cheers,
>>> 
>>> Antoine
>>> 
 On Mar 21, 2019, at 4:56 PM, Antoine Toulme  wrote:
 
 Any strong objections to Tuweni?
 
 
> On Mar 21, 2019, at 12:04 AM, Antoine Toulme  wrote:
> 
> I’m not sure about avac, doesn’t roll off the tongue.
> 
> On the theme of “no one”, I found Tuweni (from 
> https://www.lakotadictionary.org/phpBB3/nldo.php 
> ).
> 
> Would that work?
> 
>> On Mar 20, 2019, at 12:02 PM, larry mccay  wrote:
>> 
>> Apache Avac ???
>> 
>> 
>> On Wed, Mar 20, 2019 at 7:57 PM Antoine Toulme  
>> wrote:
>> 
>>> There exists an outis open source project.
>>> 
>>> Maybe we can riff on this name though.
>>> 
 On Mar 20, 2019, at 11:39, Kenneth Knowles  wrote:
 
 Indeed, http://nemo.apache.org/
 
 So I looked for similar ideas and came to Outis [2] via [1].
 
 Kenn
 
 [1] https://en.wikipedia.org/wiki/Captain_Nemo#Etymology
 [2] https://en.wikipedia.org/wiki/Outis
 
 On Wed, Mar 20, 2019 at 11:27 AM Anu Engineer 
 >>> 
 wrote:
 
> At this point you should call it “Apache Nemo” or literally Apache No
>>> One
> (, to indicate we have no affiliations or does not violate any
>>> trademarks
> or claims.
> --Anu
> 
> Just kidding, eventually I am sure you will find a good name, -- that 
> no
> one else has thought off.
> 
> 
> On 3/20/19, 10:51 AM, "Antoine Toulme"  wrote:
> 
> Deep sigh.
> 
> OK.
> 
>> On Mar 20, 2019, at 9:15 AM, Michael Wall  wrote:
>> 
>> I did find this, https://github.com/RainBlock.  Looks like code
> around
>> ethereum.  Maybe too close?
>> 
>> On Wed, Mar 20, 2019 at 11:59 AM Antoine Toulme 
> wrote:
>> 
>>> Yes, you’ve been very flexible, thank you.
>>> 
>>> Anybody with strong opinions, please chime in.
>>> 
>>> I’ll start looking for marks around rainblock.
>>> 
 On Mar 20, 2019, at 5:15 AM, Jim Jagielski 
> wrote:
 
 Personally, I'm fine w/ anything...
 
> On Mar 19, 2019, at 6:53 PM, Antoine Toulme 
>>> wrote:
> 
> I think we will need a made up name, and we likely need a name
> that is
>>> rather unambiguous across languages.
> 
> Based on our previous proposals, would you be ok with “RainBlock”?
> 
> 
>> On Mar 19, 2019, at 11:40 AM, Jim Jagielski 
> wrote:
>> 
>> Apache PawPaw
>> 
>>> On Mar 19, 2019, at 9:58 AM, Michael Wall 
> wrote:
>>> 
>>> Since Cava is the Guava for blockchains, what about sticking
> with the
>>> fruit/veggie theme?
>>> 
>>> Jackfruit
>>> Jambolan
>>> Jocote
>>> Kumquat
>>> KangKong
>>> Kabosu
>>> 
>>> I also saw the word postcava which is the "the inferior vena
> cava of
>>> vertebrates higher than fishes" according to
>>> https://www.merriam-webster.com/dictionary/postcava.  But is
> seemed
>>> like a
>>> name you could use after Cava.
>>> 
>>> Just brainstorming.
>>> 
>>> Mike
>>> 
>>> 
>>> 
>>> On Tue, Mar 19, 2019 at 8:19 AM Jim Jagielski 
>>> wrote:
>>> 
 What is somewhat funny is that the "SkyWalking" podling is on
> the
>>> cusp of
 graduation. :)
 
> On Mar 19, 2019, at 1:42 AM, Antoine Toulme <
> anto...@toulme.name>
>>> wrote:
> 
> All, the results are in, from VP Legal:
>> I am happy to approve the name in 

Re: [Cava] Suitable name search - choosing a name

[Antoine Toulme]

Legal has approved the name. We are a go with Apache Tuweni.

Thanks to all for helping figure this riddle out, and the many colors we 
painted this bike shed together :D

Antoine

> On Mar 22, 2019, at 11:57 AM, Antoine Toulme  wrote:
> 
> I have filed https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-167 
>  for this name.
> 
> 
>> On Mar 22, 2019, at 11:46 AM, Antoine Toulme  wrote:
>> 
>> “Qui ne dit mot consent”. I haven’t heard anyone say no, so this name gets 
>> to the next round.
>> 
>> Cheers,
>> 
>> Antoine
>> 
>>> On Mar 21, 2019, at 4:56 PM, Antoine Toulme  wrote:
>>> 
>>> Any strong objections to Tuweni?
>>> 
>>> 
 On Mar 21, 2019, at 12:04 AM, Antoine Toulme  wrote:
 
 I’m not sure about avac, doesn’t roll off the tongue.
 
 On the theme of “no one”, I found Tuweni (from 
 https://www.lakotadictionary.org/phpBB3/nldo.php 
 ).
 
 Would that work?
 
> On Mar 20, 2019, at 12:02 PM, larry mccay  wrote:
> 
> Apache Avac ???
> 
> 
> On Wed, Mar 20, 2019 at 7:57 PM Antoine Toulme  
> wrote:
> 
>> There exists an outis open source project.
>> 
>> Maybe we can riff on this name though.
>> 
>>> On Mar 20, 2019, at 11:39, Kenneth Knowles  wrote:
>>> 
>>> Indeed, http://nemo.apache.org/
>>> 
>>> So I looked for similar ideas and came to Outis [2] via [1].
>>> 
>>> Kenn
>>> 
>>> [1] https://en.wikipedia.org/wiki/Captain_Nemo#Etymology
>>> [2] https://en.wikipedia.org/wiki/Outis
>>> 
>>> On Wed, Mar 20, 2019 at 11:27 AM Anu Engineer >> 
>>> wrote:
>>> 
 At this point you should call it “Apache Nemo” or literally Apache No
>> One
 (, to indicate we have no affiliations or does not violate any
>> trademarks
 or claims.
 --Anu
 
 Just kidding, eventually I am sure you will find a good name, -- that 
 no
 one else has thought off.
 
 
 On 3/20/19, 10:51 AM, "Antoine Toulme"  wrote:
 
 Deep sigh.
 
 OK.
 
> On Mar 20, 2019, at 9:15 AM, Michael Wall  wrote:
> 
> I did find this, https://github.com/RainBlock.  Looks like code
 around
> ethereum.  Maybe too close?
> 
> On Wed, Mar 20, 2019 at 11:59 AM Antoine Toulme 
 wrote:
> 
>> Yes, you’ve been very flexible, thank you.
>> 
>> Anybody with strong opinions, please chime in.
>> 
>> I’ll start looking for marks around rainblock.
>> 
>>> On Mar 20, 2019, at 5:15 AM, Jim Jagielski 
 wrote:
>>> 
>>> Personally, I'm fine w/ anything...
>>> 
 On Mar 19, 2019, at 6:53 PM, Antoine Toulme 
>> wrote:
 
 I think we will need a made up name, and we likely need a name
 that is
>> rather unambiguous across languages.
 
 Based on our previous proposals, would you be ok with “RainBlock”?
 
 
> On Mar 19, 2019, at 11:40 AM, Jim Jagielski 
 wrote:
> 
> Apache PawPaw
> 
>> On Mar 19, 2019, at 9:58 AM, Michael Wall 
 wrote:
>> 
>> Since Cava is the Guava for blockchains, what about sticking
 with the
>> fruit/veggie theme?
>> 
>> Jackfruit
>> Jambolan
>> Jocote
>> Kumquat
>> KangKong
>> Kabosu
>> 
>> I also saw the word postcava which is the "the inferior vena
 cava of
>> vertebrates higher than fishes" according to
>> https://www.merriam-webster.com/dictionary/postcava.  But is
 seemed
>> like a
>> name you could use after Cava.
>> 
>> Just brainstorming.
>> 
>> Mike
>> 
>> 
>> 
>> On Tue, Mar 19, 2019 at 8:19 AM Jim Jagielski 
>> wrote:
>> 
>>> What is somewhat funny is that the "SkyWalking" podling is on
 the
>> cusp of
>>> graduation. :)
>>> 
 On Mar 19, 2019, at 1:42 AM, Antoine Toulme <
 anto...@toulme.name>
>> wrote:
 
 All, the results are in, from VP Legal:
> I am happy to approve the name in isolation. Specifically,
 the
>>> community must refrain from linking the project to any Star
 Wars
>>> references. The view of the community is that the community is
>> likely to
>>> find that difficult. It was therefore agreed to look for a

Re: [VOTE] Recommend 'Apache SkyWalking graduation to TopLevelProject' resolution to board

[Dave Fisher]

Yes, Thank you Sheng Wu

> On Mar 23, 2019, at 1:30 AM, sebb  wrote:
> 
> Thanks, looks good now!
> 
> On Sat, 23 Mar 2019 at 03:01, 吴晟 Sheng Wu  wrote:
>> 
>> Hi Sebb
>>> r32183 | wusheng | 2019-01-29 08:19:22 + (Tue, 29 Jan 2019) | 2 lines
>> Changed paths:
>>   D /dev/incubator/skywalking/6.0.0-GA
>>   A /release/incubator/skywalking/6.0.0-GA (from
>> /dev/incubator/skywalking/6.0.0-GA:32182)
>> 
>> Fixed. Log and last change time have been reset to 2019-01-21 06:24[1]
>> 
>>> Also the hash and sig links on the download page should use HTTPS when
>> referencing the archive site, same as for www.apache.org.
>> 
>> 
>> Fixed. Website updated.
>> 
>> 
>> [1] https://www.apache.org/dist/incubator/skywalking/6.0.0-GA/
>> 
>> 
>> --
>> Sheng Wu
>> Apache SkyWalking, ShardingSphere, Zipkin
>> Twitter, wusheng1108
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> -- Original --
>> From:  "sebb";
>> Date:  Sat, Mar 23, 2019 08:24 AM
>> To:  "general";
>> 
>> Subject:  Re: [VOTE] Recommend 'Apache SkyWalking graduation to 
>> TopLevelProject' resolution to board
>> 
>> 
>> 
>> On Sat, 23 Mar 2019 at 00:06, 吴晟 Sheng Wu  wrote:
>>> 
>>> Hi Sebb, Deva, Kevin
>>> 
>>> 
>>> Status update,
>>> I added the 6.0.0-GA back. And all links in website updated to 
>>> http://archive.apache.org/
>>> 
>> 
>> Thanks.
>> 
>> However the SVN history has been lost; the files look brand new as far
>> as the history is concerned.
>> I think there are ways to copy the files from previous versions in SVN
>> which preserve the history.
>> 
>> It should be possible to get them from this commit:
>> 
>> r32183 | wusheng | 2019-01-29 08:19:22 + (Tue, 29 Jan 2019) | 2 lines
>> Changed paths:
>>   D /dev/incubator/skywalking/6.0.0-GA
>>   A /release/incubator/skywalking/6.0.0-GA (from
>> /dev/incubator/skywalking/6.0.0-GA:32182)
>> 
>> In the above commit one can clearly see the provenance of the release/
>> files from the dev/ files
>> 
>> Also the hash and sig links on the download page should use HTTPS when
>> referencing the archive site, same as for www.apache.org.
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache OpenWhisk CLI (incubating) version 0.10.0

[David P Grove]

The voting is closed; the vote has passed with 3 +1 binding votes from IPMC
Members in addition to the 6 +1 votes from OpenWhisk PPMC members on the
podling voting thread.

Bertrand Delacretaz voted +1 on this thread.  Matt Sicker and Krzysztof
Sobkowiak voted +1 on the podling release vote thread referenced below.

Thanks to all who participated in the vote.  The OpenWhisk podling will
proceed with publishing and announcing the release of Apache OpenWhisk CLI
(incubating) version 0.10.0

regards,

--dave

On 2019/03/20 15:28:29, "David P Grove"  wrote:
>
>
> The Apache OpenWhisk community has voted to release Apache OpenWhisk CLI
> (incubating) version 0.10.0.  The voting thread can be found here:
>
https://lists.apache.org/thread.html/78028145da802baa3dc37e53094443550e3f5d8d66486e00d6c28406@%3Cdev.openwhisk.apache.org%3E

>
> One binding +1 vote from mentor Matt Sicker carries over from the dev
list
> thread; at least two more +1 votes are needed.
>
> We request that IPMC Members please review and vote on this incubator
> release.
>
> The Apache OpenWhisk CLI provides the command line tooling for
interacting
> with Apache OpenWhisk.
>
> This release comprises of source code distribution only. There are three
> modules (git repos) included in this CLI release. All artifacts were
built
> by PR#249 in the openwhisk-release repo from the following Git commit
IDs:
> * openwhisk-cli: eaf64ae
> * openwhisk-client-go: 4286a82
> * openwhisk-wskdeploy: 7d79fd7
>
> openwhisk-cli (55BEEB6D CDF621AB 7AA6098A 5DBCA55E 6D7E3B0C A3DAA7DF
> B44103F8 CE30ACC9 13411ECC BFF18519 3E142EC3 D27AA081 E1D47F63 14E9E708
> 90646EC7 C13756D6)
>   src.tar.gz:
>
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-cli-0.10.0-incubating-sources.tar.gz

>   sha512 checksum:
>
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-cli-0.10.0-incubating-sources.tar.gz.sha512

>   signature:
>
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-cli-0.10.0-incubating-sources.tar.gz.asc

>
> openwhisk-client-go (068DBC87 533905DB D0089CAE 74FD0B91 109992D8
D843CAA4
> 01EA87B6 9CDC9550 6D555655 4679FF36 7A52414E DCC59126 E558085D 3E960DEB
> 18804581 6B2FA019)
>   src.tar.gz:
>
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-client-go-0.10.0-incubating-sources.tar.gz

>   sha512 checksum:
>
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-client-go-0.10.0-incubating-sources.tar.gz.sha512

>   signature:
>
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-client-go-0.10.0-incubating-sources.tar.gz.asc

>
> openwhisk-wskdeploy (412B1E09 129F2884 A1D4E9DE 0A979B47 55A54FC5
61E1D328
> 325E8A12 AE504779 A2350B9F 4185582F 7782EEA5 AE9018CD 52E4AA4C 484B5211
> AA449B4B 9F9E2432)
>   src.tar.gz:
>
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-wskdeploy-0.10.0-incubating-sources.tar.gz

>   sha512 checksum:
>
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-wskdeploy-0.10.0-incubating-sources.tar.gz.sha512

>   signature:
>
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-wskdeploy-0.10.0-incubating-sources.tar.gz.asc

>
> All release artifacts were signed with key 72AF0CC22C4CF320.
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS
>
> How to verify the artifacts can be found at:
> https://cwiki.apache.org/confluence/display/OPENWHISK/How+to+verify+the
> +release+checklist+and+vote+on+OpenWhisk+modules+under+Apache
>
> Please vote on releasing the three components of Apache OpenWhisk CLI
> 0.10.0-incubating as described above.
>
> The vote will be open for at least 72 hours.
> [ ] +1 Release as Apache OpenWhisk 0.10.0-incubating: openwhisk-cli,
> openwhisk-client-go, openwhisk-wskdeploy
> [ ] +0 no opinion
> [ ] -1 Do not release and the reason
>
> Checklist for reference:
> [ ] Download links are valid.
> [ ] Checksums and PGP signatures are valid.
> [ ] DISCLAIMER is included.
> [ ] Source code artifacts have correct names matching the current
release.
> [ ] LICENSE and NOTICE files are correct for each OpenWhisk repository.
> [ ] All files have license headers if necessary.
> [ ] No compiled archives bundled in source archive.
>
> regards,
>
> --dave
>

Re: Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top Level Project' resolution to board

[Hongtao Gao]

+1 no binding

Regards, Hongtao

On Mon, Mar 25, 2019, 2:21 AM Liu Ted  wrote:

> +1 (binding)
>
> Best regards,
>
> Ted Liu,
> ASF Member, Sponsor Ambassador, Incubator PMC Member
>
>   2019 年 3 月 25 日周一 11:03，Mohammad Asif Siddiqui
> 写道：   +1 (binding)
>
> Regards
> Asif
>
> On 2019/03/19 05:21:41, "Mick Semb Wever"  wrote:
> >
> >
> > After the latest discussion amongst this dev community on this dev
> mailing list[1],  presenting Sheng Wu as the PMC Chair and the maturity
> model[2], and then the discussion again on the incubator list[3],  a vote
> for Apache SkyWalking graduating to a top level project was called and has
> passed[4]. From the past incubator discussions the PPMC altered the draft
> graduation proposal, specifically the proposed PMC list: removing some
> inactive people and adding all the podling Committers.
> >
> >
> > Apache SkyWalking entered the incubator on December of 2017.  SkyWalking
> has delivered 8 releases so far in total, and now shows a good cadence of
> successful releases.
> >
> > During the podling's time in the Apache Incubator there has been
> >  3200+ commits on development of the project,
> >  378 Issues tagged as question in GitHub created, 373 resolved,
> >  850+ Pull request created and resolved,
> >  97 different contributors,
> >9 elected new committers, and
> >3 elected new PPMC members.
> >
> > And the dev ML has had 72 participants:
> https://lists.apache.org/trends.html?d...@skywalking.apache.org:2019
> >
> > Attached is the draft Resolution for the PPMC and IPMC to vote upon.
> >
> > Please take a minute to vote on whether or not Apache SkyWalking should
> > graduate to a Top Level Project by responding with one of the following:
> >
> > [ ] +1 Apache SkyWalking should graduate.
> > [ ] +0 No opinion
> > [ ] -1 Apache SkyWalking should not graduate (please provide the reason)
> >
> > The VOTE is open for a minimum of 72 hours. As there has been previous
> discussions on past versions of this proposal, I have not preluded the vote
> with a DISCUSS email. If feedback arises the vote period will be extended
> in good faith.
> >
> > regards,
> > Mick
> >
> >
> > [1]
> https://lists.apache.org/thread.html/9aab116a5df46d10a655bbf243f525260bad7763f6f65bce19ec33bd@%3Cdev.skywalking.apache.org%3E
> > [2]
> https://cwiki.apache.org/confluence/display/SKYWALKING/Apache+Maturity+Model+Assessment+for+SkyWalking
> > [3]
> https://lists.apache.org/thread.html/68b06b2efdcd4f519cd9aa3df55d46bf0dade28002065fbad75d4195@%3Cdev.skywalking.apache.org%3E
> > [4]
> https://lists.apache.org/thread.html/9f05862dffb40a967f867ba0fee4ab8549b08736cde27571e303ab30@%3Cdev.skywalking.apache.org%3E
> >
> > 
> >
> >
> > Establish the Apache SkyWalking Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to application performance management and monitoring (APM).
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache SkyWalking Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache SkyWalking Project be and hereby is
> > responsible for the creation and maintenance of software related to
> > application performance management and monitoring (APM); and
> > be it further
> >
> > RESOLVED, that the office of "Vice President, Apache SkyWalking" be and
> > hereby is created, the person holding such office to serve at the
> > direction of the Board of Directors as the chair of the Apache
> > SkyWalking Project, and to have primary responsibility for management of
> > the projects within the scope of responsibility of the Apache SkyWalking
> > Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache SkyWalking
> > Project:
> >
> >  * Haoyang Liu  (刘浩杨)  
> >  * Hongtao Gao  (高洪涛)  
> >  * Ignasi Barrera  
> >  * Mick Semb Wever
> >  * Sheng Wu  (吴晟)  
> >  * Shinn Zhang  (张鑫)  
> >  * Willem Ning Jiang  (姜宁)
> >  * Yongsheng Peng  (彭勇升)  
> >  * DongXue Si (司冬雪)
> >  * Jian Tan (谭建)  
> >  * Kai Wang (王凯)  
> >  * Yang Bai (柏杨)  
> >  * Yao Wang (王垚)  
> >  * Zhang Kewei (张科伟)  
> >  * Can Li (李璨)  
> >  * Jiaqi Lin (林嘉绮)  
> >  * Jinlin Fu (付金林)  
> >  * Lang Li (李浪)  
> >  * Wenbin Wang (王文斌)
> >  * Yixiong Cao (曹奕雄) 

Re: [VOTE] Release Apache OpenWhisk CLI (incubating) version 0.10.0

[Bertrand Delacretaz]

Hi,

Here's my +1 for the release of the 3 archives listed below.

Checked signatures, digests, DISCLAIMER, LICENSE, NOTICE and Apache
license headers.

There's a number of empty files for all 3 modules under
./wski18n/resource which is surprising but not really a problem.

-Bertrand

On Wed, Mar 20, 2019 at 4:28 PM David P Grove  wrote:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-cli-0.10.0-incubating-sources.tar.gz
sha512 = 
55BEEB6DCDF621AB7AA6098A5DBCA55E6D7E3B0CA3DAA7DFB44103F8CE30ACC913411ECCBFF185193E142EC3D27AA081E1D47F6314E9E70890646EC7C13756D6

> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-client-go-0.10.0-incubating-sources.tar.gz
sha512 =
068DBC87533905DBD0089CAE74FD0B91109992D8D843CAA401EA87B69CDC95506D5556554679FF367A52414EDCC59126E558085D3E960DEB188045816B2FA019

> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-wskdeploy-0.10.0-incubating-sources.tar.gz
sha512=
412B1E09129F2884A1D4E9DE0A979B4755A54FC561E1D328325E8A12AE504779A2350B9F4185582F7782EEA5AE9018CD52E4AA4C484B5211AA449B4B9F9E2432

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE]: Release Apache Dubbo (Incubating) 2.7.1 [RC1]

[Willem Jiang]

+1 (binding)

I checked
the signed key and sha512 are OK
There is incubating name in the released kits.
Checked the License headers of source kit with RAT.
License and Notice file are OK
DISCLAIMER file is OK
I can build the source without any error.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Mar 22, 2019 at 5:09 PM Ian Luo  wrote:
>
> Hello all,
>
> This is a call for vote to release Apache Dubbo (Incubating) version 2.7.1.
>
> The Apache Dubbo community has voted on and approved a proposal to release
> Apache Dubbo (Incubating) version 2.7.1.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache Dubbo™ (incubating) is a high-performance, java based, open source
> RPC framework. Dubbo offers three key functionalities, which include
> interface based remote call, fault tolerance & load balancing, and
> automatic service registration & discovery.
>
> Dubbo community vote and result thread:
> https://lists.apache.org/thread.html/3c651acf5116895bc5d816ab78858a8bdd198b5b47be9eb9641681e5@%3Cdev.dubbo.apache.org%3E
>
> The release candidates (RC1):
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.7.1
>
> Git tag for the release (RC1):
> https://github.com/apache/incubator-dubbo/tree/dubbo-2.7.1
>
> Hash for the release tag:
> a36cc7520e0150d07d30e8baa0c61d5f9f11e6ed
>
> Release Notes:
> https://github.com/apache/incubator-dubbo/blob/dubbo-2.7.1/CHANGES.md
>
> The artifacts have been signed with Key: 9C44B5A6884984DB, which can be
> found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS
>
> Look at here for how to verify this release candidate:
> https://github.com/apache/incubator-dubbo-website/blob/asf-site/blog/en-us/prepare-an-apache-release.md#prepare-apache-release
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> The Apache Dubbo (Incubating) Team

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: FYI, saved the current wiki.apache.org/incubator content to svn

[Dave Fisher]

There is one massively important question in this migration and Bertrand’s 
archive is an answer. When the migration is done we should NOT preserve 
history. The reason is that each version of a page *is* a page in the migration 
and we have massive numbers of versions for each report!

There are two main areas to discuss for migration.

(1) Podling Proposals. I think these should be ported for historical purposes 
because they are not preserved in any way.

In Confluence there are capabilities to template new proposals which can be 
investigated. I’ve worked with this in the past at a $dayjob.

(2) Board Reports. I believe that these are preserved and accessible via Whimsy 
although there is some delay.

Do we want to keep for historical purposes?

In Confluence someone will need to investigate the API and how to hook to this 
from the python program that is currently used by the IPMC chair. I think I saw 
this mentioned in an email from Justin.

Regards,
Dave

Sent from my iPhone

> On Mar 25, 2019, at 2:16 AM, Bertrand Delacretaz  
> wrote:
> 
> Hi,
> 
> I have saved the contents of https://wiki.apache.org/incubator/ at
> https://svn.apache.org/repos/private/pmc/incubator/wiki-archive-march-2019/
> , in case we need it later. AFAIK https://wiki.apache.org will be
> decommissioned in May, I don't think we have much "live" content but
> those archives might be useful.
> 
> -Bertrand
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE]: Release Apache Dubbo (Incubating) 2.7.1 [RC1]

[Mark Thomas]

On 22/03/2019 09:09, Ian Luo wrote:

> Please vote accordingly:
> [X] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason

- GPG signatures are correct
- SAH512 hashes are correct
- Builds successfully from src distro

Comment only (no action required):
- Tag includes Maven wrapper and .gitignore whereas src distro does not

Mark

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

回复：Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top Level Project' resolution to board

[Liu Ted]

+1 (binding)

Best regards,

Ted Liu, 
ASF Member, Sponsor Ambassador, Incubator PMC Member 
 
  2019 年 3 月 25 日周一 11:03，Mohammad Asif Siddiqui 写道：   
+1 (binding)  
  
Regards  
Asif

On 2019/03/19 05:21:41, "Mick Semb Wever"  wrote: 
> 
> 
> After the latest discussion amongst this dev community on this dev mailing 
> list[1],  presenting Sheng Wu as the PMC Chair and the maturity model[2], and 
> then the discussion again on the incubator list[3],  a vote for Apache 
> SkyWalking graduating to a top level project was called and has passed[4]. 
> From the past incubator discussions the PPMC altered the draft graduation 
> proposal, specifically the proposed PMC list: removing some inactive people 
> and adding all the podling Committers. 
> 
> 
> Apache SkyWalking entered the incubator on December of 2017.  SkyWalking has 
> delivered 8 releases so far in total, and now shows a good cadence of 
> successful releases.
> 
> During the podling's time in the Apache Incubator there has been
>  3200+ commits on development of the project,
>  378 Issues tagged as question in GitHub created, 373 resolved,
>  850+ Pull request created and resolved,
>  97 different contributors,
>    9 elected new committers, and
>    3 elected new PPMC members.
> 
> And the dev ML has had 72 participants: 
> https://lists.apache.org/trends.html?d...@skywalking.apache.org:2019
> 
> Attached is the draft Resolution for the PPMC and IPMC to vote upon.
> 
> Please take a minute to vote on whether or not Apache SkyWalking should
> graduate to a Top Level Project by responding with one of the following:
> 
> [ ] +1 Apache SkyWalking should graduate.
> [ ] +0 No opinion
> [ ] -1 Apache SkyWalking should not graduate (please provide the reason)
> 
> The VOTE is open for a minimum of 72 hours. As there has been previous 
> discussions on past versions of this proposal, I have not preluded the vote 
> with a DISCUSS email. If feedback arises the vote period will be extended in 
> good faith.
> 
> regards,
> Mick
> 
> 
> [1] 
> https://lists.apache.org/thread.html/9aab116a5df46d10a655bbf243f525260bad7763f6f65bce19ec33bd@%3Cdev.skywalking.apache.org%3E
> [2] 
> https://cwiki.apache.org/confluence/display/SKYWALKING/Apache+Maturity+Model+Assessment+for+SkyWalking
> [3] 
> https://lists.apache.org/thread.html/68b06b2efdcd4f519cd9aa3df55d46bf0dade28002065fbad75d4195@%3Cdev.skywalking.apache.org%3E
> [4] 
> https://lists.apache.org/thread.html/9f05862dffb40a967f867ba0fee4ab8549b08736cde27571e303ab30@%3Cdev.skywalking.apache.org%3E
> 
> 
> 
> 
> Establish the Apache SkyWalking Project
> 
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to application performance management and monitoring (APM).
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache SkyWalking Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache SkyWalking Project be and hereby is
> responsible for the creation and maintenance of software related to
> application performance management and monitoring (APM); and 
> be it further
> 
> RESOLVED, that the office of "Vice President, Apache SkyWalking" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache
> SkyWalking Project, and to have primary responsibility for management of
> the projects within the scope of responsibility of the Apache SkyWalking
> Project; and be it further
> 
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache SkyWalking
> Project:
> 
>  * Haoyang Liu  (刘浩杨)          
>  * Hongtao Gao  (高洪涛)          
>  * Ignasi Barrera                              
>  * Mick Semb Wever                    
>  * Sheng Wu  (吴晟)                      
>  * Shinn Zhang  (张鑫)                  
>  * Willem Ning Jiang  (姜宁)        
>  * Yongsheng Peng  (彭勇升)      
>  * DongXue Si (司冬雪)                    
>  * Jian Tan (谭建)                              
>  * Kai Wang (王凯)                              
>  * Yang Bai (柏杨)                              
>  * Yao Wang (王垚)                              
>  * Zhang Kewei (张科伟)              
>  * Can Li (李璨)                                  
>  * Jiaqi Lin (林嘉绮)                      
>  * Jinlin Fu (付金林)                      
>  * Lang Li (李浪)                          
>  * Wenbin Wang (王文斌)            
>  * Yixiong Cao (曹奕雄)                    
> 
> 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sheng Wu (吴晟) be 
> appointed to the office of Vice President, Apache SkyWalking, to serve in 
> accordance with and subject to the direction of the 

FYI, saved the current wiki.apache.org/incubator content to svn

[Bertrand Delacretaz]

Hi,

I have saved the contents of https://wiki.apache.org/incubator/ at
https://svn.apache.org/repos/private/pmc/incubator/wiki-archive-march-2019/
, in case we need it later. AFAIK https://wiki.apache.org will be
decommissioned in May, I don't think we have much "live" content but
those archives might be useful.

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Zipkin Brave (incubating) for Apache Cassandra version 0.10.2

[Olivier Lamy]

+1

On Fri, 22 Mar 2019 at 01:29, Adrian Cole  wrote:

> The Apache Zipkin community has voted on and approved a proposal to
> release Apache Zipkin Brave (incubating) for Apache Cassandra version
> 0.10.2. The voting thread can be found here:
>
> https://lists.apache.org/thread.html/c2c55a0e347f90bcb07032b4fa79e34a6832742e7284d7f327583b23@%3Cdev.zipkin.apache.org%3E
>
> Three binding +1 vote from mentors Andriy Redko, Willem Ning Jiang and
> Mick Semb Wever carry over from the dev list thread.
>
> We now kindly request the Incubator PMC members review and vote on
> this incubator release.
>
> Apache Zipkin Brave (incubating) for Apache Cassandra allows you to
> trace activities started by Datastax Java Driver for Apache Cassandra
> all the way to inside Apache Cassandra itself. It was originally
> created by Mick at The Last Pickle and also championed by Lance at
> Smart Things.
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/zipkin/brave-cassandra/0.10.2/
>
> Git tag for the release:
> https://github.com/apache/incubator-zipkin-brave-cassandra/tree/v0.10.2
>
> Hash for the release tag:
> b8e379f33eb9f52f0742d3187252de330163cbf7
>
> Release Notes:
>
> https://github.com/apache/incubator-zipkin-brave-cassandra/releases/tag/v0.10.2
>
> The artifacts have been signed with Key : BB67A050, which can be found
> in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/zipkin/KEYS
>
> Verification Hints:
> For your convenience, the below includes detailed how-to on verifying
> a source release. Please note that this document is a work-in-progress
>
> https://cwiki.apache.org/confluence/display/ZIPKIN/Verifying+a+Source+Release
>
> The vote will be open for at least 72 hours or until necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> The Apache Zipkin (Incubating) Team
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy