Hi all, I'm only an occasional developer with sage, but I wanted to also bring up one (minor) positive for moving to github which is less technical. Moving to github would be a motivating factor for people to contribute to sagemath as it gives a pathway to work in industry (programming) if they chose to leave academia. In particular, github shows contributions made by a user to various projects. This could be a valuable tool for someone on the job market who would prefer (or has no choice) to move to industry and get a programming job. Sure, one can already currently say that one develops for sagemath, but by putting it on github it creates a unified location for future employers to look. As mentioned, this is just a minor positive, but could be a motivating factor for some.
Also, I concur with Vincent in that we should have somewhere with a list of pros/cons for either side in some kind of list fashion as currently it's a little hard to keep track of whether people are making the same arguments or new arguments. Kindly, Aram Dermenjian On Sat, 10 Sept 2022 at 09:35, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > Hello, > > I am in the same mood as Travis : if I was to consider a move to > github I would like to have a clear and complete overview of the > changes in the workflow (how do we set ticket dependencies? how > reviews will work? management of releases? etc). For me the discussion > in this thread is very premature as there is no proposal of this sort. > The "moving to github" does not specify how things will work. > > I see clear advantages of moving to github. The first being trac > maintenance and a second example that William mentioned is that it > might lower the barrier for newcomers. But there are also plenty of > reasons not to migrate. The first one I think is that we might loose > active developers. Let me recall that the move from mercurial to git > some 10 years ago made many active developers quit. > > So I would like to propose that ticket #30363 instead of being > technical (ie how do we do the move) explains > - a concrete proposal for a github workflow (there might be several of > them) > - list the pros > - list the cons > Then we could proceed with a reasonable discussion on whether we will > do such move. > > Ideally (if we had illimited developer time) I would like to encourage > the possibility of having both trac and github. If I recall correctly, > it was possible to authenticate to trac with github account and make > PR on github that automatically transformed into a ticket on trac. > > Best > Vincent > > On Sat, 10 Sept 2022 at 09:54, Dima Pasechnik <dimp...@gmail.com> wrote: > > > > > > > > On Sat, 10 Sep 2022, 05:48 Matthias Koeppe, <matthiaskoe...@gmail.com> > wrote: > >> > >> On Friday, September 9, 2022 at 9:34:16 PM UTC-7 Travis Scrimshaw wrote: > >>> > >>> I really dislike Github's decentralized approach with PR and having to > have separate clones of the repo within each user. My understanding is if > two people have different fixes, then they individually submit PRs that are > not explicitly linked with each other, much less with a specific bug report > issue. > >> > >> > >> In the PR you would include a comment such as "Fixes #1234", which > links it to an Issue (bug report). > > > > > > and this Issue will then automatically get a comment/mention linking to > the PR, no manual intervention in the Issue is needed. > > > > > >> Yes, there can be multiple competing PRs in order solve one ticket. > Better than edit wars on a Trac ticket. > >> > >> > >> -- > >> 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/2548301a-19d8-4ab5-ab1c-84f3fdcf5bbcn%40googlegroups.com > . > > > > -- > > 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/CAAWYfq3rdAfkj%3DkDLJa0TxMPxLHz4O2_stffO8F-PyiGsO0ZqQ%40mail.gmail.com > . > > -- > 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/CAGEwAAkYpD4fh%3D_QvuwmZoRSgrF6AgUeg1WWvbXMhX-DJ5hanA%40mail.gmail.com > . > -- 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/CAKQMtir03oQsrdJb06_%2Bi4cdVDtxAdZ8pszcbw3C0juqi87mXA%40mail.gmail.com.
