[Pulp-dev] Infrastructure tracker on pulp.plan.io

[Brian Bouterse]

Yes I think it would be! For anyone who is involved in those areas (or
other infra areas), let me know, and I can add you to the group. Once you
are added, you can move issues to that project as you like. Sound ok?

On Tue, Nov 28, 2017 at 9:58 AM, Daniel Alley <dalley at redhat.com> wrote:

> Would this new tracker be the proper home for issues regarding Jenkins,
> Travis, nodepool, etc?  And, if so, should we move those issues out of
> whichever trackers they exist in currently (many in "Pulp Packaging" [0], a
> few in "Pulp" [1] [2] [3], etc.)
>
> [0] https://pulp.plan.io/projects/packaging/issues
> [1] https://pulp.plan.io/issues/3124
> [2] https://pulp.plan.io/issues/3116
> [3] https://pulp.plan.io/issues/2908
>
> On Mon, Nov 27, 2017 at 5:25 PM, Brian Bouterse <bbouters at redhat.com>
> wrote:
>
>> I made a project tracker called 'Infrastructure' on pulp.plan.io [0].
>> It's managed by a new group on Redmine called 'Infrastructure Admins'. That
>> group has the Open Source Container Initiative folks and myself, so we can
>> coordinate on infra stuff. For instance, we'll be tracking things like the
>> upcoming migration of docs.pulpproject.org [1] in that tracker.
>>
>> Feedback, questions, or ideas are welcome.
>>
>> [0]: https://pulp.plan.io/projects/infrastructure/
>> [1]: https://pulp.plan.io/issues/3153
>>
>> -Brian
>>
>> _______________________________________________
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20171128/1df12a76/attachment.htm>