Re: improving mailing list info

[Frank H. Ellenberger]

Hi, Derek
Am 27.01.2017 um 16:17 schrieb Derek Atkins:
> Hi Hugh!
> Fancy meeting you over here!  :)
> Anyways, I have fixed the mailing list settings now to be more clear.
> 
> -derek
> 
> "D. Hugh Redelmeier"  writes:
:

Could you append ", without diffs" to gnucash-patches in
https://lists.gnucash.org/mailman/listinfo ?
And would it be possible to arrange -changes and -diffs together?

~Frank
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

RE: GnuCash page Documentation Update Instructions has been changed by Sunfish62

[Chris Good]

> -Original Message-
> From: David T. [mailto:sunfis...@yahoo.com]
> Sent: Friday, 27 January 2017 9:04 PM
> To: Geert Janssens 
> Cc: gnucash-devel@gnucash.org; Chris Good 
> Subject: Re: GnuCash page Documentation Update Instructions has been
> changed by Sunfish62
> 
> Geert,
> 
> Thanks as always for providing a clear explanation of the situation. You have
> gently shown me where I have misunderstood the process, and make it
> clearer to me.
> 
> I have entered a version that I think does a reasonable job of promoting git-
> maint as the commonly-used mode, but also explaining when git-master
> might be used. I also included a reference to Git#Branches for the curious.
> 
> Chris, does that work for you? I hope so!
> 
> …Now on to the next areas…
> 
> David
> 
> P.S. Chris, you don’t need to apologize to me for being argumentative; I can
> be obnoxiously argumentative as well—for which I apologize as well.
> 
> > On Jan 27, 2017, at 2:06 PM, Geert Janssens
>  wrote:
> >
> > Op vrijdag 27 januari 2017 11:09:10 CET schreef Chris Good & David T:
> >> On another point, you commented on the page that I took away
> >> information about committing to master. A few things on this: First,
> >> for documentation, a non commit contributor is only going to be
> >> documenting existing features, so they will ALWAYS be using maint.
> >> One of the wiki pages for git states this; I was merely making this agree
> with that.
> >> Second, the pages on git already go into this in more detail (which,
> >> by the way, was why I suggested having one git wiki page earlier), so
> >> adding it here only muddies the water. Third, you did precisely this
> >> with regard to the user of xmllint/xsltproc and make. David
> >>
> >> Non commit  contributors are not the only ones to use this page.
> >> Both Git and Git_For_Newbies say:
> >>  maint
> >>Bugfixes, translations, improvements of the documentation should
> >> *usually* be applied on this branch.
> > For sake of the discussion I will add the exact rule would be that you
> > should document a feature on the same branch as it is available on in
> > the gnucash repository, with maint taking priority over master if it's
> available on both.
> >
> > It's true that currently most new documentation is written for
> > features that have already been released in a stable gnucash version
> > (and hence are on the maint branch), so this documentation should go on
> the maint branch as well.
> > However this is partly because the documentation is running behind so
> > much and the current writers are still catching up (for which I'm
> > immensely grateful!)
> >
> > There is a period in each development cycle where this is not so
> > obvious. When we start releasing development snaphots - the next one
> > being 2.7.0 somewhere later this year - documenters are invited to
> > look at the new features that weren't previously released and write
> > documentation for those. Similar to how translators mostly work on the
> > maint branch, except during the prerelease period. Both are examples of
> when to create patches against the master branch.
> >
> > If you find a way to express this distinction concisely and clearly,
> > I'd love to have this at least mentioned in some way indeed.
> >
> > Geert

Hi David,

Much better thanks!
I have made a couple of slight adjustments.

1.  Changing
for example, when GnuCash is in a development cycle),
To
for example, a feature only in a future stable release),

because GnuCash is effectively always in a development cycle.

2. Changing
For more on this, see [[Git#Branches|Git - Branches]]
To
See [[Git#Branches|Git - Branches]] for more on this.

I have previously been called to task for not ending a sentence with a full 
stop.
When other points at the same list level all end in a full stop, I think we 
should be consistent.
You may have been concerned, like I was, that the full stop would cause 
problems with the link.
I now try to restructure the sentence so the link is not at the end of the 
sentence.

Regards, Chris Good


smime.p7s
Description: S/MIME cryptographic signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: improving mailing list info

[Derek Atkins]

Hi Hugh!
Fancy meeting you over here!  :)
Anyways, I have fixed the mailing list settings now to be more clear.

-derek

"D. Hugh Redelmeier"  writes:

> [beware: newbie posting]
>
> 
>
> contains a line describing gnucash-patches list:
>   gnucash-patches Patches for gnucash (makepatch format)
>
> It seems that this list is (1) read-only and (2) contains commit
> messages from the git repository
>
> Could someone change this, perhaps to:
>   gnucash-patches commit messages from GNUCash git repository (read-only)
>
> 
>
> 
>
> This says:
>
>   About gnucash-patches   
>   English (USA)
>
>   This mailing list is *only* for submitting patches against the current
>   CVS tree. Generally there is no general discussion on this list.
>
>   To see the collection of prior postings to the list, visit the
>   gnucash-patches Archives.
>
>   Or you can search the gnucash-patches Archives.
>   Using gnucash-patches
>
>   To post a message to all the list members, send email to
>   gnucash-patc...@gnucash.org.
>
> But:
>
> 1) the CVS tree has been retired
>
> 2) individuals cannot/shouldn't post to this list
>
> 3) this is list not the way to post patches
>
> The text should be reworded.  Here is a possible rewording
>
>   This mailing list broadcasts commit messages from the GNUCash
>   git repository.
>
>   To see the collection of prior postings to the list, visit the
>   gnucash-patches Archives.
>
>   Or you can search the gnucash-patches Archives.
>
>   Do not post to this list.
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>
>

