Re: Removal of old incubator releases
Thanks Justin. We should cut new releases of the main repo and runtimes. I've started a discussion thread for the main repo. On Sat, Nov 16, 2019 at 3:57 PM Justin Mclean wrote: > Hi, > > It looks like you have some old incubator releases here: > https://dist.apache.org/repos/dist/release/incubator/ > > We’re cleaning up the release area and it would be great if you can remove > these old releases. > > If for some reason you need to link to an old release you can do so with a > link to the archive area under here: [1][2] > https://archive.apache.org/dist/incubator/ > > Thanks, > Justin > > 1. https://www.apache.org/dev/mirrors#location > 2, https://www.apache.org/dev/release-distribution.html#download-links > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache OpenWhisk Catalog (v0.10.0-incubating, rc1)
We’ll sort it out I opened an issue to deal with it. We’re not the only Apache project that uses gradle. I missed you raising gradle issue before, my bad. -r > On Jul 5, 2019, at 11:13 PM, Justin Mclean wrote: > > Hi, > >> (and they are listed under the exclusions here [3]). > > I note that it lists gradle-wrapper.jar as an exclusion there as well, this > is not the case as jars containing compiled source code can’t be included in > releases. See the legal JIRA mention in my last email [1] for more info on > this particular situation. I do recall this coming up in one you r releases > as well and teh jar was removed, so I assume the documentation is just out of > date. > > Thanks, > Justin > > 1. https://issues.apache.org/jira/browse/LEGAL-288 > > > - > 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 Catalog (v0.10.0-incubating, rc1)
For future reference, https://github.com/apache/incubator-openwhisk/issues/4545 will address updating the gradlew[.bat] scripts with licenses. -r On Fri, Jul 5, 2019 at 10:27 PM Rodric Rabbah wrote: > As you found/noted in another email, gradle[w.bat] are Apache 2 licensed. > For posterity, we discussed these files [1] and [2] as examples (and they > are listed under the exclusions here [3]). Note that this is the first time > anyone on this list has raised a licensing issue wrt gradle. Since the > problem is addressed by new versions of these file, I expect that the > easiest solution forward is to pick those up in future releases. > > [1] > https://lists.apache.org/thread.html/0acc9d26f87cb7ed769759fe91c39a0158cf51d9ddbc1fc0c69ff93c@%3Cdev.openwhisk.apache.org%3E > > [2] > https://lists.apache.org/thread.html/81643aef06f2e85bb15ea4d3fbca4d928f6456473ba8de3ad72823d2@%3Cdev.openwhisk.apache.org%3E > > [3] > https://github.com/apache/incubator-openwhisk-release/blob/master/docs/license_compliance.md#general-exclusions > > On Fri, Jul 5, 2019 at 9:26 PM Justin Mclean > wrote: > >> HI, >> >> +1 (binding) >> >> I checked: >> - incubating in name >> - signatures and hashes correct >> - LICENSE still needs some work >> - NOTICE is fine >> - no unexpected binary files >> - all source files have ASF headers >> >> These files [1][2] are missing a license header, and are 3rd party files >> (I assume) whose license is not mentioned in LICENSE. How are these files >> licensed? Is their license even compatible with the Apache license? >> >> I know the answer but has the PPMC looked into this? I see no discussion >> about this on your mailing list. Look at your mailing like I see "[x] All >> files have license headers as specified by OpenWhisk project policy [1].” >> in that vote thread, this is obviously not the case as rat output clearly >> shows. >> >> I’m surprised these sort of issues keep occurring wth your releases, >> given it's a license issue it may be a graduation blocking issue. >> >> Thanks, >> Justin >> >> 1. incubator-openwhisk-catalog-0.10.0-incubating/gradlew.bat >> 2. incubator-openwhisk-catalog-0.10.0-incubating/gradlew >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >>
Re: [VOTE] Release Apache OpenWhisk Catalog (v0.10.0-incubating, rc1)
As you found/noted in another email, gradle[w.bat] are Apache 2 licensed. For posterity, we discussed these files [1] and [2] as examples (and they are listed under the exclusions here [3]). Note that this is the first time anyone on this list has raised a licensing issue wrt gradle. Since the problem is addressed by new versions of these file, I expect that the easiest solution forward is to pick those up in future releases. [1] https://lists.apache.org/thread.html/0acc9d26f87cb7ed769759fe91c39a0158cf51d9ddbc1fc0c69ff93c@%3Cdev.openwhisk.apache.org%3E [2] https://lists.apache.org/thread.html/81643aef06f2e85bb15ea4d3fbca4d928f6456473ba8de3ad72823d2@%3Cdev.openwhisk.apache.org%3E [3] https://github.com/apache/incubator-openwhisk-release/blob/master/docs/license_compliance.md#general-exclusions On Fri, Jul 5, 2019 at 9:26 PM Justin Mclean wrote: > HI, > > +1 (binding) > > I checked: > - incubating in name > - signatures and hashes correct > - LICENSE still needs some work > - NOTICE is fine > - no unexpected binary files > - all source files have ASF headers > > These files [1][2] are missing a license header, and are 3rd party files > (I assume) whose license is not mentioned in LICENSE. How are these files > licensed? Is their license even compatible with the Apache license? > > I know the answer but has the PPMC looked into this? I see no discussion > about this on your mailing list. Look at your mailing like I see "[x] All > files have license headers as specified by OpenWhisk project policy [1].” > in that vote thread, this is obviously not the case as rat output clearly > shows. > > I’m surprised these sort of issues keep occurring wth your releases, given > it's a license issue it may be a graduation blocking issue. > > Thanks, > Justin > > 1. incubator-openwhisk-catalog-0.10.0-incubating/gradlew.bat > 2. incubator-openwhisk-catalog-0.10.0-incubating/gradlew > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [Discuss] Graduate Apache OpenWhisk (incubating) as a TLP
We concluded it's not worth asking legal for an opinion on this matter and we opted instead to change the mini to full licenses. We updated the repos that have releases or are subject to upcoming releases. There are repos we will not be releasing and will archive/retire pending discussion on our project dev list since they are not being maintained and have had no releases. -r On Fri, Jul 5, 2019 at 10:17 PM Justin Mclean wrote: > Hi, > > > I created a pull request to update the license compliance [1] to replace > > MINI with FULL. As already noted we have replaced all the mini licenses > > with the full license across the relevant repos. > > > I quick search of your report shows source files still having the short > header, but I assume this will be fixed as yo make releases going forward. > > BTW If there is reason you the project needs mini headers, you can always > ask on legal discuss to see if they will allow it. This has been mentioned > before but AFAIK the project hasn’t done that. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [Discuss] Graduate Apache OpenWhisk (incubating) as a TLP
I created a pull request to update the license compliance [1] to replace MINI with FULL. As already noted we have replaced all the mini licenses with the full license across the relevant repos. [1] https://github.com/apache/incubator-openwhisk-release/pull/288 On Fri, Jul 5, 2019 at 9:48 PM Justin Mclean wrote: > Hi, > > I just took a look at your latests release and noticed it has a minor > licensing issue. In checking your voting thread, I see ether votes point to > policy [1] which I see still mentions using short headers on source files, > but below you stated this was no longer the practice? Re the licensing > issue please see [3][4], you may need to get an updated version of the > wrapper that includes the license. > > Thanks, > Justin > > > 1. > https://github.com/apache/incubator-openwhisk-release/blob/master/docs/license_compliance.md > 2. https://github.com/gradle/gradle/issues/2852 > 3. https://github.com/gradle/gradle/issues/8151 > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Apache OpenWhisk graduation to Top Level Project
> like a google.com for example. I meant gmail.com but slack rejects this and others like it (yahoo, hotmail ...). -r
Re: [VOTE] Apache OpenWhisk graduation to Top Level Project
On Sun, Jun 16, 2019 at 7:13 PM Justin Mclean wrote: > > This is the link to signup to slack for this project > http://openwhisk.apache.org/slack.html > Yep I noted that in my email, but they would need to search for it. It > would be good if the slack login page linked to that. > I don't see this as an option - at best, we can remove all the listed email domains, or add more, like a google.com for example. We'll just have to watch out and not use the direct slack links. -r
Re: [VOTE] Apache OpenWhisk graduation to Top Level Project
This is the link to signup to slack for this project http://openwhisk.apache.org/slack.html -r > On Jun 16, 2019, at 6:38 PM, Justin Mclean wrote: > > Hi, > >> There's a bit of discussion that can happen (and sometimes does) on >> the issue trackers which provide a bit more interactive yet >> asynchronous method of communication. The Slack activity is almost >> comparable to general chit chat at ApacheCon hackathons or similar. > > That may be so but I’m seeing stuff like this. Email on upcoming release [1] > points to GitHub [2] points to Slack [3] > > In order to view [3] you need to create an account and log into slack. Now I > don’t think this is a graduation issue, but the PMC might want to consider > how they bring information back from slack rather than link to it. I assume > at some point the information behind that link would be lost (free tier > right?). > > I’ll note the slack page also says "If you have an @us.ibm.com, @uk.ibm.com, > @adobe.com, @de.ibm.com, @il.ibm.com, or @apache.org email address, you can > create an account.” what if you don’t have one of those accounts? While a > committer will have an apache account, a contributor is not likely to have > any of those. (They could find this [4] and sign up). Seems like a barrier to > entry I think. > > Thanks, > Justin > > 1. > https://lists.apache.org/thread.html/ddf47c05e72426a47f0a414e1dd68cc6075fa4a60be1753318ebfe58@%3Cdev.openwhisk.apache.org%3E > 2. https://github.com/apache/incubator-openwhisk-release/issues/241 > 3. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1560540116034700 > 4. http://openwhisk.incubator.apache.org/slack.html > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
Re: [VOTE] Apache OpenWhisk graduation to Top Level Project
The link to slack contains the content I wrote in the issue. We digest the slack conversations every night and email them to the dev list so that I could have used a ponymail permalink instead. Anyone can self signup for slack there are no approvals or prohibitions on who can sign up. We should remove that text it’s misleading but may be coming from slack itself. Will check it out. Here’s an example ponymail digest https://lists.apache.org/thread.html/6dc90a0226d48c43ef3ebeaab30c0e925a5c14605caf51c27dc1e04c@%3Cdev.openwhisk.apache.org%3E -r > On Jun 16, 2019, at 6:38 PM, Justin Mclean wrote: > > Hi, > >> There's a bit of discussion that can happen (and sometimes does) on >> the issue trackers which provide a bit more interactive yet >> asynchronous method of communication. The Slack activity is almost >> comparable to general chit chat at ApacheCon hackathons or similar. > > That may be so but I’m seeing stuff like this. Email on upcoming release [1] > points to GitHub [2] points to Slack [3] > > In order to view [3] you need to create an account and log into slack. Now I > don’t think this is a graduation issue, but the PMC might want to consider > how they bring information back from slack rather than link to it. I assume > at some point the information behind that link would be lost (free tier > right?). > > I’ll note the slack page also says "If you have an @us.ibm.com, @uk.ibm.com, > @adobe.com, @de.ibm.com, @il.ibm.com, or @apache.org email address, you can > create an account.” what if you don’t have one of those accounts? While a > committer will have an apache account, a contributor is not likely to have > any of those. (They could find this [4] and sign up). Seems like a barrier to > entry I think. > > Thanks, > Justin > > 1. > https://lists.apache.org/thread.html/ddf47c05e72426a47f0a414e1dd68cc6075fa4a60be1753318ebfe58@%3Cdev.openwhisk.apache.org%3E > 2. https://github.com/apache/incubator-openwhisk-release/issues/241 > 3. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1560540116034700 > 4. http://openwhisk.incubator.apache.org/slack.html > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
Re: [VOTE] Release Apache OpenWhisk Runtimes v1.13.0-incubating
> > We've also discussed the use of "short licenses" [5] and we document our > use of the short licenses > > Which I see was some time ago but this keeps happening in your releases. > You are correct that we have an outstanding item to tighten our automated checks inline with the project's documented policy. But I'm not sure if you're implying we're doing something wrong. We don't believe the use of short license is out of line with Apache policy https://www.apache.org/legal/src-headers.html. We document which files get short licenses or license exclusions here: https://github.com/apache/incubator-openwhisk-release/blob/master/docs/license_compliance.md -r
Re: [VOTE] Apache OpenWhisk graduation to Top Level Project
Thanks for these links. I went through many of the links you provided and conducted my own search as well. I conclude that all are left over from before the project entered the Apache Incubator and the period of transition that followed. We addressed the use of IBM OpenWhisk and Bluemix OpenWhisk over several months of transition. As you might now, the project did originate out of IBM but the OpenWhisk trademark has been fully transferred now, and more over, IBM rebranded their Apache OpenWhisk offering to IBM Cloud Functions after induction into the incubator. I find adequate references to Apache OpenWhisk in the current IBM documentation. Maybe we're seeing different results of a google "OpenWhisk" search but the snippet of result for IBM Cloud I saw clearly uses Apache OpenWhisk and not IBM OpenWhisk: "Based on Apache *OpenWhisk*, IBM Cloud Functions is a polyglot functions-as-a-service (FaaS) programming platform for developing lightweight code that scalably executes on demand. ... IBM Cloud Functions provides access to the Apache *OpenWhisk* ecosystem in which anyone can contribute ..." [image: Screen Shot 2019-06-09 at 9.05.34 AM.png] The github projects in the IBM organization appear to not be maintained actively and reference Apache OpenWhisk clearly on the landing pages and README. There were several projects that at the time of induction we did not feel we needed to move to Apache and in fact we moved too many - some of which we have to now archive as we have abandoned and not maintaining. They are helper projects or experiments and not part of the core system. Are you suggesting we ask their maintainers to rename them? There is no such plan and it has not been discussed as far as I know. We are aware of that the PMC is responsible for managing their brand and trademarks and have discussed (on private list) whether action is required in the past for other instances. As someone who was one of the founding members of the project at IBM and who no longer is at IBM, I have no doubts the project was has well out grown its IBM roots. I did open an issue to address the reference to "IBM OpenWhisk" [1]. [1] https://github.com/serverless/serverless-openwhisk/issues/171 -r On Fri, Jun 7, 2019 at 10:22 PM wrote: > Hi, > > Some of the answer be be obvious here to someone who works on the project, > and already been discussed and sorted on your mailing list. So apologies if > that the case, I’m not involved with your project, so I’m just asking to > get clarity. > > A google search turns up mention of “IBM OpenWhisk” and a logo very > similar to the OpenWhisk one. e.g [1] Is the project aware of and dealing > with the branding/trademark issues here? Is this just left over from before > the project entered incubation? > > The also a lot of pages that refer to "Bluemix OpenWhisk” e.g [4] on the > IBM website. Or this page with “OpenWhisk” [5] in the URL and title but no > clear mention it’s an Apache product. > > If I google search for Openwhisk and cloud I see this result in google: > > IBM Cloud > https://www.ibm.com/cloud > Open source. Quicklinks. All open source projects · Tutorials and > training. Try OpenWhisk on Bluemix. Get started with serverless, > event-driven computing in the … > > Again Apache is not mentioned. > > Are you concerned that this may make people think that OpenWhisk in not an > Apache product and give the impression that it's owned by IBM? > > I can also see that IBM has a number of gtihub repos using the name > OpenWhisk, what’s the plan for them? > > I notice you docker images (which are labeled as part of the ASF but oddly > use the openwhisk.org domain) [6] seem to pull down the latest code > rather than approved released version. Do you think this is in line with > ASF release policy? > > Thanks, > Justin > > 1. https://serverless.com/framework/docs/providers/openwhisk/ > 2. https://github.com/IBM/openwhisk-getting-started-template > 3. https://github.com/IBM/expressjs-openwhisk > 4. > https://developer.ibm.com/tv/ibm-expands-bluemix-openwhisk-to-support-rapid-app-development/ > 5. https://developer.ibm.com/tv/openwhisk/ > 6. https://hub.docker.com/u/openwhisk > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Apache OpenWhisk graduation to Top Level Project
> I also note that you’ve been given feedback on several releases that have > had mirror issue, but the issues don’t seem to have been fixed. Is there a > plan to do so before graduation? e.g > https://lists.apache.org/thread.html/041045024538dd9d3d7bf4b32701260a63996c48e115194302dcf0c1@%3Cgeneral.incubator.apache.org%3E I had responded to that feedback and the issues you documented with links to github issues that we will address before the next release of the corresponding artifacts [1] and I just went through your feedback again to see if there was anything missed and provide an update here [2]. [1] https://lists.apache.org/thread.html/98dc0a366d53875b49210fcaa321aeafce345da4fc8944b2544f9b2f@%3Cgeneral.incubator.apache.org%3E [2] https://lists.apache.org/thread.html/db63d274374d0efd810814570d7765abee2301d36f31cabd26b0b24c@%3Cgeneral.incubator.apache.org%3E -r
Re: [VOTE] Release Apache OpenWhisk Runtimes v1.13.0-incubating
For several of the issues you noted, I opened github defects [1-4] against the relevant repos so that we will address them before the next release of the corresponding artifacts. We've also discussed the use of "short licenses" [5] and we document our use of the short licenses and license exclusions (noted for gradle) here [6] per Apache guidance [7]. [1] https://github.com/apache/incubator-openwhisk-runtime-docker/issues/69 [2] https://github.com/apache/incubator-openwhisk-runtime-python/issues/58 [3] https://github.com/apache/incubator-openwhisk-runtime-go/issues/87 [4] https://github.com/apache/incubator-openwhisk-runtime-go/issues/91 [5] https://lists.apache.org/thread.html/bbec59cc560d446a4239627dcb463bc95fb98be5eb66d525f93e5ef1@%3Cdev.openwhisk.apache.org%3E [6] https://github.com/apache/incubator-openwhisk-release/blob/master/docs/license_compliance.md [7] https://www.apache.org/legal/src-headers.html > - The go LICENSE incorrectly states you should add "Copyright 2015-2016 IBM > Corporation” to your own files > - the text of the license for Filetype 1.0.5 is not included (as required by > it's license). The pointer to the licenses should point to a copy of the > license in distribution as licenses and URLs can change over time. The license was corrected and is now the Apache license with no added text. The references to filetype were no longer relevant but > - How is this file licensed? [3] Even if is it a “free” license it may have > terms around distribution that make it incompatible with the Apache license, > and even if not then it still good to list it in LICENSE. > > Thanks,. > Justin > > 1. > ./incubator-openwhisk-runtime-docker-1.13.0-incubating/sdk/docker/buildAndPush.sh > 2. ./incubator-openwhisk-runtime-go-1.13.0-incubating/examples/Makefile > 3. > ./incubator-openwhisk-runtime-python-1.13.0-incubating/core/python3AiAction/samples/smart-body-crop/fashion-men-1.jpg > > > - > 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] Apache OpenWhisk graduation to Top Level Project
The PMC has individuals from 6 unrelated companies. I think committers add another 2 unrelated companies/entities. We expect to welcome new committers after graduation. -r > On Jun 7, 2019, at 8:25 PM, Justin Mclean wrote: > > Hi, > >> I have looked at the contributor distributions as follows: >> >> - 91 individuals with 1 commit. >> - 24 individuals with 2 commits. >> - 9 individuals with 3 commits. >> - 16 individuals with 4 commits. >> - 30 individuals with 5 or more commits (and fewer than 10). >> - 22 individuals with 10 or more commits (and fewer than 25). >> - 12 individuals with 25 or more commits (and fewer than 50). >> - 8 individuals with 50 or more commits (and fewer than 100). >> - 19 individuals with a 100 or more commits. > > Thanks for the information but I was asking about committers not contributors. > >> I don't have a diversity profile per employer. I can try to gather that. Do >> you have a suggestion for the easiest way to do this? Maybe infra has some >> tools? > > Just some rough numbers would be fine. Mostly to gauge that the project > wouldn’t be in trouble if a company pulled out. > >> We are in the process finalizing the PMC proposal and so we can note the >> diversity information as we do. > > Again rough numbers are fine, you don’t have to map this to each person, > again just to gauge that not one company is in control of the project. > > Thanks, > Justin > - > 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] Apache OpenWhisk graduation to Top Level Project
Hi Justin, thanks for your email. I have looked at the contributor distributions as follows: - 91 individuals with 1 commit. - 24 individuals with 2 commits. - 9 individuals with 3 commits. - 16 individuals with 4 commits. - 30 individuals with 5 or more commits (and fewer than 10). - 22 individuals with 10 or more commits (and fewer than 25). - 12 individuals with 25 or more commits (and fewer than 50). - 8 individuals with 50 or more commits (and fewer than 100). - 19 individuals with a 100 or more commits. I don't have a diversity profile per employer. I can try to gather that. Do you have a suggestion for the easiest way to do this? Maybe infra has some tools? We are in the process finalizing the PMC proposal and so we can note the diversity information as we do. In terms of Slack, we have discussed the perception that the project relies heavily on Slack [1] and I've opened a PR against our project webpage [2] to clarify that all important conversations happen on the project dev list. Slack is for quick informal questions, not deep technical discussions. When the latter has occurred, we have been diligent about making sure to bring the discussion to the dev list so it is accessible to all that follow the project and encourage participation that way. -r [1] https://lists.apache.org/thread.html/cc1bc85bfbd06ae588872827a5ee5c72fb3c608898f4b7d984c464e0@%3Cdev.openwhisk.apache.org%3E [2] https://github.com/apache/incubator-openwhisk-website/pull/384 On Fri, Jun 7, 2019 at 6:25 AM Justin Mclean wrote: > Hi, > > Congratulations. That’s pne of the most comprehensive maturity reports > I’ve seen. > > I would be interested is seeing some details of: > - Diversity of current committers in who they work for > - Same for the proposed PMC (if that's been decided?) > - There seems to be a heavy reliance on communication on Slack. Is this a > barrier for people from other time zones from the main developers or people > who can’t work full time of the project? > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE]: Release Apache OpenWhisk Runtime Node.js v1.14.0 (incubating)
>> You can use this UNIX script to download the release and verify the >> checklist below: > > What checklist is being verified? All of these are verified: [ ] 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. Additional steps (eg a build if relevant), are done manually. -r - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: late learnings, which could be helpful for all mentors to know
>> Instead of having to actually DO releases, at least Release Candidates >> should be created ... this would prove the general ability to do a release, >> but not actually DO it. Of course if these RCs contain bad things, they >> should not pass. > > I suspect in some cases there are repos that maybe never have a > release. In zipkin we felt like we had to do all work and it was a bad > taste to see all this high friction efforts then projects go for > graduation with dozens of repos.. probably some not even looked at. > Whatever it is, I think it should become fair at some point. In OpenWhisk we do in fact have some repos which will never be released and eventually archived/retired. It’s easier and faster for new ideas to be explored on their own without some of the oversight and reviewer commitments that come with more mature code bases. So creating release candidates prematurely makes no sense in such instances. (Tangentially, working across multiple repos has its own overheads which we have tried to address with better tooling but we aren’t “there” yet.) We have also in OpenWhisk automated a lot of the steps for preparing release candidate and doing some of the mundane checks for verifying a release. I think this has helped evaluators spend their time better judging a release candidate. The feedback has been useful to address how much we automate. -r - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
FWD: [VOTE] Apache OpenWhisk graduation to Top Level Project
This email is to notify general@i.a.o that a graduation community [VOTE] is in progress for Apache OpenWhisk (incubating). -r -- Forwarded message - From: Rodric Rabbah Date: Tue, Jun 4, 2019 at 5:25 PM Subject: [VOTE] Apache OpenWhisk graduation to Top Level Project To: Hi all, After a discussion among the Apache OpenWhisk community on the dev mailing list [1], we have completed all Trademark transfers, and we are now in the process of pruning the PMC roster, completing the podling status page and completing the project maturity model [2]. Apache OpenWhisk entered the incubator on November 23 2016. Since then, we have grown to be in the top 25 list of Apache projects by GitHub Stars at 4041, have 229 unique contributors across all our project repos, more than 2500 commits, and most importantly, our community has grown and is diversified beyond the initial founding contributors and organization. The project has come a long way in embracing The Apache Way, in no small part to our dedicated mentors and the community spirit that has grown along this journey. We are operating well as an Apache project and so we should take the next step. As such, I am calling a vote for Apache OpenWhisk to graduate to a top level project. If we agree that we should graduate to a top level project, the next step will be to draft a Resolution [3] for the PPMC and IPMC to vote upon. Please take a minute to vote on whether or not Apache OpenWhisk should graduate to a Top Level Project by responding with one of the following: [ ] +1 Apache OpenWhisk should graduate. [ ] +0 No opinion [ ] -1 Apache OpenWhisk should not graduate (please provide the reason) The VOTE is open for a minimum of 72 hours. Per Apache guidelines [4] I will notify the incubator mailing list that a community vote is under way. Thank you. -r (on behalf of the Apache OpenWhisk PPMC) [1] https://lists.apache.org/thread.html/8daa3a05148f54ca82458777e2b2b5e25ba99d39dcf8ce7dd85d0188@%3Cdev.openwhisk.apache.org%3E [2] https://cwiki.apache.org/confluence/display/OPENWHISK/Project+Maturity+Model [3] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115526932 [4] https://incubator.apache.org/guides/graduation.html#community_graduation_vote
[ANNOUNCE] Apache OpenWhisk (Incubating) runtimes version 1.1.3.0 Released
Hello Community, The Apache OpenWhisk (incubating) team is pleased to announce the source release of 13 language runtimes version 1.13.0. These language runtimes allow Apache OpenWhisk (incubating) to run serverless function in JavaScript, Python, Go, Ruby, Dotnet, Swift, PHP, Java, and Docker container. The official source release are available from https://openwhisk.apache.org/downloads.html. If you have any usage questions, or have problems when upgrading, please don't hesitate to let us know by sending feedback to d...@openwhisk.apache.org or opening a GitHub issue in the appropriate runtime project https://github.com/apache/?q=incubator-openwhisk-runtime. *Disclaimer* Apache OpenWhisk is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
Re: [VOTE] Release Apache OpenWhisk Runtimes v1.13.0-incubating
Thank you Justin for the feedback. I opened several defects to address all the points you've raised. For reference: - https://github.com/apache/incubator-openwhisk-runtime-go/issues/87 - https://github.com/apache/incubator-openwhisk-runtime-go/issues/86 - https://github.com/apache/incubator-openwhisk-runtime-go/issues/85 - https://github.com/apache/incubator-openwhisk-runtime-docker/issues/69 - https://github.com/apache/incubator-openwhisk-runtime-python/issues/58 -r On 2019/05/04 23:09:10, Justin Mclean wrote: > Hi, > > +1 (binding) > > I checked all releases: > - incubating in artefact names > - signatures and hashes fine > - NOTICE and LICENSE fine in most cases (but see below) > - Some files have incorrect headers (e.g [1]) or missing headers [2]. This > has been brought up before in previous releases. > - No unexpended binary files > - I didn’t try and compile > > LICENSE issues: > - All releases include gradlew and gradlew.bat these files do not have > headers and these 3rd part files are not mentioned in the LICENSE. > - The go LICENSE incorrectly states you should add "Copyright 2015-2016 IBM > Corporation” to your own files > - the text of the license for Filetype 1.0.5 is not included (as required by > it's license). The pointer to the licenses should point to a copy of the > license in distribution as licenses and URLs can change over time. > - How is this file licensed? [3] Even if is it a “free” license it may have > terms around distribution that make it incompatible with the Apache license, > and even if not then it still good to list it in LICENSE. > > Thanks,. > Justin > > 1. > ./incubator-openwhisk-runtime-docker-1.13.0-incubating/sdk/docker/buildAndPush.sh > 2. ./incubator-openwhisk-runtime-go-1.13.0-incubating/examples/Makefile > 3. > ./incubator-openwhisk-runtime-python-1.13.0-incubating/core/python3AiAction/samples/smart-body-crop/fashion-men-1.jpg > > > - > 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
[RESULT][VOTE] Release Apache OpenWhisk Runtimes v1.13.0-incubating
The voting is now closed. The vote has passed. 3 (+1 binding) from Bertrand Delacretaz, Justin Mclean, Matt Sicker 0 (-1 binding) The vote thread: https://lists.apache.org/thread.html/3bc8d6be4a9c4c7bce6538846a956d379e12a412647cf357521c6f8d@%3Cgeneral.incubator.apache.org%3E Many thanks to all who participated. -r - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache OpenWhisk Runtimes v1.13.0-incubating
Dear IPMC Members, The Apache OpenWhisk community has voted to release version 1.13.0-incubating of the Apache OpenWhisk Runtimes which comprise the following 9 project modules with artifacts built from the Git repositories and commit IDs listed below. Two binding +1 votes from mentors Matt Sicker and Bertrand Delacretaz carry over from the podling voting thread. The voting threads are available here [1]. At least one more +1 vote is needed. We request that IPMC Members please review and vote on this incubator release as described below. * OpenWhisk Runtime Docker: 48b8f4a239864edc178eb392a7eef287857a7a96 https://github.com/apache/incubator-openwhisk-runtime-docker/commits/48b8f4a239864edc178eb392a7eef287857a7a96 https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc1/openwhisk-runtime-docker-1.13.0-incubating-sources.tar.gz https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc1/openwhisk-runtime-docker-1.13.0-incubating-sources.tar.gz.asc https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc1/openwhisk-runtime-docker-1.13.0-incubating-sources.tar.gz.sha512 * OpenWhisk Runtime Dotnet: 50df3bad2588c7b37425fad037ae3df73198ca22 https://github.com/apache/incubator-openwhisk-runtime-dotnet/commits/50df3bad2588c7b37425fad037ae3df73198ca22 https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc1/openwhisk-runtime-dotnet-1.13.0-incubating-sources.tar.gz https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc1/openwhisk-runtime-dotnet-1.13.0-incubating-sources.tar.gz.asc https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc1/openwhisk-runtime-dotnet-1.13.0-incubating-sources.tar.gz.sha512 * OpenWhisk Runtime Go: ddd329946c1d061f256a274d6ccd23e527760e06 https://github.com/apache/incubator-openwhisk-runtime-go/commits/ddd329946c1d061f256a274d6ccd23e527760e06 https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc2/openwhisk-runtime-go-1.13.0-incubating-sources.tar.gz https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc2/openwhisk-runtime-go-1.13.0-incubating-sources.tar.gz.asc https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc2/openwhisk-runtime-go-1.13.0-incubating-sources.tar.gz.sha512 * OpenWhisk Runtime Java: 9f27bab28905bdb66dc3526b5843eaaa6f9d026c https://github.com/apache/incubator-openwhisk-runtime-java/commits/9f27bab28905bdb66dc3526b5843eaaa6f9d026c https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc1/openwhisk-runtime-java-1.13.0-incubating-sources.tar.gz https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc1/openwhisk-runtime-java-1.13.0-incubating-sources.tar.gz.asc https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc1/openwhisk-runtime-java-1.13.0-incubating-sources.tar.gz.sha512 * OpenWhisk Runtime Node.js: c173d64cba124aeccc5c2c7f5db10bd18f5a03a9 https://github.com/apache/incubator-openwhisk-runtime-nodejs/commits/c173d64cba124aeccc5c2c7f5db10bd18f5a03a9 https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc1/openwhisk-runtime-nodejs-1.13.0-incubating-sources.tar.gz https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc1/openwhisk-runtime-nodejs-1.13.0-incubating-sources.tar.gz.asc https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc1/openwhisk-runtime-nodejs-1.13.0-incubating-sources.tar.gz.sha512 * OpenWhisk Runtime PHP: 9c5d3d779425223488ca0f49100095736853f147 https://github.com/apache/incubator-openwhisk-runtime-php/commits/9c5d3d779425223488ca0f49100095736853f147 https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc1/openwhisk-runtime-php-1.13.0-incubating-sources.tar.gz https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc1/openwhisk-runtime-php-1.13.0-incubating-sources.tar.gz.asc https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc1/openwhisk-runtime-php-1.13.0-incubating-sources.tar.gz.sha512 * OpenWhisk Runtime Python: aaeb2ff494e8785abd7a5fc0ba3d902752c47732 https://github.com/apache/incubator-openwhisk-runtime-python/commits/aaeb2ff494e8785abd7a5fc0ba3d902752c47732 https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc1/openwhisk-runtime-python-1.13.0-incubating-sources.tar.gz https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.13.0-incubating-rc1/openwhisk-runtime-python-1.13.0-incubating-sources.tar.gz.asc
