15:00:47 <shertel> #startmeeting Ansible Core Public IRC Meeting
15:00:47 <zodbot> Meeting started Thu Jun  9 15:00:47 2022 UTC.
15:00:47 <zodbot> This meeting is logged and archived in a public location.
15:00:47 <zodbot> The chair is shertel. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
15:00:47 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:47 <zodbot> The meeting name has been set to 'ansible_core_public_irc_meeting'
15:01:15 <shertel> #info agenda https://github.com/ansible/community/issues/661
15:01:26 <sivel> howdy
15:02:14 <shertel> there's just one item on the agenda today, question about the future of galaxy.ansible.com
15:03:30 <sivel> I can attempt to bring up that topic in my meeting with the galaxy team next week
15:04:11 <sivel> alternatively, users can also try to talk with someone in #ansible-galaxy
15:04:11 <shertel> Okay, cool. Perhaps https://github.com/ansible/galaxy/issues/2775#issuecomment-1147821960 is just a bug?
15:04:20 <sivel> ¯\_(ツ)_/¯
15:04:40 <sivel> I guess so, I don't think it's intentional that people can not sign up for galaxy
15:04:55 <shertel> I'll redirect to #ansible-galaxy, doesn't look like mikedlr is in here
15:05:00 <sivel> s/don't think/can't imagine
15:06:39 <shertel> #topic open floor
15:07:50 <shertel> I'll end the meeting in a few minutes if no one has anything to bring up
15:09:25 <sivel> I'm going to work on changing the frequency and time of this meeting in the near future. We're likely going to switch to 1 time per month. I don't know if anyone will see this, but there it is :)
15:09:59 <shertel> works for me :)
15:10:06 <sivel> If a topic is more urgent, it can always be discussed in #ansible-devel to be brought to our attention sooner
15:11:00 <mikedlr_> hi.
15:11:08 <shertel> mikedlr_: Hi!
15:11:52 <shertel> I don't know anything specific about the future of galaxy.ansible.com, but it seems like not being able to sign up is probably a bug.
15:12:38 <shertel> Someone may know more in #ansible-galaxy.
15:12:44 <mikedlr_> That seems to definitely be true. It's been an open bug for quite a while.
15:14:22 <mikedlr_> I am just getting up to speed with irc comms after quite a bit of time away. haven't yet talked to anyone there.
15:14:31 <mikedlr_> the bug is here. https://github.com/ansible/galaxy/issues/2775
15:15:51 <sivel> yep, we've pinged it internally, but that's a different team responsible for those issues. galaxy.ansible.com is still "the thing to use"
15:16:31 <sivel> no idea on the scope of who is affected by that issue either
15:16:45 <sivel> Might just be due to specific email providers ¯\_(ツ)_/¯
15:16:53 <mikedlr_> it may be that the problem is that in the bug it isn't clear that the fact that you can't verify your email means that you can't effectively work on ansible galaxy.
15:19:19 <sivel> community galaxy is running on legacy software, that will eventually be replaced. There is some info about that from the last 2 or 3 contributor summits
15:19:23 <sivel> I guess https://www.youtube.com/watch?v=mili3ax3V4o&t=9040s
15:20:50 <shertel> mikedlr_: it looks like the Galaxy team is going to investigate that issue. First guess is that maybe the mail server broke.
15:21:56 <mikedlr_> okay, great.  That's what's needed.  Guess this is discussed on RH internal chat?
15:22:55 <shertel> Yeah, I just asked internally if anyone knew anything about that issue because I didn't see some people in ansible-galaxy.
15:25:24 <mikedlr_> well, I guess that's what I needed from this meeting. Thanks for the help. I put a message in the bug report so others following know what happened.
15:25:50 <shertel> I'll follow up on the meeting agenda f there's anything else I can pass along. I'm sure they'll comment on the issue once they determine what's going on.
15:26:14 <shertel> and np
15:28:16 <shertel> Okay, if there's nothing else...
15:28:20 <shertel> #endmeeting