On Fri, Dec 13, 2013 at 3:53 PM, Otis Gospodnetic < [email protected]> wrote:
> Aha, that's what I suspected, which is why I wanted to explicitly said I'm > probably missing something about git. Looks like I was missing one of the > core git properties :) Thanks for the info, makes sense to keep both. > > I just dug out the link, now it's part of the git book: http://git-scm.com/book/en/Distributed-Git-Distributed-Workflows Rainer > Otis > -- > Performance Monitoring * Log Analytics * Search Analytics > Solr & Elasticsearch Support * http://sematext.com/ > > > On Fri, Dec 13, 2013 at 9:50 AM, Rainer Gerhards > <[email protected]>wrote: > > > On Fri, Dec 13, 2013 at 3:46 PM, Rainer Gerhards > > <[email protected]>wrote: > > > > > On Fri, Dec 13, 2013 at 3:42 PM, Otis Gospodnetic < > > > [email protected]> wrote: > > > > > >> I agree with everything Paul said here, except the repo bit. I'm not > > sure > > >> why both Adiscon git and Github would be needed..... maybe there is > some > > >> technical reason or business reason? > > > > > > > > > what happens if github fails? SF.net has done so in the past. > > > > > > > > >> Would having both create some code > > >> sync issues? > > > > > > > > > definitely not -- git is *desgined* to support multiple repositories. > > > Actually, if you read git's design principles, doing everything on a > > single > > > repository is strongly recommended against (Linus called it "legacy > mode" > > > and non-scalable IIRC). > > > > > > > > >> Don't know enough about Git here to comment, but one thing to > > >> consider is user (contributor/developer) confusion - which one should > > they > > >> clone, work off of, etc.? > > > > > > > > > > forgot this one, sorry. If you know git (and not just the github > > front-end), you know that this really is no issue at all, because there > are > > always multiple repositories. It's impossile to work with git without > > having your local one. > > > > If you don't know git, you can still use the github site. It's just > another > > published repo. > > > > no bashing, just facts... > > Rainer > > > > > But if you think this is not a real problem, > > >> then ignore me please. > > >> > > >> > > > I hope that page clears the confusion. If not, re-wording help is > > > appreciated (or finger-pointing at what's bad): > > > > > > http://www.rsyslog.com/where-to-find-the-rsyslog-source-code/ > > > > > > Thanks again, > > > Rainer > > > > > > > > >> Otis > > >> -- > > >> Performance Monitoring * Log Analytics * Search Analytics > > >> Solr & Elasticsearch Support * http://sematext.com/ > > >> > > >> > > >> On Fri, Dec 13, 2013 at 3: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. > > >> > > > >> > 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. > > >> > > > >> > > > >> > * 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. > > >> > > > >> > > > >> > * 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://... > > >> > > > >> > > > >> > 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. > > >> > > > >> > > > >> > -- > > >> > Pavel Levshin > > >> > > > >> > > > >> > _______________________________________________ > > >> > 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.
