Re: Open up incubator wiki to all committers

Hi Justin, On Thu, Oct 10, 2019 at 2:36 PM Justin Mclean wrote: > HI, > > > I just checked the Weex report for October, and while doing so, I > realized > > that I do not have edit rights to the incubator wiki. > > I think might what have happen here is that the page has been made read > only

Open up incubator wiki to all committers

Hey all, I just checked the Weex report for October, and while doing so, I realized that I do not have edit rights to the incubator wiki. Rather than request them now, I'd like to make a different suggestion: We should add the group "committers" with RW access (but not delete) to the entire

Re: Showcase your project at ApacheCON at a Podling's Shark Tank

prize!) and you will get a chance to receive feedback that might > actually help you grow your community and ultimately graduate to the > TLP status. And! Given our awesome panel of judges: > * Myrle Krantz > * Justin Mclean > * Craig Russel > * Shane Curcur

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

+1 binding I'm looking forward to welcoming you to the fold! : o) Best, Myrle On Tue, Aug 13, 2019 at 9:10 PM Suneel Marthi wrote: > +1 binding > > Congrats !! > > On Tue, Aug 13, 2019 at 3:06 PM Julian Feinauer < > j.feina...@pragmaticminds.de> wrote: > > > +1 (binding) > > > >

Re: [Vote] Release Apache Weex (Incubating) 0.26.0-RC2

On Tue, Jul 9, 2019 at 5:24 AM 申远 wrote: > > > > * gradle build works (I had trouble with the build script in the scripts > > directory) > > If you build Weex on a Mac, could you please explain your problem here, > maybe we shall fix it before next release. We only test build script on Mac >

Re: [Vote] Release Apache Weex (Incubating) 0.26.0-RC2

Hey all, I vote +1 (binding) I checked: * incubating in name * gradle build works (I had trouble with the build script in the scripts directory) * It contains a correct NOTICE and a LICENSE and DISCLAIMER * ran ant (version 13) (Got slowed down by accidentally typing rant-ant multiple times : o)

Re: Podlings, the Incubator, relationships and Apache

Hey Alex, The Incubator plays a special role. We should be willing to take on some risks in the process of helping newer, or older projects adjust to us. But once those adjustments are complete, we should be able to expect TLP's to "color in the lines". If you believe that is impossible for

Re: LGPL dependency

get all you needed? Enough votes and all to get the release > unblocked? > > > On Jun 28, 2019, at 11:24 AM, Myrle Krantz wrote: > > > > I've said it on dev@weex, and on private@incubator, but I wanted to make > > sure and say it here too. Weex should cut the releas

Re: LGPL dependency

apologize for us blocking you for so long. Best Regards, Myrle Krantz PMC Member, Apache Incubator On Thu, Jun 27, 2019 at 6:06 AM 申远 wrote: > It looks like we have got result[1] from Legal VP, I will bring it here now > >1. It's fine if Weex only could include header files under 2-c

Re: overzealous bureaucracy (was: [VOTE] Zipkin leave incubator, return back to OpenZipkin)

On Thu, Jun 20, 2019 at 9:38 AM Lars Francke wrote: > This is very much not thought through to the end. One question raised for > example is whether projects would even want to become a TLP. > The mission states: "We do this by providing services and support for many > like-minded software

Re: overzealous bureaucracy (was: [VOTE] Zipkin leave incubator, return back to OpenZipkin)

An enthusiastic +1 from me, both for Bertrand's statement and Greg's characterization of it. : o), Myrle On Wed, Jun 19, 2019 at 2:55 PM Sheng Wu wrote: > +1 help/mentor/service > > That is my only goal as mentor to ShardingSphere today. Provide > experiences and helps as much as I could. > >

Re: overzealous bureaucracy (was: [VOTE] Zipkin leave incubator, return back to OpenZipkin)

I don't think anyone here asked for a vote with ill-will; it was mostly a matter of uncertainty (1). However, I do agree with Greg that only one vote among the departing community, taken on their public list, should be necessary when a community like Zipkin decides to leave. Nonetheless, I did

Re: [VOTE] Zipkin leave incubator, return back to OpenZipkin

