On Mar 2, 2009, at 2:14 PM, Udo Waechter wrote: > > > On 02.03.2009, at 17:45, Nigel Kersten wrote: > >> >> On Mon, Mar 2, 2009 at 8:15 AM, Steven Jenkins <[email protected]> >> wrote: >>> >>> Luke Kanies wrote: >>>> On Mar 2, 2009, at 10:01 AM, Paul Nasrat wrote: >>>> >>> No question: at this point in Puppet's life, enabling more >>> developers to >>> work on Puppet is more strategic. >> >> ++ >> >> I understand if this should be delayed until after 0.25.x is >> released, >> as that should simplify things somewhat, but I concur that enabling >> more developers is the right way to go. > > > Why would one not want more developers?
Sorry - to be clear, I *definitely* want more developers. It's just not always clear the best way to get them. I got kinda jaded on this early because I spent a bunch of time on this kind of work and saw little readership of it, but I think I was too early and too unwilling to go back and give it another shot. > > I often look at tickets and most of the time I think: Yes, I could fix > this. At least I can imagine how it could be fixed. > But then, I look into the code/and or the places where i would expect > things to happen. And then I do not understand very much. Then, I go > back to writing modules and manifests.... It would be *hugely* helpful to me if you open a documentation ticket when this happens. If there's something you can't pretty easily figure out, please let me know. Part of the problem is knowing where to start in documenting internals. I know what I think is important and complicated, but I've no real idea what you think is. > > It would help me very much if I could have some deeper insights into > how puppet internally works. It is difficult to get to that knowledge > by looking at code. Especially if the software is split up into many > classes/scripts. Like puppet is. Yes, it is well-arranged and > structured, but the flow of information between all these parts > remains mysterious. > I know where to find providers and how those work, but what about the > layer below providers and types? Heh, well, this one's easy: The only thing below the providers is the OS. If you could explain in more detail, I could probably be more helpful, but this is the kind of thing that makes documentation hard for me - I don't really know what you're looking for, and we're working from such a different context that I can't usually determine your documentation needs from the problems you have. > > Some diagrams and flow-charts would propably help already. I guess > this is not very much work for someone who already knows a lot about > the internals of puppet. I'll make sure I spend time on this post 0.25, then. It's clear that the developer community has really grown, and I think now time spent here would be rewarded. -- Every great advance in natural knowledge has involved the absolute rejection of authority. --Thomas H. Huxley --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
