project node UI changes deployed on d.o
Since I suspect there might be a backlash, and the questions [1] have already started coming in about the change, I wanted to briefly announce/summarize here. As of around 3pm PDT on 2008-10-01, all of the links to directly submit new issues are gone from project nodes on drupal.org. Duplicate issues suck a huge amount of time, and many of us maintainers spend upwards of 1/2 of our effort in our issue queues just marking things duplicate. This is a drain for maintainers, and isn't all that friendly for the end users, either. To help avoid this, we want to encourage people to view the queues and/or search for an existing issue about their topic before submitting a new one. Now, on the project nodes, you have the following issue-related choices: Support * View open issues * View all issues * View all support requests * Search issues * Report a security issue Development * View pending patches * View available tasks Note that the "View all ..." links bring you to a page that includes closed, won't fix, duplicate, etc, to improve the visibility of those issues. The "Report a security issue" link just brings you to the security team page explaining the proper procedure for reporting suspected vulnerabilities (that's been true since #218571 [2]). Every issue query result page still contains a "Create" link to submit an issue for that particular project. So, worst case, this introduces a single additional click. Furthermore, maintainers still have a "Create" link in your "My projects" [3] pages. For background on this change, check out this issue: "#310446: Remove issue creation links from project pages" [4]. Note, it's very easy to change these links (project.module provides a hook, and we're tweaking it via drupalorg.module, so my usual complaints about keeping things generic for the non-d.o use cases don't apply). So, if people have suggestions for improvements, please add them to #310446. Enjoy, -Derek (dww) p.s. I could definitely see the benefit of a "Create a new issue" link that brings you to the "view open issues" page with a drupal_set_message() about "Please look for an existing issue before you create a new one" or something. If folks are in favor of that, please reopen #310446 and let's discuss there. Thanks. [1] http://drupal.org/node/316097 [2] http://drupal.org/node/218571 [3] http://drupal.org/project/user [4] http://drupal.org/node/310446
Well, on the bright side, the new link structure of
* View open issues * View all issues * View all support request is, in my opinion, a great improvement, since usually don't care which kind of issue (task, bug, feature, etc.) it is that I'm looking for, so this will save me an extra click and a pageload every time i view an issue queue. Thanks :)
When it comes to removing the add issue link, I'm not thrilled about it, but I understand your reasoning. I do, however, think that this is a desparate measure. Making it harder to submit bugs is not really what we want. We want higher quality issues, not just less of them. What we need is a workflow like they have in Ubuntu: http://skitch.com/mikl/atwd/report-a-bug-about-ubuntu http://skitch.com/mikl/atwf/report-a-bug-about-ubuntu I know the counter to that is that it would be a lot of work to implement and the Project module maintainers don't have the time, and I can sympathise with that. That is another thorny issue for Drupal, that we have made our own tools for everything. I've once before tried advocating moving parts of what we do (translations) to Launchpad, and I'm not willing to stick my head in that particular hornet's nest again anytime soon. -- Kind regards, Mikkel Høgh <mikkel@hoegh.org> On 02/10/2008, at 09.10, Derek Wright wrote:
Since I suspect there might be a backlash, and the questions [1] have already started coming in about the change, I wanted to briefly announce/summarize here.
As of around 3pm PDT on 2008-10-01, all of the links to directly submit new issues are gone from project nodes on drupal.org.
Duplicate issues suck a huge amount of time, and many of us maintainers spend upwards of 1/2 of our effort in our issue queues just marking things duplicate. This is a drain for maintainers, and isn't all that friendly for the end users, either. To help avoid this, we want to encourage people to view the queues and/or search for an existing issue about their topic before submitting a new one.
Now, on the project nodes, you have the following issue-related choices:
Support * View open issues * View all issues * View all support requests * Search issues * Report a security issue
Development * View pending patches * View available tasks
Note that the "View all ..." links bring you to a page that includes closed, won't fix, duplicate, etc, to improve the visibility of those issues. The "Report a security issue" link just brings you to the security team page explaining the proper procedure for reporting suspected vulnerabilities (that's been true since #218571 [2]).
Every issue query result page still contains a "Create" link to submit an issue for that particular project. So, worst case, this introduces a single additional click. Furthermore, maintainers still have a "Create" link in your "My projects" [3] pages.
For background on this change, check out this issue: "#310446: Remove issue creation links from project pages" [4].
Note, it's very easy to change these links (project.module provides a hook, and we're tweaking it via drupalorg.module, so my usual complaints about keeping things generic for the non-d.o use cases don't apply). So, if people have suggestions for improvements, please add them to #310446.
Enjoy, -Derek (dww)
p.s. I could definitely see the benefit of a "Create a new issue" link that brings you to the "view open issues" page with a drupal_set_message() about "Please look for an existing issue before you create a new one" or something. If folks are in favor of that, please reopen #310446 and let's discuss there. Thanks.
[1] http://drupal.org/node/316097 [2] http://drupal.org/node/218571 [3] http://drupal.org/project/user [4] http://drupal.org/node/310446
On Oct 2, 2008, at 1:18 AM, Mikkel Høgh wrote:
What we need is a workflow like they have in Ubuntu:
Search before you post... ;) http://drupal.org/node/19386 (Sorry, couldn't resist). But yes, you're absolutely right. That's what we need. A related problem is that, especially for d.o, you need to search a bunch of different issue queues if you really want to avoid a duplicate: http://drupal.org/node/192714
I know the counter to that is that it would be a lot of work to implement and the Project module maintainers don't have the time, and I can sympathise with that.
Not at all. Well, yes, the (current) maintainers don't have the time, but we're obviously not the only people on this list who are qualified for the job. Any interested party is more than welcome to pick up the ball and run with either of these issues. #192714 used to be blocked on search-related problems (back when d.o's DB was being crippled by core search.module) but we're now running xapian on d.o, so perhaps that one can be revived without too much trouble. I don't include so many issue links in my posts to this list just for the archival fun of it. I genuinely hope that someday, people will actually jump into an issue and solve a problem or add a feature if their itch is scratchy enough. ;) Cheers, -Derek (dww)
Hooray!! for once I won't give you a hard time.. ;) Keep up the good work dww. .darrel. On Thu, Oct 2, 2008 at 4:48 AM, Derek Wright <drupal@dwwright.net> wrote:
On Oct 2, 2008, at 1:18 AM, Mikkel Høgh wrote:
What we need is a workflow like they have in Ubuntu:
Search before you post... ;)
(Sorry, couldn't resist). But yes, you're absolutely right. That's what we need.
A related problem is that, especially for d.o, you need to search a bunch of different issue queues if you really want to avoid a duplicate:
I know the counter to that is that it would be a lot of work to implement
and the Project module maintainers don't have the time, and I can sympathise with that.
Not at all. Well, yes, the (current) maintainers don't have the time, but we're obviously not the only people on this list who are qualified for the job. Any interested party is more than welcome to pick up the ball and run with either of these issues. #192714 used to be blocked on search-related problems (back when d.o's DB was being crippled by core search.module) but we're now running xapian on d.o, so perhaps that one can be revived without too much trouble.
I don't include so many issue links in my posts to this list just for the archival fun of it. I genuinely hope that someday, people will actually jump into an issue and solve a problem or add a feature if their itch is scratchy enough. ;)
Cheers, -Derek (dww)
On Thursday 02 October 2008 15:10:59 Derek Wright wrote:
Duplicate issues suck a huge amount of time, and many of us maintainers spend upwards of 1/2 of our effort in our issue queues just marking things duplicate. This is a drain for maintainers, and isn't all that friendly for the end users, either. To help avoid this, we want to encourage people to view the queues and/or search for an existing issue about their topic before submitting a new one.
Good move. Thank you very much :) Augustin.
Rock on Derek! :) On 02 Oct 2008, at 09:10, Derek Wright wrote:
Since I suspect there might be a backlash, and the questions [1] have already started coming in about the change, I wanted to briefly announce/summarize here.
As of around 3pm PDT on 2008-10-01, all of the links to directly submit new issues are gone from project nodes on drupal.org.
-- Dries Buytaert :: http://buytaert.net
participants (5)
-
augustin (beginner) -
Darrel O'Pry -
Derek Wright -
Dries Buytaert -
Mikkel Høgh