+1, and I wish OpenZipkin all the best in your future endeavors. Best, Myrle On Tue, Jun 18, 2019 at 12:21 PM Bertrand Delacretaz < bdelacre...@codeconsult.ch> wrote: > > On Mon, Jun 17, 2019 at 8:22 PM Sheng Wu > wrote: > > > > This is a call for official vote of Zipkin leave from incubator,

Re: LGPL dependency

Thank you all, YorkShen, I think at this point the best thing to do is to open a "legal" ticket at this Jira (https://issues.apache.org/jira/browse/LEGAL). I suspect that if you're only including the BSD-licensed headers, that Weex will only be dependent on BSD-licensed code. It's possible that

Re: LGPL dependency

I feel like the answers provided here up till now are too simple. I believe we have projects at Apache which seem to be using, or have used Webkit: ( https://issues.apache.org/jira/browse/COUCHDB-232?jql=text%20~%20%22webkit%22 ) * Flex * Myfaces * Shindig (?) * Cordova * Wave * Corinthia *

Re: Podling releases and release policy

On Tue, Jun 4, 2019 at 2:40 AM Greg Stein wrote: > > > > Yes, I'd like to change the disclaimer to state that releases cannot be > > considered completely reliable, should not be depended on for production, > > > I believe the above two phrases would be unfair to mature projects. In > fact, to

Open Source and EAR

Hey all, There has been some uncertainty about whether open source software falls under EAR. This blog post is meant to address this, and especially to help our Chinese podlings feel more at ease: "Statement by The Apache Software Foundation regarding US Federal Register Notice of non-US

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

+1 (binding) On Thu, May 2, 2019 at 10:01 AM Willem Jiang wrote: > +1 (binding). > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Wed, May 1, 2019 at 9:44 AM Huxing Zhang wrote: > > > > Hi All, > > > > After discussion in the Apache Dubbo community on the dev mailing > >

board report duplication

Hey incubator, It looks like part of the incubator report was "doubled". I've deleted the duplication, but I'd appreciate it if you'd check me to be sure I didn't accidentally delete something that belonged. Best, Myrle

Re: Write Access to Wiki

Has someone helped Tianqi? I'd do it, but I'm having trouble logging in right now... Best, Myrle On Thu, Apr 4, 2019 at 12:58 AM Tianqi Chen wrote: > Hi: > > Can someone give me write access to the incubator wiki? I need the > permission to migrate the podling report. > Wiki username:

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

+1 binding! On Wed, Apr 10, 2019 at 6:54 AM Furkan KAMACI wrote: > +1 (binding) > > 10 Nis 2019 Çar, saat 07:02 tarihinde larry mccay şunu > yazdı: > > > +1 > > > > On Tue, Apr 9, 2019 at 6:59 PM William Guo wrote: > > > > > +1 > > > > > > > > > William > > > > > > On Wed, Apr 10, 2019 at

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

+1 On Tue, Apr 9, 2019 at 11:18 AM Bertrand Delacretaz < bdelacre...@codeconsult.ch> wrote: > On Tue, Apr 9, 2019 at 10:08 AM Christofer Dutz wrote: > > ...Accordingly, I'm bringing the resolution up for an IPMC VOTE... > > +1 > > -Bertrand > >

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

On Tue, Apr 2, 2019 at 2:09 PM Bertrand Delacretaz < bdelacre...@codeconsult.ch> wrote: > Hi, > > On Tue, Apr 2, 2019 at 11:30 AM Geertjan Wielenga > wrote: > > ...Maybe the PPMC and IPMC vote could run in parallel... > > I think the reason for having two votes is to give an opportunity for >

Re: Voting on releases with serious unaddressed issues

On Sat, Mar 30, 2019 at 9:11 AM Ross Gardler wrote: > As for not enough votes i refer you to Roy's suggestion on board@. > Essentially votes don't need to be from IPMC members. > Hey Ross, A.) That was a suggestion and not a statement about how the incubator currently operates. If you want to

Re: [website] Incubator Cookbook - a live experiment

Hey Bertrand, I think this is a wonderful idea, and I'd love to help out with writing, proofing, and correcting anything you'd like written, proofed or corrected for this. Best, Myrle On Tue, Mar 26, 2019 at 5:57 PM Bertrand Delacretaz wrote: > Hi, > > Recent discussions make me think that

Re: Incubator wiki being deprecated

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.

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

+1 binding Best Regards, Myrle On Fri, Mar 22, 2019 at 12:55 AM Dave Fisher wrote: > +1 (binding) > > If you look at the new https://incubator.apache.org/clutch/skywalking.html > analysis you will > see activity in all repositories and that

Re: Learning to edit the incubator website

Thank you Bertrand! Finding that would've saved me a bit of time and trouble. Hopefully we've made it easier on the next person! Best, Myrle On Thu, Mar 21, 2019 at 3:08 PM Bertrand Delacretaz < bdelacre...@codeconsult.ch> wrote: > Hi Myrle, > > On Thu, Mar 21, 2019 at 11:39

Changes to Release Management documentation live, please review

Hey all, Please check: https://incubator.apache.org/guides/releasemanagement.html Feedback (and patches : o) welcome. Best Regards, Myrle

Re: Learning to edit the incubator website

Disregard my previous email. Apparently I already had it, and just needed to be patient. : o) Thank you anyways! Myrle On Thu, Mar 21, 2019 at 11:39 AM Myrle Krantz wrote: > Hey all, > > In order to publish the additional service offering with respect to > release manageme

