Errors in change proposals when transferring from wiki to Discourse & announcement mailing list

Site Help & Feedback
1

Hi Chris, Ive edited the initial post to be a manual copy-paste from the wiki page. The misinformation you referenced were examples of things intended to help change proposal owners write their change proposal and not about your exact proposal, but it is unfortunate that they showed up in the post like they were part of it :frowning: For full transparency, Allison is stepping in as change wrangler for F44 cycle, and we have been experimenting with Claude CLI on automating the very manual copy-paste-edit part of the announcements. To us, this post looked ok, but clearly it didnt work well. Thank you for highlighting these issues, its great feedback to have and we intend to bring it back to Claude to improve the automatic posting ability we are trying to get to. The announced emails are still a manual copy-paste., so with the exception of a wrong title (which I do as a person unfortunately more times than not) they should be relatively error-free. The emails are generated locally as a text file with the discussion link and angle brackets edited out, but we still then need to copy the text and paste it to the email body, much like copying the text straight from the wiki as I have always done. Whereas we thought we had Claude successfully creating a post from the wiki directly…..which, is kind of right, but still not correct :see_no_evil_monkey:

Thanks again for the feedback, and apologies for causing any unintended confusion with our experiment!

1 Like
2

Thanks for the feedback :classic_smiley: I took the liberty to shift this to a dedicated topic in site feedback.

Does it maybe make sense to change the place of beginning (= currently the wiki) of proposals in some way? Or restrict the used language elements? Having one language (wiki) in which we write the proposals and then the need to translate it into other languages (such as Discourse) seems to remain dependent on human review and thus be vulnerable (and time intensive), except cases in which languages can be mapped 1:1, which I assume is not the case here (not sure if wiki text can be 1:1 mapped to Discourse? Or is there maybe a Discourse plugin or so we can use? Might be worth a look too as there are many plugins).

It might be useful to let potentially-affected people (or, portals/forums) know, or announce it, in advance if something is deployed that has not been fully tested before, that might avoid confusion, but also allow others to help mitigate potential consequences, as then everybody is on the same page :classic_smiley: E.g., I might had been able to adjust the Discourse topic earlier, but I didn’t want to interfere as I had no idea of your workflows or the background

1 Like
3

The email just went live now, your feedback prompted the ‘hit send already!” button in my brain :sweat_smile: Introducing Allison King, F44 Change Wrangler - devel-announce - Fedora mailing-lists

I wonder should I copy it to the change proposal sub-category too for awareness over here as well?

1 Like
4

Well, might be useful to introduce someone, who starts such a position, on Discourse :classic_smiley: May it be project discussion or change proposals. Both seem to fit :classic_smiley:

1 Like
5

Thank you, I’ll add the email as a post on the project discussion category now :saluting_face:

Also the copy-paste mapped 1:1 from the wiki to a discussion post with some kind of witchery @mattdm used when setting up the sub-category, so I will bring him into the Claude experiments as he might be able to help suggest something that’ll make the AI only copy the right information and not the hidden text.

1 Like
6

Sounds good!

A worst case mitigation if it is not possible to map hidden comments from the wiki reliably 1:1 to discourse: maybe we can add a script or so that just removes them before the mapping takes place (not sure how far that is possible / easy to implement in your workflow). I could imagine that automating to remove wiki text comments might be easier than finding a way to map them. In discourse they have no value anyway.

1 Like
7

It should be trivial now that I know what to tell Claude to exclude when it generates the post. I will try that for our next change announcement and hopefully it works! Thank you very much for the suggestion, its greatly appreciated :blush:

1 Like
8

Thanks for working on this :wink:

Minor supplement: Maybe it makes sense to add Allison to an FAS group so that she gets a Fedora email address. For the wrangler position that might be useful, because the “default” for many people contributing/working with/for Fedora is, in case of a doubt, to take the username and add @fedoraproject.org when they try to reach someone.