Re: what's the latest on the update of moving from alioth to pagure.
On Wed, 19 Jul 2017, Geert Stappers wrote: > On Mon, Jul 17, 2017 at 05:59:14AM +0200, Alexander Wirt wrote: > > On Mon, 17 Jul 2017, shirish ??? wrote: > > > > > Dear all, > > > > > > While I love and loved alioth, I know for probably newish people the > > > interface is somewhat ugly. > > > > > > >From what I did see in https://lwn.net/Articles/724986/ it seems there > > > were lots of pros and cons which were discussed. I was also able to > > > converse with Alexander Wirt and download the survey which wasn't > > > available anymore for public consumption. > > > > > > Can somebody tell/share which forge are the developers looking forward > > > to replace alioth with, pagure or something else . > > > > > > The choices seem to be to do lot of coding if some project/product is > > > taken which is not mature enough or has features that we want and in > > > some cases there is restrictive licensing or/and have two products, > > > one which has foss licensing and the other which has commercial > > > aspects but more features. > > > > > > While there doesn't seem to be any hurry to replace alioth today, the > > > clock is ticking. > > > > > > There is/was some discussion about it in May 2017 > > > https://lists.debian.org/debian-devel/2017/05/msg00095.html, the > > > thread I'm reading right now. Would be nice though if somebody can > > > share what is/are the possible scenarios. > > We created a mailinglist [1] for those discussions. > > > > Alex > > > > [1] > > https://lists.alioth.debian.org/mailman/listinfo/alioth-staff-replacement > > > > Archive at http://lists.alioth.debian.org/pipermail/alioth-staff-replacement/ > > I think an interresting post is > http://lists.alioth.debian.org/pipermail/alioth-staff-replacement/Week-of-Mon-20170710/14.html > > I have full confident in Formorer that he can resist the sales team from > Gitlab. I'll choose whatever is best for debian. Alex
Re: what's the latest on the update of moving from alioth to pagure.
On Mon, Jul 17, 2017 at 05:59:14AM +0200, Alexander Wirt wrote: > On Mon, 17 Jul 2017, shirish ??? wrote: > > > Dear all, > > > > While I love and loved alioth, I know for probably newish people the > > interface is somewhat ugly. > > > > >From what I did see in https://lwn.net/Articles/724986/ it seems there > > were lots of pros and cons which were discussed. I was also able to > > converse with Alexander Wirt and download the survey which wasn't > > available anymore for public consumption. > > > > Can somebody tell/share which forge are the developers looking forward > > to replace alioth with, pagure or something else . > > > > The choices seem to be to do lot of coding if some project/product is > > taken which is not mature enough or has features that we want and in > > some cases there is restrictive licensing or/and have two products, > > one which has foss licensing and the other which has commercial > > aspects but more features. > > > > While there doesn't seem to be any hurry to replace alioth today, the > > clock is ticking. > > > > There is/was some discussion about it in May 2017 > > https://lists.debian.org/debian-devel/2017/05/msg00095.html, the > > thread I'm reading right now. Would be nice though if somebody can > > share what is/are the possible scenarios. > We created a mailinglist [1] for those discussions. > > Alex > > [1] https://lists.alioth.debian.org/mailman/listinfo/alioth-staff-replacement > Archive at http://lists.alioth.debian.org/pipermail/alioth-staff-replacement/ I think an interresting post is http://lists.alioth.debian.org/pipermail/alioth-staff-replacement/Week-of-Mon-20170710/14.html I have full confident in Formorer that he can resist the sales team from Gitlab. Groeten Geert Stappers -- Leven en laten leven
Re: what's the latest on the update of moving from alioth to pagure.
On Mon, 17 Jul 2017, shirish शिरीष wrote: > Dear all, > > While I love and loved alioth, I know for probably newish people the > interface is somewhat ugly. > > >From what I did see in https://lwn.net/Articles/724986/ it seems there > were lots of pros and cons which were discussed. I was also able to > converse with Alexander Wirt and download the survey which wasn't > available anymore for public consumption. > > Can somebody tell/share which forge are the developers looking forward > to replace alioth with, pagure or something else . > > The choices seem to be to do lot of coding if some project/product is > taken which is not mature enough or has features that we want and in > some cases there is restrictive licensing or/and have two products, > one which has foss licensing and the other which has commercial > aspects but more features. > > While there doesn't seem to be any hurry to replace alioth today, the > clock is ticking. > > There is/was some discussion about it in May 2017 > https://lists.debian.org/debian-devel/2017/05/msg00095.html, the > thread I'm reading right now. Would be nice though if somebody can > share what is/are the possible scenarios. We created a mailinglist [1] for those discussions. Alex [1] https://lists.alioth.debian.org/mailman/listinfo/alioth-staff-replacement
what's the latest on the update of moving from alioth to pagure.
Dear all, While I love and loved alioth, I know for probably newish people the interface is somewhat ugly. >From what I did see in https://lwn.net/Articles/724986/ it seems there were lots of pros and cons which were discussed. I was also able to converse with Alexander Wirt and download the survey which wasn't available anymore for public consumption. Can somebody tell/share which forge are the developers looking forward to replace alioth with, pagure or something else . The choices seem to be to do lot of coding if some project/product is taken which is not mature enough or has features that we want and in some cases there is restrictive licensing or/and have two products, one which has foss licensing and the other which has commercial aspects but more features. While there doesn't seem to be any hurry to replace alioth today, the clock is ticking. There is/was some discussion about it in May 2017 https://lists.debian.org/debian-devel/2017/05/msg00095.html, the thread I'm reading right now. Would be nice though if somebody can share what is/are the possible scenarios. -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
