Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nudging Project Creators to Comply with Organized Editing Guidelines #6298

Open
SColchester opened this issue Mar 21, 2024 · 2 comments
Open
Labels
data-quality Issues related to data quality and validation workflow priority: high scope: frontend status: todo type: feature request Adding functionality that currently does not exist ui/ux 👥

Comments

@SColchester
Copy link

SColchester commented Mar 21, 2024

Lots of projects on the Tasking Manager (likely the vast majority) do not have Wiki documentation (like this) to support them. This means that they are not complying with OSMF’s Organized Editing Guidelines (OEGs) – one of the key OEG steps is to create Wiki documentation.

Something that may nudge better behaviour on this could be a pop-up/message just after the ‘Save’ button is hit for any project that is set to ‘Published’ under the ‘Edit project’ > ‘Description’ section (only on first instance, i.e. if a project is set back to draft and then re-published the message would not show again).

May suggest popup/message has three options:

  1. I have followed the OEGs (including creating a Wiki) and want to go ahead with publishing --> action, project is Published
  2. I have not yet followed the OEGs and need more time to do this --> action, project goes back to Draft status
  3. I'm confident that the OEGs do not apply to this project and want to go ahead with publishing --> action, project is Published

Keeping track of disaster response projects is proving difficult due to the lack of Wiki documentation for responses. If a nudge like this helps mitigate that and encourages more alignment with the OEGs this will be a double win. (cc the inspiration @pedrito1414)

@petya-kangalova
Copy link
Collaborator

Discussion notes from Tasking Manager Meet Up:

Need to consider that sometimes projects are grouped (ex: Turkey and Syria response) Should be connected to the campaign level.
Autogenerating content might be too complex
Solution - pop up to ask “Have followed the OEG guidance? Response option “Yes” “No”

@ramyaragupathy ramyaragupathy added status: todo ui/ux 👥 type: feature request Adding functionality that currently does not exist data-quality Issues related to data quality and validation workflow priority: high scope: frontend labels May 1, 2024
@ramyaragupathy
Copy link
Member

related #3486

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data-quality Issues related to data quality and validation workflow priority: high scope: frontend status: todo type: feature request Adding functionality that currently does not exist ui/ux 👥
Projects
None yet
Development

No branches or pull requests

3 participants