Learning to edit the incubator website

Hey all, In order to publish the additional service offering with respect to release management, I wanted to edit this page: https://incubator.apache.org/guides/releasemanagement.html This is my first time editing the incubator website. I've never used asciidoc before either. And that page

[RESULT][VOTE] introduce "[DISCUSS]" threads for podling releases

With 5 binding votes, the vote passes. Votes received from: Myrle Krantz Justin Mclean Sheng Wu Furkan Kamaci Lars Francke I'm going to start by editing this here: https://incubator.apache.org/guides/releasemanagement.html If that's wrong, feel free to object and suggest a better location

Re: [VOTE] introduce "[DISCUSS]" threads for podling releases

Hey Bertrand, On Wed, Mar 13, 2019 at 10:54 AM Bertrand Delacretaz < bdelacre...@codeconsult.ch> wrote: > Ok, if it's specific about non-ASF releases it should be named like that > IMO. > There have been discussions about keeping ASF release votes inside the podlings lists. If one of those

Re: [VOTE] introduce "[DISCUSS]" threads for podling releases

On Wed, Mar 13, 2019 at 10:09 AM Lars Francke wrote: > Just one question: Where/how do you plan on documenting this? > I don't know yet: I will look for an appropriate place and ask for feedback. Do you have a good idea? Best, Myrle

Re: [VOTE] introduce "[DISCUSS]" threads for podling releases

< bdelacre...@codeconsult.ch> wrote: > Hi Myrle, > > On Tue, Mar 12, 2019 at 6:27 PM Myrle Krantz wrote: > > ..."Podlings should be able to request feedback by starting a "[DISCUSS]" > > thread or a "[VOTE]" thread > > Sorry that I didn't ca

Re: [VOTE] introduce "[DISCUSS]" threads for podling releases

That seems fixable I hereby amend the proposal with the following definition of "non-ASF release". If this definition is not sufficient, consider accepting the term as currently undefined and start a discussion to create a definition without blocking this vote: Amendment: "A non-ASF release *

Re: [DISCUSS] Include Incubator as part of Community Track at Apachecon NA?

Hey Dave, Would you also be interested in submitting a talk to ApacheCon EU 2019? Please keep us in mind! Best Regards, Myrle Event Lead, ApacheCon Europe On Tue, Mar 12, 2019 at 5:18 PM Dave Fisher wrote: > Hi Sharan, > > I’m thinking about submitting an Incubator focused talk for Apachecon

[VOTE] introduce "[DISCUSS]" threads for podling releases

I believe discussion has petered down on my proposal. It's time to bring it to a vote. Proposal: "Podlings should be able to request feedback by starting a "[DISCUSS]" thread or a "[VOTE]" thread. The podling can decide whether they prefer [DISCUSS] or [VOTE], but only a release which passes a

