Hi Martin,
On 6/22/09, Martin Albrecht <m...@informatik.uni-bremen.de> wrote:
>
> Hi,
>
> as mentioned earlier I am preparing a talk on how to get started with Sage
> development for Tuesday here at SD16. A first rc for my set of slides is at:
>
> http://sage.math.washington.edu/home/malb/talks/sagedev.pdf
>
> It still seems rather dull to be honest. I'd appreciate any input.
At times, it's witty. I like the way you use three famous people from
cryptology (Alice, Bob, Eve) in explaining how to write/submit
patches.
Here's a list of typos:
* Page 9, 3rd point
- Please consider submitting you code to Sage
+ Please consider submitting your code to Sage
* Page 15, code example
- sage: preparse("2")
- ’Integer(1)/Integer(2)’
+ sage: preparse ("1/2")
+ ’Integer(1)/Integer(2)’
* Page 26
This page refers to a wiki page for more information about
writing/formatting docstrings. As of Sage 4.0.2, the developer's guide
also has such information. In fact, the information on
writing/formatting docstrings as contained in the developer's guide is
adapted from the wiki page. See this section of the developer's guide:
http://www.sagemath.org/doc/developer/sage_manuals.html
* Page 34, 1st point
- sage -b main to return the the upstream version of Sage
+ sage -b main to return to the upstream version of Sage
* Page 38
- Most Sage developers seem to use an Mercurial extension called
+ Most Sage developers seem to use a Mercurial extension called
* Page 47, 4th point
- mailinglists hardly see any insults and flame wars.
+ mailing lists hardly see any insults and flame wars.
--
Regards
Minh Van Nguyen
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
