Re: [foreman-dev] Possible to move redmine Katello project under Foreman?

[Tom McKay]

Thanks @ohadlevy for making this happen.

On Tue, Aug 9, 2016 at 9:29 AM, Tom McKay  wrote:

> The katello project will be moved under foreman as a sub-project next
> week. If there are any concerns, please speak up before then. Thanks!
>
> On Thu, Aug 4, 2016 at 10:03 AM, Lukas Zapletal  wrote:
>
>> > You do realize that every other plugin except Katello is under the
>> foreman
>> > project in redmine, correct?
>>
>> I haven't realized that, sorry for the noise :-)
>>
>> --
>> Later,
>>  Lukas #lzap Zapletal
>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] Possible to move redmine Katello project under Foreman?

[Tom McKay]

The katello project will be moved under foreman as a sub-project next week.
If there are any concerns, please speak up before then. Thanks!

On Thu, Aug 4, 2016 at 10:03 AM, Lukas Zapletal  wrote:

> > You do realize that every other plugin except Katello is under the
> foreman
> > project in redmine, correct?
>
> I haven't realized that, sorry for the noise :-)
>
> --
> Later,
>  Lukas #lzap Zapletal
>
> --
> 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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] Possible to move redmine Katello project under Foreman?

[Lukas Zapletal]

> You do realize that every other plugin except Katello is under the foreman
> project in redmine, correct?

I haven't realized that, sorry for the noise :-)

-- 
Later,
 Lukas #lzap Zapletal

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] Possible to move redmine Katello project under Foreman?

[Tomas Strachota]

On 08/03/2016 06:30 PM, Tom McKay wrote:



On Wed, Aug 3, 2016 at 10:26 AM, Lukas Zapletal mailto:l...@redhat.com>> wrote:

> Is there a case for keeping katello separate any longer, or can we 
combine?

Because it's a plugin? And plugins have its own release cadence, own
planning (Release versions, Target versions) and Categories. I don't see
enough benefits of merging when I consider all the above.

I don't know, I would not like to see Discovery project merged into the
Core. I'd like to keep all plugins separate.


I'm suggesting that we make katello a subproject of foreman. There are
already plugin subprojects (eg. discovery). By moving it under the
single parent project other redmine features become usable (eg. loading
a sprint with issues from both foreman and katello).



+1 for moving it into a subproject and treating it the same as other 
plugins.



--
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+unsubscr...@googlegroups.com
.
For more options, visit https://groups.google.com/d/optout.


--
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] Possible to move redmine Katello project under Foreman?

[David Davis]

Lzap,

You do realize that every other plugin except Katello is under the foreman
project in redmine, correct?


David

On Wed, Aug 3, 2016 at 10:26 AM, Lukas Zapletal  wrote:

> > Is there a case for keeping katello separate any longer, or can we
> combine?
>
> Because it's a plugin? And plugins have its own release cadence, own
> planning (Release versions, Target versions) and Categories. I don't see
> enough benefits of merging when I consider all the above.
>
> I don't know, I would not like to see Discovery project merged into the
> Core. I'd like to keep all plugins separate.
>
> --
> Later,
>  Lukas #lzap Zapletal
>
> --
> 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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] Possible to move redmine Katello project under Foreman?

[Tom McKay]

On Wed, Aug 3, 2016 at 10:26 AM, Lukas Zapletal  wrote:

> > Is there a case for keeping katello separate any longer, or can we
> combine?
>
> Because it's a plugin? And plugins have its own release cadence, own
> planning (Release versions, Target versions) and Categories. I don't see
> enough benefits of merging when I consider all the above.
>
> I don't know, I would not like to see Discovery project merged into the
> Core. I'd like to keep all plugins separate.
>

I'm suggesting that we make katello a subproject of foreman. There are
already plugin subprojects (eg. discovery). By moving it under the single
parent project other redmine features become usable (eg. loading a sprint
with issues from both foreman and katello).

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] Possible to move redmine Katello project under Foreman?

[Ivan Necas]

On Wed, Aug 3, 2016 at 4:26 PM, Lukas Zapletal  wrote:
>> Is there a case for keeping katello separate any longer, or can we combine?
>
> Because it's a plugin? And plugins have its own release cadence, own
> planning (Release versions, Target versions) and Categories. I don't see
> enough benefits of merging when I consider all the above.

Just to make sure we are on the same page, we are not talking about
merging it into Foreman and not having the Katello sub-project,
it's about Katello having it's own tree not being in the Foreman
tree [1]. So effectively it's just a moving it to the similar place where
the rest of plugins is, rather than treating it specially.

[1] - http://projects.theforeman.org/projects

-- Ivan

>
> I don't know, I would not like to see Discovery project merged into the
> Core. I'd like to keep all plugins separate.
>
> --
> Later,
>  Lukas #lzap Zapletal
>
> --
> 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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] Possible to move redmine Katello project under Foreman?

[Lukas Zapletal]

> For example, several dev teams are experimenting with redmine "versions"
> for their sprints[1]. I don't think that a single version can include

One more thing. This will pollute Target versions, I don't like this.