Re: A smaller IPMC

+1 option #4. Based on Justin's fact-finding, these "extra" IPMC members are not the source of the IPMC's problem. Let's put the conversation about removing IPMC members to bed so that we can focus on more promising causes and cures. Best, Myrle On Fri, Mar 8, 2019 at 12:33 AM Justin Mclean

Re: [DISCUSS] Responsibilities and Improvements (was: Re: Whimsy general@ subs check

On Thu, Mar 7, 2019 at 11:07 AM Bertrand Delacretaz < bdelacre...@codeconsult.ch> wrote: > a) Asking PMC members if they want to step down from the PMC if they > seem to be inactive for a long time > > b) Forcibly removing PMC members that the PMC considers inactive > > IMO a) is fine if a PMC

Re: [DISCUSS] introduce "[DISCUSS]" threads for podling non-ASF release candidates

es outside of the ASF? Best Regards, Myrle On Tue, Feb 26, 2019 at 8:50 AM Myrle Krantz wrote: > Motivation: > > Some podlings want or need feedback on their releases before they are > ready to make official Apache releases. They want to discuss releases that > are

Re: [DISCUSS] Responsibilities and Improvements (was: Re: Whimsy general@ subs check

On Wed, Mar 6, 2019 at 4:49 PM Daniel Gruno wrote: > Or put differently; why would we care that someone is inactive on the > IPMC? Are we short on bytes on the LDAP server and need to conserve > space? ;). It should make no difference if there are inactive members of > the IPMC or not. > Have

Re: Write access to Incubator Wiki

Hey Lee, I've added you. Let me know if it doesn't work. Best, Myrle On Mon, Mar 4, 2019 at 9:09 PM lee...@gmail.com wrote: > Hi, > > May I get write access to wiki? My wiki name is *Lee Rhodes* > > Project Proposal: Apache DataSketches > > Kind Regards, > Lee Rhodes > >

Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)

When I was writing the graduation proposal for Fineract I explicitly asked each PMC member for permission to put them on the list. One guy never answered, so I removed him from the list. There's nothing really *wrong* with having inactive PMC members, but you can at least start your project's

Re: Whimsy general@ subs check (was: [DISCUSS] introduce "[DISCUSS]" threads for podling non-ASF release candidates)

On Fri, Mar 1, 2019 at 12:33 AM Justin Mclean wrote: > > And most probably do not participate. Would asking for those 100 odd > people to be removed come across as friendly? > I'd be +1 on removing them. a.) While kindness towards our fellow PMC members is important, the role of the Incubator

Re: [DISCUSS] introduce "[DISCUSS]" threads for podling non-ASF release candidates

Hey Justin, On Wed, Feb 27, 2019 at 8:33 AM Justin Mclean wrote: > How do we make podling aware they can do this? Obvious people who follow > this list may know, and we can ask mentors to pass it on to their podling > lists, on document on the website and perhaps mention it in Dave’s welcome >

Re: [DISCUSS] introduce "[DISCUSS]" threads for podling non-ASF release candidates

Dave, On Tue, Feb 26, 2019 at 10:30 PM Dave Fisher wrote: > The IPMC could consider some changes to the Incubator rules. (As proposed > mostly by Roy on private lists.) > > Allow the VOTE thread to be only on the dev@ list with 0 or 1 mentor vote > required. As long as the DISCLAIMER exists

Re: Podlings Which Need Mentors

This is a helpful collection Dave, So one way to put these facts next to each other: * We have 1 podling that has expressed concerned about too much IPMC involvement. (Possibly more who are concerned but unwilling to speak up.) * We have 8 podlings that have too little IPMC involvement. This

[DISCUSS] introduce "[DISCUSS]" threads for podling non-ASF release candidates

Motivation: Some podlings want or need feedback on their releases before they are ready to make official Apache releases. They want to discuss releases that are not yet ready for a VOTE, or that they are not sure they are ready for a vote. They may wish to make an early release outside of the

Re: Starting at the incubator and releases

Hey Mick, I see some promise in the approach you outline. I'd like to explain the advantages my project drew from the current system, so that we don't lose anything important in the process of change. Then I would like to suggest a refinement of your approach. I'm top posting here, because I'm

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: the case of the maven wrapper

