subject:"Re\: Looking for a Champion"

Dear Calvin

Thank you for the update. I have adjusted the proposal accordingly.

---
Best Regards,
Mohammad Sadoghi, PhD
Associate Professor
Exploratory Systems Lab (ExpoLab)
Department of Computer Science
University of California, Davis

ExpoLab: https://expolab.org/
ResilientDB: https://resilientdb.com/
Phone: 914-319-7937


*Statements by UC Davis:* Chancellor Gary S. May
,
Dean Corsi (College of Engineering)

, Middle East/South Asia Studies


*Personal Statement:* We stand in solidarity with the brave and determined
Iranian women and Iranian people. We are committed to upholding fundamental
human rights, maintaining equity and justice, and standing against the use
of violence, repression, and discrimination. We condemn the barbaric acts
and brutal killings in Iranian streets, of innocent people in Ukraine, and
everywhere globally.


On Fri, Aug 18, 2023 at 8:46 AM Calvin Kirs  wrote:

> On Fri, Aug 18, 2023 at 11:39 PM Calvin Kirs  wrote:
> >
> > Hi,
> >
> > Thanks for your update,
> > I checked, Anh (id: dinhtta) is not yet IPMC, so he cannot be a mentor
> > yet, but can help as an informal mentor.
> David Lyle is also not a member of IPMC
> >
> > On Fri, Aug 18, 2023 at 10:34 PM Mo Sadoghi 
> wrote:
> > >
> > > Dear all,
> > >
> > > Thank you all for the clarification.
> > >
> > > Atri, thank you very much for championing the project.
> > >
> > > I have updated the proposal accordingly.
> > >
> > > Looking forward to the next steps.
> > >
> > > ---
> > > Best Regards,
> > > Mohammad Sadoghi, PhD
> > > Associate Professor
> > > Exploratory Systems Lab (ExpoLab)
> > > Department of Computer Science
> > > University of California, Davis
> > >
> > > ExpoLab: https://expolab.org/
> > > ResilientDB: https://resilientdb.com/
> > > Phone: 914-319-7937
> > >
> > >
> > > *Statements by UC Davis:* Chancellor Gary S. May
> > > <
> https://www.ucdavis.edu/news/statement-resources-and-support-impacted-unrest-iran
> >,
> > > Dean Corsi (College of Engineering)
> > > <
> https://engineering.ucdavis.edu/news/statement-resources-and-support-those-impacted-unrest-iran
> >
> > > , Middle East/South Asia Studies
> > > <
> https://mesa.ucdavis.edu/public-statements/state-violence-against-student-protesters-iran
> >
> > >
> > > *Personal Statement:* We stand in solidarity with the brave and
> determined
> > > Iranian women and Iranian people. We are committed to upholding
> fundamental
> > > human rights, maintaining equity and justice, and standing against the
> use
> > > of violence, repression, and discrimination. We condemn the barbaric
> acts
> > > and brutal killings in Iranian streets, of innocent people in Ukraine,
> and
> > > everywhere globally.
> > >
> > >
> > > On Fri, Aug 18, 2023 at 4:33 AM Atri Sharma  wrote:
> > >
> > > > I am happy to be the champion
> > > >
> > > > On Fri, 18 Aug 2023 at 1:14 PM, Mo Sadoghi 
> wrote:
> > > >
> > > > > Dear Kevin,
> > > > >
> > > > > It would be wonderful to have you as a mentor.  Thank you so much
> for
> > > > your
> > > > > kind support.
> > > > >
> > > > > Would you be open to serving as Champion, too?
> > > > >
> > > > > Greatly appreciated.
> > > > >
> > > > > ---
> > > > > Best Regards,
> > > > > Mohammad Sadoghi, PhD
> > > > > Associate Professor
> > > > > Exploratory Systems Lab (ExpoLab)
> > > > > Department of Computer Science
> > > > > University of California, Davis
> > > > >
> > > > > ExpoLab: https://expolab.org/
> > > > > ResilientDB: https://resilientdb.com/
> > > > > Phone: 914-319-7937
> > > > >
> > > > >
> > > > > *Statements by UC Davis:* Chancellor Gary S. May
> > > > > <
> > > > >
> > > >
> https://www.ucdavis.edu/news/statement-resources-and-support-impacted-unrest-iran
> > > > > >,
> > > > > Dean Corsi (College of Engineering)
> > > > > <
> > > > >
> > > >
> https://engineering.ucdavis.edu/news/statement-resources-and-support-those-impacted-unrest-iran
> > > > > >
> > > > > , Middle East/South Asia Studies
> > > > > <
> > > > >
> > > >
> https://mesa.ucdavis.edu/public-statements/state-violence-against-student-protesters-iran
> > > > > >
> > > > >
> > > > > *Personal Statement:* We stand in solidarity with the brave and
> > > > determined
> > > > > Iranian women and Iranian people. We are committed to upholding
> > > > fundamental
> > > > > human rights, maintaining equity and justice, and standing against
> the
> > > > use
> > > > > of violence, repression, and discrimination. We condemn the
> barbaric acts
> > > > > and brutal killings in Iranian streets, of innocent people in
> Ukraine,
> > > > and
> > > > > everywhere globally.
> > > > >
> > > > >
> > > > > On Thu, Aug 17, 2023 at 11:56 PM Kevin Ratnasekera <
> > > > > djkevincr1...@gmail.com>
> > > > > wrote:
> > > > >
> > >

Re: Looking for a Champion / Mentors for ResilientDB Blockchain Platform

2023-08-18 Thread Calvin Kirs

On Fri, Aug 18, 2023 at 11:39 PM Calvin Kirs  wrote:
>
> Hi,
>
> Thanks for your update,
> I checked, Anh (id: dinhtta) is not yet IPMC, so he cannot be a mentor
> yet, but can help as an informal mentor.
David Lyle is also not a member of IPMC
>
> On Fri, Aug 18, 2023 at 10:34 PM Mo Sadoghi  wrote:
> >
> > Dear all,
> >
> > Thank you all for the clarification.
> >
> > Atri, thank you very much for championing the project.
> >
> > I have updated the proposal accordingly.
> >
> > Looking forward to the next steps.
> >
> > ---
> > Best Regards,
> > Mohammad Sadoghi, PhD
> > Associate Professor
> > Exploratory Systems Lab (ExpoLab)
> > Department of Computer Science
> > University of California, Davis
> >
> > ExpoLab: https://expolab.org/
> > ResilientDB: https://resilientdb.com/
> > Phone: 914-319-7937
> >
> >
> > *Statements by UC Davis:* Chancellor Gary S. May
> > ,
> > Dean Corsi (College of Engineering)
> > 
> > , Middle East/South Asia Studies
> > 
> >
> > *Personal Statement:* We stand in solidarity with the brave and determined
> > Iranian women and Iranian people. We are committed to upholding fundamental
> > human rights, maintaining equity and justice, and standing against the use
> > of violence, repression, and discrimination. We condemn the barbaric acts
> > and brutal killings in Iranian streets, of innocent people in Ukraine, and
> > everywhere globally.
> >
> >
> > On Fri, Aug 18, 2023 at 4:33 AM Atri Sharma  wrote:
> >
> > > I am happy to be the champion
> > >
> > > On Fri, 18 Aug 2023 at 1:14 PM, Mo Sadoghi  wrote:
> > >
> > > > Dear Kevin,
> > > >
> > > > It would be wonderful to have you as a mentor.  Thank you so much for
> > > your
> > > > kind support.
> > > >
> > > > Would you be open to serving as Champion, too?
> > > >
> > > > Greatly appreciated.
> > > >
> > > > ---
> > > > Best Regards,
> > > > Mohammad Sadoghi, PhD
> > > > Associate Professor
> > > > Exploratory Systems Lab (ExpoLab)
> > > > Department of Computer Science
> > > > University of California, Davis
> > > >
> > > > ExpoLab: https://expolab.org/
> > > > ResilientDB: https://resilientdb.com/
> > > > Phone: 914-319-7937
> > > >
> > > >
> > > > *Statements by UC Davis:* Chancellor Gary S. May
> > > > <
> > > >
> > > https://www.ucdavis.edu/news/statement-resources-and-support-impacted-unrest-iran
> > > > >,
> > > > Dean Corsi (College of Engineering)
> > > > <
> > > >
> > > https://engineering.ucdavis.edu/news/statement-resources-and-support-those-impacted-unrest-iran
> > > > >
> > > > , Middle East/South Asia Studies
> > > > <
> > > >
> > > https://mesa.ucdavis.edu/public-statements/state-violence-against-student-protesters-iran
> > > > >
> > > >
> > > > *Personal Statement:* We stand in solidarity with the brave and
> > > determined
> > > > Iranian women and Iranian people. We are committed to upholding
> > > fundamental
> > > > human rights, maintaining equity and justice, and standing against the
> > > use
> > > > of violence, repression, and discrimination. We condemn the barbaric 
> > > > acts
> > > > and brutal killings in Iranian streets, of innocent people in Ukraine,
> > > and
> > > > everywhere globally.
> > > >
> > > >
> > > > On Thu, Aug 17, 2023 at 11:56 PM Kevin Ratnasekera <
> > > > djkevincr1...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > This project looks very interesting, I am happy to help as a mentor in
> > > > the
> > > > > incubation process.
> > > > >
> > > > > Regards
> > > > > Kevin
> > > > >
> > > > > On Fri, Aug 18, 2023 at 7:05 AM Atri Sharma  wrote:
> > > > >
> > > > > > Please count me in as a mentor
> > > > > >
> > > > > > On Fri, 18 Aug 2023 at 9:45 AM, Mo Sadoghi 
> > > > > wrote:
> > > > > >
> > > > > > > Dear Calvin,
> > > > > > >
> > > > > > > Thank you so much for your kind support.
> > > > > > >
> > > > > > > It would be great to have you as a mentor. Would you be open to
> > > > serving
> > > > > > as
> > > > > > > Champion, too, given your extensive experience?
> > > > > > >
> > > > > > > Greatly appreciated.
> > > > > > >
> > > > > > > ---
> > > > > > > Best Regards,
> > > > > > > Mohammad Sadoghi, PhD
> > > > > > > Associate Professor
> > > > > > > Exploratory Systems Lab (ExpoLab)
> > > > > > > Department of Computer Science
> > > > > > > University of California, Davis
> > > > > > >
> > > > > > > ExpoLab: https://expolab.org/
> > > > > > > ResilientDB: https://resilientdb.com/
> > > > > > > Phone: 914-319-7937
> > > > > > >
> > > > > > >
> > > > > > > *Statements by UC Davis:* Chancellor Gary S. May
> > > > > > > <
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > https://www.ucdavis.edu/news/statement-resources-and-support-impacted-unrest-iran
> > > > > > > >,
> > > > > > > Dean Corsi

Re: Looking for a Champion / Mentors for ResilientDB Blockchain Platform

2023-08-18 Thread Calvin Kirs

Hi,

Thanks for your update,
I checked, Anh (id: dinhtta) is not yet IPMC, so he cannot be a mentor
yet, but can help as an informal mentor.

On Fri, Aug 18, 2023 at 10:34 PM Mo Sadoghi  wrote:
>
> Dear all,
>
> Thank you all for the clarification.
>
> Atri, thank you very much for championing the project.
>
> I have updated the proposal accordingly.
>
> Looking forward to the next steps.
>
> ---
> Best Regards,
> Mohammad Sadoghi, PhD
> Associate Professor
> Exploratory Systems Lab (ExpoLab)
> Department of Computer Science
> University of California, Davis
>
> ExpoLab: https://expolab.org/
> ResilientDB: https://resilientdb.com/
> Phone: 914-319-7937
>
>
> *Statements by UC Davis:* Chancellor Gary S. May
> ,
> Dean Corsi (College of Engineering)
> 
> , Middle East/South Asia Studies
> 
>
> *Personal Statement:* We stand in solidarity with the brave and determined
> Iranian women and Iranian people. We are committed to upholding fundamental
> human rights, maintaining equity and justice, and standing against the use
> of violence, repression, and discrimination. We condemn the barbaric acts
> and brutal killings in Iranian streets, of innocent people in Ukraine, and
> everywhere globally.
>
>
> On Fri, Aug 18, 2023 at 4:33 AM Atri Sharma  wrote:
>
> > I am happy to be the champion
> >
> > On Fri, 18 Aug 2023 at 1:14 PM, Mo Sadoghi  wrote:
> >
> > > Dear Kevin,
> > >
> > > It would be wonderful to have you as a mentor.  Thank you so much for
> > your
> > > kind support.
> > >
> > > Would you be open to serving as Champion, too?
> > >
> > > Greatly appreciated.
> > >
> > > ---
> > > Best Regards,
> > > Mohammad Sadoghi, PhD
> > > Associate Professor
> > > Exploratory Systems Lab (ExpoLab)
> > > Department of Computer Science
> > > University of California, Davis
> > >
> > > ExpoLab: https://expolab.org/
> > > ResilientDB: https://resilientdb.com/
> > > Phone: 914-319-7937
> > >
> > >
> > > *Statements by UC Davis:* Chancellor Gary S. May
> > > <
> > >
> > https://www.ucdavis.edu/news/statement-resources-and-support-impacted-unrest-iran
> > > >,
> > > Dean Corsi (College of Engineering)
> > > <
> > >
> > https://engineering.ucdavis.edu/news/statement-resources-and-support-those-impacted-unrest-iran
> > > >
> > > , Middle East/South Asia Studies
> > > <
> > >
> > https://mesa.ucdavis.edu/public-statements/state-violence-against-student-protesters-iran
> > > >
> > >
> > > *Personal Statement:* We stand in solidarity with the brave and
> > determined
> > > Iranian women and Iranian people. We are committed to upholding
> > fundamental
> > > human rights, maintaining equity and justice, and standing against the
> > use
> > > of violence, repression, and discrimination. We condemn the barbaric acts
> > > and brutal killings in Iranian streets, of innocent people in Ukraine,
> > and
> > > everywhere globally.
> > >
> > >
> > > On Thu, Aug 17, 2023 at 11:56 PM Kevin Ratnasekera <
> > > djkevincr1...@gmail.com>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > This project looks very interesting, I am happy to help as a mentor in
> > > the
> > > > incubation process.
> > > >
> > > > Regards
> > > > Kevin
> > > >
> > > > On Fri, Aug 18, 2023 at 7:05 AM Atri Sharma  wrote:
> > > >
> > > > > Please count me in as a mentor
> > > > >
> > > > > On Fri, 18 Aug 2023 at 9:45 AM, Mo Sadoghi 
> > > > wrote:
> > > > >
> > > > > > Dear Calvin,
> > > > > >
> > > > > > Thank you so much for your kind support.
> > > > > >
> > > > > > It would be great to have you as a mentor. Would you be open to
> > > serving
> > > > > as
> > > > > > Champion, too, given your extensive experience?
> > > > > >
> > > > > > Greatly appreciated.
> > > > > >
> > > > > > ---
> > > > > > Best Regards,
> > > > > > Mohammad Sadoghi, PhD
> > > > > > Associate Professor
> > > > > > Exploratory Systems Lab (ExpoLab)
> > > > > > Department of Computer Science
> > > > > > University of California, Davis
> > > > > >
> > > > > > ExpoLab: https://expolab.org/
> > > > > > ResilientDB: https://resilientdb.com/
> > > > > > Phone: 914-319-7937
> > > > > >
> > > > > >
> > > > > > *Statements by UC Davis:* Chancellor Gary S. May
> > > > > > <
> > > > > >
> > > > >
> > > >
> > >
> > https://www.ucdavis.edu/news/statement-resources-and-support-impacted-unrest-iran
> > > > > > >,
> > > > > > Dean Corsi (College of Engineering)
> > > > > > <
> > > > > >
> > > > >
> > > >
> > >
> > https://engineering.ucdavis.edu/news/statement-resources-and-support-those-impacted-unrest-iran
> > > > > > >
> > > > > > , Middle East/South Asia Studies
> > > > > > <
> > > > > >
> > > > >
> > > >
> > >
> > https://mesa.ucdavis.edu/public-statements/state-violence-against-student-protesters-iran
> > > > > > >
> > > > > >
> > > > >

Re: Looking for a Champion / Mentors for ResilientDB Blockchain Platform

Dear all,

Thank you all for the clarification.

Atri, thank you very much for championing the project.

I have updated the proposal accordingly.

Looking forward to the next steps.

---
Best Regards,
Mohammad Sadoghi, PhD
Associate Professor
Exploratory Systems Lab (ExpoLab)
Department of Computer Science
University of California, Davis

ExpoLab: https://expolab.org/
ResilientDB: https://resilientdb.com/
Phone: 914-319-7937


*Statements by UC Davis:* Chancellor Gary S. May
,
Dean Corsi (College of Engineering)

, Middle East/South Asia Studies


*Personal Statement:* We stand in solidarity with the brave and determined
Iranian women and Iranian people. We are committed to upholding fundamental
human rights, maintaining equity and justice, and standing against the use
of violence, repression, and discrimination. We condemn the barbaric acts
and brutal killings in Iranian streets, of innocent people in Ukraine, and
everywhere globally.


On Fri, Aug 18, 2023 at 4:33 AM Atri Sharma  wrote:

> I am happy to be the champion
>
> On Fri, 18 Aug 2023 at 1:14 PM, Mo Sadoghi  wrote:
>
> > Dear Kevin,
> >
> > It would be wonderful to have you as a mentor.  Thank you so much for
> your
> > kind support.
> >
> > Would you be open to serving as Champion, too?
> >
> > Greatly appreciated.
> >
> > ---
> > Best Regards,
> > Mohammad Sadoghi, PhD
> > Associate Professor
> > Exploratory Systems Lab (ExpoLab)
> > Department of Computer Science
> > University of California, Davis
> >
> > ExpoLab: https://expolab.org/
> > ResilientDB: https://resilientdb.com/
> > Phone: 914-319-7937
> >
> >
> > *Statements by UC Davis:* Chancellor Gary S. May
> > <
> >
> https://www.ucdavis.edu/news/statement-resources-and-support-impacted-unrest-iran
> > >,
> > Dean Corsi (College of Engineering)
> > <
> >
> https://engineering.ucdavis.edu/news/statement-resources-and-support-those-impacted-unrest-iran
> > >
> > , Middle East/South Asia Studies
> > <
> >
> https://mesa.ucdavis.edu/public-statements/state-violence-against-student-protesters-iran
> > >
> >
> > *Personal Statement:* We stand in solidarity with the brave and
> determined
> > Iranian women and Iranian people. We are committed to upholding
> fundamental
> > human rights, maintaining equity and justice, and standing against the
> use
> > of violence, repression, and discrimination. We condemn the barbaric acts
> > and brutal killings in Iranian streets, of innocent people in Ukraine,
> and
> > everywhere globally.
> >
> >
> > On Thu, Aug 17, 2023 at 11:56 PM Kevin Ratnasekera <
> > djkevincr1...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > This project looks very interesting, I am happy to help as a mentor in
> > the
> > > incubation process.
> > >
> > > Regards
> > > Kevin
> > >
> > > On Fri, Aug 18, 2023 at 7:05 AM Atri Sharma  wrote:
> > >
> > > > Please count me in as a mentor
> > > >
> > > > On Fri, 18 Aug 2023 at 9:45 AM, Mo Sadoghi 
> > > wrote:
> > > >
> > > > > Dear Calvin,
> > > > >
> > > > > Thank you so much for your kind support.
> > > > >
> > > > > It would be great to have you as a mentor. Would you be open to
> > serving
> > > > as
> > > > > Champion, too, given your extensive experience?
> > > > >
> > > > > Greatly appreciated.
> > > > >
> > > > > ---
> > > > > Best Regards,
> > > > > Mohammad Sadoghi, PhD
> > > > > Associate Professor
> > > > > Exploratory Systems Lab (ExpoLab)
> > > > > Department of Computer Science
> > > > > University of California, Davis
> > > > >
> > > > > ExpoLab: https://expolab.org/
> > > > > ResilientDB: https://resilientdb.com/
> > > > > Phone: 914-319-7937
> > > > >
> > > > >
> > > > > *Statements by UC Davis:* Chancellor Gary S. May
> > > > > <
> > > > >
> > > >
> > >
> >
> https://www.ucdavis.edu/news/statement-resources-and-support-impacted-unrest-iran
> > > > > >,
> > > > > Dean Corsi (College of Engineering)
> > > > > <
> > > > >
> > > >
> > >
> >
> https://engineering.ucdavis.edu/news/statement-resources-and-support-those-impacted-unrest-iran
> > > > > >
> > > > > , Middle East/South Asia Studies
> > > > > <
> > > > >
> > > >
> > >
> >
> https://mesa.ucdavis.edu/public-statements/state-violence-against-student-protesters-iran
> > > > > >
> > > > >
> > > > > *Personal Statement:* We stand in solidarity with the brave and
> > > > determined
> > > > > Iranian women and Iranian people. We are committed to upholding
> > > > fundamental
> > > > > human rights, maintaining equity and justice, and standing against
> > the
> > > > use
> > > > > of violence, repression, and discrimination. We condemn the
> barbaric
> > > acts
> > > > > and brutal killings in Iranian streets, of innocent people in
> > Ukraine,
> > > > and
> > > > > everywhere globally.
> > > > >
> > > >

Re: Looking for a Champion / Mentors for ResilientDB Blockchain Platform

2023-08-18 Thread Atri Sharma

I am happy to be the champion

On Fri, 18 Aug 2023 at 1:14 PM, Mo Sadoghi  wrote:

