Hello!! I would like to work on this fix.

Is there any language requirement for this or I can write it in any language of my choice??

Also. Any docs or references would be greatly appreciated!

What I'm thinking:

What if we have the bot track issues marked as “good first issues” or bugs assigned to new contributors, and at the end generate a report? Maybe after 3 months, it could say there were 30 new “good first issues” created, and they were fixed by person X, Y, etc.

Also, as part of that, if someone is assigned an issue, we can get a notification in the Matrix rooms. For example, “person Y has been assigned an issue.” This might make people more accountable, at least since it’s posted publicly.

Hello!! I would like to work on this fix.

Is there any language requirement for this or I can write it in any language of my choice??

Also. Any docs or references would be greatly appreciated!

Great, assigned to you now.

Generally, Python is preferred in Fedora because more people can read/write it.

I'd fork this repository to create a new branch called "issue-317" and work in there.

The various forges have their own API docs. Perhaps start with Pagure/Forgejo/GitHub:

• https://docs.pagure.org/pagure/usage/index.html#pagure-api
• https://forgejo.org/docs/latest/user/api-usage/
• https://docs.github.com/en/rest?apiVersion=2022-11-28

What I'm thinking:

What if we have the bot track issues marked as “good first issues” or bugs assigned to new contributors, and at the end generate a report? Maybe after 3 months, it could say there were 30 new “good first issues” created, and they were fixed by person X, Y, etc.

Also, as part of that, if someone is assigned an issue, we can get a notification in the Matrix rooms. For example, “person Y has been assigned an issue.” This might make people more accountable, at least since it’s posted publicly.

This is a great idea, but perhaps a separate issue? This ticket is merely about a script that a person can run to create tickets from meeting notes. What can also be done is to add certain commands to zodbot to provide info on easyfix issues and so on. For example, a new command !easyfix could list the easyfix issues. This will need to be added here (or we could create a new bot entirely too):

https://github.com/fedora-infra/maubot-fedora

Note that a bot that "tracks" anything will need to have a database of its own. I dont know if the current implementation of zodbot does this yet. So that's more advanced (also if we want to write a new bot).

Would you like to open a new issue about this @lochipi so that this ticket remains focussed on the script task?

You should talk to @abompard Aurelian, he has some kind of bot that has sim=
ilar functionality=2E He is active and responsive=2E

On 20 January 2026 9:27:39=E2=80=AFam UTC, Ankur Sinha <pagure@pagure=2Eio=

wrote:

ankursinha added a new comment to an issue you are following:
``

What I'm thinking:
=20
What if we have the bot track issues marked as =E2=80=9Cgood first issu=
es=E2=80=9D or bugs assigned to new contributors, and at the end generate a=
report? Maybe after 3 months, it could say there were 30 new =E2=80=9Cgood=
first issues=E2=80=9D created, and they were fixed by person X, Y, etc=2E
=20
Also, as part of that, if someone is assigned an issue, we can get a no=
tification in the Matrix rooms=2E For example, =E2=80=9Cperson Y has been a=
ssigned an issue=2E=E2=80=9D This might make people more accountable, at le=
ast since it=E2=80=99s posted publicly=2E
=20

This is a great idea, but perhaps a separate issue? This ticket is merely=
about a script that a person can run to create tickets from meeting notes=
=2E What can also be done is to add certain commands to zodbot to provide i=
nfo on easyfix issues and so on=2E For example, a new command !easyfix co=
uld list the easyfix issues=2E This will need to be added here:

https://github=2Ecom/fedora-infra/maubot-fedora

Note that a bot that "tracks" anything will need to have a database of it=
s own=2E I dont know if the current implementation of zodbot does this yet=
=2E So that's more advanced=2E

Would you like to open a new issue about this @lochipi so that this ticke=
t remains focussed on the script task?
``

To reply, visit the link below or just reply to this email
https://pagure=2Eio/fedora-join/Fedora-Join/issue/317

What I'm thinking:

What if we have the bot track issues marked as “good first issues” or bugs assigned to new contributors, and at the end generate a report? Maybe after 3 months, it could say there were 30 new “good first issues” created, and they were fixed by person X, Y, etc.

Also, as part of that, if someone is assigned an issue, we can get a notification in the Matrix rooms. For example, “person Y has been assigned an issue.” This might make people more accountable, at least since it’s posted publicly.

This is a great idea, but perhaps a separate issue? This ticket is merely about a script that a person can run to create tickets from meeting notes. What can also be done is to add certain commands to zodbot to provide info on easyfix issues and so on. For example, a new command !easyfix could list the easyfix issues. This will need to be added here (or we could create a new bot entirely too):

https://github.com/fedora-infra/maubot-fedora

Note that a bot that "tracks" anything will need to have a database of its own. I dont know if the current implementation of zodbot does this yet. So that's more advanced (also if we want to write a new bot).

Would you like to open a new issue about this @lochipi so that this ticket remains focussed on the script task?

Sure, let's do it on a separate issue

Hello @ankursinha sorry for the ping. But could you please provide me with some type of format which meeting notes are usually like? Would really appreciate it

They're either plaintext or HTML. Take a look here:

https://meetbot.fedoraproject.org/

You can also get just the minutes, which will include "action items" etc marked in them---so that may be quickest/easiest to parse?

Yeah I just checked the logs. I will only include minutes marked with !action.
Thanks for the help tho!

Is it okay if it takes a lil more time than expected?? I am a little busy with my college work and Hack club related stuff

No worries at all, we'll check with you in 2 weeks if that's OK? Mid feb?

Sure!
Could you also clear up my doubt??

I asked about it in matrix join fedora channel. I will just bump you with ping
On Mon, Jan 26, 2026 at 11:50=E2=80=AFPM Ankur Sinha pagure@pagure.io wro=
te:

ankursinha added a new comment to an issue you are following:
No worries at all, we'll check with you in 2 weeks if that's OK? Mid feb?

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-join/Fedora-Join/issue/317

I'd not rely on the AI generated summary at all---we should use whatever the meetbot generates since we know the format of the output.

I also filed this:

https://github.com/fedora-infra/mote/issues/817

Hello!
I have finished up working on Ticket building logic for Github and Pagure, not for Forgejo yet as I did not have a proper testing ground there.
This script also adds assignees automatically, if usernames are properly mentioned in Action Items.. Maybe I should change it to work a bit differently.
Let me know if you need any more changes :D

@chish we're migrating to forgejo here:

https://forge.fedoraproject.org/forge/forge/issues/378

Could you please create a fork there and re-open the PR there when you have a second?

This ticket has been migrated to the forgejo instance. Please find the new ticket here
https://forge.fedoraproject.org/join/Fedora-Join//issues/317