Re: Poddlings length of time in the incubator
On Tue, Aug 28, 2018 at 8:01 PM Roman Shaposhnik wrote: >... > In the past we typically shied away from setting deadlines for certain > milestones in community development within podlings. This, in my view, > somewhat encouraged this phenomenon of an "eternal podling" (active > enough not to be in the attic, not active/ApacheWay'y enough to > graduate). I feel like Quickstep, for example, can exist in this state > indefinitely. I think there is/can/should be a different bar for TLPs "idle-ness", and that of a podling. A TLP has confirmed itself for operation/oversight, even when it may slow down. A podling hasn't had that confirmation, however. One of the more continual issues within the Incubator is the amount of mentor energy to "go around". It seems that if a podling has hit a dead end, then it is best for the Incubator (as a whole) to go ahead and retire it, and apply its energies to podlings that are making progress towards graduation. Cheers, -g
Re: [VOTE] Accept Zipkin into the Apache Incubator
+1 (non-binding) — Yongsheng Peng Apache SkyWalking PPMC member > 在 2018年8月27日，11:14，Mick Semb Wever 写道： > > After a brief discussion¹ I would like to call a VOTE to accept Zipkin into > the Apache Incubator. > The full proposal is available on the wiki² and is pasted below in text form > as well. > > This vote will run at least 72 hours. Please VOTE as follows: > > [ ] +1 Accept Zipkin into the Apache Incubator > [ ] +0 No opinion > [ ] -1 Do not accept Zipkin into the Apache Incubator because… > > regards, > Mick > > [1] > https://lists.apache.org/thread.html/54798a5059db1d5716ed9910a15c92945509a25ec3b7ccb6b1215c53@%3Cgeneral.incubator.apache.org%3E > [2] https://wiki.apache.org/incubator/ZipkinProposal > > > = Abstract = > Zipkin is a distributed tracing system. It helps gather timing data needed to > troubleshoot latency problems in microservice architectures. It manages both > the collection and lookup of this data. Zipkin’s design is based on the > Google Dapper paper. > > = Proposal = > Zipkin provides a defined data model and payload type for distributed trace > data collection. It also provides an UI and http api for querying the data. > Its server implements this api and includes abstractions for storage and > transport of trace payloads. The combination of these parts avoid lock-in to > a specific tracing backend. For example, Zipkin includes integration with > different open source storage mechanisms like Apache Cassandra and > Elasticsearch. It also includes bridges to convert collected data and forward > it to service offerings such as Amazon X-Ray and Google Stackdriver. > Ecosystem offering extend this portability further. > > While primarily focused on the system, Zipkin also includes tracing libraries > which applications use to report timing information. Zipkin's core > organization includes tracer libraries written in Java, Javascript, Go, PHP > and Ruby. These libraries use the formats mentioned above to report data, as > well "B3" which is a header format needed to send trace identifiers along > with production requests. Many Zipkin libraries can also send data directly > to other services such as Amazon X-Ray and Google Stackdriver, skipping any > Zipkin infrastructure. There are also more Zipkin tracing libraries outside > the core organization than inside it. This is due to the "OpenZipkin" culture > of promoting ecosystem work. > > = Background = > Zipkin began in 2012 at Twitter during a time they were investigating > performance problems underlying the "fail whale" seen by users. The name > Zipkin is from the Turkish word for harpoon: the harpoon that will kill the > failures! Incidentally, Zipkin was not the first tracing system, it had roots > in a former system at Twitter named BigBrotherBird. It is due to > BigBrotherBird that the de-facto tracing headers we still use today include > the prefix "X-B3". > > In 2015, a community of users noticed the project was not healthy in so far > as it hadn't progressed and often didn't accept pull requests, and the > Cassandra backend was stuck on an unmaintained library. For example, the > Apache Incubator H-Trace project started in some ways as a reaction to the > inability to customize the code. The root cause of this was Twitter moving to > internal storage (Manhattan) and also the project not being managed as a > product. By mid 2015, the community regrouped as OpenZipkin and the codebase > moved from Twitter to an org also named OpenZipkin. This led to fast progress > on concerns including initially a server rewrite and Docker based deployment. > > In 2018, the second version of the data model completed, and along the way, > many new libraries became standard, including javascript, golang and PHP. The > community is dramatically larger than 2015, and Zipkin remains the most > popular tracing system despite heavy competition. > > = Rationale = > Zipkin is a de-facto distributed tracing system, which is more important as > architectures become more fine grained due to popularity of microservice or > even serverless architectures. Applications transition to use more complex > communication including asynchronous code and service mesh, increasing the > need for tools that visualize the behavior of requests as they map across an > architecture. > > Zipkin's server is focused only on distributed tracing. It is meant to be > used alongside existing logging and metrics systems. Generally, the community > optimizes brown field concerns such as interop over breaking changes such as > experimental features. The combination of code and community make Zipkin a > safe and easier choice for various sites to introduce or grow their > observability practice. > > = Initial Goals = > The initial goals are to mature OpenZipkin's community process. For example, > while OpenZipkin has a good collaborative process, it lacks formality around > project management functions de
Re: Poddlings length of time in the incubator
On Sun, Aug 26, 2018 at 1:40 PM, Julian Hyde wrote: > Regarding Quickstep. I am a mentor. (One mentor resigned earlier this > year, but the other mentor, Roman, is sufficiently engaged.) > > I am concerned that Quickstep is not going to graduate. They are > functioning well as an academic project, as evidenced by papers at top > conferences[1], but all of their contributors are from the same > university department. They have made a few efforts at community > building, but do not seem to be building a user base, or attracting > outside contributions. > > (Note that traffic for July and August is lower than usual, due to > their contributors being in academia. Traffic on the dev list should > pick up somewhat in September.) > > Embrace of Apache has been half-hearted. Note, for instance, that > their twitter account [2] still references their pre-Apache home page > [3] rather than their Apache page [4]. > > Quickstep made their first release in March 2017 but have not made > further releases. I am going encourage them to make a new release > soon. That will stimulate some community activity. But I am dubious > that this will attract outside contributors. Basically, I'm +1 on every single point that Julian makes, but having said this I'm unsure as to where can we go from here. In the past we typically shied away from setting deadlines for certain milestones in community development within podlings. This, in my view, somewhat encouraged this phenomenon of an "eternal podling" (active enough not to be in the attic, not active/ApacheWay'y enough to graduate). I feel like Quickstep, for example, can exist in this state indefinitely. Thanks, Roman. > Julian > > [1] http://www.vldb.org/pvldb/vol11/p663-patel.pdf > > [2] https://twitter.com/ApacheQuickstep > > [3] http://quickstep.cs.wisc.edu/ > > [4] http://quickstep.apache.org/ > On Sun, Aug 26, 2018 at 10:17 AM Mark Thomas wrote: >> >> On 26/08/18 02:30, Justin Mclean wrote: >> > Hi, >> > >> >> I’ve discussed this some on the ODF toolkit dev list. Development was >> >> recently moved to Git. The Incubator needs to decide if we will turnover >> >> the domains that were donated in 2011 by IBM(?) to the only consistent >> >> developer. If that is true then we can quickly let them retire, but >> >> survive on Github. >> > >> > I also saw you mentioned it in a previous incubator report for the >> > podling. What are the domain names in question? I think doing as you >> > suggested sounds like a good idea do you want to take that back to the >> > PPMC and discuss and/or vote on doing that. >> > >> > Any other IPMC members think differently? >> >> The podling PMC can make a recommendation but the decision to release a >> domain name to a third party needs the approval of VP Brand Management. >> >> We also need to find the transfer agreements (if any) for those domains >> to see what the ASF agreed to at the time of donation. It is not unheard >> of for such agreements to include a clause that ownership reverts to the >> donor if the podling does not graduate. >> >> Mark >> >> - >> 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] Accept Zipkin into the Apache Incubator
+1 binding Regards, Ate On 2018-08-27 05:14, Mick Semb Wever wrote: After a brief discussion¹ I would like to call a VOTE to accept Zipkin into the Apache Incubator. The full proposal is available on the wiki² and is pasted below in text form as well. This vote will run at least 72 hours. Please VOTE as follows: [ ] +1 Accept Zipkin into the Apache Incubator [ ] +0 No opinion [ ] -1 Do not accept Zipkin into the Apache Incubator because… regards, Mick [1] https://lists.apache.org/thread.html/54798a5059db1d5716ed9910a15c92945509a25ec3b7ccb6b1215c53@%3Cgeneral.incubator.apache.org%3E [2] https://wiki.apache.org/incubator/ZipkinProposal = Abstract = Zipkin is a distributed tracing system. It helps gather timing data needed to troubleshoot latency problems in microservice architectures. It manages both the collection and lookup of this data. Zipkin’s design is based on the Google Dapper paper. = Proposal = Zipkin provides a defined data model and payload type for distributed trace data collection. It also provides an UI and http api for querying the data. Its server implements this api and includes abstractions for storage and transport of trace payloads. The combination of these parts avoid lock-in to a specific tracing backend. For example, Zipkin includes integration with different open source storage mechanisms like Apache Cassandra and Elasticsearch. It also includes bridges to convert collected data and forward it to service offerings such as Amazon X-Ray and Google Stackdriver. Ecosystem offering extend this portability further. While primarily focused on the system, Zipkin also includes tracing libraries which applications use to report timing information. Zipkin's core organization includes tracer libraries written in Java, Javascript, Go, PHP and Ruby. These libraries use the formats mentioned above to report data, as well "B3" which is a header format needed to send trace identifiers along with production requests. Many Zipkin libraries can also send data directly to other services such as Amazon X-Ray and Google Stackdriver, skipping any Zipkin infrastructure. There are also more Zipkin tracing libraries outside the core organization than inside it. This is due to the "OpenZipkin" culture of promoting ecosystem work. = Background = Zipkin began in 2012 at Twitter during a time they were investigating performance problems underlying the "fail whale" seen by users. The name Zipkin is from the Turkish word for harpoon: the harpoon that will kill the failures! Incidentally, Zipkin was not the first tracing system, it had roots in a former system at Twitter named BigBrotherBird. It is due to BigBrotherBird that the de-facto tracing headers we still use today include the prefix "X-B3". In 2015, a community of users noticed the project was not healthy in so far as it hadn't progressed and often didn't accept pull requests, and the Cassandra backend was stuck on an unmaintained library. For example, the Apache Incubator H-Trace project started in some ways as a reaction to the inability to customize the code. The root cause of this was Twitter moving to internal storage (Manhattan) and also the project not being managed as a product. By mid 2015, the community regrouped as OpenZipkin and the codebase moved from Twitter to an org also named OpenZipkin. This led to fast progress on concerns including initially a server rewrite and Docker based deployment. In 2018, the second version of the data model completed, and along the way, many new libraries became standard, including javascript, golang and PHP. The community is dramatically larger than 2015, and Zipkin remains the most popular tracing system despite heavy competition. = Rationale = Zipkin is a de-facto distributed tracing system, which is more important as architectures become more fine grained due to popularity of microservice or even serverless architectures. Applications transition to use more complex communication including asynchronous code and service mesh, increasing the need for tools that visualize the behavior of requests as they map across an architecture. Zipkin's server is focused only on distributed tracing. It is meant to be used alongside existing logging and metrics systems. Generally, the community optimizes brown field concerns such as interop over breaking changes such as experimental features. The combination of code and community make Zipkin a safe and easier choice for various sites to introduce or grow their observability practice. = Initial Goals = The initial goals are to mature OpenZipkin's community process. For example, while OpenZipkin has a good collaborative process, it lacks formality around project management functions defined in the Apache Software Foundation (ASF). We also seek out help with brand abuse which is becoming common practice in the competitive landscape, yet demotivates volunteers. Towards volunteers, help with on boarding summer of
Re: [VOTE] Release Apache Daffodil (incubating) 2.2.0-rc2
Hi - +1 (binding) All packages: Checked signatures Verified checksums (note SHA1 are no longer desired although repository.apahce changes may not be completed) DISCLAIMER checked LICENSE checked (It looks like it should be Open Grid Forum and not Open Grid Format. Fix in the next release) NOTICE checked Source package. RAT Check passes sbt build works sbt test failed with OOM error - not concerned, but please provide better guidance on the next release Sbt it:test success. Kudos for the tests suggesting that I run `scutil --set HostName $(scutil --get LocalHostName)` Regards, Dave > On Aug 27, 2018, at 7:22 AM, Mike Beckerle wrote: > > The Apache Daffodil community has voted and approved the proposed release > of Apache Daffodil (Incubating) 2.2.0-rc2. > > 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 DFDL schemas to parse fixed format data into an infoset, which is most > commonly represented as either XML or JSON. This allows the use of > well-established XML or JSON technologies and libraries to consume, > inspect, and manipulate fixed format data in existing solutions. Daffodil > is also capable of the reverse by serializing or "unparsing" an XML or JSON > infoset back to the original data format. > > The Vote thread: > https://lists.apache.org/thread.html/e45ae80c0ed472f54517c5133c25415a4db88a5989732f441b3e225e@%3Cdev.daffodil.apache.org%3E > (note: thread includes an RC1 vote, cancelled, then RC2 vote passed.) > > The Result thread: > https://lists.apache.org/thread.html/e1f7806c404aa644ba481ede5055218492f385fd9644edaee81019ee@%3Cdev.daffodil.apache.org%3E > > All distribution packages, including signatures, digests, etc. can be found > at: > > https://dist.apache.org/repos/dist/dev/incubator/daffodil/2.2.0-rc2/ > > Staging artifacts can be found at: > > https://repository.apache.org/content/repositories/orgapachedaffodil-1007/ > > This release has been signed with PGP key 13A680AF, corresponding to > mbecke...@apache.org, which is included in the repository's KEYS file. > > This key can be found on keyservers, such as > > http://pgp.mit.edu/pks/lookup?op=get&search=0x13A680AF > > and is also available at: > > https://people.apache.org/keys/committer/mbeckerle.asc > > The release candidate has been tagged in git with v2.2.0-rc2. > > For reference, here is a list of all closed JIRAs tagged with 2.2.0: > > https://issues.apache.org/jira/issues/?filter=-1&jql=project%20%3D%20DAFFODIL%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.2.0%20order%20by%20updated%20DESC > > For a summary of the changes in this release, see: > > https://daffodil.apache.org/releases/2.2.0/ > > Please review and vote. The vote will be open for at least 72 hours, ending > not before Thursday August 30, 2018, 10:30AM EDT.US > (2018-08-30T10:30:00-04:00) > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > -Mike Beckerle > Daffodil (incubating) signature.asc Description: Message signed with OpenPGP
Re: [VOTE] Accept Zipkin into the Apache Incubator
+1 (binding) On Sun, Aug 26, 2018, 8:14 PM Mick Semb Wever wrote: > After a brief discussion¹ I would like to call a VOTE to accept Zipkin > into the Apache Incubator. > The full proposal is available on the wiki² and is pasted below in text > form as well. > > This vote will run at least 72 hours. Please VOTE as follows: > > [ ] +1 Accept Zipkin into the Apache Incubator > [ ] +0 No opinion > [ ] -1 Do not accept Zipkin into the Apache Incubator because… > > regards, > Mick > > [1] > https://lists.apache.org/thread.html/54798a5059db1d5716ed9910a15c92945509a25ec3b7ccb6b1215c53@%3Cgeneral.incubator.apache.org%3E > [2] https://wiki.apache.org/incubator/ZipkinProposal > > > > = Abstract = > Zipkin is a distributed tracing system. It helps gather timing data needed > to troubleshoot latency problems in microservice architectures. It manages > both the collection and lookup of this data. Zipkin’s design is based on > the Google Dapper paper. > > = Proposal = > Zipkin provides a defined data model and payload type for distributed > trace data collection. It also provides an UI and http api for querying the > data. Its server implements this api and includes abstractions for storage > and transport of trace payloads. The combination of these parts avoid > lock-in to a specific tracing backend. For example, Zipkin includes > integration with different open source storage mechanisms like Apache > Cassandra and Elasticsearch. It also includes bridges to convert collected > data and forward it to service offerings such as Amazon X-Ray and Google > Stackdriver. Ecosystem offering extend this portability further. > > While primarily focused on the system, Zipkin also includes tracing > libraries which applications use to report timing information. Zipkin's > core organization includes tracer libraries written in Java, Javascript, > Go, PHP and Ruby. These libraries use the formats mentioned above to report > data, as well "B3" which is a header format needed to send trace > identifiers along with production requests. Many Zipkin libraries can also > send data directly to other services such as Amazon X-Ray and Google > Stackdriver, skipping any Zipkin infrastructure. There are also more Zipkin > tracing libraries outside the core organization than inside it. This is due > to the "OpenZipkin" culture of promoting ecosystem work. > > = Background = > Zipkin began in 2012 at Twitter during a time they were investigating > performance problems underlying the "fail whale" seen by users. The name > Zipkin is from the Turkish word for harpoon: the harpoon that will kill the > failures! Incidentally, Zipkin was not the first tracing system, it had > roots in a former system at Twitter named BigBrotherBird. It is due to > BigBrotherBird that the de-facto tracing headers we still use today include > the prefix "X-B3". > > In 2015, a community of users noticed the project was not healthy in so > far as it hadn't progressed and often didn't accept pull requests, and the > Cassandra backend was stuck on an unmaintained library. For example, the > Apache Incubator H-Trace project started in some ways as a reaction to the > inability to customize the code. The root cause of this was Twitter moving > to internal storage (Manhattan) and also the project not being managed as a > product. By mid 2015, the community regrouped as OpenZipkin and the > codebase moved from Twitter to an org also named OpenZipkin. This led to > fast progress on concerns including initially a server rewrite and Docker > based deployment. > > In 2018, the second version of the data model completed, and along the > way, many new libraries became standard, including javascript, golang and > PHP. The community is dramatically larger than 2015, and Zipkin remains the > most popular tracing system despite heavy competition. > > = Rationale = > Zipkin is a de-facto distributed tracing system, which is more important > as architectures become more fine grained due to popularity of microservice > or even serverless architectures. Applications transition to use more > complex communication including asynchronous code and service mesh, > increasing the need for tools that visualize the behavior of requests as > they map across an architecture. > > Zipkin's server is focused only on distributed tracing. It is meant to be > used alongside existing logging and metrics systems. Generally, the > community optimizes brown field concerns such as interop over breaking > changes such as experimental features. The combination of code and > community make Zipkin a safe and easier choice for various sites to > introduce or grow their observability practice. > > = Initial Goals = > The initial goals are to mature OpenZipkin's community process. For > example, while OpenZipkin has a good collaborative process, it lacks > formality around project management functions defined in the Apache > Software Foundation (ASF). We also seek out help with brand abuse which is > becoming common p
Re: [RESULT][VOTE] Accept Marvin-AI into Apache Incubator
w00t!! > On Aug 27, 2018, at 6:22 PM, Daniel Takabayashi > wrote: > > Thank's everybody for the votes in this incubation process. And I know that > our work just started! > > > > Em seg, 27 de ago de 2018 às 13:23, Luciano Resende > escreveu: > >> On Tue, Aug 21, 2018 at 10:43 AM Luciano Resende >> wrote: >> >>> After the initial discussion, please vote on the acceptance of Marvin-AI >>> Project for incubation at the Apache Incubator. The full proposal is >>> available at the end of this message and on the wiki at : >>> >>> https://wiki.apache.org/incubator/Marvin-AI >>> >>> Please cast your votes: >>> >>> [ ] +1, bring Marvin-AI into Incubator >>> [ ] +0, I don't care either way >>> [ ] -1, do not bring Marvin-AI into Incubator, because... >>> >>> The vote is open for the next 72 hours and only votes from the >>> Incubator PMC are binding. >>> >>> === >>> >>> = Marvin-AI = >>> >>> == Abstract == >>> >>> Marvin-AI is an open-source artificial intelligence (AI) platform that >>> helps data scientists, prototype and productionalize complex solutions >> with >>> a scalable, low-latency, language-agnostic, and standardized architecture >>> while simplifies the process of exploration and modeling. >>> >>> == Proposal == >>> >>> Marvin helps non-experienced developers create industry-grade AI >>> applications. It has three core components: a development environment to >>> be used during data exploration and hypothesis validation (Toolbox), a >>> library which should be extended to create Marvin engines, and a Scala >>> application server which interprets engines (Engine Executor). >>> A basic premise of Marvin is that it should be language-agnostic, able to >>> interpret engines implemented in different programming languages. >>> >>> == Background == >>> >>> The Marvin AI project was initiated as an internal project at B2W Digital >>> (Brazil), the largest e-commerce company in Latin America. Nowadays, it >> is >>> used by all data scientists within the B2W team. Oftentimes, data >>> scientists don't have an extensive background in software engineering, >> yet >>> are in charge of creating AI applications that need to scale to high >>> throughput and provide millisecond-level response times. At B2W, Marvin >> AI >>> plays an important role in this process, abstracting advanced software >>> engineering procedures, allowing data scientists to focus on their >>> knowledge domain. >>> >>> == Rationale == >>> >>> With recent advances in computer architecture and a corresponding >> increase >>> in the amount of data generated by always-connected devices, AI >> algorithms >>> offer a solution to problems that have long troubled modern corporations. >>> Since AI developers come from various fields, such as statistics, >> physics, >>> and math, there exists a strong need for platforms which enable them to >>> move from prototypes to enterprise applications. Although some tools >> claim >>> to offer this service, in reality, there is no reliable open-source >>> solution. >>> >>> == Initial Goals == >>> >>> The initial goals will most likely be to merge the existing codebase into >>> a single repository, migrate it to Apache, and then integrate with the >>> Apache development process. Furthermore, we plan for incremental >>> development and releases, as per Apache guidelines. >>> >>> == Current Status == >>> >>> === Meritocracy === >>> >>> Marvin already works under principles of meritocracy. Today, Marvin >>> already has some contributors that are part of other institutions. >> Although >>> there is no formal process defined to become a committer, contributors >> that >>> make major changes/improvements to the platform are naturally granted >> write >>> access to the repository. >>> >>> >>> === Community === >>> >>> Acceptance into the Apache foundation would substantially boost both >>> Marvin's user and developer communities. The current community includes a >>> few experienced developers that have either academic or professional >>> experience with AI. The community is largely comprised of data scientists >>> working at B2W and other companies such as Cloudera, MIT, Qume Labs, >>> Laguro.com, and CBYK. Also, there is a meetup group of hundreds of users >>> who meet regularly to exchange ideas about Marvin and, more generally, >> AI. >>> >>> Reference to the group: https://www.meetup.com/marvin-ai/members/ >>> >>> === Core Developers === >>> >>> The core developers for Marvin are listed in the contributor's list and >>> initial PPMC below. These lists include B2W employees, MIT students, >> UFSCAR >>> researchers, independent contributors, and some employees of other >>> companies like Cloudera, Qume Labs, Laguro.com, and CBYK. >>> >>> === Alignment === >>> >>> The initial committers strongly believe that by being part of the Apache >>> Software Foundation, Marvin AI will be part of a comprehensive suite for >> AI >>> applications that can process big data and enable enterprises t
Re: [VOTE] Release Apache OpenWhisk (Incubating): wskdeploy module 0.9.8
+1 (binding) > On Aug 27, 2018, at 11:04 AM, Vincent S Hou wrote: > > Dear IPMC members, > > This is a call for vote to release Apache OpenWhisk (Incubating): wskdeploy > module, Version 0.9.8. > > The Apache OpenWhisk community has voted on and approved a proposal to > release Apache OpenWhisk (Incubating): wskdeploy, Version 0.9.8. > > We now kindly request the Incubator PMC members to review and vote on this > incubator release. > > Apache OpenWhisk Wskdeploy is a utility to help you describe and deploy any > part of the OpenWhisk programming model using a Manifest file written in YAML. > > OpenWhisk Wskdeploy vote thread: > https://lists.apache.org/thread.html/b2beb87458fca80d326725b8fb0e92d533f90b784f7c2cc5bbd84c31@%3Cdev.openwhisk.apache.org%3E > > OpenWhisk Wskdeploy vote result thread: > https://lists.apache.org/thread.html/caea29e3b3c8ea56f5bb3e40ee4b57153787ef193dc64ff63024230b@%3Cdev.openwhisk.apache.org%3E > > This release comprises of source code distribution only. > > The source code artifact of OpenWhisk Wskdeploy can be found at: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz > > The SHA-512 checksum for OpenWhisk Wskdeploy is > openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz: > B1979B93 573BB04B B495FA1A 8D0C1D93 ACD6371D 96BED392 A47D972C 6232AE41 > 0E1FA1DF > DB79D4AA B2D10F87 1942ED94 BF83A200 6D82EABB 2BCE951C 31B5A8D3 > > which can be found at: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz.sha512 > > The signature for OpenWhisk Wskdeploy can be found at: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz.asc > > > KEYS file is available at: > https://www.apache.org/dist/incubator/openwhisk/KEYS > This key has been validated here: > http://pgp.mit.edu/pks/lookup?search=houshengbo&op=index > > This is the first time that Apache OpenWhisk: wskdeploy request for a > release, so there is no file of CHANGELOG. > > 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 > > We are currently using the tool called > openwhisk-release(https://github.com/apache/incubator-openwhisk-release) to > release all the modules of OpenWhisk. The instruction for release managers > can be found at: > https://github.com/apache/incubator-openwhisk-release/blob/master/docs/release_instructions.md. > This tool > supports both manual and automated modes to package the source code, sign > the artifacts and upload the artifacts into Apache SVN repositories. > > 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 > > Best wishes. > Vincent Hou (侯胜博) > > Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud > > Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com, > Phone: +1(919)254-7182 > Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States > > > - > 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: Request to join the IPMC
Hi Chris, Since you're already a Foundation member you can express your interest by sending an e-mail to private@incubator.a.o. [1] As a foundation member you can subscribe to private@incubator.a.o as well. [1] https://incubator.apache.org/guides/pmc.html#joining_the_ipmc Regards, Roy Op di 28 aug. 2018 om 12:04 schreef Christofer Dutz < christofer.d...@c-ware.de>: > Hi all, > > I would like to ask to join the IPMC as I would like to help mentoring a > new project coming towards the incubator. > > Chris >
Request to join the IPMC
Hi all, I would like to ask to join the IPMC as I would like to help mentoring a new project coming towards the incubator. Chris
Re: [VOTE] Accept Zipkin into the Apache Incubator
+1 binding LieGrue, strub > Am 27.08.2018 um 05:33 schrieb 吴晟 Sheng Wu : > > +1 non-binding > > > -- > Sheng Wu > Apache SkyWalking > > > > > > > > -- Original -- > From: "mck"; > Date: Mon, Aug 27, 2018 11:15 AM > To: "general"; > > Subject: Re: [VOTE] Accept Zipkin into the Apache Incubator > > > > > >> This vote will run at least 72 hours. Please VOTE as follows: >> >> [ ] +1 Accept Zipkin into the Apache Incubator >> [ ] +0 No opinion >> [ ] -1 Do not accept Zipkin into the Apache Incubator because… > > > +1 Accept Zipkin > > - > 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
