Re: [Pulp-dev] Installer project

[Brian Bouterse]

At today's installer meeting, the installer team agreed to:
* keep the installer items in the pulpcore Redmine and not have a separate
Redmine for it
* Add a Component named 'Installer'. New installer items should be filed
with that component set. [done]
* A new saved query has been created to show installer items:
https://pulp.plan.io/projects/pulp/issues?query_id=156 [done]
* The triage query was updated to disinclude Installer items [done]
* Existing items with the 'Pulp 3 Installer' tag had that tag removed (but
others left) and Component=Installer set [done]
* The 'Pulp 3 Installer' was removed [done]


On Mon, May 11, 2020 at 10:23 AM Ina Panova  wrote:

>
> 
> Regards,
>
> Ina Panova
> Senior Software Engineer| Pulp| Red Hat Inc.
>
> "Do not go where the path may lead,
>  go instead where there is no path and leave a trail."
>
>
> On Fri, May 8, 2020 at 3:55 PM Brian Bouterse  wrote:
>
>>
>>
>> On Tue, May 5, 2020 at 10:48 AM David Davis 
>> wrote:
>>
>>> During triage today, a majority of the issues that came up were for the
>>> installer but only a handful of people could really speak to these issues.
>>> I proposed that we skip these issues during triage and let the installer
>>> team triage them.
>>>
>> I agree with this observation, a triage where not everyone can speak to
>> issues isn't a good use of time. Overall I wonder if having an all-hands
>> triage makes sense anymore given the mini-teams organization these days.
>>
>
>>> In order to do so, we'd have to create a separate project in redmine. My
>>> initial feeling is that this makes sense since the installer work has
>>> really grown into its own project and is no longer in the purview of
>>> pulpcore.
>>>
>> What about us reconfiguring the triage query to disinclude issues with
>> the installer tag on them as an alternative?
>>
>
> It feels like there will be less traction and confusion ( whether to open
> an issue against pulp or installer project) if we add an installer tag,
> however the installer team would need to make sure that installer issues
> have the tag before the triage so they do get filtered out.
>
>
>>
>>> Thoughts?
>>>
>>> I'll put a deadline on this discussion for May 8 unless we don't reach a
>>> consensus by then.
>>>
>>> David
>>> ___
>>> Pulp-dev mailing list
>>> Pulp-dev@redhat.com
>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>
>> ___
>> Pulp-dev mailing list
>> Pulp-dev@redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Installer project

[Ina Panova]

Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."


On Fri, May 8, 2020 at 3:55 PM Brian Bouterse  wrote:

>
>
> On Tue, May 5, 2020 at 10:48 AM David Davis  wrote:
>
>> During triage today, a majority of the issues that came up were for the
>> installer but only a handful of people could really speak to these issues.
>> I proposed that we skip these issues during triage and let the installer
>> team triage them.
>>
> I agree with this observation, a triage where not everyone can speak to
> issues isn't a good use of time. Overall I wonder if having an all-hands
> triage makes sense anymore given the mini-teams organization these days.
>

>> In order to do so, we'd have to create a separate project in redmine. My
>> initial feeling is that this makes sense since the installer work has
>> really grown into its own project and is no longer in the purview of
>> pulpcore.
>>
> What about us reconfiguring the triage query to disinclude issues with the
> installer tag on them as an alternative?
>

It feels like there will be less traction and confusion ( whether to open
an issue against pulp or installer project) if we add an installer tag,
however the installer team would need to make sure that installer issues
have the tag before the triage so they do get filtered out.


>
>> Thoughts?
>>
>> I'll put a deadline on this discussion for May 8 unless we don't reach a
>> consensus by then.
>>
>> David
>> ___
>> Pulp-dev mailing list
>> Pulp-dev@redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Installer project

[Mike DePaulo]

+1 to the plan.

(We discussed this at PulpCon too, and concluded this.)

On Fri, May 8, 2020 at 9:55 AM Brian Bouterse  wrote:

