RE: GnuCash page Development has been changed by Jralls
> -Original Message- > From: John Ralls [mailto:jra...@ceridwen.us] > Sent: Wednesday, 6 July 2016 1:06 PM > To: Chris Good > Cc: gnucash-devel > Subject: Re: GnuCash page Development has been changed by Jralls > > > > On Jul 5, 2016, at 4:42 PM, Chris Good > wrote: > > > > Hi John, > > > > Re your last change to http://wiki.gnucash.org/wiki/Development : > > > > Github pull requests: This is the preferred method if the change is > > non-trivial and there isn't already a bug report on the matter. > > > > The above implies to me that if there IS already a bug report, you'd > > prefer a patch. Is that correct? > > Chris, > > I'm trying to make contributing palatable to all comers. > > In reality it depends on how complex the patch is. If it's a big change I'd > rather review it on Github than in plain text on a bug. OTOH if it's a simple fix > it makes more sense and is less work to just do a format-patch and upload it > to BZ, especially if the user doesn't have a github account already. I wouldn't > want to make it seem like that sort of patch is a second-class contribution, > and I don't want to make that paragraph so laden with if-this-then-that that it > turns off casual bug-fixers. > > Can you come up with better wording? > > Regards, > John Ralls Hi John, How about: Github pull requests: This is the preferred method if the change is non-trivial. Patches are also acceptable. Let me know if this is OK and I'll do it. I'm very happy for you to spend your time more productively. Congratulations on 2.6.13 BTW. I haven't seen any reports of problems - nice! Thanks to all developers :-) 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: Authorization for commercial derivative work of GnuCash Tutorial and Concepts Guide
On Tue, Jul 5, 2016 at 8:54 PM, Ted Creedon wrote: > best thing to do is to prototype a sample & submit for approval. > > Submit to whom for approval? By what authority can anyone approve anything that might be submitted? If you said "submit for comments", I would not object. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: GnuCash page Development has been changed by Jralls
> On Jul 6, 2016, at 12:31 AM, Chris Good wrote: > >> -Original Message- >> From: John Ralls [mailto:jra...@ceridwen.us] >> Sent: Wednesday, 6 July 2016 1:06 PM >> To: Chris Good >> Cc: gnucash-devel >> Subject: Re: GnuCash page Development has been changed by Jralls >> >> >>> On Jul 5, 2016, at 4:42 PM, Chris Good >> wrote: >>> >>> Hi John, >>> >>> Re your last change to http://wiki.gnucash.org/wiki/Development : >>> >>> Github pull requests: This is the preferred method if the change is >>> non-trivial and there isn't already a bug report on the matter. >>> >>> The above implies to me that if there IS already a bug report, you'd >>> prefer a patch. Is that correct? >> >> Chris, >> >> I'm trying to make contributing palatable to all comers. >> >> In reality it depends on how complex the patch is. If it's a big change > I'd >> rather review it on Github than in plain text on a bug. OTOH if it's a > simple fix >> it makes more sense and is less work to just do a format-patch and upload > it >> to BZ, especially if the user doesn't have a github account already. I > wouldn't >> want to make it seem like that sort of patch is a second-class > contribution, >> and I don't want to make that paragraph so laden with if-this-then-that > that it >> turns off casual bug-fixers. >> >> Can you come up with better wording? >> >> Regards, >> John Ralls > > Hi John, > > How about: > > Github pull requests: This is the preferred method if the change is > non-trivial. Patches are also acceptable. > > > Let me know if this is OK and I'll do it. I'm very happy for you to spend > your time more productively. > Congratulations on 2.6.13 BTW. I haven't seen any reports of problems - > nice! > Thanks to all developers :-) Chris, That would be redundant. That line is 1 in a numbered list, and 2 is "Attach a patch to a bug report." I've reworded it to make the bugzilla statement a bullet under the item and changed it from "and there isn't..." to "If there is already a bug report on the matter be sure to include a link to the bug in the pull request and comment on the bug with a link to the pull request." I think that conveys exactly what we want. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Authorization for commercial derivative work of GnuCash Tutorial and Concepts Guide
Submit to the previous authors. Consensus. From: Aaron Laws Sent: Wednesday, July 6, 2016 6:02:36 AM To: Ted Creedon Cc: John Ralls; stepbystepf...@mtdata.com; gnucash-devel@gnucash.org Subject: Re: Authorization for commercial derivative work of GnuCash Tutorial and Concepts Guide On Tue, Jul 5, 2016 at 8:54 PM, Ted Creedon mailto:tcree...@easystreet.net>> wrote: best thing to do is to prototype a sample & submit for approval. Submit to whom for approval? By what authority can anyone approve anything that might be submitted? If you said "submit for comments", I would not object. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Authorization for commercial derivative work of GnuCash Tutorial and Concepts Guide
On Wed, Jul 6, 2016 at 10:22 AM, Ted Creedon wrote: > Submit to the previous authors. > > Consensus. > Ah yes, I think if you were able to get ahold of every author of the work, they could collectively decide to license it under different terms. I wouldn't inspire hope in that direction. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
