On Monday, October 11, 2021 at 1:31:14 AM UTC-7 Dima Pasechnik wrote: > On Mon, Oct 11, 2021 at 1:17 AM Matthias Koeppe <matthia...@gmail.com> > wrote: > >> *(3) Source repository:* Is the source maintained as part of the Sage >> repository using Trac tickets (MONOREPO); or in a separate repository on >> GitHub, GitLab, ... (MULTIREPO)? >> >> This post is dedicated to the MONOREPO vs. MULTIREPO question, and how it >> relates to (1) and (2). >> >> *Some details about MONOREPO:* >> The Sage repository already contains several separate distribution source >> trees. Since Sage 9.4 they are located in the subdirectory SAGE_ROOT/pkgs >> (see >> https://wiki.sagemath.org/ReleaseTours/sage-9.4#New_location_for_distribution_package_sources:_SAGE_ROOT.2Fpkgs >> ). >> For example, SAGE_ROOT/pkgs/*sage-sws2rst* is a self-contained source >> tree of this distribution package: It has standard Python packaging files >> such as setup.py. >> SAGE_ROOT/pkgs/*sagemath-standard* is also a source tree of this >> distribution package; but it is created in part using symbolic links into >> SAGE_ROOT/src. This is the trick that has allowed the modularization effort >> to *keep the SAGE_ROOT/src tree monolithic: *Modularization has been >> happening behind the scenes and will not change where Sage developers find >> the source files. >> >> *In favor of MONOREPO:* >> + The Sage developer community is used to using Trac >> + The process is well defined: No code "ownership" (all Sage developers >> can change any code, subject to peer review); changes are synchronized >> + There is implicit integration testing with all of Sage >> >> *Drawbacks of MONOREPO:* >> - Extra hurdle for attracting new developers from outside the Sage >> developer community (everyone who is not already a Sage developer uses >> GitHub or similar) >> - Testing infrastructure needs to be set up and maintained separately; in >> particular, integration testing with Sage. >> > > you put aside the very fact that dependence on Trac is a problem in itself >
Yes, I agree that Trac itself is a problem. But I have deliberately designed the modularization project in a way that it does NOT require changing people's development workflows. It's... modularized. -- 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/b696d0cf-45e5-4db6-b80f-ace2b0779e73n%40googlegroups.com.