On Thu, Feb 14, 2019 at 7:05 AM Mick Semb Wever wrote: > One of the tings I've noticed is that the vetos on a podling's first > release can be a bit harsh. > > On releases I would rather see such vetos replaced with comments that are > feedback, while still obvious that they are an issue that

Re: [DISCUSS] Guidelines for distribution of incubating artefacts on other platforms

Weex Mentor here. Answers inline: On Wed, Feb 13, 2019 at 8:36 AM Justin Mclean wrote: > Hi, > > > We distribute artefacts through *CocoaPods* I'm with Justin: I'm not familiar with this either, but my first skim across their information doesn't indicate they'd be fundamentally different

Re: [VOTE] Accept Training into the Apache Incubator

+1 (binding) On Wed, Feb 13, 2019 at 11:03 AM Christofer Dutz wrote: > +1 (binding) > > Chris > > Am 13.02.19, 08:58 schrieb "Lars Francke" : > > Hi everyone, > > we've discussed the proposal for the Training project in [1] and [2]. > The > proposal itself can be found on the

Re: Renaming repos and security concerns

I have no objections to you editing that into it. I do however think it's important to explain the reasons for the rules together with the rules. Please note that I've mentioned legal jeopardy, so if you're going to "strengthen" the language you may need to delete existing text to avoid

Re: Renaming repos and security concerns

Thank you. I've corrected some typos, and then added a motivation section. Questions/comments/suggestions, as always, welcome. Best Regards, Myrle On Fri, Feb 8, 2019 at 11:59 PM Justin Mclean wrote: > Hi, > > > We need to make sure that pre-Apache releases whether source or binary > are

Re: [DISCUSS] Training (incubating) Proposal

My initial thought was: this should go straight to TLP: Training should be done by people who know what they're training about: whether it be the Apache Way or a specific project. All the committers will likely be people who've at least reached committer status in a project, and most of them will

Re: Draft incubator report

Cool. I think we've generated some consensus, even if we haven't answered every question. To summarize, I'd like to change this paragraph of the report: "Again a reminder to all incubating projects and mentors that all releases made available to the general public need to be approved by the

Re: Draft incubator report

That statement would also forbid maven snapshots. Something which many projects (TLPS too) offer. Is that the intention? It’s important to me that when we forbid something that projects are doing for valid reasons that we offer an alternative within the same statement. I’ve offered a potential

Re: Draft incubator report

Hi Justin, We need a formulation which enables pre-release QA by non-coding contributors. I've given my attempt at formulating it. Please give your take on how to accomplish this. Best Regards, Myrle On Mon, Feb 4, 2019 at 10:01 PM Justin Mclean wrote: > Hi, > > > This does *not* include

Re: Draft incubator report

Hi Justin, This looks good. in your general notice about releases, please include a note about nightly builds, and any other non-releases which communities can make. In other words, after: "This includes docker, githubb, PyPi, npm and any other platform for publishing releases, and also covers

Re: Grant for wiki

You should have write access now. Best Regards, Myrle On Wed, Jan 30, 2019 at 10:46 AM Jaeyeon Baek wrote: > Greetings, > > I’m recently plan to contribute to the Apache incubator. Can someone grant > me ASF wiki write access? > > username : *caleybaek* > > Thanks, Caley. >

Re: [VOTE] Graduate Apache Unomi to TLP

+1 (binding) On Mon, Jan 21, 2019 at 3:19 PM Jean-Baptiste Onofré wrote: > Hi, > > @Bertrand, thanks for the feedback. I removed the two sections from the > graduation resolution proposal (as an erratum). > > Let's continue the vote process: > > here's my +1 (binding). > > Regards > > Erratum

Re: [VOTE] Shut down unused/inactive incubator lists

+1 On Mon, Jan 21, 2019 at 10:44 AM Andy Seaborne wrote: > +1 > > > > On 21/01/2019 00:11, sebb wrote: > > The following lists are all but inactive: > > > > announce@ Last post Jan 2008 > > android-interest@ Last post Mar 2011 > > dev@ - only general circulars > > jaxws-tck@ (private) Last post

