Proposal to move foreman hooks to redmine

Hello,

I've been giving foreman_hooks downstream support for some time. For
better integration and planning I propose to move the project to
Redmine instead of github issues.

··· -- Later, Lukas #lzap Zapletal

No thanks, I prefer to use GH issues.

··· On 18/05/16 14:01, Lukas Zapletal wrote: > I've been giving foreman_hooks downstream support for some time. For > better integration and planning I propose to move the project to > Redmine instead of github issues.


Dominic Cleal
dominic@cleal.org

> > I've been giving foreman_hooks downstream support for some time. For
> > better integration and planning I propose to move the project to
> > Redmine instead of github issues.
>
> No thanks, I prefer to use GH issues.
>

General curiosity, do you find GH issues easier overall or is it a project
size differentiation that tips the scale one way or the other?

Thanks,
Eric

··· On Wed, May 18, 2016 at 9:11 AM, Dominic Cleal wrote: > On 18/05/16 14:01, Lukas Zapletal wrote:


Dominic Cleal
dominic@cleal.org


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University

Project size really, there are only a handful of tickets to track.

··· On 19/05/16 01:00, Eric D Helms wrote: > > > On Wed, May 18, 2016 at 9:11 AM, Dominic Cleal > wrote: > > On 18/05/16 14:01, Lukas Zapletal wrote: > > I've been giving foreman_hooks downstream support for some time. For > > better integration and planning I propose to move the project to > > Redmine instead of github issues. > > No thanks, I prefer to use GH issues. > > > General curiosity, do you find GH issues easier overall or is it a > project size differentiation that tips the scale one way or the other?


Dominic Cleal
dominic@cleal.org