I think having a "support" button that is linked to sage-support is an excellent idea. Watching my students use Sage, all they ever see is the notebook. If its not there, it doesn't exist for them. Most of them don't even click on "help", they bug my TA or me about things. Actually, the "help" page is currently oriented more towards a mature user (by that I mean, someone maybe new to Sage but with at least a little programming/shell/CAS experience).
-M. Hampton On Jun 26, 11:31 am, Harald Schilly <[EMAIL PROTECTED]> wrote: > On Jun 26, 6:46 pm, kcrisman <[EMAIL PROTECTED]> wrote: > > > 2) and 3) are good but miss my point - to make it one click from the > > notebook to (for instance) the sage-support/post page > > Maybe, a link to an explanatory page like the "guidelines" with a link > to the post page is better... > > > On the other hand, making this prominent says, "we want bug reports" > > loud and clear. Or does it say, "buggy software" loud and clear? > > Anyway... > > Yes, it does ;) > The difference is, that open-source software tends to talk about their > bugs. So, it is a matter of personal background how you interpret > this. With no personal background about OSS you will probably not > think that it is worth to download and invest time if it talks too > much about bugs. > So, maybe, more prominent links should just talk about "support" and > "help" and not about "bugs"? Then, it is up to the developers to > decide, if a "support issue" is a bug, feature request or a pebkac ;) > This is probably already the current state ... > > h --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