>
>
> On Tue, May 5, 2020 at 10:48 AM David Davis  wrote:
>
>> During triage today, a majority of the issues that came up were for the
>> installer but only a handful of people could really speak to these issues.
>> I proposed that we skip these issues during triage and let the installer
>> team triage them.
>>
> I agree with this observation, a triage where not everyone can speak to
> issues isn't a good use of time. Overall I wonder if having an all-hands
> triage makes sense anymore given the mini-teams organization these days.
>
>>
>> In order to do so, we'd have to create a separate project in redmine. My
>> initial feeling is that this makes sense since the installer work has
>> really grown into its own project and is no longer in the purview of
>> pulpcore.
>>
> What about us reconfiguring the triage query to disinclude issues with the
> installer tag on them as an alternative?
>
>
>> Thoughts?
>>
>> I'll put a deadline on this discussion for May 8 unless we don't reach a
>> consensus by then.
>>
>> David
>> ___
>> Pulp-dev mailing list
>> Pulp-dev@redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>


-- 

Mike DePaulo

He / Him / His

Service Reliability Engineer, Pulp

Red Hat 

IM: mikedep333

GPG: 51745404

___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Installer project

[Brian Bouterse]

On Tue, May 5, 2020 at 10:48 AM David Davis  wrote:

> During triage today, a majority of the issues that came up were for the
> installer but only a handful of people could really speak to these issues.
> I proposed that we skip these issues during triage and let the installer
> team triage them.
>
I agree with this observation, a triage where not everyone can speak to
issues isn't a good use of time. Overall I wonder if having an all-hands
triage makes sense anymore given the mini-teams organization these days.

>
> In order to do so, we'd have to create a separate project in redmine. My
> initial feeling is that this makes sense since the installer work has
> really grown into its own project and is no longer in the purview of
> pulpcore.
>
What about us reconfiguring the triage query to disinclude issues with the
installer tag on them as an alternative?


> Thoughts?
>
> I'll put a deadline on this discussion for May 8 unless we don't reach a
> consensus by then.
>
> David
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Installer project

[David Davis]

We recently made a change to the automation so that it would start checking
projects and currently it's set up to check for the Pulp redmine project
for pulpcore changes[0]. So currently the answer would be yes. However,
we could change the commit validation to check for multiple projects.

[0] https://github.com/pulp/pulpcore/blob/master/template_config.yml#L38

David


On Fri, May 8, 2020 at 9:27 AM Dennis Kliban  wrote:

> I am +1 to creating a new redmine project.
>
> I want to point out that we plan to move installer documentation into the
> main pulpcore docs. Our CI checks for issues associated with the
> appropriate projects. Do that mean we will need to create docs issues in
> the Pulp project when the docs need to be updated for the installer?
>
> On Tue, May 5, 2020 at 11:25 AM David Davis  wrote:
>
>> Cool. If we go down this path, would this plan make sense?
>>
>> 1. Create an installer project in redmine
>> 2. Move over all issues (opened and closed) to this project that are
>> tagged "Pulp 3 installer"
>> 3. Remove the "Pulp 3 installer" tag
>>
>> David
>>
>>
>> On Tue, May 5, 2020 at 11:10 AM Fabricio Aguiar <
>> fabricio.agu...@redhat.com> wrote:
>>
>>> +1 for creating a new project,
>>> Installer query: https://pulp.plan.io/projects/pulp/issues?query_id=154
>>>
>>> Best regards,
>>> Fabricio Aguiar
>>> Software Engineer, Pulp Project
>>> Red Hat Brazil - Latam 
>>> +55 11 999652368
>>>
>>>
>>> On Tue, May 5, 2020 at 11:48 AM David Davis 
>>> wrote:
>>>
 During triage today, a majority of the issues that came up were for the
 installer but only a handful of people could really speak to these issues.
 I proposed that we skip these issues during triage and let the installer
 team triage them.

 In order to do so, we'd have to create a separate project in redmine.
 My initial feeling is that this makes sense since the installer work has
 really grown into its own project and is no longer in the purview of
 pulpcore.

 Thoughts?

 I'll put a deadline on this discussion for May 8 unless we don't reach
 a consensus by then.

 David
 ___
 Pulp-dev mailing list
 Pulp-dev@redhat.com
 https://www.redhat.com/mailman/listinfo/pulp-dev

