Hi James, Big +1 to addressing one thing at a time. In the order of importance, I might add, and documentation is up there, IMO.
Through I still think it's valuable to brainstorm and think about the general directions. Because it's nice to know where you're going when contributing, instead of fearing that your work may be useless and thrown away after a while. For example, if we decide to have GitHub as the primary go-to place (and others as backups), I would feel much better about contributing to the Wiki there, or adding issues. In the same way, once it's sorted out how the documentation will look like, it would be much clearer how to contribute, and contributions will start flowing more easily. I think. And hope :) 2013/12/15 Boylan, James <[email protected]> > Rainer and I have already been discussing the possibility of migrating > most, though not all, of the web content into the Rsyslog-docs system. We > both think this likely would be a good idea. > > However you need to do one thing at a time. Currently the focus is fixing > the existing documentation. Once that is done we'll address the next part. > If we try to change too much all at once you end up not properly > implementing it and creating more issues than the hope is to solve. > > -- James > -- Sent from my mobile -- > > ----- Reply message ----- > From: "Radu Gheorghe" <[email protected]> > To: "rsyslog-users" <[email protected]> > Subject: [rsyslog] Data source fragmentation? > Date: Sun, Dec 15, 2013 11:00 AM > > One comment regarding Logstash: The documentation you see on > logstash.net/docs is generated from code comments. So most contributions > to > logstash.net come from GitHub, even if you look at that site separately. > > I think this is an idea we can "emulate", and we already do with > rsyslog.com/doc taking the documentation from the package. Which can now > be > contributed to via GitHub. > > > 2013/12/15 Otis Gospodnetic <[email protected]> > > > Right, I mentioned something related to this in the passing in one of the > > last week's threads - in my humble opinion the benefits outweigh the > > potential costs. When Github starts having issues people will build > tools > > to export everything from it. I personally would not worry about that. > > > > But valid point with Logstash. I never got the feeling of fragmentation > > there. But I just looked and indeed the only thing Logstash uses on > Github > > is the repo. Yet, it doesn't feel fragmented.... I have a feeling that's > > because I never actually look at logstash.net or logstash.jira.com. I > > mainly see it through commits people make, so to me it felt like it's all > > on Github, when in fact it is not. > > > > Of course, just because Logstash was mentioned as having a good > > CONTRIBUTING doc, doesn't mean it should be used as the ideal example. > For > > example, here are 2 projects that are making better use of Github: > > https://github.com/elasticsearch/kibana > > https://github.com/elasticsearch/elasticsearch > > > > Otis > > -- > > Performance Monitoring * Log Analytics * Search Analytics > > Solr & Elasticsearch Support * http://sematext.com/ > > > > > > > > On Sun, Dec 15, 2013 at 11:39 AM, Rainer Gerhards > > <[email protected]>wrote: > > > > > On Sun, Dec 15, 2013 at 5:31 PM, Otis Gospodnetic < > > > [email protected]> wrote: > > > > > > > Hi, > > > > > > > > * main repo is on Github, but the issues are in some external > Bugzilla > > > > instance, where users need separate accounts and that cannot > cross-link > > > to > > > > pull requests or where users cannot easily > > @GetSomebodysAttentionLikeThis > > > > > > > > * some docs are going to be in docs in some Github repo, but there > are > > > also > > > > docs on rsyslog.com > > > > > > > > * Github has a Wiki, but it's not used and there is a separate Wiki > on > > > > rsyslog.com and it requires a separate account (same or different > from > > > > Bugzilla?) > > > > > > > > Does this feel like it will be a PITA for contributors and even > > consumers > > > > of info stored in all these various places? > > > > > > > > > > > I am glad I blogged about, so here is another reference: > > > > > > > > > > > > http://blog.gerhards.net/2013/12/why-is-rsyslog-project-running-its-own.html > > > > > > Comments are welcome. > > > > > > Rainer > > > > > > > > > > Otis > > > > -- > > > > Performance Monitoring * Log Analytics * Search Analytics > > > > Solr & Elasticsearch Support * http://sematext.com/ > > > > > > > > > > > > On Sun, Dec 15, 2013 at 3:19 AM, Radu Gheorghe < > > [email protected] > > > > >wrote: > > > > > > > > > Everything you can see under: > > > > > www.rsyslog.com/doc/<http://www.rsyslog.com/doc/> > > > > > > > > > > Is from the rsyslog package: > > > > > https://github.com/rsyslog/rsyslog/tree/master/doc > > > > > > > > > > There's also a wiki one can contribute too (once you create an > > account > > > > > which is pretty trivial): > > > > > http://wiki.rsyslog.com/index.php/Main_Page > > > > > > > > > > I guess this ^^^^^^^^ information needs to be somewhere in the "how > > to > > > > > contribute" document(s). Do you guys agree? Should I do a pull > > request > > > to > > > > > the README on github? > > > > > > > > > _______________________________________________ > > > > 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. > > > > > _______________________________________________ > > 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. > _______________________________________________ > 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.
