Greg,
I think it would be helpful for folks considering this module to know about the discussion on Dries' blog:
http://buytaert.net/comment-notifications-via-email
Knowing of how much attention Dries is paying to this module will help people choose this module (among a lot of other reasons). But I just don't think that many people will wander upon that discussion on their own and it is a really helpful discussion that I think people considering comment notification should know about. Putting it on the comment_notify project page is a great place to link this module with that discussion.
best,
Shai Gluskin
content2zero
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | comment_notify project page.txt | 3.25 KB | Shai |
Comments
Comment #1
Shai commentedFixing title of this thread
Comment #2
gregglesGreat point. Also, there's http://groups.drupal.org/node/15928 which compares all these modules and links to Dries' discussion.
Do you think the project page should link to the comparison page in addition to the link to Dries' blog or instead of it?
Also, any particular text you can propose for this?
Comment #3
Shai commentedGreg,
I guess I took your response as an invitation to do a little editing of the project page :)
Attached are the results. It's not a total re-write, but I did some significant editing. Please choose what you like. Let me know if you want to know my rationale for any of the changes.
Hope this is helpful.
best,
Shai
Comment #4
gregglesThanks Shai! This is a great help to get a 3rd party to review the changes I've made (for a real check back on the history of the page, take a look at http://drupal.org/node/23158/revisions/211390/view - it's come a long way since then).
I split apart the first paragraph since I like to keep links after the "break." I also removed the second mention of the unsubscribe "Feature" items since it was a bit redundant. And finally I changed the statement about development intensifying to be about how interest in the module has intensified - in fact development has slowed down while discussion of the module has increased ;)
Thanks and let me know if you think any more tweaks would be appropriate.
Comment #5
Shai commentedGreg,
You are welcome. Collaboration is a great thing! I checked out the old page; it has come a long way—and the module too. You've put a lot of great work into it. Thank you.
In looking at it again, maybe a couple of small tweaks...
I'd list some 5.x-2.x's features explicity. If someone is using comment_notify 5.x-1.x and isn't planning an upgrade to D6 in the near future, it's not readily apparent whether upgrading to 5.x-2.x is worthwhile.
On a related note:
Are there significant bugs in the 5.x-1.x branch? If there are, they aren't getting fixed, right? If it is your opinion that all installed 5.x-1.x instances should be upgraded to 5.x-2.x because of bugs, I think you should state that directly, and/or state that 5.x-1.x is "no longer supported."
Finally, and this is totally cosmetic, I'd change the "Credits" section to be an unordered list instead of an ordered list.
This is a great and important module.
Shai
Comment #6
Shai commentedFor the record books... just changing the title of this thread to what it's thrust turned out to be...
Comment #7
gregglesThanks again, Shai. I've incorporated most of these changes in one form or another. It seems that there are only a small number of users on the 5.x-1.x branch ( http://drupal.org/project/usage/comment_notify ) so I feel like it's better to just not even mention it so that it won't confuse the general populace who mostly care about 6.x.
Comment #8
Shai commentedGreg,
Oh yah, now I see now that in the "official release" section that 5.x-1.x is not listed. So that implicitly suggests that 5.x-1.x is not supported. I agree that more language might be confusing.
Lookin' good...
best,
Shai
Comment #9
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.