Re: [VOTE] Accept Training into the Apache Incubator

+1 On Wed, Feb 13, 2019 at 5:58 PM Lars Francke wrote: > Hi everyone, > > we've discussed the proposal for the Training project in [1] and [2]. The > proposal itself can be found on the wiki[3]. > > According to the Incubator rules[4] I'd like to call a vote to accept the > new "Training"

Re: Podlings not following ASF release policy

Hi, > Can you please elaborate on release policy issues with Singa ? > I checked a few things but couldn't find the issue. Nothing too major. If you look at the download page [1] it’s encouraging people to use docker [2] and AWS [3]. Both pages probably has some minor branding/trademark

Re: [VOTE] Release Apache NetBeans parent pom 1

-1 (binding) because the Maven groupId is using org.netbeans as prefix instead of org.apache.netbeans, and there is no need to keep using org.netbeans for this *new* artifact. I've already raised and discussed this on the Netbeans dev@ list were we agreed that it is better to cancel the vote

Re: Podlings not following ASF release policy

Noted. Thanks, Justin! Regards, Wei On Tue, Feb 19, 2019 at 4:04 PM Justin Mclean wrote: > Hi, > > > Can you please elaborate on release policy issues with Singa ? > > I checked a few things but couldn't find the issue. > > > Nothing too major. If you look at the download page [1] it’s

[CANCEL][VOTE] Release Apache NetBeans parent pom 1

Hi, As Ate mention, we cancel this vote to have better compliance with the naming Best Regards Eric -Message d'origine- De : Ate Douma Envoyé : mardi 19 février 2019 10:24 À : general@incubator.apache.org Objet : Re: [VOTE] Release Apache NetBeans parent pom 1 -1 (binding) because

[VOTE] Release Apache Daffodil (incubating) 2.3.0-rc1

Hi all, The Apache Daffodil community has voted and approved the proposed release of Apache Daffodil (incubating) 2.3.0-rc1. We now kindly request the Incubator PMC members review and vote on this incubator release. Daffodil is an open source implementation of the DFDL specification that uses

Re: [VOTE] Accept Training into the Apache Incubator

+1 (binding) > On Feb 13, 2019, at 2:57 AM, Lars Francke wrote: > > Hi everyone, > > we've discussed the proposal for the Training project in [1] and [2]. The > proposal itself can be found on the wiki[3]. > > According to the Incubator rules[4] I'd like to call a vote to accept the > new

Re: Podlings not following ASF release policy

