#17634: Rephrase the 'sage manuals' section of the developer manual
-------------------------+-------------------------------------------------
       Reporter:         |        Owner:
  ncohen                 |       Status:  needs_review
           Type:         |    Milestone:  sage-6.5
  enhancement            |   Resolution:
       Priority:  major  |    Merged in:
      Component:         |    Reviewers:
  documentation          |  Work issues:
       Keywords:         |       Commit:
        Authors:         |  adffa81b264ca4414d96e6f2d4bcc51b7e003c34
  Nathann Cohen          |     Stopgaps:
Report Upstream:  N/A    |
         Branch:         |
  public/17634           |
   Dependencies:         |
-------------------------+-------------------------------------------------

Comment (by kcrisman):

 I've been away from computer all day and don't have time to look at this
 in detail, but if you ''really'' think that moving the sws2rst thing out
 is a good idea, there had better be a link to wherever you move it to in
 the developer guide.  The reason that document even exists is because
 someone wanted to contribute to the thematic tutorials (hence, to be a
 developer!) and couldn't figure out how to do it without writing her own
 document to explain it.  So it was clearly valuable in the developer
 sense, turning things not just into rst files but into contributed
 documentation.  Does that explain it sufficiently?  Sorry if it's
 confusing because of my hurry.

--
Ticket URL: <http://trac.sagemath.org/ticket/17634#comment:4>
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