Posted by arianek on May 24, 2010 at 10:46pm
Just had a bit of a lightbulb moment (and maybe this idea has come up before?) about how to eventually kill comments on handbook pages. Someone asked how we could make sure conversations about a particular page were still visible if they were happening in the issue queue instead of as comments.
I thought, and this is what seemed like a good idea:
- add a field on the issue node-add form for a referenced d.o NID (to reference the handbook page the issue is about)
- build a view block for the handbook pages that displays any issues related to the page
Ta-da?
Considered filing an issue, but thought I'd get a sanity check here as to whether that would seem like a good solution.
Comments
Yes!
Excellent idea.
+1
Drupal programmer - http://poplarware.com
Drupal author - http://shop.oreilly.com/product/0636920034612.do
Drupal contributor - https://www.drupal.org/u/jhodgdon
Related issues
Related issues: Provide a mechanism for issue meta discussions and Improve the workflow for documentation of core API changes. In #11 of the latter, I set up a demo at http://d6.project.drupal.org/node/557272 showing how a couple of blocks could provide context for issues. It's a similar idea to what I think you're proposing - different information, similar concept.
At this point, we don't have CCK on D.O, so it's not quite possible yet to "add a field", but that should be on its way with Enable CCK and node_reference.
good good - those weren't on
good good - those weren't on my radar, thanks randy! so eventually we can get there it would seem...didn't realize there was no cck (goodness if only we could set parent and child issues to track these things better...! ack, scope creep!) ;-)
you think i ought to file a separate issue, or tack this onto one of the others?
Your issue might be somewhat different
I think your issue might be somewhat different, but chiming in on those might help us. Not sure what it takes to move forward on those. Probably we have D7 released or something. Getting CCK into the redesign might be the ticket too. We'll have to go check on that.
But another issue wouldn't hurt, if yours is different (I suspect it is not completely covered by these?)
Sounds good to me
+1
I'm in favor
I'm in favor of integrating the docs better with the projects. It sound like an obvious improvement to add a field to link the doc and the project home - there should be fields on both content types. I think it would encourage better documentation.
There seems to be a field in the project already for the documentation link, so why not the other way?
...
I would suggest you chat with dww about some of the ideas he has going forward to make sure everyone is on the same or a similar page.
separate issue...
What's being discussed here is how to integrate Handbook pages with issues that relate to those Handbook pages. What you're talking about is somewhat unrelated.
Drupal programmer - http://poplarware.com
Drupal author - http://shop.oreilly.com/product/0636920034612.do
Drupal contributor - https://www.drupal.org/u/jhodgdon
Sure, that makes sense.
Yes, thanks, I do get the distinction. I am finding it very disjointed just finding documentation sometimes.
I think it is a valid and valuable enhancement to link the issues to documentation, but, like I said, just getting the project and the docs connected is a manual and apparently optional task.
Here's a thought, now that I am getting a better handle on what we're trying to work on - What is the irritation? I think I'm hearing it's that the comments are being used as an issue queue on documentation, even if the doc is fixed, the comment never goes away because you can't close a comment like an issue. The issue queue already has an option to indicate documentation as the topic of the issue. If the community gets that field back into better use, and integrate issues and docs a little tighter, as you're working on, they could disallow comments on the Handbook pages.
It might make the documenter a more equal partner in the project and the docs person could also help maintain the issue queue, that's something that needs care and feeding like a handbook page, but it takes the developer's time away from his code (and thus does not always get done!). I know it's getting away from docs skills into release management skills to keep up with the queue, but there are only so many warm and willing bodies interested in putting time into this.
so......i think i'm going to
so......i think i'm going to go ahead and document this (i can send the link to dww so it's on his radar)
maybe randy, you can direct me on this: does this seem like more of a redesign issue? not sure which queue the issue should go in - will be sure to reference those other ones as well.
Chat with dww, redesign good idea
I think chatting with dww is a great idea, and trying to get (all) this in through the redesign is a good idea too. Derek may have the best thoughts.
issue filed here
issue filed here http://drupal.org/node/810508 and notified dww, thanks for the input (feel free to discuss further on the issue, of course!)