Hi, At http://docs.puppetlabs.com/references/latest/report.html#tagmail I read: "You must have the Ruby RRDtool library installed ... This package may also be available as ruby-rrd or rrdtool-ruby in your distribution’s package management system" Maybe it can be noted in the text, that on Debian and Ubuntu, the package is called ''librrd-ruby''. Regards, Martijn. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
> Maybe it can be noted in the text, that on Debian and Ubuntu, the package > is called ''librrd-ruby''.the best thing would be to open a documentation bug report. Oh and maybe even supply a patch? http://docs.puppetlabs.com/contribute.html ~pete -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Wait, lets see if I understand the requirements for a 5 word addition to the documentation, from a user who doesn''t already use git: 1: go to the page below 2: discover it requires git 3: figure out what git is 4: install a git client 5: figure out how to use same 6: clone the entire repo (I just cloned it, and it weighs in at 13 megs of download, 25 megs of storage) 7: make the change 8: Oops, the page finally links to the docs we needed at step 3 and 5. So now watch a bunch of screencasts. 9: Generate patches. (Fortunately, we just spent an hour watching screencasts. This should be reasonably easy.) 10: Open a ticket. Wait, gotta register with redmine. 11: Register with bug tracker 12: Create a ticket and attach the patch Doesn''t that seem .. I dunno.. insanely bad? How about: 1: go to the page below 2: discover that the change passes the triviality criteria 3: skip to 10 - register and open a ticket. On Wed, Dec 22, 2010 at 10:39 AM, Peter Meier <peter.meier@immerda.ch>wrote:> > Maybe it can be noted in the text, that on Debian and Ubuntu, the package > > is called ''librrd-ruby''. > > the best thing would be to open a documentation bug report. Oh and maybe > even supply a patch? > > http://docs.puppetlabs.com/contribute.html > > ~pete > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi, I was aware of the ''Contribute'' page, and it does indeed seem like a lot of work, even for a reasonably experienced Git user like myself. I will file a documentation bug. Thanks. Regards, Martijn. On 22-12-10 16:54, Disconnect wrote:> Wait, lets see if I understand the requirements for a 5 word addition to > the documentation, from a user who doesn''t already use git: > 1: go to the page below > 2: discover it requires git > 3: figure out what git is > 4: install a git client > 5: figure out how to use same > 6: clone the entire repo (I just cloned it, and it weighs in at 13 megs of > download, 25 megs of storage) > 7: make the change > 8: Oops, the page finally links to the docs we needed at step 3 and 5. So > now watch a bunch of screencasts. > 9: Generate patches. (Fortunately, we just spent an hour watching > screencasts. This should be reasonably easy.) > 10: Open a ticket. Wait, gotta register with redmine. > 11: Register with bug tracker > 12: Create a ticket and attach the patch > > Doesn''t that seem .. I dunno.. insanely bad? > > How about: > 1: go to the page below > 2: discover that the change passes the triviality criteria > 3: skip to 10 - register and open a ticket. > > On Wed, Dec 22, 2010 at 10:39 AM, Peter Meier <peter.meier@immerda.ch > <mailto:peter.meier@immerda.ch>> wrote: > > > Maybe it can be noted in the text, that on Debian and Ubuntu, the > package > > is called ''librrd-ruby''. > > the best thing would be to open a documentation bug report. Oh and maybe > even supply a patch? > > http://docs.puppetlabs.com/contribute.html > > ~pete > > ---- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
> Doesn''t that seem .. I dunno.. insanely bad?I wrote *maybe* (you seem to be able to read...) so what''s your problem? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, Dec 22, 2010 at 7:54 AM, Disconnect <dc.disconnect@gmail.com> wrote:> Wait, lets see if I understand the requirements for a 5 word addition to the > documentation, from a user who doesn''t already use git: > 1: go to the page below > 2: discover it requires git > 3: figure out what git is > 4: install a git client > 5: figure out how to use same > 6: clone the entire repo (I just cloned it, and it weighs in at 13 megs of > download, 25 megs of storage) > 7: make the change > 8: Oops, the page finally links to the docs we needed at step 3 and 5. So > now watch a bunch of screencasts. > 9: Generate patches. (Fortunately, we just spent an hour watching > screencasts. This should be reasonably easy.) > 10: Open a ticket. Wait, gotta register with redmine. > 11: Register with bug tracker > 12: Create a ticket and attach the patch > > Doesn''t that seem .. I dunno.. insanely bad?Don''t you think documentation deserves version control? We accept many changes where people don''t want to go through the overhead of supplying the patch themselves. If they do go to this extra effort for the project however, it''s greatly appreciated.> How about: > 1: go to the page below > 2: discover that the change passes the triviality criteria > 3: skip to 10 - register and open a ticket. > > On Wed, Dec 22, 2010 at 10:39 AM, Peter Meier <peter.meier@immerda.ch> > wrote: >> >> > Maybe it can be noted in the text, that on Debian and Ubuntu, the >> > package >> > is called ''librrd-ruby''. >> >> the best thing would be to open a documentation bug report. Oh and maybe >> even supply a patch? >> >> http://docs.puppetlabs.com/contribute.html >> >> ~pete >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to puppet-users@googlegroups.com. >> To unsubscribe from this group, send email to >> puppet-users+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 12/22/2010 05:28 PM, Nigel Kersten wrote:> On Wed, Dec 22, 2010 at 7:54 AM, Disconnect <dc.disconnect@gmail.com> wrote: >> Wait, lets see if I understand the requirements for a 5 word addition to the >> documentation, from a user who doesn''t already use git: >> 1: go to the page below >> 2: discover it requires git >> 3: figure out what git is >> 4: install a git client >> 5: figure out how to use same >> 6: clone the entire repo (I just cloned it, and it weighs in at 13 megs of >> download, 25 megs of storage) >> 7: make the change >> 8: Oops, the page finally links to the docs we needed at step 3 and 5. So >> now watch a bunch of screencasts. >> 9: Generate patches. (Fortunately, we just spent an hour watching >> screencasts. This should be reasonably easy.) >> 10: Open a ticket. Wait, gotta register with redmine. >> 11: Register with bug tracker >> 12: Create a ticket and attach the patch >> >> Doesn''t that seem .. I dunno.. insanely bad? > > Don''t you think documentation deserves version control? > > We accept many changes where people don''t want to go through the > overhead of supplying the patch themselves. > > If they do go to this extra effort for the project however, it''s > greatly appreciated.Ah, but the current "contributing" document lets git appear mandatory (observe the last paragraph, esp. point (3) of the ticket requirements). I think I shall submit a documentation bug about this ;-) Cheers, Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, Dec 22, 2010 at 11:21 AM, Peter Meier <peter.meier@immerda.ch>wrote:> > Doesn''t that seem .. I dunno.. insanely bad? > > I wrote *maybe* (you seem to be able to read...) so what''s your problem? > >You wrote:> the best thing would be to open a documentation bug report. Oh and maybe > even supply a patch? >The sarcasm in the "maybe" overflowed my monitor and ruined a perfectly good danish. It was the quintessential open source "forget you if you can''t fix it yourself" response. This is a user list - why would "be a developer" ever be an appropriate response? If you didn''t mean it that way, perhaps you should consider rephrasing it or omitting it entirely. "The best thing to do would be to open a documentation bug report in redmine: http://projects.puppetlabs.com/projects/puppet-docs/". The bar for documentation contribution by anyone not already a puppet developer is very high, and this isn''t the first time that "I have a minor fix for you" has been answered this way. On Wed, Dec 22, 2010 at 11:28 AM, Nigel Kersten <nigel@puppetlabs.com>wrote:> On Wed, Dec 22, 2010 at 7:54 AM, Disconnect <dc.disconnect@gmail.com> > wrote: > >> Doesn''t that seem .. I dunno.. insanely bad? >> > > Don''t you think documentation deserves version control? > >Did I say otherwise? A trivial 1 line patch, however, seems like a bad time to enforce a large, bulky policy.> We accept many changes where people don''t want to go through the > overhead of supplying the patch themselves. >Great! I didn''t see that reflected in the documentation, so I opened a ticket: http://projects.puppetlabs.com/issues/5633 There is no patch, in part because the policy for accepting changes needs to be specified by the project.. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
> The sarcasm in the "maybe" overflowed my monitor and ruined a perfectly good > danish. It was the quintessential open source "forget you if you can''t fix > it yourself" response. This is a user list - why would "be a developer" ever > be an appropriate response? If you didn''t mean it that way, perhaps you > should consider rephrasing it or omitting it entirely. "The best thing to do > would be to open a documentation bug report in redmine: > http://projects.puppetlabs.com/projects/puppet-docs/".Yeah, obviously my english is not good enough to not fall into the trap of misunderstood written short-communication. Or, as suggested, rephrasing would be better.> The bar for documentation contribution by anyone not already a puppet > developer is very high, and this isn''t the first time that "I have a minor > fix for you" has been answered this way.I think, that nobody has the idea that patches are required and opening a ticket is in my opinion perfectly fine. At least it ensures that the problem is trackable and hopefully won''t be forgotten. However, if people are able to provide a patch, their fixes will be applied much faster. ~pete -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, Dec 22, 2010 at 8:41 AM, Felix Frank <felix.frank@alumni.tu-berlin.de> wrote:>> We accept many changes where people don''t want to go through the >> overhead of supplying the patch themselves. >> >> If they do go to this extra effort for the project however, it''s >> greatly appreciated. > > Ah, but the current "contributing" document lets git appear mandatory > (observe the last paragraph, esp. point (3) of the ticket requirements). > > I think I shall submit a documentation bug about this ;-)Great catch. That does give a misleading impression, and we''ll get it fixed. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 12/22/2010 06:03 PM, Nigel Kersten wrote:> On Wed, Dec 22, 2010 at 8:41 AM, Felix Frank > <felix.frank@alumni.tu-berlin.de> wrote: > >>> We accept many changes where people don''t want to go through the >>> overhead of supplying the patch themselves. >>> >>> If they do go to this extra effort for the project however, it''s >>> greatly appreciated. >> >> Ah, but the current "contributing" document lets git appear mandatory >> (observe the last paragraph, esp. point (3) of the ticket requirements). >> >> I think I shall submit a documentation bug about this ;-) > > Great catch. That does give a misleading impression, and we''ll get it fixed. >Consider #5634 ;-) -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Felix Frank wrote:> On 12/22/2010 06:03 PM, Nigel Kersten wrote: >> On Wed, Dec 22, 2010 at 8:41 AM, Felix Frank >> <felix.frank@alumni.tu-berlin.de> wrote: >> >>>> We accept many changes where people don''t want to go through the >>>> overhead of supplying the patch themselves. >>>> >>>> If they do go to this extra effort for the project however, it''s >>>> greatly appreciated. >>> Ah, but the current "contributing" document lets git appear mandatory >>> (observe the last paragraph, esp. point (3) of the ticket requirements). >>> >>> I think I shall submit a documentation bug about this ;-) >> Great catch. That does give a misleading impression, and we''ll get it fixed. >> > > Consider #5634 ;-) >Felix Merged! Will be pushed when we next release. Thanks James -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.