2013/12/15 Rainer Gerhards <[email protected]>

> 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.
>
>
When I saw this one my first thought was "yeah, and your blog is yet
another place for documentation". Then I thought I'm just as guilty for
posting stuff on blog.sematext.com - yet another place.

I'm thinking if there's a way to keep this "independence", and still have a
central place to look for stuff. For example, like you have a script to
sync the GitHub repo to the Adiscon git... could we sync Bugzilla with the
issues?

Or maybe even skip trying to keep them in sync. How about leaving a note in
Bugzilla "please open issues on GitHub"? There are not that many issues
there right now, anyway. And if we know we can revert to Bugzilla, we know
we have a way out, if GitHub pulls out a SourceForge.
_______________________________________________
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.

Reply via email to