Should we allow users to edit the impactEvaluationDescription before submitting lists?

[kristoferlund]

The impactEvaluationDescription allows for badgeholders to explain how they reasoned when creating a list. We currently autogenerate this description. For example: "This list has been carefully curated and ranked by Pairwise among projects related to DAOs, ReFi, and DAO Tooling."

Should we allow the badgeholder to manually edit this field before list creation?

@GriffGreen @Zeptimus @krisjpi @MoeNick

When responding, please go beyond "yeah, that would be nice" and consider the following:

• Is it important?
• Should we prioritise it given that the list of issus is long?
• Does it introduce additional obstacles for users? One more field to fill out before list creation.

[krisjpi]

My reasons to not want to allow edits are to

• pre-empt submissions of questionable or offensive content being submitted
• ensure that Pairwise is noted as the tool used to so that others see this and can utilize the tool
• simplify UX
• not add dev time :)

My initial feeling was yes we should allow if possible, but only if it doesn't interfere with data processing. I don't anticipate a ton of people will edit much beyond a default text if we do allow it, but those who feel strongly that there should be a different or additional description can modify.

I would leave this as a low priority issue that could be elevated if there is user feedback that requests it.

[Zeptimus]

Im confident that its a important feature, i thought we were building it and told to jonas that we were doing it. At this point w/e decision was made was the best one