On Fri, Dec 13, 2013 at 3:52 PM, Boylan, James <[email protected]>wrote:
> You could even create a 'Team' in github that could have specific commiter > control over the document repo. That would allow you to have commiters > specific for that project that wouldn't be controlling any other. That's what I was thinking about - I did at least a little bit of my homework today ;) > It's a good way to setting up the repos. Not sure if something similar can > be done at git.adiscon.com or not. Though I assume it could. > > It could, but in that case I wouldn't care and just mirror the changes over. Some background info on git workflow can be found here: http://git-scm.com/book/en/Distributed-Git-Distributed-Workflows It's just a 2-minute read and may greatly improve the understanding of how git is used outside of a pure github environment. github is an incarnation of the old-style central workflow in that page's words. Rainer > -- James > > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Boylan, James > Sent: Friday, December 13, 2013 8:42 AM > To: rsyslog-users > Subject: Re: [rsyslog] separate doc project? > > It would make some things simpler. I know I spent time trying to find > where the docs were for updating thinking they already were in their own > repo until I realized it was just the one nested in the rsyslog repo. And > it would be easier to work on committer control without compromising the > primary source committing process. > > -- James > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Rainer Gerhards > Sent: Friday, December 13, 2013 8:38 AM > To: rsyslog-users > Subject: [rsyslog] separate doc project? > > Hi all, > > in spite of the recent discussions: would it make sense to create a > separate documentation project? We could do a fresh start with whatever new > system we come up with. > > IMHO we need to be far less strict with commit access in this context. > This is the prime reason I think a separate project would make sense here. > > Comments? > > 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. > _______________________________________________ > 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.