>>> ___
>> Pulp-dev mailing list
>> Pulp-dev@redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Installer project

[Dennis Kliban]

I am +1 to creating a new redmine project.

I want to point out that we plan to move installer documentation into the
main pulpcore docs. Our CI checks for issues associated with the
appropriate projects. Do that mean we will need to create docs issues in
the Pulp project when the docs need to be updated for the installer?

On Tue, May 5, 2020 at 11:25 AM David Davis  wrote:

> Cool. If we go down this path, would this plan make sense?
>
> 1. Create an installer project in redmine
> 2. Move over all issues (opened and closed) to this project that are
> tagged "Pulp 3 installer"
> 3. Remove the "Pulp 3 installer" tag
>
> David
>
>
> On Tue, May 5, 2020 at 11:10 AM Fabricio Aguiar <
> fabricio.agu...@redhat.com> wrote:
>
>> +1 for creating a new project,
>> Installer query: https://pulp.plan.io/projects/pulp/issues?query_id=154
>>
>> Best regards,
>> Fabricio Aguiar
>> Software Engineer, Pulp Project
>> Red Hat Brazil - Latam 
>> +55 11 999652368
>>
>>
>> On Tue, May 5, 2020 at 11:48 AM David Davis 
>> wrote:
>>
>>> During triage today, a majority of the issues that came up were for the
>>> installer but only a handful of people could really speak to these issues.
>>> I proposed that we skip these issues during triage and let the installer
>>> team triage them.
>>>
>>> In order to do so, we'd have to create a separate project in redmine. My
>>> initial feeling is that this makes sense since the installer work has
>>> really grown into its own project and is no longer in the purview of
>>> pulpcore.
>>>
>>> Thoughts?
>>>
>>> I'll put a deadline on this discussion for May 8 unless we don't reach a
>>> consensus by then.
>>>
>>> David
>>> ___
>>> Pulp-dev mailing list
>>> Pulp-dev@redhat.com
>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>
>> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Installer project

[Ina Panova]

+1 to the plan.

On Tue, 5 May 2020, 19:33 Fabricio Aguiar, 
wrote:

> Yes, it makes sense
>
> Best regards,
> Fabricio Aguiar
> Software Engineer, Pulp Project
> Red Hat Brazil - Latam 
> +55 11 999652368
>
>
> On Tue, May 5, 2020 at 12:24 PM David Davis  wrote:
>
>> Cool. If we go down this path, would this plan make sense?
>>
>> 1. Create an installer project in redmine
>> 2. Move over all issues (opened and closed) to this project that are
>> tagged "Pulp 3 installer"
>> 3. Remove the "Pulp 3 installer" tag
>>
>> David
>>
>>
>> On Tue, May 5, 2020 at 11:10 AM Fabricio Aguiar <
>> fabricio.agu...@redhat.com> wrote:
>>
>>> +1 for creating a new project,
>>> Installer query: https://pulp.plan.io/projects/pulp/issues?query_id=154
>>>
>>> Best regards,
>>> Fabricio Aguiar
>>> Software Engineer, Pulp Project
>>> Red Hat Brazil - Latam 
>>> +55 11 999652368
>>>
>>>
>>> On Tue, May 5, 2020 at 11:48 AM David Davis 
>>> wrote:
>>>
 During triage today, a majority of the issues that came up were for the
 installer but only a handful of people could really speak to these issues.
 I proposed that we skip these issues during triage and let the installer
 team triage them.

 In order to do so, we'd have to create a separate project in redmine.
 My initial feeling is that this makes sense since the installer work has
 really grown into its own project and is no longer in the purview of
 pulpcore.

 Thoughts?

 I'll put a deadline on this discussion for May 8 unless we don't reach
 a consensus by then.

 David
 ___
 Pulp-dev mailing list
 Pulp-dev@redhat.com
 https://www.redhat.com/mailman/listinfo/pulp-dev

>>> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Installer project

[Fabricio Aguiar]

Yes, it makes sense

Best regards,
Fabricio Aguiar
Software Engineer, Pulp Project
Red Hat Brazil - Latam 
+55 11 999652368


On Tue, May 5, 2020 at 12:24 PM David Davis  wrote:

