Just vote by email on this thread; I will tally them on Wednesday. On Sat, Oct 1, 2022, 8:57 PM erentar2002 <erentar2...@gmail.com> wrote:
> Do i vote by email or is there a voting page > On 9/23/22 08:37, Emmanuel Charpentier wrote: > > +1 for Github > > Also wishing for contingency plan for re-migrating to self-hosted Gitlab. > > Le mercredi 21 septembre 2022 à 19:23:36 UTC+2, David Roe a écrit : > >> Dear Sage developers, >> Following extensive discussion, both recently >> <https://groups.google.com/g/sage-devel/c/ayOL8_bzOfk/m/Pg-rmYAUBwAJ> >> (prompted >> by issues upgrading the trac server) and over >> <https://groups.google.com/g/sage-devel/c/yBv5MCG9SJY/m/gYOYnRhzDAAJ> the >> <https://groups.google.com/g/sage-devel/c/Xw6CNq1lyiI/m/_XcxeD_kDQAJ> >> last >> <https://groups.google.com/g/sage-devel/c/z33SLveYiIo/m/CxNxsXnBeNAJ> >> decade >> <https://groups.google.com/g/sage-devel/c/DmjL8hHJYI8/m/NG9_xmsPbFYJ>, >> we are calling a vote on switching Sage development from Trac >> <https://trac.sagemath.org/> to Github <https://www.github.com/>. We've >> created a summary of the pros and cons of each system >> <https://github.com/sagemath/sage/wiki/Github-vs-Gitlab-vs-trac>, a >> description >> of the development model to be used on github >> <https://github.com/sagemath/sage/wiki/migration-from-trac-to-Git**b>, >> and a trac ticket <https://trac.sagemath.org/ticket/30363> for >> coordinating work on the transition. More work will need to be done to >> carry out the actual transition once voting is complete. >> >> The voting will last until noon Eastern time (16:00 UTC) on Wednesday, >> October 5. Please use this thread only for sending votes, to make it >> easier to count them afterward; there is a parallel thread where you can >> make arguments in favor of either system. >> >> Finally, I will close with a plea to be involved in this vote and >> discussion even if you are not a core Sage developer. By definition, core >> Sage developers have become comfortable with trac, and I think that one of >> the major arguments in favor of github is that it will help bring in new >> contributors who are not familiar with Sage's development workfow >> <https://doc.sagemath.org/html/en/developer/index.html>. Anyone who has >> ever contributed to the Sage code base or who maintains a Sage user package >> is welcome to vote. >> David >> > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/2543b60f-4ef8-4e44-8a86-3847f7e7b8dbn%40googlegroups.com > <https://groups.google.com/d/msgid/sage-devel/2543b60f-4ef8-4e44-8a86-3847f7e7b8dbn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/51118007-9932-e69f-5eb2-0e6aeb788145%40gmail.com > <https://groups.google.com/d/msgid/sage-devel/51118007-9932-e69f-5eb2-0e6aeb788145%40gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAChs6_%3D8V9OiggmdPZXJQ1WOw16O9nkn63KVGpWVRDyP28cj6A%40mail.gmail.com.
