Thank you for bringing this up. Do we know what needs to be done to resolve
this?
I filed this task to fix the minutes not being recorded, and added it to
the open floor agenda also. https://pulp.plan.io/issues/6791
On Tue, May 19, 2020 at 6:06 PM Fabricio Aguiar
wrote:
> I just noticed one th
I just noticed one thing, supybot probably was configured to pulp-dev
It records log on pulp-dev:
https://pulpadmin.fedorapeople.org/triage/pulp-dev/2020/
The triage held on pulp-meeting could not log:
https://pulpadmin.fedorapeople.org/triage/pulp-meeting/2020/pulp-meeting.2020-05-19-14.30.html
a
The decision to do this was actually made a while ago when we noticed that
holding meetings in #pulp-dev interrupted discussions that were happening
in that channel around the same time as the meeting. However, I did not
follow through to actually announce this decision and update the website.
@bmb
Any chance we can get some background on how, why, where this decision was
made? I'm not opposed to it but having some more information in this
announcement would be helpful.
David
On Fri, May 15, 2020 at 11:21 AM Dennis Kliban wrote:
> Starting on May 19th, bug triage will be held in #pulp-me
Starting on May 19th, bug triage will be held in #pulp-meeting on
Freenode[0].
[0] https://pulpproject.org/get_involved/#meetings
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
