Ask Your Question
1

What is the best way to report small glitches in the docs?

asked 2012-03-27 08:24:43 -0500

petropolis gravatar image

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]
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
1

answered 2012-03-27 08:46:29 -0500

kcrisman gravatar image

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.

edit flag offensive delete link more

Comments

1

Well, I certainly hoped that there is a less bureaucratic (and time consuming) way for small and obvious errors in the documentation.

petropolis gravatar imagepetropolis ( 2012-03-27 10:04:21 -0500 )edit

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 :)

kcrisman gravatar imagekcrisman ( 2012-03-27 15:40:53 -0500 )edit

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.

kcrisman gravatar imagekcrisman ( 2012-03-27 15:42:02 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2012-03-27 08:24:43 -0500

Seen: 197 times

Last updated: Mar 27 '12