Can't we simply use Issue trackers for that? Redmine is quite good in
creating trackers and associating it. Also, it creates nice place for
conversation about the sprint.

An example of such a tracker:

http://projects.theforeman.org/issues/10294

-- 
Later,
 Lukas #lzap Zapletal

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] Possible to move redmine Katello project under Foreman?

[Lukas Zapletal]

> Is there a case for keeping katello separate any longer, or can we combine?

Because it's a plugin? And plugins have its own release cadence, own
planning (Release versions, Target versions) and Categories. I don't see
enough benefits of merging when I consider all the above.

I don't know, I would not like to see Discovery project merged into the
Core. I'd like to keep all plugins separate.

-- 
Later,
 Lukas #lzap Zapletal

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] Possible to move redmine Katello project under Foreman?

[Andrew Kofink]

+1 to less separation of the two projects in our overhead organization of
issues/features.

Andrew Kofink

Software Engineering Intern
Red Hat Satellite 6
akof...@redhat.com

On Wed, Aug 3, 2016 at 4:08 AM, Marek Hulán  wrote:

> +1 for moving into Foreman project subtree
>
> --
> Marek
>
> On Tuesday 02 of August 2016 17:36:53 Ivan Necas wrote:
> > I think having everything under one tree makes sense. Long-term, the
> > goal is to turn
> > Katello to not feel like a separate project, but rather an extension.
> >
> > +1
> >
> > Of course I'm not aware of some possible consequences if there are any?
> >
> > -- Ivan
> >
> > On Tue, Aug 2, 2016 at 3:56 PM, Tom McKay 
> wrote:
> > > As we try to work towards better bugzilla and redmine component
> > > definitions
> > > and relations, I keep finding myself wishing I could use redmine for
> both
> > > foreman and katello issues together.
> > >
> > > For example, several dev teams are experimenting with redmine
> "versions"
> > > for their sprints[1]. I don't think that a single version can include
> > > issues from both foreman and katello projects. If katello was a
> > > subproject of foreman, though, then teams could bring any issue into
> > > their sprint view.
> > >
> > > Is there a case for keeping katello separate any longer, or can we
> > > combine?
> > >
> > > [1]
> > >
> http://projects.theforeman.org/projects/foreman/roadmap#Team_Ivan_Iteratio
> > > n_1
> > >
> > > --
> > > 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+unsubscr...@googlegroups.com.
> > > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] Possible to move redmine Katello project under Foreman?

[Marek Hulán]

+1 for moving into Foreman project subtree

--
Marek

On Tuesday 02 of August 2016 17:36:53 Ivan Necas wrote:
> I think having everything under one tree makes sense. Long-term, the
> goal is to turn
> Katello to not feel like a separate project, but rather an extension.
> 
> +1
> 
> Of course I'm not aware of some possible consequences if there are any?
> 
> -- Ivan
> 
> On Tue, Aug 2, 2016 at 3:56 PM, Tom McKay  wrote:
> > As we try to work towards better bugzilla and redmine component
> > definitions
> > and relations, I keep finding myself wishing I could use redmine for both
> > foreman and katello issues together.
> > 
> > For example, several dev teams are experimenting with redmine "versions"
> > for their sprints[1]. I don't think that a single version can include
> > issues from both foreman and katello projects. If katello was a
> > subproject of foreman, though, then teams could bring any issue into
> > their sprint view.
> > 
> > Is there a case for keeping katello separate any longer, or can we
> > combine?
> > 
> > [1]
> > http://projects.theforeman.org/projects/foreman/roadmap#Team_Ivan_Iteratio
> > n_1
> > 
> > --
> > 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+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] Possible to move redmine Katello project under Foreman?

[Ivan Necas]

I think having everything under one tree makes sense. Long-term, the
goal is to turn
Katello to not feel like a separate project, but rather an extension.

+1

Of course I'm not aware of some possible consequences if there are any?

-- Ivan

On Tue, Aug 2, 2016 at 3:56 PM, Tom McKay  wrote:
> As we try to work towards better bugzilla and redmine component definitions
> and relations, I keep finding myself wishing I could use redmine for both
> foreman and katello issues together.
>
> For example, several dev teams are experimenting with redmine "versions" for
> their sprints[1]. I don't think that a single version can include issues
> from both foreman and katello projects. If katello was a subproject of
> foreman, though, then teams could bring any issue into their sprint view.
>
> Is there a case for keeping katello separate any longer, or can we combine?
>
> [1]
> http://projects.theforeman.org/projects/foreman/roadmap#Team_Ivan_Iteration_1
>
> --
> 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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[foreman-dev] Possible to move redmine Katello project under Foreman?

[Tom McKay]

As we try to work towards better bugzilla and redmine component definitions
and relations, I keep finding myself wishing I could use redmine for both
foreman and katello issues together.

For example, several dev teams are experimenting with redmine "versions"
for their sprints[1]. I don't think that a single version can include
issues from both foreman and katello projects. If katello was a subproject
of foreman, though, then teams could bring any issue into their sprint view.

Is there a case for keeping katello separate any longer, or can we combine?

[1]
http://projects.theforeman.org/projects/foreman/roadmap#Team_Ivan_Iteration_1

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.