Hi, Radu is 100% right here. This is what managers often do. They don't do everything themselves. They act as enablers. They remove barriers. For example, I know that at Lucene/Solr we've put a good amount of effort in things like these:
https://www.google.com/search?q=how+to+contribute+to+lucene https://www.google.com/search?q=how+to+contribute+to+solr Check out what's there. Compare to: https://www.google.com/search?q=how+to+contribute+to+rsyslog and the #1 hit: http://www.rsyslog.com/doc/how2help.html So the enablement here should/could be about making it easy to learn how built, how to patch, point people to sending PRs, etc. I see https://github.com/rsyslog/rsyslog/blob/master/doc/build_from_repo.html , but I can't really read it easily and it's not really linked from anywhere visible (like the README) I just added the github link to http://en.wikipedia.org/wiki/Rsyslog#External_links - should help with Google juice. Re helping out - we should help with the PR through blogging on http://blog.sematext.com -- see http://blog.sematext.com/tag/rsyslog/ + https://twitter.com/otisg/status/411508544664387584 Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ On Fri, Dec 13, 2013 at 5:29 AM, Radu Gheorghe <[email protected]>wrote: > 2013/12/13 Rainer Gerhards <[email protected]> > > > On Fri, Dec 13, 2013 at 10:25 AM, Radu Gheorghe <[email protected] > > >wrote: > > > > > 2013/12/13 Rainer Gerhards <[email protected]> > > > > > > > On Fri, Dec 13, 2013 at 9:46 AM, Radu Gheorghe < > > [email protected] > > > > >wrote: > > > > > > > > > Hi Rainer, > > > > > > > > > > Yes, thanks, I want :) > > > > > > > > > > > > > Will have you added today. You'll receive private mail later on. > > > > > > > > > > Thanks! > > > > > > > > > > > > > > > > > > > > Though I think I'll begin by contributing doc improvements via > GitHub > > > > > first. I'll also think of an (easy) way to make the documentation > > more > > > > > obvious, more up-to-date. > > > > > > > > > > In the light of the latest discussions, this is easier said than > > done, > > > so > > > > > for now I think we have quite a lot of ideas and we need to switch > to > > > > > actually doing them :) > > > > > > > > > > > > > Year, this unfortunately was in the past 10 years the point where the > > > > efforts came to a harsh stop ;) I hope it'll be different this time > > (hope > > > > dies last ;)). > > > > > > > > > > > With the risk of starting another philosophical discussion, I'd like to > > add > > > a comment. Actually, it's an opinion, that goes like this: when one or > > more > > > people come with general suggestions like the ones I see more and more > > of, > > > there's an underlying need. Typically, the person > > > suggesting/complaining/etc can't solve the need on their own and they > > need > > > help. > > > > > > For example, if the complaint is "documentation sucks", one typically > > needs > > > help in solving that. The two extremes of "ok, I'll fix it" and "why > > don't > > > you fix it?" are rarely the solution. Because you're already probably > > aware > > > of the problem, do you'd fix it if you had time. But you're already > > doing A > > > LOT of stuff, so you don't. Conversely, the person suggesting probably > > > knows they can contribute a fix. But they can't for some reason (time, > > > skills, fear that the project is too closed, fear that the project will > > go > > > in the "wrong" direction, etc). > > > > > > I think the solution is to meet in the middle somehow, and everyone > > > interested could contribute just a bit. And I think we're all doing > this > > to > > > a certain extent. For example, I've seen you just closed an issue on > > GitHub > > > today. > > > > > > Actually, I just became aware that github requires an explicit "close" -- > > it was done for quite a while... > > > > > > > Cool: activity -> awareness -> hopefully more contributors. You're > > > giving me access rights to contribute documentation. Cool: easier for > me > > to > > > contribute -> more contributions from me -> more awareness -> hopefully > > > more contributors. You've explained that you accept contributions, how > > > Adiscon works and what drives rsyslog development. Cool: people have > more > > > confidence that the project is "open", are more aware of how they can > > > contribute -> hopefully more contributors. I can go on for a while. > > > > > > The bad news is that all this requires people to invest time. It not > free > > > for you to do all this, it's not free for me to contribute, it's not > free > > > for any of us to brainstorm (more or less constructively) like we did > in > > > the recent threads. But it doesn't need to be "all or nothing", I thing > > > small stuff, small optimizations add up. And I hope this will pay off > in > > > the long run. > > > > > > > It's sometimes hard to see this "outside picture", especially if you are > > highly tied in to some other activities. Again, this is why I appreciate > > these comments so much. I'll definitely give it anyother try. > > > > There are some days left before the holiday break, and maybe that's the > > thing to concentrate on now. Actually, it may be worth putting down > > development for a couple of weeks in order to tackle that beast. If doc > and > > these things are actually the top problem for rsyslog to reach it's > > potential, fixing that probably helps much more than new features. I have > > to admit I don't like to do (that kind of) doc, and I am not good and > > relatively slow at it, but it may be the thing that needs to go on top of > > the TODO list... > > > > > Not trying to put you off or anything, but I'm wondering if maybe instead > of writing documentation, your effort would be better invested in making it > easier for others to contribute docs. > > And when I'm saying "wondering", I really mean I don't know what's best. > Because on the other hand, you're the one writing most of the code, and you > know what to write in the docs :) > > This is more complicated than even optimistic-me anticipated... > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > DON'T LIKE THAT. > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