> Dear Kevin,
>
> It would be wonderful to have you as a mentor.  Thank you so much for your
> kind support.
>
> Would you be open to serving as Champion, too?
>
> Greatly appreciated.
>
> ---
> Best Regards,
> Mohammad Sadoghi, PhD
> Associate Professor
> Exploratory Systems Lab (ExpoLab)
> Department of Computer Science
> University of California, Davis
>
> ExpoLab: https://expolab.org/
> ResilientDB: https://resilientdb.com/
> Phone: 914-319-7937
>
>
> *Statements by UC Davis:* Chancellor Gary S. May
> <
> https://www.ucdavis.edu/news/statement-resources-and-support-impacted-unrest-iran
> >,
> Dean Corsi (College of Engineering)
> <
> https://engineering.ucdavis.edu/news/statement-resources-and-support-those-impacted-unrest-iran
> >
> , Middle East/South Asia Studies
> <
> https://mesa.ucdavis.edu/public-statements/state-violence-against-student-protesters-iran
> >
>
> *Personal Statement:* We stand in solidarity with the brave and determined
> Iranian women and Iranian people. We are committed to upholding fundamental
> human rights, maintaining equity and justice, and standing against the use
> of violence, repression, and discrimination. We condemn the barbaric acts
> and brutal killings in Iranian streets, of innocent people in Ukraine, and
> everywhere globally.
>
>
> On Thu, Aug 17, 2023 at 11:56 PM Kevin Ratnasekera <
> djkevincr1...@gmail.com>
> wrote:
>
> > Hi,
> >
> > This project looks very interesting, I am happy to help as a mentor in
> the
> > incubation process.
> >
> > Regards
> > Kevin
> >
> > On Fri, Aug 18, 2023 at 7:05 AM Atri Sharma  wrote:
> >
> > > Please count me in as a mentor
> > >
> > > On Fri, 18 Aug 2023 at 9:45 AM, Mo Sadoghi 
> > wrote:
> > >
> > > > Dear Calvin,
> > > >
> > > > Thank you so much for your kind support.
> > > >
> > > > It would be great to have you as a mentor. Would you be open to
> serving
> > > as
> > > > Champion, too, given your extensive experience?
> > > >
> > > > Greatly appreciated.
> > > >
> > > > ---
> > > > Best Regards,
> > > > Mohammad Sadoghi, PhD
> > > > Associate Professor
> > > > Exploratory Systems Lab (ExpoLab)
> > > > Department of Computer Science
> > > > University of California, Davis
> > > >
> > > > ExpoLab: https://expolab.org/
> > > > ResilientDB: https://resilientdb.com/
> > > > Phone: 914-319-7937
> > > >
> > > >
> > > > *Statements by UC Davis:* Chancellor Gary S. May
> > > > <
> > > >
> > >
> >
> https://www.ucdavis.edu/news/statement-resources-and-support-impacted-unrest-iran
> > > > >,
> > > > Dean Corsi (College of Engineering)
> > > > <
> > > >
> > >
> >
> https://engineering.ucdavis.edu/news/statement-resources-and-support-those-impacted-unrest-iran
> > > > >
> > > > , Middle East/South Asia Studies
> > > > <
> > > >
> > >
> >
> https://mesa.ucdavis.edu/public-statements/state-violence-against-student-protesters-iran
> > > > >
> > > >
> > > > *Personal Statement:* We stand in solidarity with the brave and
> > > determined
> > > > Iranian women and Iranian people. We are committed to upholding
> > > fundamental
> > > > human rights, maintaining equity and justice, and standing against
> the
> > > use
> > > > of violence, repression, and discrimination. We condemn the barbaric
> > acts
> > > > and brutal killings in Iranian streets, of innocent people in
> Ukraine,
> > > and
> > > > everywhere globally.
> > > >
> > > >
> > > > On Thu, Aug 17, 2023 at 7:15 PM Calvin Kirs  wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > >Please count me in, I'm interested in this project and I am
> happy
> > > > > to help as a mentor.
> > > > >
> > > > > I have been involved in the incubation process of several projects
> > and
> > > > > have experience with this.
> > > > >
> > > > > On Fri, Aug 18, 2023 at 9:40 AM 俊平堵  wrote:
> > > > > >
> > > > > > Hi,
> > > > > > The project looks interesting to me and I am happy to help as
> > > > mentor.
> > > > > >  BTW, I am PMC of hadoop, Ozone, and mentor Yunikorn,
> Evenmesh,
> > > > > Linkis,
> > > > > > etc. towards Apache TLP.
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > JP
> > > > > >
> > > > > > Mo Sadoghi  于2023年8月18日周五 05:55写道：
> > > > > >
> > > > > > > Dear Apache Members,
> > > > > > >
> > > > > > > Hope you are safe and well.
> > > > > > >
> > > > > > > Over the past 6 years, we have been developing a distributed
> > > > blockchain
> > > > > > > framework, called ResilientDB ,
> which
> > > has
> > > > > been
> > > > > > > open-sourced 
> since
> > > > 2019.
> > > > > > > ResilientDB is a lightweight and highly performant framework
> > > (written
> > > > > in
> > > > > > > C++) that has been extensively evaluated and refined resulting
> in
> > > > over
> > > > > 20
> > > > > > > publications and 2 books. It allows for easy integration with
> > > various
> > > > > > > Byzantine Fault-Tolerant (BFT) and Crash

Re: Looking for a Champion / Mentors for ResilientDB Blockchain Platform

2023-08-18 Thread Daniel Gruno

On 2023-08-18 09:54, Calvin Kirs wrote:

Hi Mohammad,

We usually just need one champion, I see David expressing interest and
I think he is a good champion.

David would not be admissible as a champion, as that requires a person
to be either a foundation member or officer. See
https://incubator.apache.org/guides/roles_and_responsibilities.html#Champion
for details.

On Fri, Aug 18, 2023 at 12:15 PM Mo Sadoghi wrote:

Dear Calvin,

Thank you so much for your kind support.

It would be great to have you as a mentor. Would you be open to serving as
Champion, too, given your extensive experience?

Greatly appreciated.

---
Best Regards,
Mohammad Sadoghi, PhD
Associate Professor
Exploratory Systems Lab (ExpoLab)
Department of Computer Science
University of California, Davis

ExpoLab: https://expolab.org/
ResilientDB: https://resilientdb.com/
Phone: 914-319-7937

Statements by UC Davis: Chancellor Gary S. May, Dean Corsi (College of
Engineering), Middle East/South Asia Studies

Personal Statement: We stand in solidarity with the brave and determined
Iranian women and Iranian people. We are committed to upholding fundamental
human rights, maintaining equity and justice, and standing against the use of
violence, repression, and discrimination. We condemn the barbaric acts and
brutal killings in Iranian streets, of innocent people in Ukraine, and
everywhere globally.

On Thu, Aug 17, 2023 at 7:15 PM Calvin Kirs wrote:

Hi,

Please count me in, I'm interested in this project and I am happy
to help as a mentor.

I have been involved in the incubation process of several projects and
have experience with this.

On Fri, Aug 18, 2023 at 9:40 AM 俊平堵 wrote:

Hi,
The project looks interesting to me and I am happy to help as mentor.
BTW, I am PMC of hadoop, Ozone, and mentor Yunikorn, Evenmesh, Linkis,
etc. towards Apache TLP.

Thanks,

Mo Sadoghi 于2023年8月18日周五 05:55写道：

Dear Apache Members,

Hope you are safe and well.

Over the past 6 years, we have been developing a distributed blockchain
framework, called ResilientDB , which has been
open-sourced since 2019.
ResilientDB is a lightweight and highly performant framework (written in
C++) that has been extensively evaluated and refined resulting in over 20
publications and 2 books. It allows for easy integration with various
Byzantine Fault-Tolerant (BFT) and Crash Fault-Tolerant (CFT) consensus
protocols. ResilientDB has been a key educational tool, thus far, 1
postdoc, 3 Ph.D., and 13 MSc students have graduated while working on it.
Furthermore, it has been used in the classroom for the past 5 years with
several hundred students utilizing it for their course projects. The
current core team of ResilientDB consists of 1 Postdoc, 2 PhD, 8 MSc, and 6
BSc. In addition to academic success, it has been utilized by our industry
partners (e.g., Radix Ltd and Mysten Labs
) for analysis and as an industrial-strength
framework to implement their consensus protocols. The broader team of
active contributors currently included UCB, UCI, UPenn, and McMaster U.

Our ResilientDB platform has now reached a stable point in its product
life-cycle, and we believe it is now an excellent candidate to be
considered for the Apache Incubation program to further expand its reach
and development by building a larger community and ecosystem around it.
Furthermore, considering the thriving field of blockchain / distributed
ledger, Apache does not have any core blockchain software in its portfolio.

We are looking for champions and mentors for our project. Your kind support
is greatly appreciated. We look forward to growing and expanding our
product as part of the Apache community.

Here is the live / latest draft of the proposal.

https://docs.google.com/document/d/12WPvs1A7tqH8VjkMrgXTGQ_z4fiL6f6oi32e7bxSjXc/edit?usp=sharing