-- 
   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
   Member, MIT Student Information Processing Board  (SIPB)
   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
   warl...@mit.eduPGP key available
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: GnuCash page Documentation Update Instructions has been changed by Sunfish62

[David T. via gnucash-devel]

Geert,

Thanks as always for providing a clear explanation of the situation. You have 
gently shown me where I have misunderstood the process, and make it clearer to 
me. 

I have entered a version that I think does a reasonable job of promoting 
git-maint as the commonly-used mode, but also explaining when git-master might 
be used. I also included a reference to Git#Branches for the curious.

Chris, does that work for you? I hope so!

…Now on to the next areas…

David

P.S. Chris, you don’t need to apologize to me for being argumentative; I can be 
obnoxiously argumentative as well—for which I apologize as well.

> On Jan 27, 2017, at 2:06 PM, Geert Janssens  
> wrote:
> 
> Op vrijdag 27 januari 2017 11:09:10 CET schreef Chris Good & David T:
>> On another point, you commented on the page that I took
>> away information about committing to master. A few things on this: First,
>> for documentation, a non commit contributor is only going to be documenting
>> existing features, so they will ALWAYS be using maint. One of the wiki
>> pages for git states this; I was merely making this agree with that.
>> Second, the pages on git already go into this in more detail (which, by the
>> way, was why I suggested having one git wiki page earlier), so adding it
>> here only muddies the water. Third, you did precisely this with regard to
>> the user of xmllint/xsltproc and make. David
>> 
>> Non commit  contributors are not the only ones to use this page.
>> Both Git and Git_For_Newbies say:
>>  maint
>>Bugfixes, translations, improvements of the documentation should
>> *usually* be applied on this branch.
> For sake of the discussion I will add the exact rule would be that you should 
> document a feature on the same branch as it is available on in the gnucash 
> repository, with maint taking priority over master if it's available on both.
> 
> It's true that currently most new documentation is written for features that 
> have already been released in a stable gnucash version (and hence are on the 
> maint branch), so this documentation should go on the maint branch as well. 
> However this is partly because the documentation is running behind so much 
> and 
> the current writers are still catching up (for which I'm immensely grateful!)
> 
> There is a period in each development cycle where this is not so obvious. 
> When 
> we start releasing development snaphots - the next one being 2.7.0 somewhere 
> later this year - documenters are invited to look at the new features that 
> weren't previously released and write documentation for those. Similar to how 
> translators mostly work on the maint branch, except during the prerelease 
> period. Both are examples of when to create patches against the master branch.
> 
> If you find a way to express this distinction concisely and clearly, I'd love 
> to have this at least mentioned in some way indeed.
> 
> Geert

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: add comments to clarify that taxtxf.scm is US-specific

[Geert Janssens]

Op donderdag 26 januari 2017 15:34:22 CET schreef John Ralls:
> > On Jan 26, 2017, at 3:13 PM, D. Hugh Redelmeier  wrote:
> > 
> > src/report/locale-specific/us/taxtxf.scm is specific to US tax codes.
> > Add comments to make this clear.
> > 
> > diff --git a/src/report/locale-specific/us/taxtxf.scm
> > b/src/report/locale-specific/us/taxtxf.scm index 7b7e628..e339f2c 100644
> > --- a/src/report/locale-specific/us/taxtxf.scm
> > +++ b/src/report/locale-specific/us/taxtxf.scm
> > @@ -3,9 +3,9 @@
> > ;;
> > ;; updated by  J. Alex Aycinena, July 2008, October 2009
> > ;;
> > -;; This report prints transaction detail and account totals for
> > Tax-related -;; accounts sorted by form/schedule, copy, line and tax
> > code, and exports TXF -;; files for import to TaxCut, TurboTax, etc.
> > +;; This report prints transaction details and account totals for accounts
> > +;; relevant to United States taxes, sorted by form/schedule, copy, line
> > +;; and tax code, and exports TXF files for import to TaxCut, TurboTax,
> > etc. ;;
> > ;; For this to work, the user has to segregate taxable and not taxable
> > ;; income to different accounts, as well as deductible and non-
> 
> Dear Dr. Redelmeier,
> 
> We don't accept patches on the mailing list. Please see
> http://wiki.gnucash.org/wiki/Development#Submitting_Patches for ways that
> you can contribute code.
> 
> In this particular case, though, your patch adds nothing. It's a comment in
> code; such comments are intended solely for developers, and since the path
> to the file includes directories "locale-specific" and "us" it seems pretty
> blindingly obvious that it's for US taxes.
> 
I disagree. While it's only a minor adjustment in the comments, I believe good 
comments are useful as well. We developers tend to consider things obvious 
because we know them for a long time already, but newcomers have to discover a 
lot of implicit knowledge. So if the slight rewording in the comments improves 
this situation for new people, we should include it.

I do agree on the patch submission process of course. In this case however 
since it's such a small patch, I have applied it as is. There's no need to 
resubmit it. For future patches however, please follow the instructions on
http://wiki.gnucash.org/wiki/Development#Submitting_Patches

Thanks for your contribution :)

Geert

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel