Meta-issue for all discussion and work on improving the main channel for Drupal contributions.

Comments

yoroy’s picture

yoroy CreditAttribution: yoroy commented
Project: Drupal.org infrastructure »
Component: Other » Everything Else

Core conversation by Leisa and Rfay: http://chicago2011.drupal.org/coreconv/redesigning-issue-queue

"The issue queue is the source of real problems in getting Drupal work done and redesigning it could have really a really positive impact on the way we work together."

Presentation outline: https://docs.google.com/present/edit?id=0ATSj3ekASkFxZGRzZDVzdzdfNDk3Y3F...

#1060798: Enable apachsolr 'related posts' block for issues (and forums?)

There's loads more but the contrast between these two items (wording, scope) is a good indicator of the bridges we need to build here.

#569552: Provide a mechanism for issue meta discussions

yoroy’s picture

yoroy CreditAttribution: yoroy commented
Project: » Drupal.org infrastructure
Component: Everything Else » Other
drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm commented

subscribe.

leisareichelt’s picture

leisareichelt CreditAttribution: leisareichelt commented
Project: » Drupal.org infrastructure
Component: Everything Else » Other

also subscribing and thereby illustrating one of the issues we need to address ;)

tvn’s picture

tvn CreditAttribution: tvn commented

subscribe

rfay’s picture

rfay
Primary language English
Location Palisade, CO, USA
CreditAttribution: rfay commented

subscribe.

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
CreditAttribution: klonos commented

subscribing...

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
CreditAttribution: klonos commented

@rfay: hey Randy... while at it at Drupalcon why not also put the subscribe-without-posting-a-comment issue on the table? People get "false alerts" of issue having an update (either by email or through the dashboard) only to see that a person or two have simply subscribed. Here's the related issue: #288726: Allow users to subscribe without posting a comment. Thanx in advance for considering this ;)

rfay’s picture

rfay
Primary language English
Location Palisade, CO, USA
CreditAttribution: rfay commented

I definitely agree. My part, though, is about things that we can do just by changing process (without any investment in development).

I'll remember though, and hope to see you there. This is a conversation... Half the time is for prodding, the other half for conversation with the people who come.

dww’s picture

dww
we/he/they
CreditAttribution: dww commented

Given that #569552: Provide a mechanism for issue meta discussions isn't done yet, I'm guessing that this issue will be pretty useless in its current form.

I'd like to propose we move this whole discussion to a wiki subpage of Drupal.org high-priority features where we can meaningfully collect and organize links to individual issues that we can actually accomplish. That'd also be a place to discuss the bigger picture. Folks can just use comments on there as if they were here. We don't need a testbot for this issue, and it doesn't really have a meaningful status or someone assigned to it, so I think the community initiatives wiki pages are a much better medium for the discussion.

Re: subscribe -- there's nothing really to discuss, we just need to do it. I'm hoping to schedule a BoF at DCC (or take time at the Friday code sprint) to work on implementation. There's already a section about this on the page I link above, in fact.

Thanks,
-Derek

dww’s picture

dww
we/he/they
CreditAttribution: dww commented

To help move this along, I just:

A) Split off the subscription stuff into a subpage: "Real" issue subscriptions.

B) Added another subpage for this initiative: Redesign the issue queue. While I was at it, I went through the project_issue, bluecheese and redesign issue queues and found all the issues that seemed potentially related to this. For now, they're just an unordered blob. It'd probably be helpful to organize those by topic (e.g. workflow, functionality, visual design, etc), but I wanted to at least collect all the issues in one place as a first step.

Given these new wiki pages, I'm tempted to just lock comments on this thread, since I don't see how it's going to help us move forward to keep this open. But, I don't want to stifle anyone's initiative either, so I'll leave it open for now. But I'd strongly suggest moving to editing the wiki or adding comments there, not here.

Thanks to rfay, Leisa and yoroy for getting this started!

Cheers,
-Derek

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
CreditAttribution: klonos commented

@Randy: thanx mate, but unfortunately I am not attending :(

@Derek: I hear you!

yoroy’s picture

yoroy CreditAttribution: yoroy commented

Thanks for starting those pages and collecting the links Derek. I was looking forward to creating one last epic, self-referential trainwreck of a monster meta issue here. :)

We'll want to set some concrete goals and get a good picture of how people use and fail to use the issue queue. Where do newbies stumble, what can we improve for power users etc. Have a design process. Maybe this issue can be used for status updates and pointers to current activities elsewhere. Maybe lock comments indeed and re-open only for new summaries with next actions.

For now it would be better indeed if those interested in this topic go read (and add to) #569552: Provide a mechanism for issue meta discussions. Yup, already 80 comments in, but has lots of solid input from veteran contributors.

Next for this issue here would then be a summary of the core conversation in Chicago with rough outline for plan of attack and what's needed next.

yoroy’s picture

yoroy CreditAttribution: yoroy commented

For those interested in the larger initiative around making our collaboration tools a friendlier and more effective place to collaborate: http://groups.drupal.org/prairie

arianek’s picture

arianek CreditAttribution: arianek commented

subs

dasjo’s picture

dasjo
he/him
Primary language German
Location Zurich
CreditAttribution: dasjo commented

subscribe

dww’s picture

dww
we/he/they
CreditAttribution: dww commented
Status: Active » Closed (duplicate)

Sorry folks, nothing is actually going to happen in this issue. There are two vastly better places to participate in the formulation and implementation of a plan:

A) The new Prairie initiaitive group on g.d.o.

B) The Redesign the issue queue community initiative wiki page.

Having a 3rd place to try to discuss this huge over-arching topic in a single issue will get us no where, so I'm going to call this duplicate and I'm going to lock comments. There's nothing concrete to actually accomplish here, and there's going to be a flood of pointless subscribe comments (more so now that arianek linked here from her otherwise awesome blog post). ;)

I'm not trying to discourage participation in this discussion, far from it! I just want people to contribute in a useful way, and this particular issue unfortunately isn't it... Join the Prairie group! Help edit the wiki!

Thanks,
-Derek