Re: [IPMC] What to do with retired podling repositories

If we can’t name a reason for keeping the data, I’d be inclined to just delete. We are not data squirrels. : o), Myrle On Sun, Jan 13, 2019 at 10:15 AM Daniel Gruno wrote: > Hello IPMC and other folks, > > We have a big bunch of retired podlings with git repositories on > git-wip-us. As we

Re: Discussion board vs. user mailing list in incubating project

How’s their discussion board archived? -Myrle On Sat, Jan 12, 2019 at 7:01 PM Sebastian wrote: > Hi, > > I recently received a question from a project that is considering to > apply to the incubator and I did not know the answer, so I would like to > ask for your input on that. > > The project

Re: Draft incubator report for January 2019

Hey Justin, I just signed off weex... and then realized I was signing off on a report that was already submitted. Sorry about that. Best Regards, Myrle On Mon, Jan 7, 2019 at 8:55 AM Justin Mclean wrote: > Hi, > > Currently there's a couple of projects don’t have any sign offs. While we >

Re: Request incubator wiki admin access

Thank you Daniel! On Thu, Dec 27, 2018 at 6:29 PM Daniel Gruno wrote: > On 12/27/18 6:22 PM, Myrle Krantz wrote: > > Sorry, forgot to say that: myrle > > You should be good to go now :) > > > > > On Thu, Dec 27, 2018 at 3:52 PM Daniel Gruno > wrote: > >

Re: Request incubator wiki admin access

Sorry, forgot to say that: myrle On Thu, Dec 27, 2018 at 3:52 PM Daniel Gruno wrote: > On 12/27/18 3:44 PM, Myrle Krantz wrote: > > I'd like to be able to give users from the project I'm mentoring write > > access. > > > > Best Regards, > > Myrle > >

Request incubator wiki admin access

I'd like to be able to give users from the project I'm mentoring write access. Best Regards, Myrle

Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

+1 gitbox is wonderful. On Tue, Dec 11, 2018 at 3:33 AM Dave Fisher wrote: > +1 > > Sent from my iPhone > > > On Dec 10, 2018, at 6:19 PM, Paul King wrote: > > > > +1 > > > >> On Tue, Dec 11, 2018 at 6:56 AM Roy Lenferink > wrote: > >> > >> Hi all, > >> > >> The Apache Incubator is still

Re: [VOTE] Graduate Apache Airflow to TLP

+1 binding -Myrle On Thu, Dec 6, 2018 at 7:37 AM Huxing Zhang wrote: > +1 (Non-binding) > > On Thu, Dec 6, 2018 at 7:38 AM Jakob Homan wrote: > > > > Hello- > > > > The Airflow podling community has VOTEd[0] to graduate, following a > > very successful DISCUSS[1]. Accordingly I'm bringing

Re: [VOTE] - Release Apache Weex (Incubating) 0.20.0 [RC1]

+1 (binding) I've checked the following: * Disclaimer * License * Notice * Compile from source * Hashes * Signature (good but signing with an apache email address would be better.) * Rat checks for headers * incubating in name Best Regards, Myrle On Mon, Nov 26, 2018 at 3:16 PM Jonathan Dong

Re: [NEW MENTOR REQUIRED] Apache Weex (incubating)

I would be interested in helping out as a mentor with Weex. I've never mentored a project before, but I have brought my own project through the incubator. Best Regards, Myrle On Tue, Nov 20, 2018 at 3:38 AM Willem Jiang wrote: > There could be some new IPMC member onboard recently. It could

Re: [VOTE] Retire ODF Toolkit

+1 On Sun, Nov 18, 2018 at 10:35 PM Justin Mclean wrote: > Hi, > > +1 Staying in the incubator won't help the project further. > > Thanks, > Justin > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For

Re: How to review so-called "binary releases"?

On Wed, Nov 14, 2018 at 1:12 PM Daniel Shahaf wrote: > The answer to (1) depends on the build platform and toolchain. > Reproducible builds [in the sense of "building the same source twice > gives bit-for-bit identical binaries"] can help with it. When the > answer is negative, the next

Re: How to review so-called "binary releases"?