Currently, we have *Anh Dinh*, Apache SINGA’s PMC, as our Apache mentor
(cc'ed).

---
Best Regards,
Mohammad Sadoghi, PhD
Associate Professor
Exploratory Systems Lab (ExpoLab)
Department of Computer Science
University of California, Davis

ExpoLab: https://expolab.org/
ResilientDB: https://resilientdb.com/
Phone: 914-319-7937

--
Best wishes！
CalvinKirs

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Looking for a Champion / Mentors for ResilientDB Blockchain Platform

2023-08-18 Thread Calvin Kirs

Hi Mohammad,

We usually just need one champion, I see David expressing interest and
I think he is a good champion.

On Fri, Aug 18, 2023 at 12:15 PM Mo Sadoghi  wrote:
>
> Dear Calvin,
>
> Thank you so much for your kind support.
>
> It would be great to have you as a mentor. Would you be open to serving as 
> Champion, too, given your extensive experience?
>
> Greatly appreciated.
>
> ---
> Best Regards,
> Mohammad Sadoghi, PhD
> Associate Professor
> Exploratory Systems Lab (ExpoLab)
> Department of Computer Science
> University of California, Davis
>
> ExpoLab: https://expolab.org/
> ResilientDB: https://resilientdb.com/
> Phone: 914-319-7937
>
>
> Statements by UC Davis: Chancellor Gary S. May, Dean Corsi (College of 
> Engineering), Middle East/South Asia Studies
>
> Personal Statement: We stand in solidarity with the brave and determined 
> Iranian women and Iranian people. We are committed to upholding fundamental 
> human rights, maintaining equity and justice, and standing against the use of 
> violence, repression, and discrimination. We condemn the barbaric acts and 
> brutal killings in Iranian streets, of innocent people in Ukraine, and 
> everywhere globally.
>
>
> On Thu, Aug 17, 2023 at 7:15 PM Calvin Kirs  wrote:
>>
>> Hi,
>>
>>Please count me in, I'm interested in this project and I am happy
>> to help as a mentor.
>>
>> I have been involved in the incubation process of several projects and
>> have experience with this.
>>
>> On Fri, Aug 18, 2023 at 9:40 AM 俊平堵  wrote:
>> >
>> > Hi,
>> > The project looks interesting to me and I am happy to help as mentor.
>> >  BTW, I am PMC of hadoop, Ozone, and mentor Yunikorn, Evenmesh, Linkis,
>> > etc. towards Apache TLP.
>> >
>> > Thanks,
>> >
>> > JP
>> >
>> > Mo Sadoghi  于2023年8月18日周五 05:55写道：
>> >
>> > > Dear Apache Members,
>> > >
>> > > Hope you are safe and well.
>> > >
>> > > Over the past 6 years, we have been developing a distributed blockchain
>> > > framework, called ResilientDB , which has been
>> > > open-sourced  since 2019.
>> > > ResilientDB is a lightweight and highly performant framework (written in
>> > > C++) that has been extensively evaluated and refined resulting in over 20
>> > > publications and 2 books. It allows for easy integration with various
>> > > Byzantine Fault-Tolerant (BFT) and Crash Fault-Tolerant (CFT) consensus
>> > > protocols. ResilientDB has been a key educational tool, thus far, 1
>> > > postdoc, 3 Ph.D., and 13 MSc students have graduated while working on it.
>> > > Furthermore, it has been used in the classroom for the past 5 years with
>> > > several hundred students utilizing it for their course projects. The
>> > > current core team of ResilientDB consists of 1 Postdoc, 2 PhD, 8 MSc, 
>> > > and 6
>> > > BSc.  In addition to academic success, it has been utilized by our 
>> > > industry
>> > > partners (e.g., Radix Ltd  and Mysten Labs
>> > > ) for analysis and as an industrial-strength
>> > > framework to implement their consensus protocols. The broader team of
>> > > active contributors currently included UCB, UCI, UPenn, and McMaster U.
>> > >
>> > > Our ResilientDB platform has now reached a stable point in its product
>> > > life-cycle, and we believe it is now an excellent candidate to be
>> > > considered for the Apache Incubation program to further expand its reach
>> > > and development by building a larger community and ecosystem around it.
>> > > Furthermore, considering the thriving field of blockchain / distributed
>> > > ledger, Apache does not have any core blockchain software in its 
>> > > portfolio.
>> > >
>> > > We are looking for champions and mentors for our project. Your kind 
>> > > support
>> > > is greatly appreciated. We look forward to growing and expanding our
>> > > product as part of the Apache community.
>> > >
>> > > Here is the live / latest draft of the proposal.
>> > >
>> > > https://docs.google.com/document/d/12WPvs1A7tqH8VjkMrgXTGQ_z4fiL6f6oi32e7bxSjXc/edit?usp=sharing
>> > >
>> > > Currently, we have *Anh Dinh*, Apache SINGA’s PMC, as our Apache mentor
>> > > (cc'ed).
>> > >
>> > > ---
>> > > Best Regards,
>> > > Mohammad Sadoghi, PhD
>> > > Associate Professor
>> > > Exploratory Systems Lab (ExpoLab)
>> > > Department of Computer Science
>> > > University of California, Davis
>> > >
>> > > ExpoLab: https://expolab.org/
>> > > ResilientDB: https://resilientdb.com/
>> > > Phone: 914-319-7937
>> > >
>>
>>
>>
>> --
>> Best wishes！
>> CalvinKirs
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>


-- 
Best wishes！
CalvinKirs

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For

Re: Looking for a Champion / Mentors for ResilientDB Blockchain Platform

Dear Kevin,

It would be wonderful to have you as a mentor.  Thank you so much for your
kind support.

Would you be open to serving as Champion, too?

Greatly appreciated.

---
Best Regards,
Mohammad Sadoghi, PhD
Associate Professor
Exploratory Systems Lab (ExpoLab)
Department of Computer Science
University of California, Davis

ExpoLab: https://expolab.org/
ResilientDB: https://resilientdb.com/
Phone: 914-319-7937


*Statements by UC Davis:* Chancellor Gary S. May
,
Dean Corsi (College of Engineering)

, Middle East/South Asia Studies


*Personal Statement:* We stand in solidarity with the brave and determined
Iranian women and Iranian people. We are committed to upholding fundamental
human rights, maintaining equity and justice, and standing against the use
of violence, repression, and discrimination. We condemn the barbaric acts
and brutal killings in Iranian streets, of innocent people in Ukraine, and
everywhere globally.


On Thu, Aug 17, 2023 at 11:56 PM Kevin Ratnasekera 
wrote:

> Hi,
>
> This project looks very interesting, I am happy to help as a mentor in the
> incubation process.
>
> Regards
> Kevin
>
> On Fri, Aug 18, 2023 at 7:05 AM Atri Sharma  wrote:
>
> > Please count me in as a mentor
> >
> > On Fri, 18 Aug 2023 at 9:45 AM, Mo Sadoghi 
> wrote:
> >
> > > Dear Calvin,
> > >
> > > Thank you so much for your kind support.
> > >
> > > It would be great to have you as a mentor. Would you be open to serving
> > as
> > > Champion, too, given your extensive experience?
> > >
> > > Greatly appreciated.
> > >
> > > ---
> > > Best Regards,
> > > Mohammad Sadoghi, PhD
> > > Associate Professor
> > > Exploratory Systems Lab (ExpoLab)
> > > Department of Computer Science
> > > University of California, Davis
> > >
> > > ExpoLab: https://expolab.org/
> > > ResilientDB: https://resilientdb.com/
> > > Phone: 914-319-7937
> > >
> > >
> > > *Statements by UC Davis:* Chancellor Gary S. May
> > > <
> > >
> >
> https://www.ucdavis.edu/news/statement-resources-and-support-impacted-unrest-iran
> > > >,
> > > Dean Corsi (College of Engineering)
> > > <
> > >
> >
> https://engineering.ucdavis.edu/news/statement-resources-and-support-those-impacted-unrest-iran
> > > >
> > > , Middle East/South Asia Studies
> > > <
> > >
> >
> https://mesa.ucdavis.edu/public-statements/state-violence-against-student-protesters-iran
> > > >
> > >
> > > *Personal Statement:* We stand in solidarity with the brave and
> > determined
> > > Iranian women and Iranian people. We are committed to upholding
> > fundamental
> > > human rights, maintaining equity and justice, and standing against the
> > use
> > > of violence, repression, and discrimination. We condemn the barbaric
> acts
> > > and brutal killings in Iranian streets, of innocent people in Ukraine,
> > and
> > > everywhere globally.
> > >
> > >
> > > On Thu, Aug 17, 2023 at 7:15 PM Calvin Kirs  wrote:
> > >
> > > > Hi,
> > > >
> > > >Please count me in, I'm interested in this project and I am happy
> > > > to help as a mentor.
> > > >
> > > > I have been involved in the incubation process of several projects
> and
> > > > have experience with this.
> > > >
> > > > On Fri, Aug 18, 2023 at 9:40 AM 俊平堵  wrote:
> > > > >
> > > > > Hi,
> > > > > The project looks interesting to me and I am happy to help as
> > > mentor.
> > > > >  BTW, I am PMC of hadoop, Ozone, and mentor Yunikorn, Evenmesh,
> > > > Linkis,
> > > > > etc. towards Apache TLP.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > JP
> > > > >
> > > > > Mo Sadoghi  于2023年8月18日周五 05:55写道：
> > > > >
> > > > > > Dear Apache Members,
> > > > > >
> > > > > > Hope you are safe and well.
> > > > > >
> > > > > > Over the past 6 years, we have been developing a distributed
> > > blockchain
> > > > > > framework, called ResilientDB , which
> > has
> > > > been
> > > > > > open-sourced  since
> > > 2019.
> > > > > > ResilientDB is a lightweight and highly performant framework
> > (written
> > > > in
> > > > > > C++) that has been extensively evaluated and refined resulting in
> > > over
> > > > 20
> > > > > > publications and 2 books. It allows for easy integration with
> > various
> > > > > > Byzantine Fault-Tolerant (BFT) and Crash Fault-Tolerant (CFT)
> > > consensus
> > > > > > protocols. ResilientDB has been a key educational tool, thus
> far, 1
> > > > > > postdoc, 3 Ph.D., and 13 MSc students have graduated while
> working
> > on
> > > > it.
> > > > > > Furthermore, it has been used in the classroom for the past 5
> years
> > > > with
> > > > > > several hundred students utilizing it for their course projects.
> > The
> > > > > > current core team of ResilientDB consists of 1

Re: Looking for a Champion / Mentors for ResilientDB Blockchain Platform

Dear Atri,

Thank you so much for your kind support.

Thank you very much for your kind willingness to serve as a mentor. Greatly
appreciated.

Would you be open to serving as Champion, too?

---
Best Regards,
Mohammad Sadoghi, PhD
Associate Professor
Exploratory Systems Lab (ExpoLab)
Department of Computer Science
University of California, Davis

ExpoLab: https://expolab.org/
ResilientDB: https://resilientdb.com/
Phone: 914-319-7937


*Statements by UC Davis:* Chancellor Gary S. May
,
Dean Corsi (College of Engineering)

, Middle East/South Asia Studies


*Personal Statement:* We stand in solidarity with the brave and determined
Iranian women and Iranian people. We are committed to upholding fundamental
human rights, maintaining equity and justice, and standing against the use
of violence, repression, and discrimination. We condemn the barbaric acts
and brutal killings in Iranian streets, of innocent people in Ukraine, and
everywhere globally.


On Thu, Aug 17, 2023 at 10:05 PM Atri Sharma  wrote:

> Please count me in as a mentor
>
> On Fri, 18 Aug 2023 at 9:45 AM, Mo Sadoghi  wrote:
>
> > Dear Calvin,
> >
> > Thank you so much for your kind support.
> >
> > It would be great to have you as a mentor. Would you be open to serving
> as
> > Champion, too, given your extensive experience?
> >
> > Greatly appreciated.
> >
> > ---
> > Best Regards,
> > Mohammad Sadoghi, PhD
> > Associate Professor
> > Exploratory Systems Lab (ExpoLab)
> > Department of Computer Science
> > University of California, Davis
> >
> > ExpoLab: https://expolab.org/
> > ResilientDB: https://resilientdb.com/
> > Phone: 914-319-7937
> >
> >
> > *Statements by UC Davis:* Chancellor Gary S. May
> > <
> >
> https://www.ucdavis.edu/news/statement-resources-and-support-impacted-unrest-iran
> > >,
> > Dean Corsi (College of Engineering)
> > <
> >
> https://engineering.ucdavis.edu/news/statement-resources-and-support-those-impacted-unrest-iran
> > >
> > , Middle East/South Asia Studies
> > <
> >
> https://mesa.ucdavis.edu/public-statements/state-violence-against-student-protesters-iran
> > >
> >
> > *Personal Statement:* We stand in solidarity with the brave and
> determined
> > Iranian women and Iranian people. We are committed to upholding
> fundamental
> > human rights, maintaining equity and justice, and standing against the
> use
> > of violence, repression, and discrimination. We condemn the barbaric acts
> > and brutal killings in Iranian streets, of innocent people in Ukraine,
> and
> > everywhere globally.
> >
> >
> > On Thu, Aug 17, 2023 at 7:15 PM Calvin Kirs  wrote:
> >
> > > Hi,
> > >
> > >Please count me in, I'm interested in this project and I am happy
> > > to help as a mentor.
> > >
> > > I have been involved in the incubation process of several projects and
> > > have experience with this.
> > >
> > > On Fri, Aug 18, 2023 at 9:40 AM 俊平堵  wrote:
> > > >
> > > > Hi,
> > > > The project looks interesting to me and I am happy to help as
> > mentor.
> > > >  BTW, I am PMC of hadoop, Ozone, and mentor Yunikorn, Evenmesh,
> > > Linkis,
> > > > etc. towards Apache TLP.
> > > >
> > > > Thanks,
> > > >
> > > > JP
> > > >
> > > > Mo Sadoghi  于2023年8月18日周五 05:55写道：
> > > >
> > > > > Dear Apache Members,
> > > > >
> > > > > Hope you are safe and well.
> > > > >
> > > > > Over the past 6 years, we have been developing a distributed
> > blockchain
> > > > > framework, called ResilientDB , which
> has
> > > been
> > > > > open-sourced  since
> > 2019.
> > > > > ResilientDB is a lightweight and highly performant framework
> (written
> > > in
> > > > > C++) that has been extensively evaluated and refined resulting in
> > over
> > > 20
> > > > > publications and 2 books. It allows for easy integration with
> various
> > > > > Byzantine Fault-Tolerant (BFT) and Crash Fault-Tolerant (CFT)
> > consensus
> > > > > protocols. ResilientDB has been a key educational tool, thus far, 1
> > > > > postdoc, 3 Ph.D., and 13 MSc students have graduated while working
> on
> > > it.
> > > > > Furthermore, it has been used in the classroom for the past 5 years
> > > with
> > > > > several hundred students utilizing it for their course projects.
> The
> > > > > current core team of ResilientDB consists of 1 Postdoc, 2 PhD, 8
> MSc,
> > > and 6
> > > > > BSc.  In addition to academic success, it has been utilized by our
> > > industry
> > > > > partners (e.g., Radix Ltd  and Mysten
> > Labs
> > > > > ) for analysis and as an
> > industrial-strength
> > > > > framework to implement their consensus protocols. The broader team
> of
> > > > > active contributors

Re: Looking for a Champion / Mentors for ResilientDB Blockchain Platform

2023-08-18 Thread Kevin Ratnasekera

Hi,

This project looks very interesting, I am happy to help as a mentor in the
incubation process.

Regards
Kevin

On Fri, Aug 18, 2023 at 7:05 AM Atri Sharma  wrote:

> Please count me in as a mentor
>
> On Fri, 18 Aug 2023 at 9:45 AM, Mo Sadoghi  wrote:
>
> > Dear Calvin,
> >
> > Thank you so much for your kind support.
> >
> > It would be great to have you as a mentor. Would you be open to serving
> as
> > Champion, too, given your extensive experience?
> >
> > Greatly appreciated.
> >
> > ---
> > Best Regards,
> > Mohammad Sadoghi, PhD
> > Associate Professor
> > Exploratory Systems Lab (ExpoLab)
> > Department of Computer Science
> > University of California, Davis
> >
> > ExpoLab: https://expolab.org/
> > ResilientDB: https://resilientdb.com/
> > Phone: 914-319-7937
> >
> >
> > *Statements by UC Davis:* Chancellor Gary S. May
> > <
> >
> https://www.ucdavis.edu/news/statement-resources-and-support-impacted-unrest-iran
> > >,
> > Dean Corsi (College of Engineering)
> > <
> >
> https://engineering.ucdavis.edu/news/statement-resources-and-support-those-impacted-unrest-iran
> > >
> > , Middle East/South Asia Studies
> > <
> >
> https://mesa.ucdavis.edu/public-statements/state-violence-against-student-protesters-iran
> > >
> >
> > *Personal Statement:* We stand in solidarity with the brave and
> determined
> > Iranian women and Iranian people. We are committed to upholding
> fundamental
> > human rights, maintaining equity and justice, and standing against the
> use
> > of violence, repression, and discrimination. We condemn the barbaric acts
> > and brutal killings in Iranian streets, of innocent people in Ukraine,
> and
> > everywhere globally.
> >
> >
> > On Thu, Aug 17, 2023 at 7:15 PM Calvin Kirs  wrote:
> >
> > > Hi,
> > >
> > >Please count me in, I'm interested in this project and I am happy
> > > to help as a mentor.
> > >
> > > I have been involved in the incubation process of several projects and
> > > have experience with this.
> > >
> > > On Fri, Aug 18, 2023 at 9:40 AM 俊平堵  wrote:
> > > >
> > > > Hi,
> > > > The project looks interesting to me and I am happy to help as
> > mentor.
> > > >  BTW, I am PMC of hadoop, Ozone, and mentor Yunikorn, Evenmesh,
> > > Linkis,
> > > > etc. towards Apache TLP.
> > > >
> > > > Thanks,
> > > >
> > > > JP
> > > >
> > > > Mo Sadoghi  于2023年8月18日周五 05:55写道：
> > > >
> > > > > Dear Apache Members,
> > > > >
> > > > > Hope you are safe and well.
> > > > >
> > > > > Over the past 6 years, we have been developing a distributed
> > blockchain
> > > > > framework, called ResilientDB , which
> has
> > > been
> > > > > open-sourced  since
> > 2019.
> > > > > ResilientDB is a lightweight and highly performant framework
> (written
> > > in
> > > > > C++) that has been extensively evaluated and refined resulting in
> > over
> > > 20
> > > > > publications and 2 books. It allows for easy integration with
> various
> > > > > Byzantine Fault-Tolerant (BFT) and Crash Fault-Tolerant (CFT)
> > consensus
> > > > > protocols. ResilientDB has been a key educational tool, thus far, 1
> > > > > postdoc, 3 Ph.D., and 13 MSc students have graduated while working
> on
> > > it.
> > > > > Furthermore, it has been used in the classroom for the past 5 years
> > > with
> > > > > several hundred students utilizing it for their course projects.
> The
> > > > > current core team of ResilientDB consists of 1 Postdoc, 2 PhD, 8
> MSc,
> > > and 6
> > > > > BSc.  In addition to academic success, it has been utilized by our
> > > industry
> > > > > partners (e.g., Radix Ltd  and Mysten
> > Labs
> > > > > ) for analysis and as an
> > industrial-strength
> > > > > framework to implement their consensus protocols. The broader team
> of
> > > > > active contributors currently included UCB, UCI, UPenn, and
> McMaster
> > U.
> > > > >
> > > > > Our ResilientDB platform has now reached a stable point in its
> > product
> > > > > life-cycle, and we believe it is now an excellent candidate to be
> > > > > considered for the Apache Incubation program to further expand its
> > > reach
> > > > > and development by building a larger community and ecosystem around
> > it.
> > > > > Furthermore, considering the thriving field of blockchain /
> > distributed
> > > > > ledger, Apache does not have any core blockchain software in its
> > > portfolio.
> > > > >
> > > > > We are looking for champions and mentors for our project. Your kind
> > > support
> > > > > is greatly appreciated. We look forward to growing and expanding
> our
> > > > > product as part of the Apache community.
> > > > >
> > > > > Here is the live / latest draft of the proposal.
> > > > >
> > > > >
> > >
> >
> https://docs.google.com/document/d/12WPvs1A7tqH8VjkMrgXTGQ_z4fiL6f6oi32e7bxSjXc/edit?usp=sharing
> > > > >
> > > > > Currently, we have *Anh Dinh*, Apache SINGA’s PMC, as our Apache
> > mentor
> > > > >

Re: Looking for a Champion / Mentors for ResilientDB Blockchain Platform

2023-08-17 Thread Atri Sharma

Please count me in as a mentor

On Fri, 18 Aug 2023 at 9:45 AM, Mo Sadoghi  wrote:

> Dear Calvin,
>
> Thank you so much for your kind support.
>
> It would be great to have you as a mentor. Would you be open to serving as
> Champion, too, given your extensive experience?
>
> Greatly appreciated.
>
> ---
> Best Regards,
> Mohammad Sadoghi, PhD
> Associate Professor
> Exploratory Systems Lab (ExpoLab)
> Department of Computer Science
> University of California, Davis
>
> ExpoLab: https://expolab.org/
> ResilientDB: https://resilientdb.com/
> Phone: 914-319-7937
>
>
> *Statements by UC Davis:* Chancellor Gary S. May
> <
> https://www.ucdavis.edu/news/statement-resources-and-support-impacted-unrest-iran
> >,
> Dean Corsi (College of Engineering)
> <
> https://engineering.ucdavis.edu/news/statement-resources-and-support-those-impacted-unrest-iran
> >
> , Middle East/South Asia Studies
> <
> https://mesa.ucdavis.edu/public-statements/state-violence-against-student-protesters-iran
> >
>
> *Personal Statement:* We stand in solidarity with the brave and determined
> Iranian women and Iranian people. We are committed to upholding fundamental
> human rights, maintaining equity and justice, and standing against the use
> of violence, repression, and discrimination. We condemn the barbaric acts
> and brutal killings in Iranian streets, of innocent people in Ukraine, and
> everywhere globally.
>
>
> On Thu, Aug 17, 2023 at 7:15 PM Calvin Kirs  wrote:
>
> > Hi,
> >
> >Please count me in, I'm interested in this project and I am happy
> > to help as a mentor.
> >
> > I have been involved in the incubation process of several projects and
> > have experience with this.
> >
> > On Fri, Aug 18, 2023 at 9:40 AM 俊平堵  wrote:
> > >
> > > Hi,
> > > The project looks interesting to me and I am happy to help as
> mentor.
> > >  BTW, I am PMC of hadoop, Ozone, and mentor Yunikorn, Evenmesh,
> > Linkis,
> > > etc. towards Apache TLP.
> > >
> > > Thanks,
> > >
> > > JP
> > >
> > > Mo Sadoghi  于2023年8月18日周五 05:55写道：
> > >
> > > > Dear Apache Members,
> > > >
> > > > Hope you are safe and well.
> > > >
> > > > Over the past 6 years, we have been developing a distributed
> blockchain
> > > > framework, called ResilientDB , which has
> > been
> > > > open-sourced  since
> 2019.
> > > > ResilientDB is a lightweight and highly performant framework (written
> > in
> > > > C++) that has been extensively evaluated and refined resulting in
> over
> > 20
> > > > publications and 2 books. It allows for easy integration with various
> > > > Byzantine Fault-Tolerant (BFT) and Crash Fault-Tolerant (CFT)
> consensus
> > > > protocols. ResilientDB has been a key educational tool, thus far, 1
> > > > postdoc, 3 Ph.D., and 13 MSc students have graduated while working on
> > it.
> > > > Furthermore, it has been used in the classroom for the past 5 years
> > with
> > > > several hundred students utilizing it for their course projects. The
> > > > current core team of ResilientDB consists of 1 Postdoc, 2 PhD, 8 MSc,
> > and 6
> > > > BSc.  In addition to academic success, it has been utilized by our
> > industry
> > > > partners (e.g., Radix Ltd  and Mysten
> Labs
> > > > ) for analysis and as an
> industrial-strength
> > > > framework to implement their consensus protocols. The broader team of
> > > > active contributors currently included UCB, UCI, UPenn, and McMaster
> U.
> > > >
> > > > Our ResilientDB platform has now reached a stable point in its
> product
> > > > life-cycle, and we believe it is now an excellent candidate to be
> > > > considered for the Apache Incubation program to further expand its
> > reach
> > > > and development by building a larger community and ecosystem around
> it.
> > > > Furthermore, considering the thriving field of blockchain /
> distributed
> > > > ledger, Apache does not have any core blockchain software in its
> > portfolio.
> > > >
> > > > We are looking for champions and mentors for our project. Your kind
> > support
> > > > is greatly appreciated. We look forward to growing and expanding our
> > > > product as part of the Apache community.
> > > >
> > > > Here is the live / latest draft of the proposal.
> > > >
> > > >
> >
> https://docs.google.com/document/d/12WPvs1A7tqH8VjkMrgXTGQ_z4fiL6f6oi32e7bxSjXc/edit?usp=sharing
> > > >
> > > > Currently, we have *Anh Dinh*, Apache SINGA’s PMC, as our Apache
> mentor
> > > > (cc'ed).
> > > >
> > > > ---
> > > > Best Regards,
> > > > Mohammad Sadoghi, PhD
> > > > Associate Professor
> > > > Exploratory Systems Lab (ExpoLab)
> > > > Department of Computer Science
> > > > University of California, Davis
> > > >
> > > > ExpoLab: https://expolab.org/
> > > > ResilientDB: https://resilientdb.com/
> > > > Phone: 914-319-7937
> > > >
> >
> >
> >
> > --
> > Best wishes！
> > CalvinKirs
> >
> >

Re: Looking for a Champion / Mentors for ResilientDB Blockchain Platform

2023-08-17 Thread Mo Sadoghi

Dear Calvin,

Thank you so much for your kind support.

It would be great to have you as a mentor. Would you be open to serving as
Champion, too, given your extensive experience?

Greatly appreciated.

---
Best Regards,
Mohammad Sadoghi, PhD
Associate Professor
Exploratory Systems Lab (ExpoLab)
Department of Computer Science
University of California, Davis

ExpoLab: https://expolab.org/
ResilientDB: https://resilientdb.com/
Phone: 914-319-7937


*Statements by UC Davis:* Chancellor Gary S. May
,
Dean Corsi (College of Engineering)

, Middle East/South Asia Studies


*Personal Statement:* We stand in solidarity with the brave and determined
Iranian women and Iranian people. We are committed to upholding fundamental
human rights, maintaining equity and justice, and standing against the use
of violence, repression, and discrimination. We condemn the barbaric acts
and brutal killings in Iranian streets, of innocent people in Ukraine, and
everywhere globally.


On Thu, Aug 17, 2023 at 7:15 PM Calvin Kirs  wrote:

> Hi,
>
>Please count me in, I'm interested in this project and I am happy
> to help as a mentor.
>
> I have been involved in the incubation process of several projects and
> have experience with this.
>
> On Fri, Aug 18, 2023 at 9:40 AM 俊平堵  wrote:
> >
> > Hi,
> > The project looks interesting to me and I am happy to help as mentor.
> >  BTW, I am PMC of hadoop, Ozone, and mentor Yunikorn, Evenmesh,
> Linkis,
> > etc. towards Apache TLP.
> >
> > Thanks,
> >
> > JP
> >
> > Mo Sadoghi  于2023年8月18日周五 05:55写道：
> >
> > > Dear Apache Members,
> > >
> > > Hope you are safe and well.
> > >
> > > Over the past 6 years, we have been developing a distributed blockchain
> > > framework, called ResilientDB , which has
> been
> > > open-sourced  since 2019.
> > > ResilientDB is a lightweight and highly performant framework (written
> in
> > > C++) that has been extensively evaluated and refined resulting in over
> 20
> > > publications and 2 books. It allows for easy integration with various
> > > Byzantine Fault-Tolerant (BFT) and Crash Fault-Tolerant (CFT) consensus
> > > protocols. ResilientDB has been a key educational tool, thus far, 1
> > > postdoc, 3 Ph.D., and 13 MSc students have graduated while working on
> it.
> > > Furthermore, it has been used in the classroom for the past 5 years
> with
> > > several hundred students utilizing it for their course projects. The
> > > current core team of ResilientDB consists of 1 Postdoc, 2 PhD, 8 MSc,
> and 6
> > > BSc.  In addition to academic success, it has been utilized by our
> industry
> > > partners (e.g., Radix Ltd  and Mysten Labs
> > > ) for analysis and as an industrial-strength
> > > framework to implement their consensus protocols. The broader team of
> > > active contributors currently included UCB, UCI, UPenn, and McMaster U.
> > >
> > > Our ResilientDB platform has now reached a stable point in its product
> > > life-cycle, and we believe it is now an excellent candidate to be
> > > considered for the Apache Incubation program to further expand its
> reach
> > > and development by building a larger community and ecosystem around it.
> > > Furthermore, considering the thriving field of blockchain / distributed
> > > ledger, Apache does not have any core blockchain software in its
> portfolio.
> > >
> > > We are looking for champions and mentors for our project. Your kind
> support
> > > is greatly appreciated. We look forward to growing and expanding our
> > > product as part of the Apache community.
> > >
> > > Here is the live / latest draft of the proposal.
> > >
> > >
> https://docs.google.com/document/d/12WPvs1A7tqH8VjkMrgXTGQ_z4fiL6f6oi32e7bxSjXc/edit?usp=sharing
> > >
> > > Currently, we have *Anh Dinh*, Apache SINGA’s PMC, as our Apache mentor
> > > (cc'ed).
> > >
> > > ---
> > > Best Regards,
> > > Mohammad Sadoghi, PhD
> > > Associate Professor
> > > Exploratory Systems Lab (ExpoLab)
> > > Department of Computer Science
> > > University of California, Davis
> > >
> > > ExpoLab: https://expolab.org/
> > > ResilientDB: https://resilientdb.com/
> > > Phone: 914-319-7937
> > >
>
>
>
> --
> Best wishes！
> CalvinKirs
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Looking for a Champion / Mentors for ResilientDB Blockchain Platform

2023-08-17 Thread Mo Sadoghi

Dear Junping

Thank you so much for your kind support.

It would be wonderful to have you as a mentor or Champion if you are open
to it given your extensive experience.

---
Best Regards,
Mohammad Sadoghi, PhD
Associate Professor
Exploratory Systems Lab (ExpoLab)
Department of Computer Science
University of California, Davis

ExpoLab: https://expolab.org/
ResilientDB: https://resilientdb.com/
Phone: 914-319-7937


*Statements by UC Davis:* Chancellor Gary S. May
,
Dean Corsi (College of Engineering)

, Middle East/South Asia Studies


*Personal Statement:* We stand in solidarity with the brave and determined
Iranian women and Iranian people. We are committed to upholding fundamental
human rights, maintaining equity and justice, and standing against the use
of violence, repression, and discrimination. We condemn the barbaric acts
and brutal killings in Iranian streets, of innocent people in Ukraine, and
everywhere globally.


On Thu, Aug 17, 2023 at 6:40 PM 俊平堵  wrote:

> Hi,
> The project looks interesting to me and I am happy to help as mentor.
>  BTW, I am PMC of hadoop, Ozone, and mentor Yunikorn, Evenmesh, Linkis,
> etc. towards Apache TLP.
>
> Thanks,
>
> JP
>
> Mo Sadoghi  于2023年8月18日周五 05:55写道：
>
> > Dear Apache Members,
> >
> > Hope you are safe and well.
> >
> > Over the past 6 years, we have been developing a distributed blockchain
> > framework, called ResilientDB , which has been
> > open-sourced  since 2019.
> > ResilientDB is a lightweight and highly performant framework (written in
> > C++) that has been extensively evaluated and refined resulting in over 20
> > publications and 2 books. It allows for easy integration with various
> > Byzantine Fault-Tolerant (BFT) and Crash Fault-Tolerant (CFT) consensus
> > protocols. ResilientDB has been a key educational tool, thus far, 1
> > postdoc, 3 Ph.D., and 13 MSc students have graduated while working on it.
> > Furthermore, it has been used in the classroom for the past 5 years with
> > several hundred students utilizing it for their course projects. The
> > current core team of ResilientDB consists of 1 Postdoc, 2 PhD, 8 MSc,
> and 6
> > BSc.  In addition to academic success, it has been utilized by our
> industry
> > partners (e.g., Radix Ltd  and Mysten Labs
> > ) for analysis and as an industrial-strength
> > framework to implement their consensus protocols. The broader team of
> > active contributors currently included UCB, UCI, UPenn, and McMaster U.
> >
> > Our ResilientDB platform has now reached a stable point in its product
> > life-cycle, and we believe it is now an excellent candidate to be
> > considered for the Apache Incubation program to further expand its reach
> > and development by building a larger community and ecosystem around it.
> > Furthermore, considering the thriving field of blockchain / distributed
> > ledger, Apache does not have any core blockchain software in its
> portfolio.
> >
> > We are looking for champions and mentors for our project. Your kind
> support
> > is greatly appreciated. We look forward to growing and expanding our
> > product as part of the Apache community.
> >
> > Here is the live / latest draft of the proposal.
> >
> >
> https://docs.google.com/document/d/12WPvs1A7tqH8VjkMrgXTGQ_z4fiL6f6oi32e7bxSjXc/edit?usp=sharing
> >
> > Currently, we have *Anh Dinh*, Apache SINGA’s PMC, as our Apache mentor
> > (cc'ed).
> >
> > ---
> > Best Regards,
> > Mohammad Sadoghi, PhD
> > Associate Professor
> > Exploratory Systems Lab (ExpoLab)
> > Department of Computer Science
> > University of California, Davis
> >
> > ExpoLab: https://expolab.org/
> > ResilientDB: https://resilientdb.com/
> > Phone: 914-319-7937
> >
>

Re: Looking for a Champion / Mentors for ResilientDB Blockchain Platform

2023-08-17 Thread Mo Sadoghi

Dear David

Thank you so much for your kind support. It would be wonderful to have you
as a Champion (and mentor).

---
Best Regards,
Mohammad Sadoghi, PhD
Associate Professor
Exploratory Systems Lab (ExpoLab)
Department of Computer Science
University of California, Davis

ExpoLab: https://expolab.org/
ResilientDB: https://resilientdb.com/
Phone: 914-319-7937


*Statements by UC Davis:* Chancellor Gary S. May
,
Dean Corsi (College of Engineering)

, Middle East/South Asia Studies


*Personal Statement:* We stand in solidarity with the brave and determined
Iranian women and Iranian people. We are committed to upholding fundamental
human rights, maintaining equity and justice, and standing against the use
of violence, repression, and discrimination. We condemn the barbaric acts
and brutal killings in Iranian streets, of innocent people in Ukraine, and
everywhere globally.


On Thu, Aug 17, 2023 at 5:35 PM David Lyle  wrote:

> Hello,
>
> I’d be honored to Champion or mentor your project as you see fit. I’ve only
> had one experience helping to move a project, Apache Metron, through the
> process, but happy to help.
>
> Thanks!
>
> -David…
>
> On Thu, Aug 17, 2023 at 16:55 Mo Sadoghi  wrote:
>
> > Dear Apache Members,
> >
> > Hope you are safe and well.
> >
> > Over the past 6 years, we have been developing a distributed blockchain
> > framework, called ResilientDB , which has been
> > open-sourced  since 2019.
> > ResilientDB is a lightweight and highly performant framework (written in
> > C++) that has been extensively evaluated and refined resulting in over 20
> > publications and 2 books. It allows for easy integration with various
> > Byzantine Fault-Tolerant (BFT) and Crash Fault-Tolerant (CFT) consensus
> > protocols. ResilientDB has been a key educational tool, thus far, 1
> > postdoc, 3 Ph.D., and 13 MSc students have graduated while working on it.
> > Furthermore, it has been used in the classroom for the past 5 years with
> > several hundred students utilizing it for their course projects. The
> > current core team of ResilientDB consists of 1 Postdoc, 2 PhD, 8 MSc,
> and 6
> > BSc.  In addition to academic success, it has been utilized by our
> industry
> > partners (e.g., Radix Ltd  and Mysten Labs
> > ) for analysis and as an industrial-strength
> > framework to implement their consensus protocols. The broader team of
> > active contributors currently included UCB, UCI, UPenn, and McMaster U.
> >
> > Our ResilientDB platform has now reached a stable point in its product
> > life-cycle, and we believe it is now an excellent candidate to be
> > considered for the Apache Incubation program to further expand its reach
> > and development by building a larger community and ecosystem around it.
> > Furthermore, considering the thriving field of blockchain / distributed
> > ledger, Apache does not have any core blockchain software in its
> portfolio.
> >
> > We are looking for champions and mentors for our project. Your kind
> support
> > is greatly appreciated. We look forward to growing and expanding our
> > product as part of the Apache community.
> >
> > Here is the live / latest draft of the proposal.
> >
> >
> https://docs.google.com/document/d/12WPvs1A7tqH8VjkMrgXTGQ_z4fiL6f6oi32e7bxSjXc/edit?usp=sharing
> >
> > Currently, we have *Anh Dinh*, Apache SINGA’s PMC, as our Apache mentor
> > (cc'ed).
> >
> > ---
> > Best Regards,
> > Mohammad Sadoghi, PhD
> > Associate Professor
> > Exploratory Systems Lab (ExpoLab)
> > Department of Computer Science
> > University of California, Davis
> >
> > ExpoLab: https://expolab.org/
> > ResilientDB: https://resilientdb.com/
> > Phone: 914-319-7937
> >
>

Re: Looking for a Champion / Mentors for ResilientDB Blockchain Platform

2023-08-17 Thread Calvin Kirs

Hi,

   Please count me in, I'm interested in this project and I am happy
to help as a mentor.

I have been involved in the incubation process of several projects and
have experience with this.

On Fri, Aug 18, 2023 at 9:40 AM 俊平堵  wrote:
>
> Hi,
> The project looks interesting to me and I am happy to help as mentor.
>  BTW, I am PMC of hadoop, Ozone, and mentor Yunikorn, Evenmesh, Linkis,
> etc. towards Apache TLP.
>
> Thanks,
>
> JP
>
> Mo Sadoghi  于2023年8月18日周五 05:55写道：
>
> > Dear Apache Members,
> >
> > Hope you are safe and well.
> >
> > Over the past 6 years, we have been developing a distributed blockchain
> > framework, called ResilientDB , which has been
> > open-sourced  since 2019.
> > ResilientDB is a lightweight and highly performant framework (written in
> > C++) that has been extensively evaluated and refined resulting in over 20
> > publications and 2 books. It allows for easy integration with various
> > Byzantine Fault-Tolerant (BFT) and Crash Fault-Tolerant (CFT) consensus
> > protocols. ResilientDB has been a key educational tool, thus far, 1
> > postdoc, 3 Ph.D., and 13 MSc students have graduated while working on it.
> > Furthermore, it has been used in the classroom for the past 5 years with
> > several hundred students utilizing it for their course projects. The
> > current core team of ResilientDB consists of 1 Postdoc, 2 PhD, 8 MSc, and 6
> > BSc.  In addition to academic success, it has been utilized by our industry
> > partners (e.g., Radix Ltd  and Mysten Labs
> > ) for analysis and as an industrial-strength
> > framework to implement their consensus protocols. The broader team of
> > active contributors currently included UCB, UCI, UPenn, and McMaster U.
> >
> > Our ResilientDB platform has now reached a stable point in its product
> > life-cycle, and we believe it is now an excellent candidate to be
> > considered for the Apache Incubation program to further expand its reach
> > and development by building a larger community and ecosystem around it.
> > Furthermore, considering the thriving field of blockchain / distributed
> > ledger, Apache does not have any core blockchain software in its portfolio.
> >
> > We are looking for champions and mentors for our project. Your kind support
> > is greatly appreciated. We look forward to growing and expanding our
> > product as part of the Apache community.
> >
> > Here is the live / latest draft of the proposal.
> >
> > https://docs.google.com/document/d/12WPvs1A7tqH8VjkMrgXTGQ_z4fiL6f6oi32e7bxSjXc/edit?usp=sharing
> >
> > Currently, we have *Anh Dinh*, Apache SINGA’s PMC, as our Apache mentor
> > (cc'ed).
> >
> > ---
> > Best Regards,
> > Mohammad Sadoghi, PhD
> > Associate Professor
> > Exploratory Systems Lab (ExpoLab)
> > Department of Computer Science
> > University of California, Davis
> >
> > ExpoLab: https://expolab.org/
> > ResilientDB: https://resilientdb.com/
> > Phone: 914-319-7937
> >



-- 
Best wishes！
CalvinKirs

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Looking for a Champion / Mentors for ResilientDB Blockchain Platform

2023-08-17 Thread 俊平堵

Hi,
The project looks interesting to me and I am happy to help as mentor.
 BTW, I am PMC of hadoop, Ozone, and mentor Yunikorn, Evenmesh, Linkis,
etc. towards Apache TLP.

Thanks,

JP

Mo Sadoghi  于2023年8月18日周五 05:55写道：

> Dear Apache Members,
>
> Hope you are safe and well.
>
> Over the past 6 years, we have been developing a distributed blockchain
> framework, called ResilientDB , which has been
> open-sourced  since 2019.
> ResilientDB is a lightweight and highly performant framework (written in
> C++) that has been extensively evaluated and refined resulting in over 20
> publications and 2 books. It allows for easy integration with various
> Byzantine Fault-Tolerant (BFT) and Crash Fault-Tolerant (CFT) consensus
> protocols. ResilientDB has been a key educational tool, thus far, 1
> postdoc, 3 Ph.D., and 13 MSc students have graduated while working on it.
> Furthermore, it has been used in the classroom for the past 5 years with
> several hundred students utilizing it for their course projects. The
> current core team of ResilientDB consists of 1 Postdoc, 2 PhD, 8 MSc, and 6
> BSc.  In addition to academic success, it has been utilized by our industry
> partners (e.g., Radix Ltd  and Mysten Labs
> ) for analysis and as an industrial-strength
> framework to implement their consensus protocols. The broader team of
> active contributors currently included UCB, UCI, UPenn, and McMaster U.
>
> Our ResilientDB platform has now reached a stable point in its product
> life-cycle, and we believe it is now an excellent candidate to be
> considered for the Apache Incubation program to further expand its reach
> and development by building a larger community and ecosystem around it.
> Furthermore, considering the thriving field of blockchain / distributed
> ledger, Apache does not have any core blockchain software in its portfolio.
>
> We are looking for champions and mentors for our project. Your kind support
> is greatly appreciated. We look forward to growing and expanding our
> product as part of the Apache community.
>
> Here is the live / latest draft of the proposal.
>
> https://docs.google.com/document/d/12WPvs1A7tqH8VjkMrgXTGQ_z4fiL6f6oi32e7bxSjXc/edit?usp=sharing
>
> Currently, we have *Anh Dinh*, Apache SINGA’s PMC, as our Apache mentor
> (cc'ed).
>
> ---
> Best Regards,
> Mohammad Sadoghi, PhD
> Associate Professor
> Exploratory Systems Lab (ExpoLab)
> Department of Computer Science
> University of California, Davis
>
> ExpoLab: https://expolab.org/
> ResilientDB: https://resilientdb.com/
> Phone: 914-319-7937
>

Re: Looking for a Champion / Mentors for ResilientDB Blockchain Platform

2023-08-17 Thread David Lyle

Hello,

I’d be honored to Champion or mentor your project as you see fit. I’ve only
had one experience helping to move a project, Apache Metron, through the
process, but happy to help.

Thanks!

-David…

On Thu, Aug 17, 2023 at 16:55 Mo Sadoghi  wrote:

> Dear Apache Members,
>
> Hope you are safe and well.
>
> Over the past 6 years, we have been developing a distributed blockchain
> framework, called ResilientDB , which has been
> open-sourced  since 2019.
> ResilientDB is a lightweight and highly performant framework (written in
> C++) that has been extensively evaluated and refined resulting in over 20
> publications and 2 books. It allows for easy integration with various
> Byzantine Fault-Tolerant (BFT) and Crash Fault-Tolerant (CFT) consensus
> protocols. ResilientDB has been a key educational tool, thus far, 1
> postdoc, 3 Ph.D., and 13 MSc students have graduated while working on it.
> Furthermore, it has been used in the classroom for the past 5 years with
> several hundred students utilizing it for their course projects. The
> current core team of ResilientDB consists of 1 Postdoc, 2 PhD, 8 MSc, and 6
> BSc.  In addition to academic success, it has been utilized by our industry
> partners (e.g., Radix Ltd  and Mysten Labs
> ) for analysis and as an industrial-strength
> framework to implement their consensus protocols. The broader team of
> active contributors currently included UCB, UCI, UPenn, and McMaster U.
>
> Our ResilientDB platform has now reached a stable point in its product
> life-cycle, and we believe it is now an excellent candidate to be
> considered for the Apache Incubation program to further expand its reach
> and development by building a larger community and ecosystem around it.
> Furthermore, considering the thriving field of blockchain / distributed
> ledger, Apache does not have any core blockchain software in its portfolio.
>
> We are looking for champions and mentors for our project. Your kind support
> is greatly appreciated. We look forward to growing and expanding our
> product as part of the Apache community.
>
> Here is the live / latest draft of the proposal.
>
> https://docs.google.com/document/d/12WPvs1A7tqH8VjkMrgXTGQ_z4fiL6f6oi32e7bxSjXc/edit?usp=sharing
>
> Currently, we have *Anh Dinh*, Apache SINGA’s PMC, as our Apache mentor
> (cc'ed).
>
> ---
> Best Regards,
> Mohammad Sadoghi, PhD
> Associate Professor
> Exploratory Systems Lab (ExpoLab)
> Department of Computer Science
> University of California, Davis
>
> ExpoLab: https://expolab.org/
> ResilientDB: https://resilientdb.com/
> Phone: 914-319-7937
>

RE: Re: Looking for a Champion (and mentors) for the Hexagon Toolkit

2023-08-11 Thread Juan José Aguililla

Hi, thanks for checking the project. I understand your concern, I
thought that maybe someone here could be interested in taking part in
the project. However, seeing that that's not an option, I'll try to
get more people involved and maybe try again another time.


Cheers,
Juanjo

On 2023/08/10 08:45:05 PJ Fanning wrote:
> Hi Juan José,
>
> Your project looks like you've put a lot of time and effort into it.
> It certainly looks like a good candidate.
>
> My one concern is that Apache Incubator projects require votes about
> procedural items like doing releases so that means you need to have a
> few community members to start with. It is an important goal of any
> incubating project to grow the community over time but the ASF rules
> require that you have to start with a few active members.
>
> Do you have a few Hexagon contributors who would be interested in
> acting as PPMC [1] members of a potential Apache Incubator project?
>
> It can be quite a time consuming process to bring code into an Apache
> Incubator project and to modify all the code and documentation to
> apply the correct licensing and branding.
>
> Regards,
> PJ
>
> [1] https://incubator.apache.org/guides/ppmc.html
>
> On Wed, 9 Aug 2023 at 22:56, Juan José Aguililla
>  wrote:
> >
> > Hello Apache Members,
> >
> > I would love to move the Hexagon Toolkit development to the ASF. To
> > briefly describe the project: Hexagon is a microservices toolkit
> > written in Kotlin. Its purpose is to ease the building of server
> > applications (Web applications or REST APIs).
> >
> > The project's goals are:
> > * Provide a programmatic way to handle HTTP requests. With a similar
> > developer experience as Javalin: https://javalin.io or Express:
> > https://expressjs.com
> > * Provide a tool backed by an OSS foundation instead of a company
> > * Modular architecture
> >   * Each functionality has its own "Port"
> >   * Ports are implemented by adapters. They can be switched without
> > changing application code
> >   * Modules are layered (i.e.: REST > HTTP Server) not carrying unused
> > functionalities (and their dependencies)
> >   * Orthogonal ports: Ports can be used by other Ports or standalone
> > as opposed to duplicating code (i.e.: JSON on HTTP clients and
> > servers)
> > * No code generation (on the core). It can be added later to generate
> > code, but not relying on code generation to create applications
> > * Bare minimum dependencies. Ideally, only a third party dependency by 
> > adapter
> > * Native Image: client applications can generate native images easily
> > (the toolkit tests are passed natively on Windows, macOS and Linux)
> > * No reflection. This makes easier to reason about programs, and eases
> > the native image generation
> > * Developed in Kotlin and meant to be used with Kotlin, but I'm
> > considering porting it to Java
> >
> > The reasons to enter the Apache Incubator are:
> > * First, to get feedback to decide if it is worthy to keep the project
> > open, and know which changes would be needed to make it appealing to
> > developers.
> > * Second, to create a community around to take the toolkit further
> > * And lastly, to get a broader reach for developers to use it for
> > their applications
> >
> > These are some relevant links:
> > * https://hexagonkt.com
> > * https://github.com/hexagonkt
> > * https://twitter.com/hexagon_kt
> >
> > Thank you very much for your time! I keep waiting for news from your side.
> >
> >
> > Cheers,
> > Juanjo
> >
> > -
> > 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: Looking for a Champion (and mentors) for the Hexagon Toolkit

2023-08-10 Thread PJ Fanning

Hi Juan José,

Your project looks like you've put a lot of time and effort into it.
It certainly looks like a good candidate.

My one concern is that Apache Incubator projects require votes about
procedural items like doing releases so that means you need to have a
few community members to start with. It is an important goal of any
incubating project to grow the community over time but the ASF rules
require that you have to start with a few active members.

Do you have a few Hexagon contributors who would be interested in
acting as PPMC [1] members of a potential Apache Incubator project?

It can be quite a time consuming process to bring code into an Apache
Incubator project and to modify all the code and documentation to
apply the correct licensing and branding.

Regards,
PJ

[1] https://incubator.apache.org/guides/ppmc.html

On Wed, 9 Aug 2023 at 22:56, Juan José Aguililla
 wrote:
>
> Hello Apache Members,
>
> I would love to move the Hexagon Toolkit development to the ASF. To
> briefly describe the project: Hexagon is a microservices toolkit
> written in Kotlin. Its purpose is to ease the building of server
> applications (Web applications or REST APIs).
>
> The project's goals are:
> * Provide a programmatic way to handle HTTP requests. With a similar
> developer experience as Javalin: https://javalin.io or Express:
> https://expressjs.com
> * Provide a tool backed by an OSS foundation instead of a company
> * Modular architecture
>   * Each functionality has its own "Port"
>   * Ports are implemented by adapters. They can be switched without
> changing application code
>   * Modules are layered (i.e.: REST > HTTP Server) not carrying unused
> functionalities (and their dependencies)
>   * Orthogonal ports: Ports can be used by other Ports or standalone
> as opposed to duplicating code (i.e.: JSON on HTTP clients and
> servers)
> * No code generation (on the core). It can be added later to generate
> code, but not relying on code generation to create applications
> * Bare minimum dependencies. Ideally, only a third party dependency by adapter
> * Native Image: client applications can generate native images easily
> (the toolkit tests are passed natively on Windows, macOS and Linux)
> * No reflection. This makes easier to reason about programs, and eases
> the native image generation
> * Developed in Kotlin and meant to be used with Kotlin, but I'm
> considering porting it to Java
>
> The reasons to enter the Apache Incubator are:
> * First, to get feedback to decide if it is worthy to keep the project
> open, and know which changes would be needed to make it appealing to
> developers.
> * Second, to create a community around to take the toolkit further
> * And lastly, to get a broader reach for developers to use it for
> their applications
>
> These are some relevant links:
> * https://hexagonkt.com
> * https://github.com/hexagonkt
> * https://twitter.com/hexagon_kt
>
> Thank you very much for your time! I keep waiting for news from your side.
>
>
> Cheers,
> Juanjo
>
> -
> 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: Looking for a champion: HyperIoT

2023-01-27 Thread Aristide Cittadino

; @Chris, I'm very happy that you are interested to help here, I think
> that they can change the license and I'll try to bring Aristide Cittadino
> of ACSoftware in this thread to let him participate in this discussion with
> all of us.
> >
> > @Dave, probably we can manage everything easily bringing the project
> under the Apache License.
> >
> > Thank you all for all your feedback and we will receive some comments
> also from Aristide very soon.
> >
> > Cheers,
> > PJ
> >
> >
> >
> > On 2023/01/12 14:58:44 Dave Fisher wrote:
> > >
> > >
> > > Sent from my iPhone
> > >
> > > > On Jan 12, 2023, at 5:42 AM, Christofer Dutz <
> christofer.d...@c-ware.de> wrote:
> > > >
> > > > Hi,
> > > >
> > > > So, I did have a look at the website and indeed it looks
> interesting.
> > > > However, when I looked at the GitHub repo and the GPL2 yelled at me.
> > > >
> > > > Are you able to do a re-licensing? I mean … can you ask everyone who
> contributed to the project if they agree to re-licensing it under the
> Apache 2.0 license?
> > >
> > > The only community to go through the Petri process accomplished this
> license conversion from GPL.
> > >
> > > petri.apache.org
> > >
> > > This was BuildStream which was a gnu project community.
> > >
> > > If there is a community Petri might be a good start.
> > > >
> > > > If that’s not possible, I guess this is the end of the line for
> Apache. If it’s possible I am still keeping my hand up for being your
> Mentor and possibly championing the project.
> > >
> > > I noticed that this project is heavily dependent on Storm. I strongly
> suggest that they get involved in that project ASAP.
> > >
> > > Regards,
> > > Dave
> > >
> > > >
> > > > Chris
> > > >
> > > >
> > > >
> > > > From: Christofer Dutz 
> > > > Date: Thursday, 12. January 2023 at 14:22
> > > > To: general@incubator.apache.org 
> > > > Subject: Re: Looking for a champion: HyperIoT
> > > > Hi all,
> > > >
> > > > well … it being used is not a requirement … some projects have been
> joining Apache even without a single user, but we want at least a minimum
> on community around it.
> > > >
> > > > As I’m really into the (I)IoT topic and I currently have one
> Mentoring slot open … I would be raising my hand for being interested to
> help.
> > > >
> > > > Give me a bit of time to read up on what the project is about.
> > > >
> > > > Chris
> > > >
> > > >
> > > > From: Enrico Olivelli 
> > > > Date: Thursday, 12. January 2023 at 11:26
> > > > To: general@incubator.apache.org 
> > > > Subject: Re: Looking for a champion: HyperIoT
> > > > Piergiorgio,
> > > > Is this project already OSS ?
> > > > Is this project already used by other companies?
> > > >
> > > > If it doesn't meet those requirements I don't think that it will
> have
> > > > a happy story in the Incubator.
> > > >
> > > > I have never been a Mentor for an incubating project but I have been
> > > > following this list for quite some time,
> > > > and my understanding is that a project that wants to enter the ASF
> > > > MUST already be an OSS project with active users.
> > > >
> > > > just my 2 cents
> > > > Enrico
> > > >
> > > >> Il giorno gio 12 gen 2023 alle ore 09:17 tison <
> wander4...@gmail.com>
> > > >> ha scritto:
> > > >>
> > > >>> I'm an ASF Member, I could also help here for writing the proposal
> but I'm
> > > >>> not a PMC member for the Incubator project, I'm a committer for my
> past
> > > >>> incubation experience related to Apache ManifoldCF.
> > > >>
> > > >> FYI, as an ASF Member, you can request to become a IPMC member
> anytime:
> > > >>
> > > >>> Individuals may be nominated to join the IPMC after a vote which
> passes.
> > > >> Individuals may choose to bring themselves or others to the
> attention of
> > > >> the IPMC. Additionally, any Member of the Apache Software
> Foundation may
> > > >> join the IPMC by request.
> > > >>
> >

Re: Looking for a champion: HyperIoT

2023-01-13 Thread Aristide Cittadino

e is a community Petri might be a good start.
> > >
> > > If that’s not possible, I guess this is the end of the line for
Apache. If it’s possible I am still keeping my hand up for being your
Mentor and possibly championing the project.
> >
> > I noticed that this project is heavily dependent on Storm. I strongly
suggest that they get involved in that project ASAP.
> >
> > Regards,
> > Dave
> >
> > >
> > > Chris
> > >
> > >
> > >
> > > From: Christofer Dutz 
> > > Date: Thursday, 12. January 2023 at 14:22
> > > To: general@incubator.apache.org 
> > > Subject: Re: Looking for a champion: HyperIoT
> > > Hi all,
> > >
> > > well … it being used is not a requirement … some projects have been
joining Apache even without a single user, but we want at least a minimum
on community around it.
> > >
> > > As I’m really into the (I)IoT topic and I currently have one
Mentoring slot open … I would be raising my hand for being interested to
help.
> > >
> > > Give me a bit of time to read up on what the project is about.
> > >
> > > Chris
> > >
> > >
> > > From: Enrico Olivelli 
> > > Date: Thursday, 12. January 2023 at 11:26
> > > To: general@incubator.apache.org 
> > > Subject: Re: Looking for a champion: HyperIoT
> > > Piergiorgio,
> > > Is this project already OSS ?
> > > Is this project already used by other companies?
> > >
> > > If it doesn't meet those requirements I don't think that it will have
> > > a happy story in the Incubator.
> > >
> > > I have never been a Mentor for an incubating project but I have been
> > > following this list for quite some time,
> > > and my understanding is that a project that wants to enter the ASF
> > > MUST already be an OSS project with active users.
> > >
> > > just my 2 cents
> > > Enrico
> > >
> > >> Il giorno gio 12 gen 2023 alle ore 09:17 tison 

> > >> ha scritto:
> > >>
> > >>> I'm an ASF Member, I could also help here for writing the proposal
but I'm
> > >>> not a PMC member for the Incubator project, I'm a committer for my
past
> > >>> incubation experience related to Apache ManifoldCF.
> > >>
> > >> FYI, as an ASF Member, you can request to become a IPMC member
anytime:
> > >>
> > >>> Individuals may be nominated to join the IPMC after a vote which
passes.
> > >> Individuals may choose to bring themselves or others to the
attention of
> > >> the IPMC. Additionally, any Member of the Apache Software Foundation
may
> > >> join the IPMC by request.
> > >>
> > >> ... from
https://incubator.apache.org/guides/roles_and_responsibilities.html
> > >> .
> > >>
> > >> Best,
> > >> tison.
> > >>
> > >>
> > >> Piergiorgio Lucidi  于2023年1月12日周四 16:06写道：
> > >>
> > >>> Hi folks,
> > >>>
> > >>> ACSoftware contacted me because they would like to donate their
platform
> > >>> named HyperIoT to the Foundation. I'm searching for a champion to
build the
> > >>> incubation proposal.
> > >>>
> > >>> I'm an ASF Member, I could also help here for writing the proposal
but I'm
> > >>> not a PMC member for the Incubator project, I'm a committer for my
past
> > >>> incubation experience related to Apache ManifoldCF.
> > >>>
> > >>> They currently published only the backend services on their GitHub
account
> > >>> but they are going to also share all the UI modules:
> > >>> https://github.com/ACSoftwareTeam/HyperIoT-Platform
> > >>>
> > >>> You can find more information and some screenshots here:
> > >>> https://hyperiot.cloud/
> > >>>
> > >>> Below is an overview of this platform.
> > >>>
> > >>> HyperIoT is an OpenSource Cloud Native platform entirely based on
Apache
> > >>> Technologies for managing big data from any IoT network.
> > >>> The platform captures the information sent from any source by
managing data
> > >>> compression, running statistics or machine/deep learning
algorithms,
> > >>> presenting data to the end user in realtime and offline mode (saved
data).
> > >>>
> > >>> It consists of the following macro-components (entirely built on

Re: Looking for a champion: HyperIoT

2023-01-13 Thread Piergiorgio Lucidi

Hi,

ACSoftware shared all the modules in their GitHub account and they also changed 
the license:
https://github.com/orgs/ACSoftwareTeam/repositories

They are going to improve the documentation in order to facilitate the adoption 
process.
More information will be provided directly by Aristide that now is following 
this list.

Please share your feedback.
Cheers,
PJ

On 2023/01/12 15:23:17 Piergiorgio Lucidi wrote:
> Hi folks,
> 
> @tison, yes probably it could be useful to be part of IPMC for this and any 
> other project, it would be great to help also on this side of the ASF.
> 
> @Enrico, the project is not fully open source at the moment, they shared all 
> the backend services, but they are going to finalize this process sharing the 
> entire set of services. And yes, the platform is used by several companies in 
> production.
> 
> @Chris, I'm very happy that you are interested to help here, I think that 
> they can change the license and I'll try to bring Aristide Cittadino of 
> ACSoftware in this thread to let him participate in this discussion with all 
> of us.
> 
> @Dave, probably we can manage everything easily bringing the project under 
> the Apache License.
> 
> Thank you all for all your feedback and we will receive some comments also 
> from Aristide very soon.
> 
> Cheers,
> PJ
> 
> 
> 
> On 2023/01/12 14:58:44 Dave Fisher wrote:
> > 
> > 
> > Sent from my iPhone
> > 
> > > On Jan 12, 2023, at 5:42 AM, Christofer Dutz  
> > > wrote:
> > > 
> > > Hi,
> > > 
> > > So, I did have a look at the website and indeed it looks interesting.
> > > However, when I looked at the GitHub repo and the GPL2 yelled at me.
> > > 
> > > Are you able to do a re-licensing? I mean … can you ask everyone who 
> > > contributed to the project if they agree to re-licensing it under the 
> > > Apache 2.0 license?
> > 
> > The only community to go through the Petri process accomplished this 
> > license conversion from GPL.
> > 
> > petri.apache.org
> > 
> > This was BuildStream which was a gnu project community.
> > 
> > If there is a community Petri might be a good start.
> > > 
> > > If that’s not possible, I guess this is the end of the line for Apache. 
> > > If it’s possible I am still keeping my hand up for being your Mentor and 
> > > possibly championing the project.
> > 
> > I noticed that this project is heavily dependent on Storm. I strongly 
> > suggest that they get involved in that project ASAP.
> > 
> > Regards,
> > Dave
> > 
> > > 
> > > Chris
> > > 
> > > 
> > > 
> > > From: Christofer Dutz 
> > > Date: Thursday, 12. January 2023 at 14:22
> > > To: general@incubator.apache.org 
> > > Subject: Re: Looking for a champion: HyperIoT
> > > Hi all,
> > > 
> > > well … it being used is not a requirement … some projects have been 
> > > joining Apache even without a single user, but we want at least a minimum 
> > > on community around it.
> > > 
> > > As I’m really into the (I)IoT topic and I currently have one Mentoring 
> > > slot open … I would be raising my hand for being interested to help.
> > > 
> > > Give me a bit of time to read up on what the project is about.
> > > 
> > > Chris
> > > 
> > > 
> > > From: Enrico Olivelli 
> > > Date: Thursday, 12. January 2023 at 11:26
> > > To: general@incubator.apache.org 
> > > Subject: Re: Looking for a champion: HyperIoT
> > > Piergiorgio,
> > > Is this project already OSS ?
> > > Is this project already used by other companies?
> > > 
> > > If it doesn't meet those requirements I don't think that it will have
> > > a happy story in the Incubator.
> > > 
> > > I have never been a Mentor for an incubating project but I have been
> > > following this list for quite some time,
> > > and my understanding is that a project that wants to enter the ASF
> > > MUST already be an OSS project with active users.
> > > 
> > > just my 2 cents
> > > Enrico
> > > 
> > >> Il giorno gio 12 gen 2023 alle ore 09:17 tison 
> > >> ha scritto:
> > >> 
> > >>> I'm an ASF Member, I could also help here for writing the proposal but 
> > >>> I'm
> > >>> not a PMC member for the Incubator project, I'm a committer for my past
> > >>> incubation experience related to Apache Manifold

Re: Looking for a champion: HyperIoT

2023-01-12 Thread Piergiorgio Lucidi

Hi folks,

@tison, yes probably it could be useful to be part of IPMC for this and any 
other project, it would be great to help also on this side of the ASF.

@Enrico, the project is not fully open source at the moment, they shared all 
the backend services, but they are going to finalize this process sharing the 
entire set of services. And yes, the platform is used by several companies in 
production.

@Chris, I'm very happy that you are interested to help here, I think that they 
can change the license and I'll try to bring Aristide Cittadino of ACSoftware 
in this thread to let him participate in this discussion with all of us.

@Dave, probably we can manage everything easily bringing the project under the 
Apache License.

Thank you all for all your feedback and we will receive some comments also from 
Aristide very soon.

Cheers,
PJ



On 2023/01/12 14:58:44 Dave Fisher wrote:
> 
> 
> Sent from my iPhone
> 
> > On Jan 12, 2023, at 5:42 AM, Christofer Dutz  
> > wrote:
> > 
> > Hi,
> > 
> > So, I did have a look at the website and indeed it looks interesting.
> > However, when I looked at the GitHub repo and the GPL2 yelled at me.
> > 
> > Are you able to do a re-licensing? I mean … can you ask everyone who 
> > contributed to the project if they agree to re-licensing it under the 
> > Apache 2.0 license?
> 
> The only community to go through the Petri process accomplished this license 
> conversion from GPL.
> 
> petri.apache.org
> 
> This was BuildStream which was a gnu project community.
> 
> If there is a community Petri might be a good start.
> > 
> > If that’s not possible, I guess this is the end of the line for Apache. If 
> > it’s possible I am still keeping my hand up for being your Mentor and 
> > possibly championing the project.
> 
> I noticed that this project is heavily dependent on Storm. I strongly suggest 
> that they get involved in that project ASAP.
> 
> Regards,
> Dave
> 
> > 
> > Chris
> > 
> > 
> > 
> > From: Christofer Dutz 
> > Date: Thursday, 12. January 2023 at 14:22
> > To: general@incubator.apache.org 
> > Subject: Re: Looking for a champion: HyperIoT
> > Hi all,
> > 
> > well … it being used is not a requirement … some projects have been joining 
> > Apache even without a single user, but we want at least a minimum on 
> > community around it.
> > 
> > As I’m really into the (I)IoT topic and I currently have one Mentoring slot 
> > open … I would be raising my hand for being interested to help.
> > 
> > Give me a bit of time to read up on what the project is about.
> > 
> > Chris
> > 
> > 
> > From: Enrico Olivelli 
> > Date: Thursday, 12. January 2023 at 11:26
> > To: general@incubator.apache.org 
> > Subject: Re: Looking for a champion: HyperIoT
> > Piergiorgio,
> > Is this project already OSS ?
> > Is this project already used by other companies?
> > 
> > If it doesn't meet those requirements I don't think that it will have
> > a happy story in the Incubator.
> > 
> > I have never been a Mentor for an incubating project but I have been
> > following this list for quite some time,
> > and my understanding is that a project that wants to enter the ASF
> > MUST already be an OSS project with active users.
> > 
> > just my 2 cents
> > Enrico
> > 
> >> Il giorno gio 12 gen 2023 alle ore 09:17 tison 
> >> ha scritto:
> >> 
> >>> I'm an ASF Member, I could also help here for writing the proposal but I'm
> >>> not a PMC member for the Incubator project, I'm a committer for my past
> >>> incubation experience related to Apache ManifoldCF.
> >> 
> >> FYI, as an ASF Member, you can request to become a IPMC member anytime:
> >> 
> >>> Individuals may be nominated to join the IPMC after a vote which passes.
> >> Individuals may choose to bring themselves or others to the attention of
> >> the IPMC. Additionally, any Member of the Apache Software Foundation may
> >> join the IPMC by request.
> >> 
> >> ... from 
> >> https://incubator.apache.org/guides/roles_and_responsibilities.html
> >> .
> >> 
> >> Best,
> >> tison.
> >> 
> >> 
> >> Piergiorgio Lucidi  于2023年1月12日周四 16:06写道：
> >> 
> >>> Hi folks,
> >>> 
> >>> ACSoftware contacted me because they would like to donate their platform
> >>> named HyperIoT to the Foundation. I'm searching for a champion to build 
> >>> the
> >>> incu

Re: Looking for a champion: HyperIoT

2023-01-12 Thread Dave Fisher




Sent from my iPhone

> On Jan 12, 2023, at 5:42 AM, Christofer Dutz  
> wrote:
> 
> Hi,
> 
> So, I did have a look at the website and indeed it looks interesting.
> However, when I looked at the GitHub repo and the GPL2 yelled at me.
> 
> Are you able to do a re-licensing? I mean … can you ask everyone who 
> contributed to the project if they agree to re-licensing it under the Apache 
> 2.0 license?

The only community to go through the Petri process accomplished this license 
conversion from GPL.

petri.apache.org

This was BuildStream which was a gnu project community.

If there is a community Petri might be a good start.
> 
> If that’s not possible, I guess this is the end of the line for Apache. If 
> it’s possible I am still keeping my hand up for being your Mentor and 
> possibly championing the project.

I noticed that this project is heavily dependent on Storm. I strongly suggest 
that they get involved in that project ASAP.

Regards,
Dave

> 
> Chris
> 
> 
> 
> From: Christofer Dutz 
> Date: Thursday, 12. January 2023 at 14:22
> To: general@incubator.apache.org 
> Subject: Re: Looking for a champion: HyperIoT
> Hi all,
> 
> well … it being used is not a requirement … some projects have been joining 
> Apache even without a single user, but we want at least a minimum on 
> community around it.
> 
> As I’m really into the (I)IoT topic and I currently have one Mentoring slot 
> open … I would be raising my hand for being interested to help.
> 
> Give me a bit of time to read up on what the project is about.
> 
> Chris
> 
> 
> From: Enrico Olivelli 
> Date: Thursday, 12. January 2023 at 11:26
> To: general@incubator.apache.org 
> Subject: Re: Looking for a champion: HyperIoT
> Piergiorgio,
> Is this project already OSS ?
> Is this project already used by other companies?
> 
> If it doesn't meet those requirements I don't think that it will have
> a happy story in the Incubator.
> 
> I have never been a Mentor for an incubating project but I have been
> following this list for quite some time,
> and my understanding is that a project that wants to enter the ASF
> MUST already be an OSS project with active users.
> 
> just my 2 cents
> Enrico
> 
>> Il giorno gio 12 gen 2023 alle ore 09:17 tison 
>> ha scritto:
>> 
>>> I'm an ASF Member, I could also help here for writing the proposal but I'm
>>> not a PMC member for the Incubator project, I'm a committer for my past
>>> incubation experience related to Apache ManifoldCF.
>> 
>> FYI, as an ASF Member, you can request to become a IPMC member anytime:
>> 
>>> Individuals may be nominated to join the IPMC after a vote which passes.
>> Individuals may choose to bring themselves or others to the attention of
>> the IPMC. Additionally, any Member of the Apache Software Foundation may
>> join the IPMC by request.
>> 
>> ... from https://incubator.apache.org/guides/roles_and_responsibilities.html
>> .
>> 
>> Best,
>> tison.
>> 
>> 
>> Piergiorgio Lucidi  于2023年1月12日周四 16:06写道：
>> 
>>> Hi folks,
>>> 
>>> ACSoftware contacted me because they would like to donate their platform
>>> named HyperIoT to the Foundation. I'm searching for a champion to build the
>>> incubation proposal.
>>> 
>>> I'm an ASF Member, I could also help here for writing the proposal but I'm
>>> not a PMC member for the Incubator project, I'm a committer for my past
>>> incubation experience related to Apache ManifoldCF.
>>> 
>>> They currently published only the backend services on their GitHub account
>>> but they are going to also share all the UI modules:
>>> https://github.com/ACSoftwareTeam/HyperIoT-Platform
>>> 
>>> You can find more information and some screenshots here:
>>> https://hyperiot.cloud/
>>> 
>>> Below is an overview of this platform.
>>> 
>>> HyperIoT is an OpenSource Cloud Native platform entirely based on Apache
>>> Technologies for managing big data from any IoT network.
>>> The platform captures the information sent from any source by managing data
>>> compression, running statistics or machine/deep learning algorithms,
>>> presenting data to the end user in realtime and offline mode (saved data).
>>> 
>>> It consists of the following macro-components (entirely built on top of
>>> Apache Technologies):
>>> 
>>> - Realtime and Enrichments (Kafka and Storm): Realtime configuration and
>>> visualization of data coming from sources with the possibility of defining
>>> e

Re: Looking for a champion: HyperIoT

2023-01-12 Thread Calvin Kirs

On Thu, Jan 12, 2023 at 9:22 PM Christofer Dutz
 wrote:
>
> Hi all,
>
> well … it being used is not a requirement … some projects have been joining 
> Apache even without a single user, but we want at least a minimum on 
> community around it.

Having said that, I would still recommend trying open source before
considering an incubator first, to first make sure that open source is
really the way to go for you.
>
> As I’m really into the (I)IoT topic and I currently have one Mentoring slot 
> open … I would be raising my hand for being interested to help.
>
> Give me a bit of time to read up on what the project is about.
>
> Chris
>
>
> From: Enrico Olivelli 
> Date: Thursday, 12. January 2023 at 11:26
> To: general@incubator.apache.org 
> Subject: Re: Looking for a champion: HyperIoT
> Piergiorgio,
> Is this project already OSS ?
> Is this project already used by other companies?
>
> If it doesn't meet those requirements I don't think that it will have
> a happy story in the Incubator.
>
> I have never been a Mentor for an incubating project but I have been
> following this list for quite some time,
> and my understanding is that a project that wants to enter the ASF
> MUST already be an OSS project with active users.
>
> just my 2 cents
> Enrico
>
> Il giorno gio 12 gen 2023 alle ore 09:17 tison 
> ha scritto:
> >
> > > I'm an ASF Member, I could also help here for writing the proposal but I'm
> > > not a PMC member for the Incubator project, I'm a committer for my past
> > > incubation experience related to Apache ManifoldCF.
> >
> > FYI, as an ASF Member, you can request to become a IPMC member anytime:
> >
> > > Individuals may be nominated to join the IPMC after a vote which passes.
> > Individuals may choose to bring themselves or others to the attention of
> > the IPMC. Additionally, any Member of the Apache Software Foundation may
> > join the IPMC by request.
> >
> > ... from https://incubator.apache.org/guides/roles_and_responsibilities.html
> > .
> >
> > Best,
> > tison.
> >
> >
> > Piergiorgio Lucidi  于2023年1月12日周四 16:06写道：
> >
> > > Hi folks,
> > >
> > > ACSoftware contacted me because they would like to donate their platform
> > > named HyperIoT to the Foundation. I'm searching for a champion to build 
> > > the
> > > incubation proposal.
> > >
> > > I'm an ASF Member, I could also help here for writing the proposal but I'm
> > > not a PMC member for the Incubator project, I'm a committer for my past
> > > incubation experience related to Apache ManifoldCF.
> > >
> > > They currently published only the backend services on their GitHub account
> > > but they are going to also share all the UI modules:
> > > https://github.com/ACSoftwareTeam/HyperIoT-Platform
> > >
> > > You can find more information and some screenshots here:
> > > https://hyperiot.cloud/
> > >
> > > Below is an overview of this platform.
> > >
> > > HyperIoT is an OpenSource Cloud Native platform entirely based on Apache
> > > Technologies for managing big data from any IoT network.
> > > The platform captures the information sent from any source by managing 
> > > data
> > > compression, running statistics or machine/deep learning algorithms,
> > > presenting data to the end user in realtime and offline mode (saved data).
> > >
> > > It consists of the following macro-components (entirely built on top of
> > > Apache Technologies):
> > >
> > > - Realtime and Enrichments (Kafka and Storm): Realtime configuration and
> > > visualization of data coming from sources with the possibility of defining
> > > enrichment rules on incoming data
> > >
> > > - Events and Alarm Management (Storm): Data are analyzed in real time with
> > > the possibility of reporting any alarms by sending timely notifications
> > > either to the device or using other channels such as email
> > >
> > > - Persistence (HBase and Hadoop) : Data is saved in a secure mode
> > >
> > > - Statistics and Machine Learning (Apache Spark): It is possible to run
> > > periodically, on the saved data, machine learning algorithms or generic
> > > statistics presenting the results of these computations in the user's
> > > dashboard.
> > >
> > > HyperIoT cloud infrastructure constitutes a generic server-side
> > > architecture suitable for cross-cutting applications in various
> > > manufactu

Re: Looking for a champion: HyperIoT

2023-01-12 Thread Christofer Dutz

Hi,

So, I did have a look at the website and indeed it looks interesting.
However, when I looked at the GitHub repo and the GPL2 yelled at me.

Are you able to do a re-licensing? I mean … can you ask everyone who 
contributed to the project if they agree to re-licensing it under the Apache 
2.0 license?

If that’s not possible, I guess this is the end of the line for Apache. If it’s 
possible I am still keeping my hand up for being your Mentor and possibly 
championing the project.

Chris



From: Christofer Dutz 
Date: Thursday, 12. January 2023 at 14:22
To: general@incubator.apache.org 
Subject: Re: Looking for a champion: HyperIoT
Hi all,

well … it being used is not a requirement … some projects have been joining 
Apache even without a single user, but we want at least a minimum on community 
around it.

As I’m really into the (I)IoT topic and I currently have one Mentoring slot 
open … I would be raising my hand for being interested to help.

Give me a bit of time to read up on what the project is about.

Chris


From: Enrico Olivelli 
Date: Thursday, 12. January 2023 at 11:26
To: general@incubator.apache.org 
Subject: Re: Looking for a champion: HyperIoT
Piergiorgio,
Is this project already OSS ?
Is this project already used by other companies?

If it doesn't meet those requirements I don't think that it will have
a happy story in the Incubator.

I have never been a Mentor for an incubating project but I have been
following this list for quite some time,
and my understanding is that a project that wants to enter the ASF
MUST already be an OSS project with active users.

just my 2 cents
Enrico

Il giorno gio 12 gen 2023 alle ore 09:17 tison 
ha scritto:
>
> > I'm an ASF Member, I could also help here for writing the proposal but I'm
> > not a PMC member for the Incubator project, I'm a committer for my past
> > incubation experience related to Apache ManifoldCF.
>
> FYI, as an ASF Member, you can request to become a IPMC member anytime:
>
> > Individuals may be nominated to join the IPMC after a vote which passes.
> Individuals may choose to bring themselves or others to the attention of
> the IPMC. Additionally, any Member of the Apache Software Foundation may
> join the IPMC by request.
>
> ... from https://incubator.apache.org/guides/roles_and_responsibilities.html
> .
>
> Best,
> tison.
>
>
> Piergiorgio Lucidi  于2023年1月12日周四 16:06写道：
>
> > Hi folks,
> >
> > ACSoftware contacted me because they would like to donate their platform
> > named HyperIoT to the Foundation. I'm searching for a champion to build the
> > incubation proposal.
> >
> > I'm an ASF Member, I could also help here for writing the proposal but I'm
> > not a PMC member for the Incubator project, I'm a committer for my past
> > incubation experience related to Apache ManifoldCF.
> >
> > They currently published only the backend services on their GitHub account
> > but they are going to also share all the UI modules:
> > https://github.com/ACSoftwareTeam/HyperIoT-Platform
> >
> > You can find more information and some screenshots here:
> > https://hyperiot.cloud/
> >
> > Below is an overview of this platform.
> >
> > HyperIoT is an OpenSource Cloud Native platform entirely based on Apache
> > Technologies for managing big data from any IoT network.
> > The platform captures the information sent from any source by managing data
> > compression, running statistics or machine/deep learning algorithms,
> > presenting data to the end user in realtime and offline mode (saved data).
> >
> > It consists of the following macro-components (entirely built on top of
> > Apache Technologies):
> >
> > - Realtime and Enrichments (Kafka and Storm): Realtime configuration and
> > visualization of data coming from sources with the possibility of defining
> > enrichment rules on incoming data
> >
> > - Events and Alarm Management (Storm): Data are analyzed in real time with
> > the possibility of reporting any alarms by sending timely notifications
> > either to the device or using other channels such as email
> >
> > - Persistence (HBase and Hadoop) : Data is saved in a secure mode
> >
> > - Statistics and Machine Learning (Apache Spark): It is possible to run
> > periodically, on the saved data, machine learning algorithms or generic
> > statistics presenting the results of these computations in the user's
> > dashboard.
> >
> > HyperIoT cloud infrastructure constitutes a generic server-side
> > architecture suitable for cross-cutting applications in various
> > manufacturing sectors. The infrastructure allows a user, without the
> > intervention of external developers, to be able to:
> >
&g

Re: Looking for a champion: HyperIoT

2023-01-12 Thread Christofer Dutz

Hi all,

well … it being used is not a requirement … some projects have been joining 
Apache even without a single user, but we want at least a minimum on community 
around it.

As I’m really into the (I)IoT topic and I currently have one Mentoring slot 
open … I would be raising my hand for being interested to help.

Give me a bit of time to read up on what the project is about.

Chris


From: Enrico Olivelli 
Date: Thursday, 12. January 2023 at 11:26
To: general@incubator.apache.org 
Subject: Re: Looking for a champion: HyperIoT
Piergiorgio,
Is this project already OSS ?
Is this project already used by other companies?

If it doesn't meet those requirements I don't think that it will have
a happy story in the Incubator.

I have never been a Mentor for an incubating project but I have been
following this list for quite some time,
and my understanding is that a project that wants to enter the ASF
MUST already be an OSS project with active users.

just my 2 cents
Enrico

Il giorno gio 12 gen 2023 alle ore 09:17 tison 
ha scritto:
>
> > I'm an ASF Member, I could also help here for writing the proposal but I'm
> > not a PMC member for the Incubator project, I'm a committer for my past
> > incubation experience related to Apache ManifoldCF.
>
> FYI, as an ASF Member, you can request to become a IPMC member anytime:
>
> > Individuals may be nominated to join the IPMC after a vote which passes.
> Individuals may choose to bring themselves or others to the attention of
> the IPMC. Additionally, any Member of the Apache Software Foundation may
> join the IPMC by request.
>
> ... from https://incubator.apache.org/guides/roles_and_responsibilities.html
> .
>
> Best,
> tison.
>
>
> Piergiorgio Lucidi  于2023年1月12日周四 16:06写道：
>
> > Hi folks,
> >
> > ACSoftware contacted me because they would like to donate their platform
> > named HyperIoT to the Foundation. I'm searching for a champion to build the
> > incubation proposal.
> >
> > I'm an ASF Member, I could also help here for writing the proposal but I'm
> > not a PMC member for the Incubator project, I'm a committer for my past
> > incubation experience related to Apache ManifoldCF.
> >
> > They currently published only the backend services on their GitHub account
> > but they are going to also share all the UI modules:
> > https://github.com/ACSoftwareTeam/HyperIoT-Platform
> >
> > You can find more information and some screenshots here:
> > https://hyperiot.cloud/
> >
> > Below is an overview of this platform.
> >
> > HyperIoT is an OpenSource Cloud Native platform entirely based on Apache
> > Technologies for managing big data from any IoT network.
> > The platform captures the information sent from any source by managing data
> > compression, running statistics or machine/deep learning algorithms,
> > presenting data to the end user in realtime and offline mode (saved data).
> >
> > It consists of the following macro-components (entirely built on top of
> > Apache Technologies):
> >
> > - Realtime and Enrichments (Kafka and Storm): Realtime configuration and
> > visualization of data coming from sources with the possibility of defining
> > enrichment rules on incoming data
> >
> > - Events and Alarm Management (Storm): Data are analyzed in real time with
> > the possibility of reporting any alarms by sending timely notifications
> > either to the device or using other channels such as email
> >
> > - Persistence (HBase and Hadoop) : Data is saved in a secure mode
> >
> > - Statistics and Machine Learning (Apache Spark): It is possible to run
> > periodically, on the saved data, machine learning algorithms or generic
> > statistics presenting the results of these computations in the user's
> > dashboard.
> >
> > HyperIoT cloud infrastructure constitutes a generic server-side
> > architecture suitable for cross-cutting applications in various
> > manufacturing sectors. The infrastructure allows a user, without the
> > intervention of external developers, to be able to:
> >
> > - Configure communication between the IoT network and the cloud (without
> > writing code but following graphically guided processes)
> > - Have a set of predefined statistics for the data being processed
> > - Upload your own analytics algorithms (for more technical users)
> > - Access an intuitive web interface for configurations and access to
> > real-time and historical data via different graphical widgets
> > - Share the information collected
> >
> > The easy use of the platform through graphically guided processes allows it
> > to be used even by personnel

Re: Looking for a champion: HyperIoT

2023-01-12 Thread Enrico Olivelli

Piergiorgio,
Is this project already OSS ?
Is this project already used by other companies?

If it doesn't meet those requirements I don't think that it will have
a happy story in the Incubator.

I have never been a Mentor for an incubating project but I have been
following this list for quite some time,
and my understanding is that a project that wants to enter the ASF
MUST already be an OSS project with active users.

just my 2 cents
Enrico

Il giorno gio 12 gen 2023 alle ore 09:17 tison 
ha scritto:
>
> > I'm an ASF Member, I could also help here for writing the proposal but I'm
> > not a PMC member for the Incubator project, I'm a committer for my past
> > incubation experience related to Apache ManifoldCF.
>
> FYI, as an ASF Member, you can request to become a IPMC member anytime:
>
> > Individuals may be nominated to join the IPMC after a vote which passes.
> Individuals may choose to bring themselves or others to the attention of
> the IPMC. Additionally, any Member of the Apache Software Foundation may
> join the IPMC by request.
>
> ... from https://incubator.apache.org/guides/roles_and_responsibilities.html
> .
>
> Best,
> tison.
>
>
> Piergiorgio Lucidi  于2023年1月12日周四 16:06写道：
>
> > Hi folks,
> >
> > ACSoftware contacted me because they would like to donate their platform
> > named HyperIoT to the Foundation. I'm searching for a champion to build the
> > incubation proposal.
> >
> > I'm an ASF Member, I could also help here for writing the proposal but I'm
> > not a PMC member for the Incubator project, I'm a committer for my past
> > incubation experience related to Apache ManifoldCF.
> >
> > They currently published only the backend services on their GitHub account
> > but they are going to also share all the UI modules:
> > https://github.com/ACSoftwareTeam/HyperIoT-Platform
> >
> > You can find more information and some screenshots here:
> > https://hyperiot.cloud/
> >
> > Below is an overview of this platform.
> >
> > HyperIoT is an OpenSource Cloud Native platform entirely based on Apache
> > Technologies for managing big data from any IoT network.
> > The platform captures the information sent from any source by managing data
> > compression, running statistics or machine/deep learning algorithms,
> > presenting data to the end user in realtime and offline mode (saved data).
> >
> > It consists of the following macro-components (entirely built on top of
> > Apache Technologies):
> >
> > - Realtime and Enrichments (Kafka and Storm): Realtime configuration and
> > visualization of data coming from sources with the possibility of defining
> > enrichment rules on incoming data
> >
> > - Events and Alarm Management (Storm): Data are analyzed in real time with
> > the possibility of reporting any alarms by sending timely notifications
> > either to the device or using other channels such as email
> >
> > - Persistence (HBase and Hadoop) : Data is saved in a secure mode
> >
> > - Statistics and Machine Learning (Apache Spark): It is possible to run
> > periodically, on the saved data, machine learning algorithms or generic
> > statistics presenting the results of these computations in the user's
> > dashboard.
> >
> > HyperIoT cloud infrastructure constitutes a generic server-side
> > architecture suitable for cross-cutting applications in various
> > manufacturing sectors. The infrastructure allows a user, without the
> > intervention of external developers, to be able to:
> >
> > - Configure communication between the IoT network and the cloud (without
> > writing code but following graphically guided processes)
> > - Have a set of predefined statistics for the data being processed
> > - Upload your own analytics algorithms (for more technical users)
> > - Access an intuitive web interface for configurations and access to
> > real-time and historical data via different graphical widgets
> > - Share the information collected
> >
> > The easy use of the platform through graphically guided processes allows it
> > to be used even by personnel who do not have specific knowledge about IoT
> > topics, data streaming, big data, etc...
> >
> > This will help spread the benefits of IoT and Industry 4.0 technologies
> > even to personnel who are not exactly experts.
> >
> > Thank you for your support.
> >
> > Cheers,
> > PJ
> >
> > --
> > Piergiorgio
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Looking for a champion: HyperIoT

2023-01-12 Thread tison

> I'm an ASF Member, I could also help here for writing the proposal but I'm
> not a PMC member for the Incubator project, I'm a committer for my past
> incubation experience related to Apache ManifoldCF.

FYI, as an ASF Member, you can request to become a IPMC member anytime:

> Individuals may be nominated to join the IPMC after a vote which passes.
Individuals may choose to bring themselves or others to the attention of
the IPMC. Additionally, any Member of the Apache Software Foundation may
join the IPMC by request.

... from https://incubator.apache.org/guides/roles_and_responsibilities.html
.

Best,
tison.


Piergiorgio Lucidi  于2023年1月12日周四 16:06写道：

> Hi folks,
>
> ACSoftware contacted me because they would like to donate their platform
> named HyperIoT to the Foundation. I'm searching for a champion to build the
> incubation proposal.
>
> I'm an ASF Member, I could also help here for writing the proposal but I'm
> not a PMC member for the Incubator project, I'm a committer for my past
> incubation experience related to Apache ManifoldCF.
>
> They currently published only the backend services on their GitHub account
> but they are going to also share all the UI modules:
> https://github.com/ACSoftwareTeam/HyperIoT-Platform
>
> You can find more information and some screenshots here:
> https://hyperiot.cloud/
>
> Below is an overview of this platform.
>
> HyperIoT is an OpenSource Cloud Native platform entirely based on Apache
> Technologies for managing big data from any IoT network.
> The platform captures the information sent from any source by managing data
> compression, running statistics or machine/deep learning algorithms,
> presenting data to the end user in realtime and offline mode (saved data).
>
> It consists of the following macro-components (entirely built on top of
> Apache Technologies):
>
> - Realtime and Enrichments (Kafka and Storm): Realtime configuration and
> visualization of data coming from sources with the possibility of defining
> enrichment rules on incoming data
>
> - Events and Alarm Management (Storm): Data are analyzed in real time with
> the possibility of reporting any alarms by sending timely notifications
> either to the device or using other channels such as email
>
> - Persistence (HBase and Hadoop) : Data is saved in a secure mode
>
> - Statistics and Machine Learning (Apache Spark): It is possible to run
> periodically, on the saved data, machine learning algorithms or generic
> statistics presenting the results of these computations in the user's
> dashboard.
>
> HyperIoT cloud infrastructure constitutes a generic server-side
> architecture suitable for cross-cutting applications in various
> manufacturing sectors. The infrastructure allows a user, without the
> intervention of external developers, to be able to:
>
> - Configure communication between the IoT network and the cloud (without
> writing code but following graphically guided processes)
> - Have a set of predefined statistics for the data being processed
> - Upload your own analytics algorithms (for more technical users)
> - Access an intuitive web interface for configurations and access to
> real-time and historical data via different graphical widgets
> - Share the information collected
>
> The easy use of the platform through graphically guided processes allows it
> to be used even by personnel who do not have specific knowledge about IoT
> topics, data streaming, big data, etc...
>
> This will help spread the benefits of IoT and Industry 4.0 technologies
> even to personnel who are not exactly experts.
>
> Thank you for your support.
>
> Cheers,
> PJ
>
> --
> Piergiorgio
>

Re: Looking for a Champion: FuzzyLite

2023-01-05 Thread Jason Porter

Oh, you are correct. I am so sorry.

Jason Porter
Software Engineer
He/Him/His

IBM

On Jan 5, 2023, at 08:54, Eric Covener  wrote:

On Thu, Jan 5, 2023 at 10:52 AM Jason Porter  wrote:

We do have a list of initial committers willing to work on the project. I’m not 
sure what you’re suggesting we’re missing.

Jason Porter

This thread is about a different proposal.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Looking for a Champion: FuzzyLite

2023-01-05 Thread Eric Covener

On Thu, Jan 5, 2023 at 10:52 AM Jason Porter  wrote:
>
> We do have a list of initial committers willing to work on the project. I’m 
> not sure what you’re suggesting we’re missing.
>
> Jason Porter

This thread is about a different proposal.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Looking for a Champion: FuzzyLite

2023-01-05 Thread Jason Porter

We do have a list of initial committers willing to work on the project. I’m not 
sure what you’re suggesting we’re missing.

Jason Porter
Software Engineer
He/Him/His

IBM

On Jan 5, 2023, at 08:44, PJ Fanning  wrote:

Hi Juan,
I'm willing to assist with putting together a proposal for admission to the 
Incubator.

You might notice in this Pekko example [1] and other proposals include a team 
of initial contributors. The rules within which Incubator podlings operate 
require that you have at least 3 individuals willing to vote on releases and 
such like.

I still think it might make sense to try to attract some volunteers before 
proceeding with creating the proposal. The Pekko team publicised the project in 
Github and on Social Media and was able to get a number of volunteers in this 
way.

[1] https://cwiki.apache.org/confluence/display/INCUBATOR/PekkoProposal
[2] https://github.com/mdedetrich/akka-apache-project/discussions/3

Do you think this is an ok way to proceed?

Regards,
PJ



On 2022/12/20 22:23:31 Juan Rada-Vilela wrote:
Hi PJ,

Thanks for your email.

Only a few people have contributed, and not constantly. I have been the
main driver of the engineering efforts.

I am thinking of Apache as a way to start a community and keep the
development on the projects more active.

Juan.


On Wed, 21 Dec 2022 at 01:06, PJ Fanning  wrote:

Resending and including OP, just in case.

-- Forwarded message -
From: PJ Fanning 
Date: Tue, 20 Dec 2022 at 13:02
Subject: Re: Looking for a Champion: FuzzyLite
To: 


Thanks Juan for your interest in contributing this work to the ASF.

I have a question about whether there are any other people who have
contributed to FuzzyLite and if they would be interested in continuing
to contribute as part of a FuzzyLite PMC?

One of the most important aspects of an ASF project is building a
community.

On Tue, 20 Dec 2022 at 08:29, Juan Rada-Vilela  wrote:

Hi,

I have created over the past years three projects: fuzzylite (C++),
jfuzzylite (Java), and pyfuzzylite (Python), which are well designed and
engineered libraries for fuzzy logic controllers, a field within
Artificial
Intelligence. Their repositories are in github.com/fuzzylite, and the
home
page is fuzzylite.com

I am considering having them for incubation at Apache, so I am looking
for
a Champion to first find  if there is interest in the ASF, and maybe
start
with one?

Kind regards,

Juan.



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Looking for a Champion: FuzzyLite

2023-01-05 Thread PJ Fanning

Hi Juan,
I'm willing to assist with putting together a proposal for admission to the 
Incubator.

You might notice in this Pekko example [1] and other proposals include a team 
of initial contributors. The rules within which Incubator podlings operate 
require that you have at least 3 individuals willing to vote on releases and 
such like.

I still think it might make sense to try to attract some volunteers before 
proceeding with creating the proposal. The Pekko team publicised the project in 
Github and on Social Media and was able to get a number of volunteers in this 
way.

[1] https://cwiki.apache.org/confluence/display/INCUBATOR/PekkoProposal 
[2] https://github.com/mdedetrich/akka-apache-project/discussions/3

Do you think this is an ok way to proceed?

Regards,
PJ



On 2022/12/20 22:23:31 Juan Rada-Vilela wrote:
> Hi PJ,
> 
> Thanks for your email.
> 
> Only a few people have contributed, and not constantly. I have been the
> main driver of the engineering efforts.
> 
> I am thinking of Apache as a way to start a community and keep the
> development on the projects more active.
> 
> Juan.
> 
> 
> On Wed, 21 Dec 2022 at 01:06, PJ Fanning  wrote:
> 
> > Resending and including OP, just in case.
> >
> > -- Forwarded message -
> > From: PJ Fanning 
> > Date: Tue, 20 Dec 2022 at 13:02
> > Subject: Re: Looking for a Champion: FuzzyLite
> > To: 
> >
> >
> > Thanks Juan for your interest in contributing this work to the ASF.
> >
> > I have a question about whether there are any other people who have
> > contributed to FuzzyLite and if they would be interested in continuing
> > to contribute as part of a FuzzyLite PMC?
> >
> > One of the most important aspects of an ASF project is building a
> > community.
> >
> > On Tue, 20 Dec 2022 at 08:29, Juan Rada-Vilela  wrote:
> > >
> > > Hi,
> > >
> > > I have created over the past years three projects: fuzzylite (C++),
> > > jfuzzylite (Java), and pyfuzzylite (Python), which are well designed and
> > > engineered libraries for fuzzy logic controllers, a field within
> > Artificial
> > > Intelligence. Their repositories are in github.com/fuzzylite, and the
> > home
> > > page is fuzzylite.com
> > >
> > > I am considering having them for incubation at Apache, so I am looking
> > for
> > > a Champion to first find  if there is interest in the ASF, and maybe
> > start
> > > with one?
> > >
> > > Kind regards,
> > >
> > > Juan.
> >
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Looking for a Champion: FuzzyLite

2022-12-20 Thread Juan Rada-Vilela

Hi PJ,

Thanks for your email.

Only a few people have contributed, and not constantly. I have been the
main driver of the engineering efforts.

I am thinking of Apache as a way to start a community and keep the
development on the projects more active.

Juan.


On Wed, 21 Dec 2022 at 01:06, PJ Fanning  wrote:

> Resending and including OP, just in case.
>
> -- Forwarded message -
> From: PJ Fanning 
> Date: Tue, 20 Dec 2022 at 13:02
> Subject: Re: Looking for a Champion: FuzzyLite
> To: 
>
>
> Thanks Juan for your interest in contributing this work to the ASF.
>
> I have a question about whether there are any other people who have
> contributed to FuzzyLite and if they would be interested in continuing
> to contribute as part of a FuzzyLite PMC?
>
> One of the most important aspects of an ASF project is building a
> community.
>
> On Tue, 20 Dec 2022 at 08:29, Juan Rada-Vilela  wrote:
> >
> > Hi,
> >
> > I have created over the past years three projects: fuzzylite (C++),
> > jfuzzylite (Java), and pyfuzzylite (Python), which are well designed and
> > engineered libraries for fuzzy logic controllers, a field within
> Artificial
> > Intelligence. Their repositories are in github.com/fuzzylite, and the
> home
> > page is fuzzylite.com
> >
> > I am considering having them for incubation at Apache, so I am looking
> for
> > a Champion to first find  if there is interest in the ASF, and maybe
> start
> > with one?
> >
> > Kind regards,
> >
> > Juan.
>

Re: Looking for a Champion: FuzzyLite

2022-12-20 Thread PJ Fanning

Thanks Juan for your interest in contributing this work to the ASF.

I have a question about whether there are any other people who have
contributed to FuzzyLite and if they would be interested in continuing
to contribute as part of a FuzzyLite PMC?

One of the most important aspects of an ASF project is building a community.

On Tue, 20 Dec 2022 at 08:29, Juan Rada-Vilela  wrote:
>
> Hi,
>
> I have created over the past years three projects: fuzzylite (C++),
> jfuzzylite (Java), and pyfuzzylite (Python), which are well designed and
> engineered libraries for fuzzy logic controllers, a field within Artificial
> Intelligence. Their repositories are in github.com/fuzzylite, and the home
> page is fuzzylite.com
>
> I am considering having them for incubation at Apache, so I am looking for
> a Champion to first find  if there is interest in the ASF, and maybe start
> with one?
>
> Kind regards,
>
> Juan.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Looking for a champion: resurrect log4j 1.x

2022-01-09 Thread Ralph Goers

Justin, 

See https://lists.apache.org/thread/fz19gsjnlh84nxgxj0jyy2rzrol1dx9b 
 and 
https://twitter.com/qos_ch/status/1479938932213223424 
.

However, it is worth noting that https://github.com/albfernandez/log4j/ 
 has had a release in Maven Central for 
2 years and published 2 releases in the last month.

Ralph

> On Jan 9, 2022, at 12:35 AM, Justin Mclean  wrote:
> 
> Hi,
> 
> The incubation list for for conversations about new project proposals, 
> releases and graduations and similar things. I think this thread has got off 
> topic and you should probably carry on the conversation back on the logging 
> project lists.
> 
> Building a community around EOLed software, even if it is used would be 
> difficult. However, there is nothing stopping people who are interested 
> forking log4j 1.x and working on it elsewhere. Has that option been 
> considered?
> 
> Kind Regards,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
>

Re: Looking for a champion: resurrect log4j 1.x

2022-01-08 Thread Justin Mclean

Hi,

The incubation list for for conversations about new project proposals, releases 
and graduations and similar things. I think this thread has got off topic and 
you should probably carry on the conversation back on the logging project lists.

Building a community around EOLed software, even if it is used would be 
difficult. However, there is nothing stopping people who are interested forking 
log4j 1.x and working on it elsewhere. Has that option been considered?

Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Looking for a champion: resurrect log4j 1.x

The JMSAppender is an optional module. I think you will get the distinction. It 
doesn’t break the world to remove it, unlike changing the class hierarchy of 
Appender or removing a method on an extension interface used by same, I think 
the distinction is clear. We might find agreement in the response to concern 
about removal as “this is a maintenance version, you will need to upgrade”. The 
key is to take a practical approach to what the users are asking for now not a 
perhaps cleaner but absolutist position that strands and frustrates them. What 
we (users) are doing in the wild is simply taking the last log4j 1 release, 
removing JMSAppender.class from the JAR, and publishing them to our Nexus or 
whatever with a modified version. This is what regulators and compliance 
officers will care about. It is being done as a stopgap and I can’t say if it 
would be acceptable or not as a final solution. My guess is not, for what it’s 
worth. A release by the foundation would. Users do not need all theoretical CVE 
worthy issues addressed at at once, just the one. Just like many have avoided 
the concurrency issues listed earlier and don’t need up front solutions for 
those either. Just a new release without JMSAppender. 

> On Jan 8, 2022, at 6:34 PM, Matt Sicker  wrote:
> 
> 
>>> On Jan 8, 2022, at 19:39, Andrew Purtell  wrote:
>>> 
>>> Are you using the JMS appender? Are you using the socket receiver? If the
>> answer is no to those questions, you don’t have security concerns besides
>> the more glaring fact that you’re depending on end of life software that
>> has been marked as such for going on 7 years now.
>> 
>> I know you keep returning to the end of life designation in these
>> discussions, but do not acknowledge that the users of this EOL version were
>> deliberately stranded by incompatible API and configuration file formats.
>> There is a reason we are stuck on Log4J 1. I wish you could just hear this,
>> acknowledge it, and service the concerns of users in this regard without
>> the dictatorial attitude by continuing to release version 1 with security
>> fixes applied. That's all I think interested parties here want.
> 
> Which security fixes? Part of the EOL status has meant that anytime someone 
> has tried reporting a new security vulnerability in log4j1, we’ve informed 
> them that the version is EOL. No new CVEs published. Being EOL, less security 
> review is being done other than thorough audits of old software. This would 
> be like opening Pandora’s Box, and that’s one of the reasons why software is 
> sometimes effectively abandoned before being declared end of life.
> 
>> My employer, for example, will be forced to accommodate government
>> compliance officers' demands for a CVE-free version of Log4J to be included
>> in our products. If Log4J 1 were to satisfy that requirement, this
>> necessitates at least a release of 1 without the JMSAppender or with the
>> JNDI issues therein addressed some other way. (I would advocate removal.)
> 
> So you couldn’t upgrade to version 2 due to incompatibility (which still has 
> no concrete examples; did you know that we’ve improved compatibility several 
> times since version 2.0?), yet right out of the gate you want to break 
> compatibility in version 1 by just nuking a feature.
> 
>> Since I volunteered on this thread to maintain a resurrected Log4J 1 --
>> whatever form that would take can be debated, it's not material for this
>> point -- this would be the maintenance philosophy I would adopt or
>> advocate, for what it is worth:
>> 
>>  - Start with latest/last Log4J 1 release.
>>  - Security vulnerabilities addressed. JMSAppender to be immediately
>>  removed.
> 
> To be more constructive, I’d suggest following the compatibility-oriented 
> philosophy of guarding this class with a feature flag to opt in. Being such 
> an old library used so extensively, there are bound to be a non-trivial 
> number of legitimate users of this appender.
> 
>>  - Pay down the build system tech debt - migrate to Maven 3.
> 
> That would be expected; I wouldn’t want anyone to have to dig up ancient VMs 
> just to build and release the project!
> 
>>  - No API changes.
> 
> This makes sense of course, but I should note that one of the historical 
> reasons why both Logback and Log4j2 exist is because Log4j1 doesn’t have a 
> clear delineation between its API and implementation, and some problems 
> cannot be fixed without breaking the effective API.
> 
>>  - No new appenders.
>>  - Additional security fixes as required. Typical 'maintenance mode'
>>  stuff.
> 
> Given the limited changes desired (which mostly sound fine otherwise), I 
> don’t have a real problem with doing this. Not everyone on the PMC has the 
> same opinions, but we all agreed on making it EOL. One of the recurring 
> concerns, though, was that continued maintenance of version 1 in any form 
> will require adding someone to the PMC to oversee that as no one else in the 
> current PMC wants

Re: Looking for a champion: resurrect log4j 1.x

> On Jan 8, 2022, at 19:39, Andrew Purtell  wrote:
> 
>> Are you using the JMS appender? Are you using the socket receiver? If the
> answer is no to those questions, you don’t have security concerns besides
> the more glaring fact that you’re depending on end of life software that
> has been marked as such for going on 7 years now.
> 
> I know you keep returning to the end of life designation in these
> discussions, but do not acknowledge that the users of this EOL version were
> deliberately stranded by incompatible API and configuration file formats.
> There is a reason we are stuck on Log4J 1. I wish you could just hear this,
> acknowledge it, and service the concerns of users in this regard without
> the dictatorial attitude by continuing to release version 1 with security
> fixes applied. That's all I think interested parties here want.

Which security fixes? Part of the EOL status has meant that anytime someone has 
tried reporting a new security vulnerability in log4j1, we’ve informed them 
that the version is EOL. No new CVEs published. Being EOL, less security review 
is being done other than thorough audits of old software. This would be like 
opening Pandora’s Box, and that’s one of the reasons why software is sometimes 
effectively abandoned before being declared end of life.

> My employer, for example, will be forced to accommodate government
> compliance officers' demands for a CVE-free version of Log4J to be included
> in our products. If Log4J 1 were to satisfy that requirement, this
> necessitates at least a release of 1 without the JMSAppender or with the
> JNDI issues therein addressed some other way. (I would advocate removal.)

So you couldn’t upgrade to version 2 due to incompatibility (which still has no 
concrete examples; did you know that we’ve improved compatibility several times 
since version 2.0?), yet right out of the gate you want to break compatibility 
in version 1 by just nuking a feature.

> Since I volunteered on this thread to maintain a resurrected Log4J 1 --
> whatever form that would take can be debated, it's not material for this
> point -- this would be the maintenance philosophy I would adopt or
> advocate, for what it is worth:
> 
>   - Start with latest/last Log4J 1 release.
>   - Security vulnerabilities addressed. JMSAppender to be immediately
>   removed.

To be more constructive, I’d suggest following the compatibility-oriented 
philosophy of guarding this class with a feature flag to opt in. Being such an 
old library used so extensively, there are bound to be a non-trivial number of 
legitimate users of this appender.

>   - Pay down the build system tech debt - migrate to Maven 3.

That would be expected; I wouldn’t want anyone to have to dig up ancient VMs 
just to build and release the project!

>   - No API changes.

This makes sense of course, but I should note that one of the historical 
reasons why both Logback and Log4j2 exist is because Log4j1 doesn’t have a 
clear delineation between its API and implementation, and some problems cannot 
be fixed without breaking the effective API.

>   - No new appenders.
>   - Additional security fixes as required. Typical 'maintenance mode'
>   stuff.

Given the limited changes desired (which mostly sound fine otherwise), I don’t 
have a real problem with doing this. Not everyone on the PMC has the same 
opinions, but we all agreed on making it EOL. One of the recurring concerns, 
though, was that continued maintenance of version 1 in any form will require 
adding someone to the PMC to oversee that as no one else in the current PMC 
wants to do the release work. Joining the PMC isn’t a trivial thing; it 
requires some sustained commitment to the project by first becoming a committer 
and then being invited to the PMC. This is also why I’ve suggested it could 
help to contribute to the backward compatibility of version 2 as a related way 
to do something that could easily lead to becoming a committer.

> I have lurked in some discussion here and elsewhere and I really don't see
> that much daylight between the Logging PMCs position on 1 and what users
> like myself want of it. I hear concerns about resurrecting 1 that seem
> focused on some theoretical future development of 1 that I don't think
> anyone is actually interested in doing. If I can be said to be
> representative of a Log4J 1 user that would like to stay on 1, the vision
> is "just fix security bugs, please, we will upgrade or migrate to something
> else someday, don't change API or configuration file formats, thanks".
> There exists the possibility that some day a theoretical required security
> fix cannot be accomplished without a breaking change. We can cross that
> bridge when and if we come to it. It may never happen. Or, it might, and
> then 1 has truly reached the end of the road.

Deleting those appenders is a breaking change. And I suspect fixing some things 
might be breaking changes based on the history of the PMC here:

Re: Looking for a champion: resurrect log4j 1.x

2022-01-08 Thread Dave Fisher

In this current form this discussion belongs either on dev@logging or board@.

Several people here are perfectly capable of forming a proposal, but are 
choosing to have an unproductive discussion.

At this point a new podling would be a hostile fork and those are not accepted.

Sent from my iPhone

> On Jan 8, 2022, at 5:44 PM, Andrew Purtell  wrote:
> 
> The discussion continues here because the Logging PMC is intransigent and
> non-responsive to the concerns already well established by parties on this
> thread. I don't see how this can be resolved without you "giving in".
> Perhaps that is the problem, but I don't want to be an armchair
> psychiatrist, I just want a logging library without known security bugs
> that remains compatible with existing code and configuration formats and
> does not force me to transitively upgrade/rebuild/modify the world.
> 
>> On Sat, Jan 8, 2022 at 5:00 PM Ralph Goers 
>> wrote:
>> 
>> 
>> 
 On Jan 8, 2022, at 4:34 PM, Andrew Purtell  wrote:
>>> 
>>> The Logging PMC is the hostile party here as far as I can tell, operating
>>> in defiance of the community of users that have made the points I have
>> just
>>> written here abundantly clear for years.
>> 
>> The Logging PMC is the owner of Log4j 1.x. We declared it EOL in 2015. Not
>> one single complaint was received nor were any proposals made to the PMC
>> until over 6 years later. This is not the sign of a hostile PMC but one
>> that has
>> moved on from unmaintainable software. Heck, even Ceki abandoned it years
>> before its last release to concentrate on its replacement.
>> 
>> The PMC held a discussion on the dev mailing list. Out of non-PMC members
>> there were very few responses. One person was in favor of reviving the
>> project
>> even to the point of fixing bugs and continuing development beyond just
>> fixing
>> CVEs. Leo Simmons did offer to help. Here is what he said during the
>> discussion:
>> 
>>I think I made clear what I am interested in through several emails
>> and in code.
>>I've also pointed out what I wouldn't do (like step up as a maintainer
>> on a.
>>permanent basis, or incubate something).
>> 
>>I think all the relevant arguments on how to proceed with 1.x have been
>>made (a few times…).
>>I don't have anything new to add.
>>I'll accept the vote outcome.
>> 
>> So we had two people expressing interest, one with no hope of ever being
>> offered
>> commit rights due to his behavior on our lists and in reviewing the other
>> projects
>> he participates on.
>> 
>> So we were left with the choice of us allowing Leo to do that work and us
>> having
>> to spend time reviewing the PRs and applying them. Frankly, none of us
>> were
>> interested enough in this to spend that kind of time, especially since we
>> know at
>> least two usable drop-in replacements for Log4j 1.2 that fix the CVEs
>> already exist.
>> 
>> I seriously think the outcome would have been different had Ceki offered
>> to help
>> while the discussion was going on. Instead, he decided to offer to help
>> after the
>> PMC posted its announcement of the vote results and the reasons why we
>> voted
>> that way.
>> 
>> Since the Logging Services PMC is responsible for Log4j1 I fail to see why
>> a
>> discussion is even continuing on this list. The Logging Services PMC has
>> made
>> clear that it is not going to sponsor a podling for this and the PMC still
>> retains
>> ownership of the code.
>> 
>> Ralph
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 
> 
> -- 
> Best regards,
> Andrew
> 
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>   - A23, Crosstalk


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Looking for a champion: resurrect log4j 1.x

The discussion continues here because the Logging PMC is intransigent and
non-responsive to the concerns already well established by parties on this
thread. I don't see how this can be resolved without you "giving in".
Perhaps that is the problem, but I don't want to be an armchair
psychiatrist, I just want a logging library without known security bugs
that remains compatible with existing code and configuration formats and
does not force me to transitively upgrade/rebuild/modify the world.

On Sat, Jan 8, 2022 at 5:00 PM Ralph Goers 
wrote:

>
>
> > On Jan 8, 2022, at 4:34 PM, Andrew Purtell  wrote:
> >
> > The Logging PMC is the hostile party here as far as I can tell, operating
> > in defiance of the community of users that have made the points I have
> just
> > written here abundantly clear for years.
>
> The Logging PMC is the owner of Log4j 1.x. We declared it EOL in 2015. Not
> one single complaint was received nor were any proposals made to the PMC
> until over 6 years later. This is not the sign of a hostile PMC but one
> that has
> moved on from unmaintainable software. Heck, even Ceki abandoned it years
> before its last release to concentrate on its replacement.
>
> The PMC held a discussion on the dev mailing list. Out of non-PMC members
> there were very few responses. One person was in favor of reviving the
> project
> even to the point of fixing bugs and continuing development beyond just
> fixing
> CVEs. Leo Simmons did offer to help. Here is what he said during the
> discussion:
>
> I think I made clear what I am interested in through several emails
> and in code.
> I've also pointed out what I wouldn't do (like step up as a maintainer
> on a.
> permanent basis, or incubate something).
>
> I think all the relevant arguments on how to proceed with 1.x have been
> made (a few times…).
> I don't have anything new to add.
> I'll accept the vote outcome.
>
> So we had two people expressing interest, one with no hope of ever being
> offered
> commit rights due to his behavior on our lists and in reviewing the other
> projects
> he participates on.
>
> So we were left with the choice of us allowing Leo to do that work and us
> having
> to spend time reviewing the PRs and applying them. Frankly, none of us
> were
> interested enough in this to spend that kind of time, especially since we
> know at
> least two usable drop-in replacements for Log4j 1.2 that fix the CVEs
> already exist.
>
> I seriously think the outcome would have been different had Ceki offered
> to help
> while the discussion was going on. Instead, he decided to offer to help
> after the
> PMC posted its announcement of the vote results and the reasons why we
> voted
> that way.
>
> Since the Logging Services PMC is responsible for Log4j1 I fail to see why
> a
> discussion is even continuing on this list. The Logging Services PMC has
> made
> clear that it is not going to sponsor a podling for this and the PMC still
> retains
> ownership of the code.
>
> Ralph
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
Best regards,
Andrew

Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
   - A23, Crosstalk

Re: Looking for a champion: resurrect log4j 1.x

> Are you using the JMS appender? Are you using the socket receiver? If the
answer is no to those questions, you don’t have security concerns besides
the more glaring fact that you’re depending on end of life software that
has been marked as such for going on 7 years now.

I know you keep returning to the end of life designation in these
discussions, but do not acknowledge that the users of this EOL version were
deliberately stranded by incompatible API and configuration file formats.
There is a reason we are stuck on Log4J 1. I wish you could just hear this,
acknowledge it, and service the concerns of users in this regard without
the dictatorial attitude by continuing to release version 1 with security
fixes applied. That's all I think interested parties here want.

My employer, for example, will be forced to accommodate government
compliance officers' demands for a CVE-free version of Log4J to be included
in our products. If Log4J 1 were to satisfy that requirement, this
necessitates at least a release of 1 without the JMSAppender or with the
JNDI issues therein addressed some other way. (I would advocate removal.)

Since I volunteered on this thread to maintain a resurrected Log4J 1 --
whatever form that would take can be debated, it's not material for this
point -- this would be the maintenance philosophy I would adopt or
advocate, for what it is worth:

   - Start with latest/last Log4J 1 release.
   - Security vulnerabilities addressed. JMSAppender to be immediately
   removed.
   - Pay down the build system tech debt - migrate to Maven 3.
   - No API changes.
   - No new appenders.
   - Additional security fixes as required. Typical 'maintenance mode'
   stuff.

I have lurked in some discussion here and elsewhere and I really don't see
that much daylight between the Logging PMCs position on 1 and what users
like myself want of it. I hear concerns about resurrecting 1 that seem
focused on some theoretical future development of 1 that I don't think
anyone is actually interested in doing. If I can be said to be
representative of a Log4J 1 user that would like to stay on 1, the vision
is "just fix security bugs, please, we will upgrade or migrate to something
else someday, don't change API or configuration file formats, thanks".
There exists the possibility that some day a theoretical required security
fix cannot be accomplished without a breaking change. We can cross that
bridge when and if we come to it. It may never happen. Or, it might, and
then 1 has truly reached the end of the road.

On Sat, Jan 8, 2022 at 4:17 PM Matt Sicker  wrote:

> Answers below:
>
> > On Jan 8, 2022, at 17:34, Andrew Purtell  wrote:
> >
> > Log4J 1 has known concurrency issues but many projects live with them or
> > work around them. For example, several "Big Data" Apache projects have
> been
> > fine with it, themselves internally highly concurrent and performance
> > sensitive. Log4J 1 might not be a Platonic ideal, but certainly good
> > enough, as evidenced by the popularity of those projects, operational in
> > numerous high scale and/or performance sensitive environments.
>
> It’s also a fairly common source of application performance problems that
> leads to reduction in logs being stored and the added difficulty of
> debugging problems with less context. Here are just some of the Bugzilla
> issues you’ve been conveniently ignoring for years:
>
> 50213   Category callAppenders synchronization causes
> java.lang.Thread.State: BLOCKED
> 46878   Deadlock in 1.2.15 caused by AsyncAppender and
> ThrowableInformation classes
> 41214   Deadlock with RollingFileAppender
> 44700   Log4J locks rolled log files (files can’t be deleted)
> 49481   Log4j stops writing to file, and then causes server to lockup
> 50323   Vulnerability in NTEventLogAppender
> 50463   AsyncAppender causing deadlock when dispatcher thread dies
> 50858   Classloader leak when using Log4j in a webapp container such as
> Tomcat, WebLogic
> 52141   [STUCK] ExecuteThread...Blocked trying to get lock:
> org/apache/log4j/Logger@0xc501e0a8[fat lock]
> 54009   Thread is getting Blocked
> 54325   Concurrency issues in AppenderAttachableImpl
>
> > In a perfect world Log4J 2 would have been API compatible and
> configuration
> > format compatible with 1, such that everyone could have migrated years
> ago,
>
> Can you point out any specific incompatibilities? Particularly in the
> current version.
>
> > but the Logging PMC/devs decided otherwise. Whether or not we assess that
> > as desirable, we arrive at the present, with hundreds, perhaps thousands,
> > of open source and internal projects stuck on Log4J 1 due to API or
> > operational compatibility concerns that would carry downstream to their
> > users. No matter what direction one might look (Log4J2, logback, etc.)
> > there are compatibility blockers. Staying with Log4J 1 can be very much
> > acceptable for this reason if the security concerns are addressed.
>
> Are you using the JMS appender? Are you using

Re: Looking for a champion: resurrect log4j 1.x

2022-01-08 Thread Ralph Goers

> On Jan 8, 2022, at 4:34 PM, Andrew Purtell  wrote:
> 
> The Logging PMC is the hostile party here as far as I can tell, operating
> in defiance of the community of users that have made the points I have just
> written here abundantly clear for years.

The Logging PMC is the owner of Log4j 1.x. We declared it EOL in 2015. Not 
one single complaint was received nor were any proposals made to the PMC 
until over 6 years later. This is not the sign of a hostile PMC but one that 
has 
moved on from unmaintainable software. Heck, even Ceki abandoned it years 
before its last release to concentrate on its replacement.

The PMC held a discussion on the dev mailing list. Out of non-PMC members 
there were very few responses. One person was in favor of reviving the project 
even to the point of fixing bugs and continuing development beyond just fixing 
CVEs. Leo Simmons did offer to help. Here is what he said during the discussion:

I think I made clear what I am interested in through several emails and in 
code.
I've also pointed out what I wouldn't do (like step up as a maintainer on 
a.  
permanent basis, or incubate something).

I think all the relevant arguments on how to proceed with 1.x have been
made (a few times…).
I don't have anything new to add.
I'll accept the vote outcome.

So we had two people expressing interest, one with no hope of ever being 
offered 
commit rights due to his behavior on our lists and in reviewing the other 
projects 
he participates on.

So we were left with the choice of us allowing Leo to do that work and us 
having 
to spend time reviewing the PRs and applying them. Frankly, none of us were 
interested enough in this to spend that kind of time, especially since we know 
at 
least two usable drop-in replacements for Log4j 1.2 that fix the CVEs already 
exist.

I seriously think the outcome would have been different had Ceki offered to 
help 
while the discussion was going on. Instead, he decided to offer to help after 
the 
PMC posted its announcement of the vote results and the reasons why we voted 
that way.

Since the Logging Services PMC is responsible for Log4j1 I fail to see why a 
discussion is even continuing on this list. The Logging Services PMC has made 
clear that it is not going to sponsor a podling for this and the PMC still 
retains 
ownership of the code.

Ralph
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Looking for a champion: resurrect log4j 1.x

Answers below:

> On Jan 8, 2022, at 17:34, Andrew Purtell  wrote:
> 
> Log4J 1 has known concurrency issues but many projects live with them or
> work around them. For example, several "Big Data" Apache projects have been
> fine with it, themselves internally highly concurrent and performance
> sensitive. Log4J 1 might not be a Platonic ideal, but certainly good
> enough, as evidenced by the popularity of those projects, operational in
> numerous high scale and/or performance sensitive environments.

It’s also a fairly common source of application performance problems that leads 
to reduction in logs being stored and the added difficulty of debugging 
problems with less context. Here are just some of the Bugzilla issues you’ve 
been conveniently ignoring for years:

50213   Category callAppenders synchronization causes java.lang.Thread.State: 
BLOCKED
46878   Deadlock in 1.2.15 caused by AsyncAppender and ThrowableInformation 
classes
41214   Deadlock with RollingFileAppender
44700   Log4J locks rolled log files (files can’t be deleted)
49481   Log4j stops writing to file, and then causes server to lockup
50323   Vulnerability in NTEventLogAppender
50463   AsyncAppender causing deadlock when dispatcher thread dies
50858   Classloader leak when using Log4j in a webapp container such as Tomcat, 
WebLogic
52141   [STUCK] ExecuteThread...Blocked trying to get lock: 
org/apache/log4j/Logger@0xc501e0a8[fat lock]
54009   Thread is getting Blocked
54325   Concurrency issues in AppenderAttachableImpl

> In a perfect world Log4J 2 would have been API compatible and configuration
> format compatible with 1, such that everyone could have migrated years ago,

Can you point out any specific incompatibilities? Particularly in the current 
version.

> but the Logging PMC/devs decided otherwise. Whether or not we assess that
> as desirable, we arrive at the present, with hundreds, perhaps thousands,
> of open source and internal projects stuck on Log4J 1 due to API or
> operational compatibility concerns that would carry downstream to their
> users. No matter what direction one might look (Log4J2, logback, etc.)
> there are compatibility blockers. Staying with Log4J 1 can be very much
> acceptable for this reason if the security concerns are addressed.

Are you using the JMS appender? Are you using the socket receiver? If the 
answer is no to those questions, you don’t have security concerns besides the 
more glaring fact that you’re depending on end of life software that has been 
marked as such for going on 7 years now.

> Sure, it
> won't evolve much, and there will remain gotchas, but that is true with
> anything... Some gotchas exceed others in concern. Compare lack of
> asynchronous logging with the risks of a turing complete substitution
> engine operating on untrusted user input.

This is bullshit. JNDI is what leads to your Turing completeness. Not to 
mention that this substitution feature is meant for the configuration file, not 
for log messages, and the library has been updated as such regardless of 
downstream users possibly relying on the default behavior before it was 
apparent there was a security flaw. Based on how tepid you are about upgrading 
for even the slightest inconvenience, there’s a reason why version 2 maintains 
as much backward compatibility as possible by default to be least surprising. 
Plenty of work and security review has since been put into the library to 
disable and remove everything concerning related to string substitution of 
configuration files using JNDI, but this is also a wider problem for any 
library or application that uses JNDI without restricting it to only java URIs 
(e.g., users that use LDAP via JNDI).

If the only reason you want to resurrect version 1 is due to a bug in version 
2, then I suggest you leave the software industry entirely as nearly 100% of 
software in existence has flaws, many of them critical.

> The Logging PMC is the hostile party here as far as I can tell, operating
> in defiance of the community of users that have made the points I have just
> written here abundantly clear for years.

So far, we had one contributor show up with a complete hostile attitude who 
refused to engage with the PMC and explain what he wanted to do besides go wild 
with version 1. Later, Ceki came back and made his first commit in probably a 
decade attempting to do the same less than a day after we had completed voting 
on what to do with version 1, again, without ANY comments about what his 
intentions were or any engagement with the PMC. So far, these two people have 
spent most of their time trolling in other mailing lists on Apache or elsewhere 
about the situation while continuing to ignore the PMC’s arguments.

If you have a desire to update version 1 that doesn’t boil down to “log4j2 bad 
bcuz log4shell lol get rekt n00bz”, please explain.

> 
> On Sat, Jan 8, 2022 at 1:58 PM Matt Sicker  wrote:
> 
>> The problem with v1 is that it doesn’t “just work”. There are

Re: Looking for a champion: resurrect log4j 1.x

Log4J 1 has known concurrency issues but many projects live with them or
work around them. For example, several "Big Data" Apache projects have been
fine with it, themselves internally highly concurrent and performance
sensitive. Log4J 1 might not be a Platonic ideal, but certainly good
enough, as evidenced by the popularity of those projects, operational in
numerous high scale and/or performance sensitive environments.

In a perfect world Log4J 2 would have been API compatible and configuration
format compatible with 1, such that everyone could have migrated years ago,
but the Logging PMC/devs decided otherwise. Whether or not we assess that
as desirable, we arrive at the present, with hundreds, perhaps thousands,
of open source and internal projects stuck on Log4J 1 due to API or
operational compatibility concerns that would carry downstream to their
users. No matter what direction one might look (Log4J2, logback, etc.)
there are compatibility blockers. Staying with Log4J 1 can be very much
acceptable for this reason if the security concerns are addressed. Sure, it
won't evolve much, and there will remain gotchas, but that is true with
anything... Some gotchas exceed others in concern. Compare lack of
asynchronous logging with the risks of a turing complete substitution
engine operating on untrusted user input.

The Logging PMC is the hostile party here as far as I can tell, operating
in defiance of the community of users that have made the points I have just
written here abundantly clear for years.

On Sat, Jan 8, 2022 at 1:58 PM Matt Sicker  wrote:

> The problem with v1 is that it doesn’t “just work”. There are numerous
> dead locks and other concurrency problems that were unable to be fixed
> without breaking various points of compatibility which is why Logback and
> Log4j2 even exist rather than continuing v1. There would also be difficulty
> in making a new release without volunteers contributing to the existing PMC
> to eventually join the PMC to be able to more directly create releases.
> Apache isn’t going to allow a hostile fork at the Incubator, so it’d still
> need to work with us or create an external fork that can’t be confused with
> the Apache version (which would still require a bunch of source code
> changes to point to the new package name if not already using shading or
> similar repackaging).
>
> I think it’s been said before, but contributing to the v2 backward
> compatibility system is a great way to join the project in such a way as to
> eventually form new releases of v1 with a greater understanding of the full
> impact of changing anything about v1 after such a long time. A poorly made
> release still wouldn’t be a drop in upgrade for projects that haven’t
> bothered upgrading in several years, and one that starts to introduce
> incompatible API changes would further complicate backward compatibility in
> v2 as well as complicating external projects that rely on a stable legacy
> API to convert from (like Logback’s config file converter thing or the
> numerous custom plugins for v1). So far, we haven’t seen any reasonably
> serious proposals of how anyone expects to do this without causing further
> mayhem in the future.
>
> —
> Matt Sicker
>
> > On Jan 8, 2022, at 14:32, Rohit Yadav  wrote:
> >
> > Hi Matt,
> >
> > Thanks for replying. I think the main issues I found following the guide
> [1] for Apache CloudStack (ACS) are:
> >
> > - APIs are not backward compatible fully, certainly everywhere the
> imports have to be fixed
> > - The config xml files are not fully compatible requiring some changes
> > - Our codebase is pretty large with several maven modules/projects
> enabled by certain flags, testing changes and ensuring CloudStack works
> post-migration adds effort and risks
> > - Lack of an automatic tooling that can do this reliably and efficiently
> (for example, the Go lang ecosystem has gofmt and other tooling to migrate
> codebase across std library/lang changes).
> > - ACS's own tech debt and dependency issues: for example, we're using
> log4j-extras (https://logging.apache.org/log4j/extras/) which is
> completely discontinued, and have code tied around gson library (for one or
> more reason, we've hesitated to upgrade both log4j and gson dependencies)
> >
> > Appreciate all the hard work the Log4j team is doing and we'll report
> issues as/when we hit them. As a consumer of the dependency, 1.x gave us
> enough mileage and end of the day we want logging to be boring that just
> works; and therefore I'm simply exploring all possible options (both
> migration to 2.x or support/maintain 1.x fork) while understanding their
> tradeoffs.
> >
> > [1] https://logging.apache.org/log4j/2.x/manual/migration.html
> >
> >> On 2022/01/08 19:51:07 Matt Sicker wrote:
> >> It would be nice if you filed any issues with Log4j2 about problems
> with migration. It would have been nice to hear about these issues back
> when v1 stopped development, but this is the next best time to do

Re: Looking for a champion: resurrect log4j 1.x

The problem with v1 is that it doesn’t “just work”. There are numerous dead 
locks and other concurrency problems that were unable to be fixed without 
breaking various points of compatibility which is why Logback and Log4j2 even 
exist rather than continuing v1. There would also be difficulty in making a new 
release without volunteers contributing to the existing PMC to eventually join 
the PMC to be able to more directly create releases. Apache isn’t going to 
allow a hostile fork at the Incubator, so it’d still need to work with us or 
create an external fork that can’t be confused with the Apache version (which 
would still require a bunch of source code changes to point to the new package 
name if not already using shading or similar repackaging).

I think it’s been said before, but contributing to the v2 backward 
compatibility system is a great way to join the project in such a way as to 
eventually form new releases of v1 with a greater understanding of the full 
impact of changing anything about v1 after such a long time. A poorly made 
release still wouldn’t be a drop in upgrade for projects that haven’t bothered 
upgrading in several years, and one that starts to introduce incompatible API 
changes would further complicate backward compatibility in v2 as well as 
complicating external projects that rely on a stable legacy API to convert from 
(like Logback’s config file converter thing or the numerous custom plugins for 
v1). So far, we haven’t seen any reasonably serious proposals of how anyone 
expects to do this without causing further mayhem in the future.

—
Matt Sicker

> On Jan 8, 2022, at 14:32, Rohit Yadav  wrote:
> 
> Hi Matt,
> 
> Thanks for replying. I think the main issues I found following the guide [1] 
> for Apache CloudStack (ACS) are:
> 
> - APIs are not backward compatible fully, certainly everywhere the imports 
> have to be fixed
> - The config xml files are not fully compatible requiring some changes
> - Our codebase is pretty large with several maven modules/projects enabled by 
> certain flags, testing changes and ensuring CloudStack works post-migration 
> adds effort and risks
> - Lack of an automatic tooling that can do this reliably and efficiently (for 
> example, the Go lang ecosystem has gofmt and other tooling to migrate 
> codebase across std library/lang changes).
> - ACS's own tech debt and dependency issues: for example, we're using 
> log4j-extras (https://logging.apache.org/log4j/extras/) which is completely 
> discontinued, and have code tied around gson library (for one or more reason, 
> we've hesitated to upgrade both log4j and gson dependencies)
> 
> Appreciate all the hard work the Log4j team is doing and we'll report issues 
> as/when we hit them. As a consumer of the dependency, 1.x gave us enough 
> mileage and end of the day we want logging to be boring that just works; and 
> therefore I'm simply exploring all possible options (both migration to 2.x or 
> support/maintain 1.x fork) while understanding their tradeoffs.
> 
> [1] https://logging.apache.org/log4j/2.x/manual/migration.html
> 
>> On 2022/01/08 19:51:07 Matt Sicker wrote:
>> It would be nice if you filed any issues with Log4j2 about problems with 
>> migration. It would have been nice to hear about these issues back when v1 
>> stopped development, but this is the next best time to do so. The Log4j team 
>> are actively working to fill in any remaining gaps on backward 
>> compatibility; making new releases of EOL software with numerous 
>> implementation errors inherent to its architecture seems like going 
>> backwards.
>> 
>> —
>> Matt Sicker
>> 
 On Jan 8, 2022, at 13:45, Rohit Yadav  wrote:
>>> 
>>> Hi all, 
>>> 
>>> I agree and extend support for Andrew's remarks. Apache CloudStack too uses 
>>> log4j 1.x and our use case is simply a logging library that 1.x just 
>>> satisfies. The effort to migrate to 2.x is not quick, at least in our 
>>> initial investigation and a migration may likely require huge effort in 
>>> testing.
>>> 
>>> Assuming this quick upgrade path doesn't exist, and I already read 
>>> struggles by other projects trying to migrate to 2.x - maintaining 1.x and 
>>> doing a 1.2.x release makes more sense than investing weeks in migration 
>>> and testing to 2.x, while maintaining the same artifact IDs. I'm up for 
>>> volunteering and supporting 1.x maintenance.
>>> 
>>> Regards, 
>>> Rohit Yadav 
>>> PMC, Apache CloudStack
>>> 
>>> On 2021/12/21 21:54:34 Andrew Purtell wrote:
> as for the v1 :: COBOL analogy, that’s not a bad comparison. Basically,
 users who haven’t bothered to upgrade in 10 years will have to end up
 paying astronomical costs for consultants who can still work on ancient
 software effectively to help modify their systems.

 I have to take some exception to this. If the log4j 2.x configuration files
 were compatible _enough_ with 1.x then taking this position would be
 understandable. However, because

Re: Looking for a champion: resurrect log4j 1.x

2022-01-08 Thread Rohit Yadav

Hi Matt,

Thanks for replying. I think the main issues I found following the guide [1] 
for Apache CloudStack (ACS) are:

- APIs are not backward compatible fully, certainly everywhere the imports have 
to be fixed
- The config xml files are not fully compatible requiring some changes
- Our codebase is pretty large with several maven modules/projects enabled by 
certain flags, testing changes and ensuring CloudStack works post-migration 
adds effort and risks
- Lack of an automatic tooling that can do this reliably and efficiently (for 
example, the Go lang ecosystem has gofmt and other tooling to migrate codebase 
across std library/lang changes).
- ACS's own tech debt and dependency issues: for example, we're using 
log4j-extras (https://logging.apache.org/log4j/extras/) which is completely 
discontinued, and have code tied around gson library (for one or more reason, 
we've hesitated to upgrade both log4j and gson dependencies)

Appreciate all the hard work the Log4j team is doing and we'll report issues 
as/when we hit them. As a consumer of the dependency, 1.x gave us enough 
mileage and end of the day we want logging to be boring that just works; and 
therefore I'm simply exploring all possible options (both migration to 2.x or 
support/maintain 1.x fork) while understanding their tradeoffs.

[1] https://logging.apache.org/log4j/2.x/manual/migration.html

On 2022/01/08 19:51:07 Matt Sicker wrote:
> It would be nice if you filed any issues with Log4j2 about problems with 
> migration. It would have been nice to hear about these issues back when v1 
> stopped development, but this is the next best time to do so. The Log4j team 
> are actively working to fill in any remaining gaps on backward compatibility; 
> making new releases of EOL software with numerous implementation errors 
> inherent to its architecture seems like going backwards.
> 
> —
> Matt Sicker
> 
> > On Jan 8, 2022, at 13:45, Rohit Yadav  wrote:
> > 
> > Hi all, 
> > 
> > I agree and extend support for Andrew's remarks. Apache CloudStack too uses 
> > log4j 1.x and our use case is simply a logging library that 1.x just 
> > satisfies. The effort to migrate to 2.x is not quick, at least in our 
> > initial investigation and a migration may likely require huge effort in 
> > testing.
> > 
> > Assuming this quick upgrade path doesn't exist, and I already read 
> > struggles by other projects trying to migrate to 2.x - maintaining 1.x and 
> > doing a 1.2.x release makes more sense than investing weeks in migration 
> > and testing to 2.x, while maintaining the same artifact IDs. I'm up for 
> > volunteering and supporting 1.x maintenance.
> > 
> > Regards, 
> > Rohit Yadav 
> > PMC, Apache CloudStack
> > 
> > On 2021/12/21 21:54:34 Andrew Purtell wrote:
> >>> as for the v1 :: COBOL analogy, that’s not a bad comparison. Basically,
> >> users who haven’t bothered to upgrade in 10 years will have to end up
> >> paying astronomical costs for consultants who can still work on ancient
> >> software effectively to help modify their systems.
> >> 
> >> I have to take some exception to this. If the log4j 2.x configuration files
> >> were compatible _enough_ with 1.x then taking this position would be
> >> understandable. However, because they are not compatible in the way that
> >> users require -- and the backwards compatibility is still marked as
> >> 'experimental', even -- it is not great to blame users "who haven't
> >> bothered to upgrade in 10 years". Turning this around, why is backwards
> >> compatibility still experimental after 10 years? I am involved with several
> >> Apache projects where we would love to upgrade from log4j 1 to log4j 2, and
> >> have been talking about it for _years_. However, we have not been able to
> >> easily do so because we actually care about operational cross-version
> >> compatibility for our users. On some of these projects we are still stuck
> >> on log4j 1.
> >> 
> >> I also support continuing releasing for log4j 1.x, and would volunteer some
> >> of my time to assist in the effort.
> >> 
> >> 
> >> On Tue, Dec 21, 2021 at 12:34 PM Matt Sicker  wrote:
> >> 
> >>> Nobody in the Logging PMC is blocking a release here. What we don’t want
> >>> is to falsely advertise that v1 is still under development. We already 
> >>> have
> >>> a huge increase in mailing list, PR, and other traffic ever since
> >>> Log4Shell, and if we resurrect v1, then it’ll quickly become impossible to
> >>> keep up with all the activity given the size of the PMC. If any 
> >>> non-trivial
> >>> work is to be done in v1, we’d prefer to see more than one person working
> >>> on that, especially if we want to add more PMC members to oversee v1 in 
> >>> the
> >>> first place.
> >>> 
> >>> And as for the v1 :: COBOL analogy, that’s not a bad comparison.
> >>> Basically, users who haven’t bothered to upgrade in 10 years will have to
> >>> end up paying astronomical costs for consultants who can still work on
> >>> ancient software

Re: Looking for a champion: resurrect log4j 1.x

It would be nice if you filed any issues with Log4j2 about problems with 
migration. It would have been nice to hear about these issues back when v1 
stopped development, but this is the next best time to do so. The Log4j team 
are actively working to fill in any remaining gaps on backward compatibility; 
making new releases of EOL software with numerous implementation errors 
inherent to its architecture seems like going backwards.

—
Matt Sicker

> On Jan 8, 2022, at 13:45, Rohit Yadav  wrote:
> 
> Hi all, 
> 
> I agree and extend support for Andrew's remarks. Apache CloudStack too uses 
> log4j 1.x and our use case is simply a logging library that 1.x just 
> satisfies. The effort to migrate to 2.x is not quick, at least in our initial 
> investigation and a migration may likely require huge effort in testing.
> 
> Assuming this quick upgrade path doesn't exist, and I already read struggles 
> by other projects trying to migrate to 2.x - maintaining 1.x and doing a 
> 1.2.x release makes more sense than investing weeks in migration and testing 
> to 2.x, while maintaining the same artifact IDs. I'm up for volunteering and 
> supporting 1.x maintenance.
> 
> Regards, 
> Rohit Yadav 
> PMC, Apache CloudStack
> 
> On 2021/12/21 21:54:34 Andrew Purtell wrote:
>>> as for the v1 :: COBOL analogy, that’s not a bad comparison. Basically,
>> users who haven’t bothered to upgrade in 10 years will have to end up
>> paying astronomical costs for consultants who can still work on ancient
>> software effectively to help modify their systems.
>> 
>> I have to take some exception to this. If the log4j 2.x configuration files
>> were compatible _enough_ with 1.x then taking this position would be
>> understandable. However, because they are not compatible in the way that
>> users require -- and the backwards compatibility is still marked as
>> 'experimental', even -- it is not great to blame users "who haven't
>> bothered to upgrade in 10 years". Turning this around, why is backwards
>> compatibility still experimental after 10 years? I am involved with several
>> Apache projects where we would love to upgrade from log4j 1 to log4j 2, and
>> have been talking about it for _years_. However, we have not been able to
>> easily do so because we actually care about operational cross-version
>> compatibility for our users. On some of these projects we are still stuck
>> on log4j 1.
>> 
>> I also support continuing releasing for log4j 1.x, and would volunteer some
>> of my time to assist in the effort.
>> 
>> 
>> On Tue, Dec 21, 2021 at 12:34 PM Matt Sicker  wrote:
>> 
>>> Nobody in the Logging PMC is blocking a release here. What we don’t want
>>> is to falsely advertise that v1 is still under development. We already have
>>> a huge increase in mailing list, PR, and other traffic ever since
>>> Log4Shell, and if we resurrect v1, then it’ll quickly become impossible to
>>> keep up with all the activity given the size of the PMC. If any non-trivial
>>> work is to be done in v1, we’d prefer to see more than one person working
>>> on that, especially if we want to add more PMC members to oversee v1 in the
>>> first place.
>>> 
>>> And as for the v1 :: COBOL analogy, that’s not a bad comparison.
>>> Basically, users who haven’t bothered to upgrade in 10 years will have to
>>> end up paying astronomical costs for consultants who can still work on
>>> ancient software effectively to help modify their systems. Was Maven even
>>> widely used back when v1 was popular? Or were people still using a mix of
>>> make or Ant?
>>> --
>>> Matt Sicker
>>> 
 On Dec 21, 2021, at 07:13, Romain Manni-Bucau 
>>> wrote:
 
 Le mar. 21 déc. 2021 à 12:33, Enrico Olivelli  a
 écrit :
 
> Vladimir,
> I totally support this proposal.
> 
> Which are actually the steps we need to cut a release of log4j 1.x ?
> - establish an Apache project ?
> 
 
 1. Send a patch to apply on
 http://svn.apache.org/repos/asf/logging/log4j/trunk
 
 
> - do the fix
> 
 
 2. Get it applied
 
 
> - cut a release
> 
> Can this be done inside another Apache Project who "adopts" the log4j
> sources if the Logging Project doesn't want to do it ?
> 
 
 The PMC of log4j2 is logging project so it should be done there, if not
>>> the
 project can be forked inside Apache but should change of package until we
 get the perms to reuse the same one which means likely as much work as
>>> just
 getting it done at logging project so hope it is not needed ;).
 
 
> 
> Enrico
> 
> 
> Il giorno mar 21 dic 2021 alle ore 08:36 Vladimir Sitnikov <
> sitnikov.vladi...@gmail.com> ha scritto:
> 
>>> Just wondering, is it even fulfilling the criteria of incubation?
>> 
>> I believe, the world does not need "active development in log4j 1.x"
>> nowadays.
>> What everybody needs from log4j 1.x is to fix security issues, fix

Re: Looking for a champion: resurrect log4j 1.x

2022-01-08 Thread Rohit Yadav

Hi all, 

I agree and extend support for Andrew's remarks. Apache CloudStack too uses 
log4j 1.x and our use case is simply a logging library that 1.x just satisfies. 
The effort to migrate to 2.x is not quick, at least in our initial 
investigation and a migration may likely require huge effort in testing.

Assuming this quick upgrade path doesn't exist, and I already read struggles by 
other projects trying to migrate to 2.x - maintaining 1.x and doing a 1.2.x 
release makes more sense than investing weeks in migration and testing to 2.x, 
while maintaining the same artifact IDs. I'm up for volunteering and supporting 
1.x maintenance.

Regards, 
Rohit Yadav 
PMC, Apache CloudStack

On 2021/12/21 21:54:34 Andrew Purtell wrote:
> > as for the v1 :: COBOL analogy, that’s not a bad comparison. Basically,
> users who haven’t bothered to upgrade in 10 years will have to end up
> paying astronomical costs for consultants who can still work on ancient
> software effectively to help modify their systems.
> 
> I have to take some exception to this. If the log4j 2.x configuration files
> were compatible _enough_ with 1.x then taking this position would be
> understandable. However, because they are not compatible in the way that
> users require -- and the backwards compatibility is still marked as
> 'experimental', even -- it is not great to blame users "who haven't
> bothered to upgrade in 10 years". Turning this around, why is backwards
> compatibility still experimental after 10 years? I am involved with several
> Apache projects where we would love to upgrade from log4j 1 to log4j 2, and
> have been talking about it for _years_. However, we have not been able to
> easily do so because we actually care about operational cross-version
> compatibility for our users. On some of these projects we are still stuck
> on log4j 1.
> 
> I also support continuing releasing for log4j 1.x, and would volunteer some
> of my time to assist in the effort.
> 
> 
> On Tue, Dec 21, 2021 at 12:34 PM Matt Sicker  wrote:
> 
> > Nobody in the Logging PMC is blocking a release here. What we don’t want
> > is to falsely advertise that v1 is still under development. We already have
> > a huge increase in mailing list, PR, and other traffic ever since
> > Log4Shell, and if we resurrect v1, then it’ll quickly become impossible to
> > keep up with all the activity given the size of the PMC. If any non-trivial
> > work is to be done in v1, we’d prefer to see more than one person working
> > on that, especially if we want to add more PMC members to oversee v1 in the
> > first place.
> >
> > And as for the v1 :: COBOL analogy, that’s not a bad comparison.
> > Basically, users who haven’t bothered to upgrade in 10 years will have to
> > end up paying astronomical costs for consultants who can still work on
> > ancient software effectively to help modify their systems. Was Maven even
> > widely used back when v1 was popular? Or were people still using a mix of
> > make or Ant?
> > --
> > Matt Sicker
> >
> > > On Dec 21, 2021, at 07:13, Romain Manni-Bucau 
> > wrote:
> > >
> > > Le mar. 21 déc. 2021 à 12:33, Enrico Olivelli  a
> > > écrit :
> > >
> > >> Vladimir,
> > >> I totally support this proposal.
> > >>
> > >> Which are actually the steps we need to cut a release of log4j 1.x ?
> > >> - establish an Apache project ?
> > >>
> > >
> > > 1. Send a patch to apply on
> > > http://svn.apache.org/repos/asf/logging/log4j/trunk
> > >
> > >
> > >> - do the fix
> > >>
> > >
> > > 2. Get it applied
> > >
> > >
> > >> - cut a release
> > >>
> > >> Can this be done inside another Apache Project who "adopts" the log4j
> > >> sources if the Logging Project doesn't want to do it ?
> > >>
> > >
> > > The PMC of log4j2 is logging project so it should be done there, if not
> > the
> > > project can be forked inside Apache but should change of package until we
> > > get the perms to reuse the same one which means likely as much work as
> > just
> > > getting it done at logging project so hope it is not needed ;).
> > >
> > >
> > >>
> > >> Enrico
> > >>
> > >>
> > >> Il giorno mar 21 dic 2021 alle ore 08:36 Vladimir Sitnikov <
> > >> sitnikov.vladi...@gmail.com> ha scritto:
> > >>
> >  Just wondering, is it even fulfilling the criteria of incubation?
> > >>>
> > >>> I believe, the world does not need "active development in log4j 1.x"
> > >>> nowadays.
> > >>> What everybody needs from log4j 1.x is to fix security issues, fix
> > >>> outstanding issues (if any),
> > >>> keep the project buildable (e.g. avoid using outdated build systems),
> > >> etc.
> > >>>
> >  it doesn't seem that sustainability is proven.
> > >>>
> > >>> The problem is log4j 1.x is like COBOL of logging. There are apps that
> > >> are
> > >>> just stuck with log4j 1.x.
> > >>> The proof of sustainability is that lots of existing apps will never
> > >>> upgrade to 2.x because 2.x is incompatible.
> > >>> If the compatibility layer of 2.x would be improved to handle 99.999%
> > of
> >

Re: Looking for a champion: resurrect log4j 1.x

2022-01-05 Thread Christian Grobmeier

Hello,

I just came across this thread - same as Ralph, I currently don't mentor any 
podlings. However, I am still on the Logging PMC.

On Thu, Dec 23, 2021, at 07:05, Vladimir Sitnikov wrote:
> Ralph>I was busy
>
> The world is on fire with log4j, so if you have no time left for 1.x, then,
> please, just let others do the maintenance.

You have been constantly treating others with disrespect. 

Nobody of us committed any time for log4j1 since 2012, and since 2015 it is 
EOL. Nobody of us even thought about giving any time to log4j1 until you came 
up on this list. I think it is fair to say the world is on fire with log4j2 BUT 
NOT with log4j1.

There is no new security issues with log4j1. Instead we retired log4j1 for many 
reasons, including some multithreading issues which require heavy architectural 
changes - which we then fixed with log4j2. Nobody was able to fix it back then.

Maybe I have missed something, but we never accepted a single podling for just 
one release, with one committer, with the original PMC opposing this step. And 
this for two security issues which are 10 years old which are not comparable to 
the ones we found in log4j2.

I recommend looking at the Logging Chairs statement for details if interested 
which will be sent soon.

Also, I don't think Cobol and Log4j 1 match up. 

That being said, the PMCs job - especially those people dealing with this issue 
- has been excellent so far, and this email thread looks like some of us were 
blocking all the time. That's not true and is a wrong impression. We just 
haven't heard good arguments for resurrecting log4j1.

Cheers
Christian

>
> Ralph>My recollection was me saying if I had the code in a git repo getting
> it into a GitHub repo would be easy.
>
> I do not want to dilute "svn -> git" question any further, so, if you have
> time (apparently, you do respond on logging and here),
> consider answering at https://issues.apache.org/jira/browse/LOG4J2-3272
>
> ---
>
> Ralph, my response was
> https://lists.apache.org/thread/jzym3z270jqr84m8o4m7pxlmpk8frr4z
> Literally, you have **nothing** to do except blessing the migration in
> order to get Git and GitHub open for log4j 1.x .
>
> You even ignored "[VOTE] Move log4j 1.x from SVN to Git..."
> https://lists.apache.org/thread/ssbdg44gy7txzl16xxd097t7orco52g2
>
> You still keep asking "if git repo exists or not". Who cares if git repo
> exists?
> I offer you help with getting the things done, yet you ask questions as if
> I ask you to do the work.
>
> Vladimir

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Looking for a champion: resurrect log4j 1.x

2021-12-22 Thread Vladimir Sitnikov

Ralph>I was busy

The world is on fire with log4j, so if you have no time left for 1.x, then,
please, just let others do the maintenance.

Ralph>My recollection was me saying if I had the code in a git repo getting
it into a GitHub repo would be easy.

I do not want to dilute "svn -> git" question any further, so, if you have
time (apparently, you do respond on logging and here),
consider answering at https://issues.apache.org/jira/browse/LOG4J2-3272

---

Ralph, my response was
https://lists.apache.org/thread/jzym3z270jqr84m8o4m7pxlmpk8frr4z
Literally, you have **nothing** to do except blessing the migration in
order to get Git and GitHub open for log4j 1.x .

You even ignored "[VOTE] Move log4j 1.x from SVN to Git..."
https://lists.apache.org/thread/ssbdg44gy7txzl16xxd097t7orco52g2

You still keep asking "if git repo exists or not". Who cares if git repo
exists?
I offer you help with getting the things done, yet you ask questions as if
I ask you to do the work.

Vladimir

Re: Looking for a champion: resurrect log4j 1.x

2021-12-22 Thread Duo Zhang

OK, thank you for the feedback.

Will open issues and also discuss threads on the mailing list for these
things.

Ralph Goers  于2021年12月23日周四 08:10写道：

>
>
> > On Dec 21, 2021, at 9:22 PM, 张铎(Duo Zhang) 
> wrote:
> >
> > But in my experience, first, the log4j12 bridge is not perfect. For
> > example, since hadoop is still on log4j 1.x, I need to add log4j12 bridge
> > dependency if I want to run UTs based on hadoop mini cluster, and then I
> > need to manually copy some code from log4j1 in order to make it work,
> this
> > is an example
> >
> >
> https://github.com/apache/hbase/blob/master/hbase-logging/src/test/java/org/apache/log4j/FileAppender.java
> >
> > I know in the bridge you will create log4j2 appender instead when reading
> > the configuration file of log4j1, but since the appenders in log4j1 lack
> of
> > some abilities, it is common that lots of projects will implement their
> own
> > appender, I think we should take care of these usages and make them
> migrate
> > smoothly.
>
> I do not know if you are aware but the experimental support we added a few
> releases ago should
> be able to use Log4j 1 Appenders in Log4j2. It is experimental simply
> because we have no idea what wild
> and crazy things uses are relying on in Log4j 1 since nothing was private.
> We need user feedback.
>
> >
> > And then, while fully migrating to log4j2, there is another annoying
> > problem, the
> >
> > log4j.rootLogger=INFO,console
> >
> > grammar is gone! It is used among almost all the projects I've seen, and
> we
> > just drop the support for it!
>
> Again, support for Log4j 1 configuration files is part of the experimental
> support. We finally received
> our first bug report on it so someone is using it.
>
> Ralph
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Looking for a champion: resurrect log4j 1.x

> On Dec 22, 2021, at 12:35 AM, Vladimir Sitnikov  
> wrote:
> 
> 
> I already asked Logging PMC to enable Git and GitHub for 1.x, and they
> rejected it:
> https://lists.apache.org/thread/ssbdg44gy7txzl16xxd097t7orco52g2

My recollection was me saying if I had the code in a git repo getting it into a 
GitHub repo would be easy. 
But I wasn’t going to do the work. But it appears the code is in Gitbox. If so, 
getting it into an updatable 
GitHub repo should be easy - except the name you probably want to use is the 
one used by Gitbox.

We’ve also asked what your plans would be for all the issues that are in 
Bugzilla. It seems you would rather 
use Jira or GitHub issues. I don’t blame you there. But will you just ignore 
all those old problems? 
I don’t recall getting an answer. But maybe you did. I was busy.

Ralph

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Looking for a champion: resurrect log4j 1.x

> On Dec 21, 2021, at 10:24 PM, Vladimir Sitnikov  
> wrote:
> 
> Matt>Nobody in the Logging PMC is blocking a release here.
> 
> Matt, thanks for the reply, however, it is false :(
> I see you are positive, however, many more replies were quite negative.
> 
> Ralph Goers says: "We’ve stated several times that we don’t think
> resurrecting Log4j 1.x permanently is a good idea."
> https://lists.apache.org/thread/vz80p3v78xgposon3pcxbnb9729snnxt
> 
> Gary Gregory says: "As I've stated before, IF there is a 1.2.18, it should
> ONLY be for CVEs,"
> https://lists.apache.org/thread/53h130p0kdkspn4kj2hq39vkgpyzgvp7
> 
> They both are on Logging PMC, and they both have negative opinions on
> making progress with v1.
> I do not really understand what "ONLY be for CVEs" means (e.g. does it
> allow upgrading from Maven2 to Maven3?),
> but I do not want to get accidentally blocked by "oh, this change is not
> allowed because it is not a CVE fix".

Of course we have opinions. But me saying I don’t think it is a good idea 
doesn’t mean 
“No, it isn’t going to happen”.  I’ve said I think lots of things are bad ideas 
and then 
changed my mind. But the emphasis here should really be on getting consensus 
from 
those who are trying to do work on Log4j 1.x. Do they just want a 1.2.18 
release or a 
continuing sub-project. I know you are very vocal about wanting a continuing 
sub-project 
but I’ve not really heard anybody else say they are in it for the long haul.

Ralph
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Looking for a champion: resurrect log4j 1.x




> On Dec 21, 2021, at 9:22 PM, 张铎(Duo Zhang)  wrote:
> 
> But in my experience, first, the log4j12 bridge is not perfect. For
> example, since hadoop is still on log4j 1.x, I need to add log4j12 bridge
> dependency if I want to run UTs based on hadoop mini cluster, and then I
> need to manually copy some code from log4j1 in order to make it work, this
> is an example
> 
> https://github.com/apache/hbase/blob/master/hbase-logging/src/test/java/org/apache/log4j/FileAppender.java
> 
> I know in the bridge you will create log4j2 appender instead when reading
> the configuration file of log4j1, but since the appenders in log4j1 lack of
> some abilities, it is common that lots of projects will implement their own
> appender, I think we should take care of these usages and make them migrate
> smoothly.

I do not know if you are aware but the experimental support we added a few 
releases ago should 
be able to use Log4j 1 Appenders in Log4j2. It is experimental simply because 
we have no idea what wild 
and crazy things uses are relying on in Log4j 1 since nothing was private. We 
need user feedback.

> 
> And then, while fully migrating to log4j2, there is another annoying
> problem, the
> 
> log4j.rootLogger=INFO,console
> 
> grammar is gone! It is used among almost all the projects I've seen, and we
> just drop the support for it!

Again, support for Log4j 1 configuration files is part of the experimental 
support. We finally received 
our first bug report on it so someone is using it.

Ralph
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Looking for a champion: resurrect log4j 1.x