Re: RW access for german account charts
Nathan Buchanan [EMAIL PROTECTED] writes: Same here...maybe we could make users register for an account similar to how an account is needed for the wiki. Other than that...I like the idea. I'm sorry if the security person in me disagrees; I don't want any random yokel to have a login account on the server. The security wrappers we use MIGHT have bugs in them, so I'd prefer at least a LITTLE vetting. But perhaps reducing the bar to access would be a good thing Yet I can't agree to just allow anyone with an email address access. -derek -- 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 [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: RW access for german account charts
Christian Stimming wrote: It would be fine to have more people with write access to gnucash/trunk/accounts/de_DE/ . OK, so what is the next step? In case you guys go with Chris' suggestion of a separate branch, I'd only ask you not to name it mob. As a contributor, I think I and anyone else deserves to be treated with respect and mob does not quite express that to me. I am sure it was not meant offensively, but the wording is not so super, I'd say. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: RW access for german account charts
On Mon, Sep 03, 2007 at 04:03:13PM +0200, Rolf Leggewie wrote: Christian Stimming wrote: It would be fine to have more people with write access to gnucash/trunk/accounts/de_DE/ . OK, so what is the next step? In case you guys go with Chris' suggestion of a separate branch, I'd only ask you not to name it mob. As a contributor, I think I and anyone else deserves to be treated with respect and mob does not quite express that to me. I am sure it was not meant offensively, but the wording is not so super, I'd say. hehe. I can see your point. While the actual branch name is not important, the designation as a mob branch is actually a term of art. The term is a reference to an essay [1], and it's a term I've seen used by several different projects. Admittedly, it's probably not widely used outside of communities that use a distributed SCM, so I should have explained the term. Nevertheless, I don't think we have any say over the definition of that term. It's certainly not a derogatory term, so I expect it will eventually lose any intial negative connotations people have with it. As to the point at hand, it doesn't seem like anyone is too interested in figuring out how to implement this with svn, so it's probably easiest just to give you access to the directory. So, send Derek or Josh your public key, and see what happens. :) -chris [1] http://www.dreamsongs.com/MobSoftware.html ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: RW access for german account charts
Chris Shoemaker wrote: So, send Derek or Josh your public key, and see what happens. :) Done. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: RW access for german account charts
On 8/31/07, Derek Atkins [EMAIL PROTECTED] wrote: Chris Shoemaker [EMAIL PROTECTED] writes: My recommendation would be to maintain a mob branch. This is a publicly-writable branch from which other devs can cherry-pick commits. This would come in handy for the occasional currency updates, too. And, sometimes, there are good patches that hang out in bugzilla for too long - just because they don't have much visibility. Define publically writable branch? I'm not sure I like the implecation of that. It would require changing the security model on the server to allow unauthenticated writes via svn://, etc.. I'm not sure I like that idea. Same here...maybe we could make users register for an account similar to how an account is needed for the wiki. Other than that...I like the idea. -chris -derek -- 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 [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel -- _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Got Mole problems? Call Avogadro at 6.02 x 10^23. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
RW access for german account charts
Hi, I am interested in maintaining German business related accounts (mainly SKR04 which is what I use). This is very uninteresting work that is of big concern to any German business user, but nobody else. Unfortuntately, that precludes all main devs. Thus, I was wondering if it was possible to seperate out RW privileges for files related to German accounts. If so, I would like to apply for them. And since this is probably more than a single person with a full-time job can achieve on his own, I would hope that Frank Ellenberger would apply as well. I hope it is clear what I am talking about, if not, ask. I originally raised this in http://bugzilla.gnome.org/show_bug.cgi?id=433428#c15 The reason that the normal way of send patches is not ideal is (quoting myself from IRC) (14:53:53) Rolf: Because there are lots of changes to be done right now (14:54:06) Rolf: Because this is shitty work noone wants to do (14:54:18) Rolf: Because you have half-assed implementations all over the place There are more reasons. It really boils down to make it easy for the one that is trying to fix this while encouraging others to chip in as well. If possible, there could be a small group of people with RW access for maintaining the German accounts only. This would not affect gnucash core. Regards Rolf Leggewie ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: RW access for german account charts
On Fri, Aug 31, 2007 at 03:34:33PM +0200, Rolf Leggewie wrote: Hi, I am interested in maintaining German business related accounts (mainly SKR04 which is what I use). This is very uninteresting work that is of big concern to any German business user, but nobody else. Unfortuntately, that precludes all main devs. Thus, I was wondering if it was possible to seperate out RW privileges for files related to German accounts. If so, I would like to apply for them. And since this is probably more than a single person with a full-time job can achieve on his own, I would hope that Frank Ellenberger would apply as well. I hope it is clear what I am talking about, if not, ask. I originally raised this in http://bugzilla.gnome.org/show_bug.cgi?id=433428#c15 The reason that the normal way of send patches is not ideal is (quoting myself from IRC) (14:53:53) Rolf: Because there are lots of changes to be done right now (14:54:06) Rolf: Because this is shitty work noone wants to do (14:54:18) Rolf: Because you have half-assed implementations all over the place There are more reasons. It really boils down to make it easy for the one that is trying to fix this while encouraging others to chip in as well. If possible, there could be a small group of people with RW access for maintaining the German accounts only. This would not affect gnucash core. My recommendation would be to maintain a mob branch. This is a publicly-writable branch from which other devs can cherry-pick commits. This would come in handy for the occasional currency updates, too. And, sometimes, there are good patches that hang out in bugzilla for too long - just because they don't have much visibility. -chris ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: RW access for german account charts
Chris Shoemaker [EMAIL PROTECTED] writes: My recommendation would be to maintain a mob branch. This is a publicly-writable branch from which other devs can cherry-pick commits. This would come in handy for the occasional currency updates, too. And, sometimes, there are good patches that hang out in bugzilla for too long - just because they don't have much visibility. Define publically writable branch? I'm not sure I like the implecation of that. It would require changing the security model on the server to allow unauthenticated writes via svn://, etc.. I'm not sure I like that idea. -chris -derek -- 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 [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
