#16030: Use "git trac" in the developer guide
-------------------------------------+-------------------------------------
       Reporter:  vbraun             |        Owner:
           Type:  enhancement        |       Status:  needs_review
       Priority:  major              |    Milestone:  sage-6.2
      Component:  documentation      |   Resolution:
       Keywords:                     |    Merged in:
        Authors:  Volker Braun       |    Reviewers:  Ralf Stephan
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/kcrisman/ticket/16030            |  e5ebea680cc3281acb9761d625d23426a6ebdb54
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by kcrisman):

 > It should be clear that you won't get very far if you can't compile
 Sage.
 Well, it might not be to someone who has never heard the word "compile"
 before.  Such people should still be able to try out things like adding
 doctests or examples.
 > The "Rebuilding Sage" section already links to the install guide.
 Nope, turns out it was missing `http://` - I'll fix that in a jiffy now.
 > I disagree with you presenting "sage -dev" as an equal alternative.
 Having two competing ways to achieve the same thing is a shitty UI. People
 read the manual because they want to know what is recommended, not what
 one could also do but later learns that most developers don't do. PEP 20:
 "There should be one-- and preferably only one --obvious way to do it."
 I don't know that I always agree with PEP 20.  There are benefits -
 mathematically, for sure - in having more than one way to do things.  I
 would argue this is also true in computer things - I like that I can
 either double-click on a folder OR use the Terminal to "open" it;
 depending on context, they are both useful options.  In fact, this is why
 many people like Perl, right?  Sometimes it's just personality or
 preference, though I do prefer the Python way on this most of the time.
 But it shouldn't be a dogma.

 Anyway, it's not worth discussing at length here; I know you feel this way
 about it (see discussion above).  I was just trying to soften the language
 while still presenting `git trac` as the preferred option.  I don't feel
 like I changed the wording to have it be an equal alternative, but I'm
 open to suggestions while still presenting `sage -dev` as a possible
 option for those who looking for it.

--
Ticket URL: <http://trac.sagemath.org/ticket/16030#comment:55>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to