[sage-devel] Re: questions about the "Programming guide"

On Aug 17, 7:31 pm, John H Palmieri <[EMAIL PROTECTED]> wrote: > I've been thinking about editing the Sage Programming Guide, and I > have many questions. See for a first draft. --~--~-~--~~~---~--~~ To post to this

[sage-devel] Re: questions about the "Programming guide"

On Aug 19, 2008, at 11:43 AM, John H Palmieri wrote: > > On Aug 19, 3:00 am, Martin Albrecht <[EMAIL PROTECTED]> > wrote: >> On Tuesday 19 August 2008, mhampton wrote: >> > - the SPKG inclusion guidelines should probably also go into > the Dev > manual. >> >> I meant: >> >>htt

[sage-devel] Re: questions about the "Programming guide"

On Aug 19, 3:00 am, Martin Albrecht <[EMAIL PROTECTED]> wrote: > On Tuesday 19 August 2008, mhampton wrote: > > > > >  - the SPKG inclusion guidelines should probably also go into the Dev > > > > manual. > > I meant: > >    http://wiki.sagemath.org/spkg/InclusionProcedure Great, I don't think I

[sage-devel] Re: questions about the "Programming guide"

On Tue, Aug 19, 2008 at 2:59 AM, Martin Albrecht <[EMAIL PROTECTED]> wrote: > > On Tuesday 19 August 2008, John H Palmieri wrote: >> It says: >> "You might also write additional documentation in \Latex, which is not >> to >> be part of any source code file. The examples in this documentation >> s

[sage-devel] Re: questions about the "Programming guide"

On Tuesday 19 August 2008, mhampton wrote: > > > - the SPKG inclusion guidelines should probably also go into the Dev > > > manual. > > > > Where can I find these guidelines? > > http://wiki.sagemath.org/TracGuidelines These are the Trac guidelines, I meant: http://wiki.sagemath.org/spkg/Inc

[sage-devel] Re: questions about the "Programming guide"

On Tuesday 19 August 2008, John H Palmieri wrote: > It says: > "You might also write additional documentation in \Latex, which is not > to > be part of any source code file. The examples in this documentation > should be contained in verbatim environments. The examples should be > tested using \

[sage-devel] Re: questions about the "Programming guide"

> Although these improvements could possibly go in TracGuidelines, I > feel that they may be useful in developer docs, (especially for new > developers, I'm sure both of these points are non-issues for seasoned > developers). My impression is: The wiki is a wonderful resource of outdated, random

[sage-devel] Re: questions about the "Programming guide"

I'd also like to add a couple of issues I had with the sage documentation: The process of submitting a patch isn't documented clearly enough. For example, nowhere does it say that if you have a ticked with a patch, you need to manually add [with patch; needs review] It would be nice to have an up

[sage-devel] Re: questions about the "Programming guide"

On Mon, Aug 18, 2008 at 9:35 PM, Alec Mihailovs <[EMAIL PROTECTED]> wrote: > > Guys, I started to read that recently, and it's really appalling. How long > do you post on the Usenet? One of the first thing one should to learn is not > to quote the previous message in full, or most of it. Quote onl

[sage-devel] Re: questions about the "Programming guide"

Just random pick from today's mail, follows below, and sorry for top posting. 100+ lines of quotting (I didn't really count, it may be less than that) and 4 lines of comment. With my spam rules (everything with more than 50% of quotting goes to junk mail) it went directly there, where it belong

[sage-devel] Re: questions about the "Programming guide"

> - Show quoted text - I didn't mean exactly your post. It was just a note in general. What is the point in quoting if you read posts in Google? Everything is there, above. It's just clogging my mail and I really don't see any point in it. What is the point? Alec --~--~-~--~~--

[sage-devel] Re: questions about the "Programming guide"

On Aug 18, 9:35 pm, "Alec Mihailovs" <[EMAIL PROTECTED]> wrote: > Guys, I started to read that recently, and it's really appalling. How long > do you post on the Usenet? One of the first thing one should to learn is not > to quote the previous message in full, or most of it. Quote only the part >

[sage-devel] Re: questions about the "Programming guide"

Guys, I started to read that recently, and it's really appalling. How long do you post on the Usenet? One of the first thing one should to learn is not to quote the previous message in full, or most of it. Quote only the part that you respond to. Please. Alec --~--~-~--~~--

[sage-devel] Re: questions about the "Programming guide"

On Aug 18, 8:33 pm, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > On Aug 18, 2008, at 4:41 PM, John H Palmieri wrote: > > > On Aug 18, 2:02 am, Martin Albrecht <[EMAIL PROTECTED]> > > wrote: > >> On Monday 18 August 2008, John H Palmieri wrote: > > >>> I've been thinking about editing the Sage Pr

[sage-devel] Re: questions about the "Programming guide"

On Aug 18, 2008, at 4:41 PM, John H Palmieri wrote: > On Aug 18, 2:02 am, Martin Albrecht <[EMAIL PROTECTED]> > wrote: >> On Monday 18 August 2008, John H Palmieri wrote: >> >>> I've been thinking about editing the Sage Programming Guide, and I >>> have many questions. >> >> Great! The survey sho

[sage-devel] Re: questions about the "Programming guide"

> > - the SPKG inclusion guidelines should probably also go into the Dev > > manual. > > Where can I find these guidelines? > http://wiki.sagemath.org/TracGuidelines --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsub

[sage-devel] Re: questions about the "Programming guide"

On Aug 18, 2:02 am, Martin Albrecht <[EMAIL PROTECTED]> wrote: > On Monday 18 August 2008, John H Palmieri wrote: > > > I've been thinking about editing the Sage Programming Guide, and I > > have many questions. > > Great! The survey showed that good developer docs is one of our main > weaknesse

[sage-devel] Re: questions about the "Programming guide"

More questions about the Programming Guide: It says: "You might also write additional documentation in \Latex, which is not to be part of any source code file. The examples in this documentation should be contained in verbatim environments. The examples should be tested using \code{sage-testtex

[sage-devel] Re: questions about the "Programming guide"

On Monday 18 August 2008, John H Palmieri wrote: > I've been thinking about editing the Sage Programming Guide, and I > have many questions. Great! The survey showed that good developer docs is one of our main weaknesses. > First, what do you think about changing the name to the Sage > Develope