Should we port the comment display code from 2.x to 3.x?

Personally, I don't think we need this. We preach the standard-based architecture of node gallery, and displaying other nodes comments is against that imho.

new user to node_gallery here. I would really like to have gallery comments show up on all the image node pages so that there is only one set of comments for a gallery.
If nobody else wants this, I will port this myself and submit a patch. I just don't understand why you wouldn't want this feature at least as an *option*.

edit: I definitely need this feature for our large site. I'll be porting and submitting patch shortly. If you don't need it, i'll just keep it under my local custom patches.

Well, the problem I have with the feature is that it messes with a core drupal feature and makes it inconsistent. If a user submits a comment from an image page, do you save it for the gallery or for the image? And what happens if the admin moves that specific image to a different gallery? Do you move the comment?
It just doesn't work for me.

I agree that the hack for $node->comment and the inability to preserve image comments if an image is moved to another gallery are behaviors that don't fit cleanly the gallery node and image node separation. For my use case however, it's completely necessary and I figure that others who want the awesome integration with plupload, sorting of images, gallery navigation, views integration, tokenized page URL for each image, etc. etc. but need the comments like this will appreciate it. I've completed the port and I'm packaging up now. I'm fine with just submitting the patch to this issue for those folks who absolutely need it if you don't intend on packaging with module.

Here is the comment display functionality ported to 3.x-dev

@justintime - I think that's reasonable. The only thing is how to factor out the storage of the setting currently in node_gallery_relationships.settings and set in node_gallery_relationship_settings_defaults() function?

on a separate but related note, I'm adding functionality to inherit $gallery_node->taxonomy into $image_node. Thoughts on integration?

i've decided my approach was too much of a hack on your module and my use case more fits with a simple gallery node + imagefield cck fields with additional meta fields and using a custom pager that loads an imagefield and it's related data based on the ?page=N in the url.