You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@milagro.apache.org by Giorgio Zoppi <gi...@gmail.com> on 2022/11/02 12:23:23 UTC
Re: archive
Dear all,
I would like to put up at vote to archive js repo also.
+1 binding vote.
In each archived repo it should explicitly state in the readme that it is
no longer actively maintained and you are welcome to take the ownership
Again less is more. Simplicity is mandatory.
Best Regards,
Giorgio
Il Lun 31 Ott 2022, 18:38 Riccardo Iaconelli <ri...@kde.org> ha scritto:
> Dear Kealan,
>
> On 2022/10/28 15:33:11 Kealan McCusker wrote:
> > Hi All
> >
> > I propose to merge develop into master and from now on use master as the
> > default branch
> > for these repo's;
> >
> > https://github.com/apache/incubator-milagro-crypto-c
> > https://github.com/apache/incubator-milagro-MPC
> > https://github.com/apache/incubator-milagro-crypto-js
>
> Big +1 from me. It was a pain to deal with a double merge and I don't
> understand why we should keep doing this. It's just clunky.
>
> > I also propose to public archive these repo's
> >
> > https://github.com/apache/incubator-milagro-mfa-server
> > https://github.com/apache/incubator-milagro-crypto-rust
>
> Re: MFA, absolutely yes.
>
> Re Rust, absolutely yes, if all the code there is definitely dead and no
> more development should happen. In any case, before doing that I would
> update the readme outlining the status of the repository, and with the
> instructions on how this status could be un-frozen (e.g. stepping up as
> maintainer on this list?).
>
> However, if the current code is not insecure and development could still be
> picked up by others in the community, I suggest just marking the code as
> unmaintained, detailing what needs to happen and moving on. The reason for
> this is that an archived repository cannot receive pull requests or
> community contributions, which is not necessarily what we might want.
>
> > Is that okay with everyone?
> >
> > regards
> >
> > Kealan
>
> Thanks for caring about this!
>
> Riccardo
> --
> Pace Peace Paix Paz Frieden Pax Pokój Friður Fred Béke Heddwch
> Hasiti Lapé Hetep Malu Mир Wolakota Santiphap Irini Peoch שלום
> Shanti Vrede Baris Rój Mír Taika Rongo Sulh Mir Py'guapy 평화 和平
>
Re: archive
Posted by Kealan McCusker <ke...@gmail.com>.
Hi Giorgio
There has not been anything to add to this repo for years but I do use it
quite a bit,
So it is -1 from me.
regards
Kealan
On Wed, 2 Nov 2022 at 12:23, Giorgio Zoppi <gi...@gmail.com> wrote:
> Dear all,
> I would like to put up at vote to archive js repo also.
> +1 binding vote.
> In each archived repo it should explicitly state in the readme that it is
> no longer actively maintained and you are welcome to take the ownership
> Again less is more. Simplicity is mandatory.
> Best Regards,
> Giorgio
>
> Il Lun 31 Ott 2022, 18:38 Riccardo Iaconelli <ri...@kde.org> ha
> scritto:
>
> > Dear Kealan,
> >
> > On 2022/10/28 15:33:11 Kealan McCusker wrote:
> > > Hi All
> > >
> > > I propose to merge develop into master and from now on use master as
> the
> > > default branch
> > > for these repo's;
> > >
> > > https://github.com/apache/incubator-milagro-crypto-c
> > > https://github.com/apache/incubator-milagro-MPC
> > > https://github.com/apache/incubator-milagro-crypto-js
> >
> > Big +1 from me. It was a pain to deal with a double merge and I don't
> > understand why we should keep doing this. It's just clunky.
> >
> > > I also propose to public archive these repo's
> > >
> > > https://github.com/apache/incubator-milagro-mfa-server
> > > https://github.com/apache/incubator-milagro-crypto-rust
> >
> > Re: MFA, absolutely yes.
> >
> > Re Rust, absolutely yes, if all the code there is definitely dead and no
> > more development should happen. In any case, before doing that I would
> > update the readme outlining the status of the repository, and with the
> > instructions on how this status could be un-frozen (e.g. stepping up as
> > maintainer on this list?).
> >
> > However, if the current code is not insecure and development could still
> be
> > picked up by others in the community, I suggest just marking the code as
> > unmaintained, detailing what needs to happen and moving on. The reason
> for
> > this is that an archived repository cannot receive pull requests or
> > community contributions, which is not necessarily what we might want.
> >
> > > Is that okay with everyone?
> > >
> > > regards
> > >
> > > Kealan
> >
> > Thanks for caring about this!
> >
> > Riccardo
> > --
> > Pace Peace Paix Paz Frieden Pax Pokój Friður Fred Béke Heddwch
> > Hasiti Lapé Hetep Malu Mир Wolakota Santiphap Irini Peoch שלום
> > Shanti Vrede Baris Rój Mír Taika Rongo Sulh Mir Py'guapy 평화 和平
> >
>