> Cool. If we go down this path, would this plan make sense?
>
> 1. Create an installer project in redmine
> 2. Move over all issues (opened and closed) to this project that are
> tagged "Pulp 3 installer"
> 3. Remove the "Pulp 3 installer" tag
>
> David
>
>
> On Tue, May 5, 2020 at 11:10 AM Fabricio Aguiar <
> fabricio.agu...@redhat.com> wrote:
>
>> +1 for creating a new project,
>> Installer query: https://pulp.plan.io/projects/pulp/issues?query_id=154
>>
>> Best regards,
>> Fabricio Aguiar
>> Software Engineer, Pulp Project
>> Red Hat Brazil - Latam 
>> +55 11 999652368
>>
>>
>> On Tue, May 5, 2020 at 11:48 AM David Davis 
>> wrote:
>>
>>> During triage today, a majority of the issues that came up were for the
>>> installer but only a handful of people could really speak to these issues.
>>> I proposed that we skip these issues during triage and let the installer
>>> team triage them.
>>>
>>> In order to do so, we'd have to create a separate project in redmine. My
>>> initial feeling is that this makes sense since the installer work has
>>> really grown into its own project and is no longer in the purview of
>>> pulpcore.
>>>
>>> Thoughts?
>>>
>>> I'll put a deadline on this discussion for May 8 unless we don't reach a
>>> consensus by then.
>>>
>>> David
>>> ___
>>> Pulp-dev mailing list
>>> Pulp-dev@redhat.com
>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>
>>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Installer project

[David Davis]

Cool. If we go down this path, would this plan make sense?

1. Create an installer project in redmine
2. Move over all issues (opened and closed) to this project that are tagged
"Pulp 3 installer"
3. Remove the "Pulp 3 installer" tag

David


On Tue, May 5, 2020 at 11:10 AM Fabricio Aguiar 
wrote:

> +1 for creating a new project,
> Installer query: https://pulp.plan.io/projects/pulp/issues?query_id=154
>
> Best regards,
> Fabricio Aguiar
> Software Engineer, Pulp Project
> Red Hat Brazil - Latam 
> +55 11 999652368
>
>
> On Tue, May 5, 2020 at 11:48 AM David Davis  wrote:
>
>> During triage today, a majority of the issues that came up were for the
>> installer but only a handful of people could really speak to these issues.
>> I proposed that we skip these issues during triage and let the installer
>> team triage them.
>>
>> In order to do so, we'd have to create a separate project in redmine. My
>> initial feeling is that this makes sense since the installer work has
>> really grown into its own project and is no longer in the purview of
>> pulpcore.
>>
>> Thoughts?
>>
>> I'll put a deadline on this discussion for May 8 unless we don't reach a
>> consensus by then.
>>
>> David
>> ___
>> Pulp-dev mailing list
>> Pulp-dev@redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Installer project

[Fabricio Aguiar]

+1 for creating a new project,
Installer query: https://pulp.plan.io/projects/pulp/issues?query_id=154

Best regards,
Fabricio Aguiar
Software Engineer, Pulp Project
Red Hat Brazil - Latam 
+55 11 999652368


On Tue, May 5, 2020 at 11:48 AM David Davis  wrote:

> During triage today, a majority of the issues that came up were for the
> installer but only a handful of people could really speak to these issues.
> I proposed that we skip these issues during triage and let the installer
> team triage them.
>
> In order to do so, we'd have to create a separate project in redmine. My
> initial feeling is that this makes sense since the installer work has
> really grown into its own project and is no longer in the purview of
> pulpcore.
>
> Thoughts?
>
> I'll put a deadline on this discussion for May 8 unless we don't reach a
> consensus by then.
>
> David
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Installer project

[David Davis]

During triage today, a majority of the issues that came up were for the
installer but only a handful of people could really speak to these issues.
I proposed that we skip these issues during triage and let the installer
team triage them.

In order to do so, we'd have to create a separate project in redmine. My
initial feeling is that this makes sense since the installer work has
really grown into its own project and is no longer in the purview of
pulpcore.

Thoughts?

I'll put a deadline on this discussion for May 8 unless we don't reach a
consensus by then.

David
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev