# Weird link on PyPI

**URL:** <https://forum.ansible.com/t/weird-link-on-pypi/40061>\
**Category:** Project Discussions\
**Tags:** community-wg\
**Created:** [February 4, 2025, 7:17pm UTC](https://forum.ansible.com/t/weird-link-on-pypi/40061 "2025-02-04T19:17:43Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [February 4, 2025, 7:17pm UTC](https://forum.ansible.com/t/weird-link-on-pypi/40061/1 "2025-02-04T19:17:43Z")

</div>

On [PyPI](https://pypi.org/project/ansible/11.2.0/) there’s a link to the archived community repo:

> Join a [Working Group](https://github.com/ansible/community/wiki), an organized community devoted to a specific technology domain or platform.

This isn’t really great. I think we should change this, but I’m not really sure how to do it.

---

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [February 4, 2025, 7:26pm UTC](https://forum.ansible.com/t/weird-link-on-pypi/40061/2 "2025-02-04T19:26:16Z")

</div>

I believe it must be changed in [https://github.com/ansible-community/antsibull-build/blob/main/src/antsibull\_build/data/ansible-readme.rst](https://github.com/ansible-community/antsibull-build/blob/main/src/antsibull_build/data/ansible-readme.rst) and then another release published. The readme is pulled from the package once uploaded to pypi.

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [February 4, 2025, 9:33pm UTC](https://forum.ansible.com/t/weird-link-on-pypi/40061/3 "2025-02-04T21:33:16Z")

</div>

Yes, what @sivel said. Nothing more to add 🙂

---

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [February 5, 2025, 6:18pm UTC](https://forum.ansible.com/t/weird-link-on-pypi/40061/4 "2025-02-05T18:18:14Z")

</div>

Should we replace this with another link, or should we drop this completely?

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [February 5, 2025, 10:11pm UTC](https://forum.ansible.com/t/weird-link-on-pypi/40061/5 "2025-02-05T22:11:29Z")

</div>

How about changing it to

> Join [Forum Groups](https://forum.ansible.com/g) you are interested in, which are groups of users that are interested in specific topics, like a a specific technology domain or platform.

with a link to the forum’s group list?

---

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [February 6, 2025, 4:40pm UTC](https://forum.ansible.com/t/weird-link-on-pypi/40061/6 "2025-02-06T16:40:13Z")

</div>

Good idea to link to the forum!

But having both “interested” and “specific” twice in one sentence doesn’t sound good. I’ve changed this a little bit: [Fix outdated link on PyPI](https://github.com/ansible-community/antsibull-build/pull/649)

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [February 8, 2025, 12:43pm UTC](https://forum.ansible.com/t/weird-link-on-pypi/40061/7 "2025-02-08T12:43:30Z")

</div>

That’s why I posted it here instead of creating a PR directly, in the hope that someone improves my formulation 😉 Thanks for creating the PR @mariolenz!
