I just realized that I was not really clear with my initial question. Sorry about that. What I actually meant to ask for was "what bug tracker to use for web-site related issues". So not about rsyslog bugs and enhancements, but all those things that need to be changed *on the web site itself* (there are ample as we have seen in the past days). This question still is open, but I tend even more to do a dummy project on github like rsyslog-website just to get things to one central place.
Looks like I also initiated the broader discussion on which bug tracker to use in general. We currently run a bugzilla (for quite some while) and I fully agree that it takes time to maintain it. Now after some good experience with github, I admit that I would actually prefer to move to a single location, and github would probably be the right one. I think I'll especially check Tomas suggestion that we can get backups out of github, which would really relieve me of many of the issues I had with a github-only approach. Assuming this works, I'd go ahead and change the existing bugzilla to become a read-only reference and add new trackers to github, only. If we run into issues with github, we could reverse that process at some later time. As usual, comments are more than welcome. Rainer On Thu, Feb 13, 2014 at 10:33 AM, Thomas D. <whi...@whissi.de> wrote: > Hi, > > I would use only one place. It doesn't matter if it is something you > provider or Github or BitBucket or.. but I prefer a single location. > > +1 for GitHub: It is well known and many people contributing to Open > Source projects already have an account. So I see higher chances for new > contributing people because they don't have to register somewhere else > just to post a bug and/or a fix. > > Also: I don't know how familiar you are with hosting/maintaining such > services (it isn't enough just to install Bugzilla, you have to do > maintenance, backups..). So using a service like GitHub may give you > more time for the project.. > > BUT.. if you don't host it yourself you should look into a way to backup > all your project data in case you have to move away from the "cloud" > solution you choose. > I know that this is possible with GitHub so I would recommend you to > create a workflow/automatic process to dump all the projects data (not > just the repository, also the issue tracker, Wiki...) on a regular base. > And you should really know that you are having a valid backup because > when trouble arise it is maybe already too late ;) > > > -Thomas > _______________________________________________ > 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.
