I would like to test Procid on an issue where everyone (almost everyone) participate through Procid. A good issue will be one that has the following criteria:

  • Has a fair amount of ideas.
  • Is related to interface design or usability (this is not a requirement, but it may work better on a more subjective issue).
  • Is not fully resolved.
  • There are fair amount of comments and discussions.

I found a couple of issues that are good candidates:

  1. #2035079: [PP-1] Figure out what to do with the install/uninstall modules page
  2. #2064351: Add show/hide descriptions from configuration page to all forms
  3. #2052831: Improved UI layout and UX for the file clean-up configuration

Comments

mitchell’s picture

mitchell commented
Issue summary: View changes

Before it is used in core development, it may be beneficial to evaluate it in contrib issue queues and further develop it with that feedback. If at least a handful of users are reporting on the appropriateness/usefulness of the designs, the concepts may be affirmed or continually/substantially improved and bugs/features added/removed. And, by showing a good flow in some (later highlighted) issues and by picking up some projects with moderately sized user-bases, it will be possible 1) to show how it works and that it is effective for a wider audience and 2) to continue to refine it in light of real world experiences.

Updated issue summary links to use automatic issue link format.

yesct’s picture

yesct commented

@mitchell can you recommend a couple particular contrib issues?

@rzilouc2 and I were discussing in irc
Plan is to post a short comment on 3 issues saying they are being considered for procid testing. (to reach the people following which we dont have a list of, instead of just contacting the people who have commented)

And here to explain why each of those issues was chosen.

Also discussed using *this* issue as a test issue since it needs to have a decision made and needs criteria established for making decision.

--
We can use this issue to draft the "how to participate in Procid testing" blurb that we will put on issues that are used for testing. Info should include how to install, a demo link, what dta is collected and where it is stored and how the info will be used, why that issue was selected for testing... maybe more info.

rzilouc2’s picture

rzilouc2 commented

Here is a draft of the comment we are going to post to the selected issues, please let me know what you think:

This issue was selected to evaluate a new-add on developed for the Drupal issue queue, called Procid. If you are interested to follow or comment on this issue, please install Procid and participate in the issue using this tool.

What is Procid?

Procid is a user script for drupal.org. It offers multiple interactive features to make the Drupal issue queue a more effective medium for resolving issues. You can watch a demo on YouTube.

How do I install Procid?

Follow these instructions to install Procid: https://github.com/albaloo/procid-client/blob/master/Procid-Evaluation-I...

What data will be collected?

Procid will only log your interactions with the tool for the purpose of evaluation. The logged data will include the action performed (e.g. clicking on a lens or adding a new criteria), the time, and the performer's Drupal username. To comply with the open source/ open data policy, the collected data will be published in the Procid project's page on weekly basis. The usernames will only be published with the consent of the owner and otherwise will be anonomyzed.

For more detail information on Procid's data collection procedure, you can take a look at procid-client and procid-server code on Github.

How do I provide feedback?

  1. Creating a new issue on Github.
  2. Creating a new issue on Procid's Issue Queue on Drupal.org.
  3. Sending an email to Roshanak Zilouchian.
  4. Commenting on a discussion about Procid on Drupal.org.
  5. Using the "Give Feedback on Procid" Button on Procid's first page.
mitchell’s picture

mitchell commented

@YesCT: That's a really tough question, because it requires an awareness over thousands of ongoing projects. I'm afraid that I won't be able to help recommend any projects for testing. However, I do feel that an appropriate way to go about this would be to put a section on the project page that invites interested project maintainers to work it into their issue queue's workflow, and in another section, list the projects that are using it.

@rzilouc2: One way to start building awareness for your project is to go through the git approval process. This not only gets more eyeballs on your code but will expose potential projects' maintainers to the utility of your addon.

yesct’s picture

yesct commented

#1882712: Language admin form: move top-level language properties to table form row would make a good candidate to try this out on.

yesct’s picture

yesct commented
Title: Evaluating Procid » Evaluating Procid, a tool to help the drupal community improve the consensus building process for d.o issues

better title, so makes more sense when linked from places.

yesct’s picture

yesct commented
Issue tags: +prairie

Related to the Prairie Initiative proposal: https://groups.drupal.org/node/327438 "Improving Collaboration and Consensus Building in Drupal Issue Queue"