Hi Justin, The download page of SINGA is ( https://singa.incubator.apache.org/en/downloads.html ). The page that you mentioned is the index page. The official ASF releases are in the downloads page. The index page is the landing page of the website and it contains all the different ways to get

Re: [Cava] Suitable name search

+1 keeping as-is. > On Feb 18, 2019, at 1:28 PM, Antoine Toulme wrote: > > First, a heartfelt thank you to all for participating in this discussion. > > I am tempted to keep Cava _for now_ given this late feedback, and proceed to > proposing the project. > To be more precise, I recommend we

Re: [VOTE] Accept Training into the Apache Incubator

PS: I'd also like to be added to the initial Contributor's list, if possible. > On Feb 19, 2019, at 8:51 AM, Jim Jagielski wrote: > > +1 (binding) > >> On Feb 13, 2019, at 2:57 AM, Lars Francke wrote: >> >> Hi everyone, >> >> we've discussed the proposal for the Training project in [1] and

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

I don't think there are some trouble to access apache project website from China. ServiceComb project has a chinese version[1]. We didn't get any complain about having trouble to access it from China. [1]http://servicecomb.apache.org/cn/ Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On

Re: [PROPOSAL] New blockchain project: Cava

I see nothing wrong w/ Cava and see no need to change it, esp before incubation. > On Feb 18, 2019, at 11:40 AM, John D. Ament wrote: > > On Tue, Feb 5, 2019 at 6:52 PM Michael Wall wrote: > >> Interesting proposal. I would be interested in helping. Seems like you >> don't need anymore

Re: [VOTE] Accept Training into the Apache Incubator

I'd be happy to add you but I have honestly no idea what the rules say about changing a proposal after the vote has already started? On Tue, Feb 19, 2019 at 2:59 PM Jim Jagielski wrote: > PS: I'd also like to be added to the initial Contributor's list, if > possible. > > > On Feb 19, 2019, at

Re: [VOTE] Release Apache Daffodil (incubating) 2.3.0-rc1

Hi - Note below. > On Feb 19, 2019, at 5:21 AM, Steve Lawrence wrote: > > Hi all, > > The Apache Daffodil community has voted and approved the proposed > release of Apache Daffodil (incubating) 2.3.0-rc1. > > We now kindly request the Incubator PMC members review and vote on this > incubator

Re: Podlings not following ASF release policy

Quoting from the document - Unique Enough Names The name needs be unique enough to avoid confusion with software that already exists. For the community to be able to protect its reputation for quality and openness, its name needs to unique enough to have potential as a trademark. But this isn’t

Re: Starting at the incubator and releases

> On Feb 19, 2019, at 3:10 PM, Kevin A. McGrail wrote: > > On 2/19/2019 6:07 PM, Dave Fisher wrote: >> (5) Go and develop in The Apache Way! >> >> Only once these four things happen can we start any timer on the first >> Apache Release. > > Four, no FIVE things! Don't forget the Spanish

Re: Starting at the incubator and releases

Hi, > (1) Mentor or champion bootstraps the podling files and mailing lists then > starts: > (2) Onboard the individuals to join the mailing lists, file ICLAs and get > their apache ids. > (3) SGA must be filed. (Or it is determined that ICLA covers everything) > (Domain transfer?) > (4)

Re: Starting at the incubator and releases

Hi Justin On Tue, Feb 19, 2019 at 5:38 PM Justin Mclean wrote: > Hi, > > Looking at some of the situations we currently have I think we may need > some more general guidance for incubating projects and making releases > after just joining the incubator. In this context “non approved” means >

Re: Starting at the incubator and releases

Hi, Thanks for tech feedback John. > This is a loaded statement, since PPMC's can never make releases. The IPMC > approves the release always within the scope of Apache. I did say above that it does need to be approved by the PPMC and IPMC I’ll see if I can reword. >> Ideally within six

Re: [VOTE] Accept Training into the Apache Incubator

I have added Jim. If there are any objections to this please let me know. I'm now going to count the votes. On Tue, Feb 19, 2019 at 10:29 PM Henry Saputra wrote: > +1 (binding) > > Good luck guys > > On Tue, Feb 12, 2019 at 11:58 PM Lars Francke > wrote: > > > Hi everyone, > > > > we've

Re: [VOTE] Accept Training into the Apache Incubator

The vote for accepting "Training" into the Apache Incubator passes* with 21 binding +1 votes, 6 non-binding +1 votes and no other votes. * Because of the late addition of Jim to the Proposal I'll leave everyone another 24h to object (we are in no rush) before I'll go and make this official.

Re: [VOTE] Release Apache Daffodil (incubating) 2.3.0-rc1

Hi - (1) To be fixed on the next release: (a) Please do not include the KEYS file in the source release zip. Refer the users back to the location: https://dist.apache.org/repos/dist/release/incubator/daffodil/KEYS

Re: [VOTE] Accept Training into the Apache Incubator

+1 (binding) Good luck guys On Tue, Feb 12, 2019 at 11:58 PM Lars Francke wrote: > Hi everyone, > > we've discussed the proposal for the Training project in [1] and [2]. The > proposal itself can be found on the wiki[3]. > > According to the Incubator rules[4] I'd like to call a vote to accept

Re: the case of the maven wrapper

Hi, This is what I would do: a) Use the version with the new header. [1] b) Add nothing to NOTICE as it ALv2 license but the 3rd party project has no NOTICE file. c) Add if you want a few lines to LICENSE saying the file is ALv2 licensed and mention the owner. It’s unfortunate that the

Re: [PROPOSAL] New blockchain project: Cava

Hi, It can be a large amount of work to change the name once in graduation, website content and mailing lists need to change, your users will need to resubscribe to your mailing list and you may loose some if your community in the process. It’s up the project but I would suggest starting

Re: [VOTE] Accept Training into the Apache Incubator

I think very strictly the rules would say no. But I also don’t think anyone here will object if you add Jim anyways. Best, Myrle On Tue, Feb 19, 2019 at 3:18 PM Lars Francke wrote: > I'd be happy to add you but I have honestly no idea what the rules say > about changing a proposal after the

Re: [Cava] Suitable name search

Jim, The potential conflict is a small San Francisco blockchain software comp[any called kava.io . Regards, Dave > On Feb 19, 2019, at 5:50 AM, Jim Jagielski wrote: > > +1 keeping as-is. > >> On Feb 18, 2019, at 1:28 PM, Antoine Toulme wrote: >> >> First, a heartfelt

Starting at the incubator and releases

Hi, Looking at some of the situations we currently have I think we may need some more general guidance for incubating projects and making releases after just joining the incubator. In this context “non approved” means releases or distributions not approved by the PPPM and IPMC (usually by

Re: Starting at the incubator and releases

I think this might be a really important faq on the top of the list of OK, now we are voted in, what's next?  and a FAQ about releases. On 2/19/2019 5:38 PM, Justin Mclean wrote: > Hi, > > Looking at some of the situations we currently have I think we may need some > more general guidance for

Re: Starting at the incubator and releases

On 2/19/2019 6:07 PM, Dave Fisher wrote: > (5) Go and develop in The Apache Way! > > Only once these four things happen can we start any timer on the first Apache > Release. Four, no FIVE things!  Don't forget the Spanish Inquisition. Agreed.  We need to setup the reason hurdles with a carrot

Re: Starting at the incubator and releases

We have to make sure that the steps that occur before work can proceed are addressed. (1) Mentor or champion bootstraps the podling files and mailing lists then starts: (2) Onboard the individuals to join the mailing lists, file ICLAs and get their apache ids. (3) SGA must be filed. (Or it is