Re: [DISCUSS] Accept SAFplus into the Apache Incubator

2025-05-03 Thread PJ Fanning
Hi everyone, I am going to have to drop out as champion for SAFplus. I don't think there is a strong enough community within SAFplus. I don't think we are going to get enough mentors and generally, there appears to be disinterest in this project among the Incubator PMC. The answers about whether

Re: [DISCUSS] Accept SAFplus into the Apache Incubator

2025-05-01 Thread Hung Ta
Hi PJ, Thanks a lot for your advices. For issue 2, the list was sent. What do you need from us that the contributors ' permission (means what do we prove you that all contributors agree to the license change?) Thanks, Hung On Thu, May 1, 2025, 3:15 AM PJ Fanning wrote: > Hi Hung, > To me, the

Re: [DISCUSS] Accept SAFplus into the Apache Incubator

2025-04-30 Thread PJ Fanning
Hi Hung, To me, the main issues are: 1. The lack of ASF Incubator PMC members who are interested in mentoring this project. We typically require at least 3 mentors. 2. The license change depends on whether you have the permission from previous contributors to change the license. I think more work i

Re: [DISCUSS] Accept SAFplus into the Apache Incubator

2025-04-30 Thread Hung Ta
Hi Justin, PJ, Sorry for bothering you but I see there is not your activity for our project for several weeks. What should I do to make its progress? Thanks, Hung On Wed, Apr 16, 2025, 10:27 AM Hung Ta wrote: > Hi Justtin, > > >> As a first step, can you supply a list of all contributors and w

Re: [DISCUSS] Accept SAFplus into the Apache Incubator

2025-04-15 Thread Hung Ta
Hi Justtin, > As a first step, can you supply a list of all contributors and whether > they were employed by OpenClovis? As PJ said, we also need to know if they > signed CLAs or not. > > Here is the list (I don't know if they signed the CLAs or not). hoangle (hoangle...@gmail.com) karthick18

Re: [DISCUSS] Accept SAFplus into the Apache Incubator

2025-04-10 Thread justin
Hi, > All contributors were employed by OpenClovis, which means the company paid > them for their code, so the Intellectual Property Rights in this case must > belong to the company. While that is generally the case, just because a company paid for code, does not always mean they own the copyri

Re: [DISCUSS] Accept SAFplus into the Apache Incubator

2025-04-07 Thread Hung Ta
Hi Justin, > All contributors were employed by OpenClovis, which means the company paid > > them for their code, so the Intellectual Property Rights in this case > must > > belong to the company. > > Looking at the contributors here [1], I see some are not part of the Open > Clovis organisation. H

Re: [DISCUSS] Accept SAFplus into the Apache Incubator

2025-04-07 Thread Hung Ta
Hi Justin and PJ, All contributors were employed by OpenClovis, which means the company paid them for their code, so the Intellectual Property Rights in this case must belong to the company. Therefore, the company has full copyrights for the product, in contrast, the contributors have no any copyr

Re: [DISCUSS] Accept SAFplus into the Apache Incubator

2025-04-07 Thread Hung Ta
Hi Justin, > > > I, on behalf of the contributors, confirmed that we agree to the license > change. > > We need a bit more than that. Can we see where all of the contribitors > have agreed to this? > > As a first step, can you supply a list of all contributors and whether > they were employed by

Re: [DISCUSS] Accept SAFplus into the Apache Incubator

2025-04-06 Thread Justin Mclean
HI, > I, on behalf of the contributors, confirmed that we agree to the license > change. We need a bit more than that. Can we see where all of the contribitors have agreed to this? As a first step, can you supply a list of all contributors and whether they were employed by OpenClovis? As PJ

Re: [DISCUSS] Accept SAFplus into the Apache Incubator

2025-04-05 Thread Hung Ta
Hi PJ, I, on behalf of the contributors, confirmed that we agree to the license change. Thanks. On Sat, Apr 5, 2025, 8:05 PM PJ Fanning wrote: > Hi Hung, > Could you clarify the position regarding changing the license? This > will require that previous code contributors will need to agree to

Re: [DISCUSS] Accept SAFplus into the Apache Incubator

2025-04-05 Thread PJ Fanning
Hi Hung, Could you clarify the position regarding changing the license? This will require that previous code contributors will need to agree to the license change. If they have signed CLAs with OpenClovis or have/had employment contracts with OpenClovis, then those people can be assumed to have giv

Re: [DISCUSS] Accept SAFplus into the Apache Incubator

2025-04-04 Thread Hung Ta
Hi Paul, The issues were tracked through http://cloviszilla.openclovis.com but when migrating data to the new cloud server, there are some issues not resolved yet, so it cannot be opened now. We'll fix it. And another tracking place is github, of course. Besides that, many customers reported iss

Re: [DISCUSS] Accept SAFplus into the Apache Incubator

2025-04-04 Thread Paul King
The other worrying thing is that there has been no blogs, issues, PRs in the project for 8+ years. On Sat, Apr 5, 2025 at 4:29 AM Dave Fisher wrote: > > A major concern is that the codebase is currently GPL-2.0 licensed. > Converting all of the OpenClovis included code will be needed and some >

Re: [DISCUSS] Accept SAFplus into the Apache Incubator

2025-04-04 Thread Dave Fisher
A major concern is that the codebase is currently GPL-2.0 licensed. Converting all of the OpenClovis included code will be needed and some clarity if all of the contributors have allowed OpenClovis to modify the license for their contributions. Best, Dave > On Apr 4, 2025, at 10:47 AM, PJ Fann

[DISCUSS] Accept SAFplus into the Apache Incubator

2025-04-04 Thread PJ Fanning
Hi everyone, I'd like to formally begin the discussion about accepting SAFplus into the Apache Incubator. The proposal is: https://cwiki.apache.org/confluence/display/INCUBATOR/SAFplusProposal Related Thread: https://lists.apache.org/thread/hn87t6gtqh5cp3nx269okghzf0ty0x3z One of the main issues