On Fri, Dec 13, 2013 at 9:37 AM, Pavel Levshin <[email protected]> wrote:
> 13.12.2013 0:12, Rainer Gerhards: > > On Thu, Dec 12, 2013 at 8:01 PM, Otis Gospodnetic < >> [email protected]> wrote: >> >> Hi, >>> >>> Thanks David & Rainer. The last few emails were very constructive and >>> pragmatic. Based on what I heard I'd think you'd want to push things >>> towards Github. Ignore Apache for now at least. >>> * Make Github *the only* source (i.e. not Adiscon git) >>> >>> why? >> > > I see no reason to make it *the only*, but it should be more visible than > it is now, and, if so, it should be at least equal to Adiscon repo in terms > of "actuality". Taking me as an example, I've found this GitHub repository > by accident, while browsing through other obsolete forks. > > I have taken my developer hat off today to look into these issues. If there is an even remote chance this will help with contributions, it's worth it. I've begun to do some writeups. This one addresses what you say: http://www.rsyslog.com/where-to-find-the-rsyslog-source-code/ > GitHub interface is more user-friendly than git.adicson.com, it has many > usable features, and it allows to contribute more than a single patch. > > ack (but I usually work with git on the command line, going through a web app -if that's required- sounds like a bad idea for me; but so far this was never required). > > * Make >>> >>> https://github.com/rgerhards/rsyslog/blob/master/doc/build_ >>> from_repo.htmlmore >>> prominent (and markup, not HTML) >>> >>> "markup, not HTML" easy said... >> > > Indeed, but this is a major problem with rsyslog documentation. HTML does > not imply anything about how things should look. Therefore, > differently-looking doc pages become an ugly, unstructured heap. This also > prevents others to contribute or improve docs. > > Many years ago, I've used Perl POD in an alike situation. It is > oversimplified, and this allows to concentrate on contents. It helped in my > case. But I do not think this one is suitable for rsyslog. > > I hope someone knows a format which will fit rsyslog better. > > RST is a good fit, as Radu said. But it also needs work, both for setting up the build system as well as converting the existing doc set. Would definitely be a win. New things I've authored in RST. > * Link it from rsyslog.com. Your github repo clearly doesn't have much >>> Google juice. Maybe David can pull some strings? ;) >>> >>> >>> that'll happen tomorrow >> > > I would suggest to have GitHub repos crosslinked from git.adiscon.com, > also. BTW, some of smaller adiscon repos did not work for me when I've > tried to pull via http://... good idea! Will see that we can do that today. > > what saddens me is that we seem to be conceived as "closed". The root of >> rsyslog is that we wanted to provide a real open soure alternative to an >> (at that time) becoming more and more closed syslog-ng: >> > > Rsyslog can appear "closed", indeed, because it is not obvious for anyone > not on the list that you, being a maintainer, backed by a company, will > accept anything. It needs some PR to form public opinion. For example, a > track of succesful pull requests, or even a "banner" on main page of > official site, and much more than that. Try to look to the project from > outside, and you'll see. > Looking from the outside is obviously not always easy. That (among others) is why I appreciate the feedback on this list so much. And as I have written yesterday, some help with the PR would be immensely useful and highly appreciated. Thanks! 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.