I had understood the reason that the foundation only officially supports source releases to be the fear of undetected malware in the release (like in the Ken Thompson hack). Is that correct? Are we all are in agreement that the probability of that kind of hack is very low? I'd extend that by

Re: [PROPOSAL] Changing requirements for IPMC

On Wed, Nov 7, 2018 at 7:10 PM Dave Fisher wrote: > Hi - > > >> ...I propose this: > >> > >> If someone has done several of the following: > >> - has been involved in an incubating project from start to finish > >> - has been a release manager > >> - has assembled LICENSE and NOTICE files > >> -

[RESULT] [IP CLEARANCE] Mifos I/O -> Fineract CN

This measure passes by lazy consensus. Regards, Myrle On Wed, Apr 18, 2018 at 11:01 AM, Myrle Krantz <my...@apache.org> wrote: > Hi, > > the Apache Fineract project has received Mifos I/O as a contribution > and wishes to accept it as Fineract CN. > > - A snapshot

[IP CLEARANCE] Mifos I/O -> Fineract CN

ache.org Let's not forget filling our the IP clearance stuff: https://incubator.apache.org/ip-clearance/index.html > On Jan 22, 2018, at 11:27 AM, Myrle Krantz <my...@apache.org> wrote: > > Hey all, > > Anyone subscribed to the commits mailing list will have noticed th

Accepting Fineract CN code into TLP Apache Fineract

steps to get the code accepted by the Apache Software Foundation? Best Regards, Myrle Krantz, Committer, Apache Fineract - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h

Re: [DISCUSS] Podlings & Gitbox Usage

+1 (non-binding) On Fri, Jul 28, 2017 at 6:05 PM, Suneel Marthi wrote: > +1 > > On Fri, Jul 28, 2017 at 11:48 AM, John D. Ament > wrote: > >> All, >> >> As many are aware, Infra has been rolling out a new service that allows >> projects to leverage git

Re: ASF hosted binaries collecting user data without an explicit opt-in

Out of curiousity: Do we ever let domains like this expire? Greets, Myrle On Thu, Jun 8, 2017 at 4:55 PM, Chris Mattmann wrote: > Makes sense to me. > > Cheers, > Chris > > > > > On 6/8/17, 1:42 AM, "Greg Stein" wrote: > > On Thu, Jun 8, 2017 at 3:10

Re: Good examples of licensing in ASF produced web apps?

Hey John, On Sat, May 27, 2017 at 1:42 AM, John D. Ament wrote: > On Fri, May 26, 2017 at 7:39 PM Roman Shaposhnik > wrote: >> >> However, if somebody can spare me this agony -- I'd appreciate it ;-) >> >> > I believe Fineract would be a good

Re: Coming to ApacheCON? Showcase your project at a Podling Shark Tank!

Hi JB, Last year at ApacheCon EU a nearly graduated project presented at the shark tank, and I found it quite helpful in starting the graduation process for Fineract. So IMHO: yes it does make sense. Maybe less for the project itself, and more for the audience. Greets, Myrle On Wed, 19 Apr

[RESULT] [VOTE] Apache Fineract podling graduation

, Myrle Krantz <my...@apache.org> wrote: > Greetings Incubator, > > I propose that we graduate Apache Fineract from the Incubator. The > full text of the proposal is below. > > This is a restarted VOTE thread to correct an error in the resolution > from the original threa

[VOTE] Apache Fineract podling graduation (restarted with corrected proposal)

/1cbc738bbb4083e50b7772d5226b88d3fe321b91451303a69dbc4fa8@%3Cgeneral.incubator.apache.org%3E] And here's the DISCUSS thread: [https://lists.apache.org/thread.html/630d3ec22b4f72f827cd817a0a4da5c3c52dee4f96f47a1369f5dc50@%3Cgeneral.incubator.apache.org%3E] Thank you, Myrle Krantz Resolution

Re: [VOTE] Apache Fineract podling graduation

On Wed, Mar 22, 2017 at 12:51 PM, Jim Jagielski <j...@jagunet.com> wrote: > >> On Mar 21, 2017, at 1:35 PM, Myrle Krantz <my...@apache.org> wrote: >> >> >> I've attached a new version of the resolution below with the WHEREAS >> attached. Do I need t

