Cool! It looks like we've switched to let's-do-something mode :) Luckily it looks like I have some rsyslog-related work ahead of me and I hope I can contribute back as much of that as possible (especially ES-related stuff). I can't make any promises, but definitely those discussions and suggestions help a lot.
2013/12/13 Rainer Gerhards <[email protected]> > On Fri, Dec 13, 2013 at 11: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] > > > > 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. > > > > I will probably try to get some RST generation mechanism in place, which > would be a very good starting point. That, however, boils down to another > autotools project, which always is a nightmare for me and takes eternally > ... until Michael comes by again and again and fixes my mess. But for this > to make sense, doc needs to be converted etc. As I can't ask Adiscon to pay > someone else to do that, that's obviously something that needs to go into > my non-paid work budget... > > > > > > 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 :) > > > > that's only partially true. For all, I can't iterate enough that I am NOT > GOOD AT writing NON-EXPERT doc. This is the area rsyslog doc lacks much. > > Also, I don't know anything about the hot topics of how to tune /connect > to/ mange with things like ES. While I accept everything, I am > unfortunately not that super-guru that knows the ins and outs of > everything. And... oh wonder, this is the other area where the rsyslog doc > is very bad. Think what you mentioned yourself about ES and logstash and > folks not even knowing rsyslog supports it. OF course, I can write a > "rsyslog does ES" post on the homepage, but will that weak content attract > folks? For sure not. > > So now it's time to ask your company if they are serious in contributing > back and giving you a couple of free days to work on that. You got the > access permissons, Florian is ready to help you get going if that's > required ... so it's totally in YOUR hands ;) Is your company open enough > to support that? Does it thrash schedules and priorities like we do when > important topics come up? Think about how quickly we acted on what was > discussed yesterday -- because it makes sense. Not bashing, but ust taking > your and Otis' comments seriously. > > > > > > This is more complicated than even optimistic-me anticipated... > > > > Welcome in the real life ;) I try to find a balance in the real rsyslog > world for 10 yrs now, and it's always the same... > > Rainer > _______________________________________________ > 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.
