On Wed, Jul 25, 2018 at 8:03 AM jplab <jeanphilippela...@gmail.com> wrote: > > Hi, > > It is great to have a recent snapshot of the status of Sage and a wishlist! > > This summer marks the 10th year when my brother showed me Sage for > the first time at the beginning of my master (So happy I did not need to > use Maple or Matematica any more...). It is awesome to see it so > lively and to be able to participate in improving it! > > On the number of contribution graph, it seems that the number increased > since the move to git in around 2014? Is that accurate? > > About moving trac to github, I have been aware of gitlab, an "open-core" > competitor of gitlab. My institution uses it instead of github as its platform > for internal collaborations. As I am not an expert in this respect, but I find > it interesting to consider, as you mention that your computer was 100% > open source apart from Magma. Here's a letter from the CEO of gitlab, > from 2 years ago last week: > > https://about.gitlab.com/2016/07/20/gitlab-is-open-core-github-is-closed-source/ > > which ends by: > > "In conclusion (TLDR), GitLab has an open core business model and ships > both open and closed source software. GitHub hosts most open source > projects but ships closed source software." > > For what it's worth, I thought I would mention it here...
We've been keeping quiet about it because we want things to be working before we start a big discussion / flame war about it but Julian Rüth and I have already been making some inroads towards enhancing Sage development on GitLab (as opposed to GitHub), which we chose in part *because* we believe it to be more politically palatable to the Sage community (this was even before the Microsoft buyout news), as well as the ability to go self-hosted if needed, as well as the nice built-in continuous integration capabilities. I discussed this a bit in a recent ticket: https://trac.sagemath.org/ticket/25914 See also Julian's herculean effort in: https://trac.sagemath.org/ticket/24655 Also, FWIW I should be clear, I personally do *not* want to kill of Sage's Trac any time soon. But I do think there are benefits to accepting contributions through GitLab including but not limited to: 1) More accessible, especially to newcomers, who don't have to learn a new tool / workflow (even if they have not used GitLab before, it's reasonably familiar to anyone who's used GitHub, and allows logging in with their existing GitHub credentials). 2) Just hands-down better code review UX. and eventually, 3) A better continuous integration experience too--the sage patchbot is quite nice, but it will be even nicer to have a *consistent* manner of feedback for changes, whereas sage's informal patchbot fleet is notoriously unreliable. (The buildbot fleet, on the other hand, still has great value in providing slower CI on a wider range of platforms). In order to allow Trac and GitLab to be used simultaneously I've even been working on integration between the two through their respective APIs through Sage's Trac plugin. See e.g.: https://github.com/sagemath/sage_trac_plugin/commit/69aee69c6ac8b0ae67ac483a5085e3e71145bb1c All this is to say, this is one bullet point in William's slides that is being worked on. I believe some others are being worked on too, as able, but progress is slow. I agree with all the main bullet points (other than the one minor one I pointed out ;) -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