Re: [VOTE] Apache Fineract podling graduation

appointed to serve as the initial members of the Apache Fineract Project: * Vishwas Babu AJ <vishwasb...@apache.org> * Edward Cable <edca...@apache.org> * Markus Geiss <mage...@apache.org> * Sander van der Heijden <shey...@apache.org> * Ishan Khanna <ishan1...@apac

[VOTE] Apache Fineract podling graduation

er van der Heijden <shey...@apache.org> * Ishan Khanna <ishan1...@apache.org> * Myrle Krantz <myrl...@apache.org> * Terence Monteiro <tere...@apache.org> * Adi Nayaran Raju <rajua...@apache.org> * Gaurav Saini <gsai...@apache.org> * Nazeer Hussain Shaik <

Re: [DISCUSS] Apache Fineract podling graduation

On Tue, Mar 14, 2017 at 1:57 PM, John D. Ament <johndam...@apache.org> wrote: > On Tue, Mar 14, 2017 at 8:34 AM Myrle Krantz <my...@apache.org> wrote: > > > Hey Jon, > > > > Cool. So it'd be something like the text below. I have a question > >

Re: [DISCUSS] Apache Fineract podling graduation

by are appointed to serve as the initial members of the Apache Fineract Project: * Vishwas Babu AJ <vishwasb...@apache.org> * Edward Cable <edca...@apache.org> * Markus Geiss <mage...@apache.org> * Sander van der Heijden <shey...@apache.org> * Ishan Khanna <ishan1...@apache.org>

Re: [DISCUSS] Apache Fineract podling graduation

Hey Jon, On Tue, Mar 14, 2017 at 11:20 AM, John D. Ament wrote: > Understood. I think Fineract's ready to go. What I would recommend as > next steps are to draft a proposal in private and agree to that proposal. > Then you can start the incubator vote. I'll point out

Re: [DISCUSS] Apache Fineract podling graduation

Delacretaz < bdelacre...@codeconsult.ch> wrote: > Hi Myrle, > > On Mon, Mar 13, 2017 at 8:47 PM, Myrle Krantz <my...@apache.org> wrote: > > ...The incubating Apache Fineract community believes it is time to > graduate to > > TLP... > > Did you guys have a vote

[DISCUSS] Apache Fineract podling graduation

l One Partiko Intrasoft Technologies Limited Thank you, Myrle Krantz Resolution: Establish the Apache Fineract 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 C

[jira] [Commented] (INCUBATOR-191) Submission: Anonymous-41

[ https://issues.apache.org/jira/browse/INCUBATOR-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15861074#comment-15861074 ] Myrle Krantz commented on INCUBATOR-191: This is wierdly similar to the Fineract logo

Re: [ANNOUNCE] Apache Fineract 0.6.0-incubating Release

ll Finflux. That's pretty introductory material; perhaps you had something more specific in mind? Greets, Myrle *Myrle Krantz* Solutions Architect RɅĐɅЯ, The Mifos Initiative mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org <http://facebook.com/mifos> <http://ww

Re: [VOTE] Release Apache Fineract 0.6.0 (incubating)

On Thu, Jan 12, 2017 at 3:58 AM, John D. Ament wrote: > Nazeer, > > Sorry but -1. There was a ticket raised to address release issues in the > prior release vote. The IPMC typically looks to see those release issue > tickets reolved in the following release. > >

Re: [DISCUSS] publishing docker image for podling

On Thu, Jan 5, 2017 at 8:13 PM, Roman Shaposhnik wrote: > On Thu, Jan 5, 2017 at 1:32 AM, Greg Stein wrote: > > Taking off my Infrastructure hat from within that issue, and speaking to > > this from a Foundation policy standpoint ... I think this is

Re: [VOTE] Drop incubating requirement of Maven artifacts

+1 non-binding If a best practice targets only maven and not the others, wouldn't that be a reason for a podling to consider avoiding using maven to distribute binaries at all? Is it fair for Apache to disadvantage maven that way? Can Apache enforce policies about binaries not released under

  1   2   >