For example on page number theory the section 'Divisors' says:
Sage uses divisors(n) for the number [...] of divisors of n ...
and adds the example
divisors(28) [1, 2, 4, 7, 14, 28]
Get a Trac account, check to make sure there isn't already one open for this, and open a new ticket! Any issue, no matter how small, deserves a ticket - certainly any errors.
Well, I certainly hoped that there is a less bureaucratic (and time consuming) way for small and obvious errors in the documentation.
Yes, there is - it's called asking someone else to do so :) One way or another someone must do so. Naturally, reporting it on sage-support or here might lead to that as well. This way we cleverly get people to become Sage contributors :)
As to why Trac tickets at all for "trivial" things: This way we have a full accounting of such things. Any change in Sage currently *must* have a ticket associated with it. The idea is that everything in Sage is open to full public discussion; that does add a layer of bureaucracy, but has saved us from countless dumb introductions of bugs. In the doc case, it usually becomes an opportunity for people to do some additional cleaning up of whitespace or other typos at the same time.
Asked: 13 years ago
Seen: 721 times
Last updated: Mar 27 '12
Copyright Sage, 2010. Some rights reserved under creative commons license. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
