Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Sorry for the delay in getting back to this project. It looks as though my father-in-law will not survive his stroke. But I should have more time for this than I did over the last few days, at least for the next few days.
A question or two about how you'd like to proceed:
Bug reports: Would you prefer that I continue to add individual documentation bug reports and track them in the first post in this task, or would you prefer that I just add them as individual comments in this task?
Drafts: I'd suggest that we exchange drafts by email rather than posting them here. Posting here would seem likely to add to the already confusing site search engine's by producing largely duplicative entries. Or should we use CVS?
Drafts: yes, we should probably do that by email. You have my address already.
Bug reports: Hmm, it's easier to track issues one-by-one. It might also be nice to distribute the docs with the module (CVS) in addition to having them in the handbooks. On the other had it might be nice to have them all in one place (single issue). Does anyone else have a preference?
I'm sorry to hear that, Paul. I know how it can be because my mother is now being counted in hours.
It's hard to lose a parent. I lost both of mine in the early 90s. I still get the urge to give them a telephone call at least once a day and have a huge hole in my very being that will never be filled. One of the surprising things you might be on the watch for was the sometimes almost overwhelming anger I felt at first because my parents left me.
On the documentation bug reports, I'll post them as separate issues and maintain an index of them in the first post of this thread for now. We can always change that approach later.
On distributing the documentation, it seems to make more sense to me to just have a link to it in the Readme or an application shortcut to the documentation distributed with the module. That way, folks will be encouraged to rely on the most up-to-date version of the documentation.
Well, I've been her almost sole care-giver for 2½ years. I don't think I'll feel that anger as much as I might at my family for having me give up my career and then end up with virtually no support.
That approach is fine. The link is in the README.txt file now.
Comments
Comment #1
Marbux commentedRelated issues
Comment #2
Marbux commentedHi, Nancy,
Sorry for the delay in getting back to this project. It looks as though my father-in-law will not survive his stroke. But I should have more time for this than I did over the last few days, at least for the next few days.
A question or two about how you'd like to proceed:
Bug reports: Would you prefer that I continue to add individual documentation bug reports and track them in the first post in this task, or would you prefer that I just add them as individual comments in this task?
Drafts: I'd suggest that we exchange drafts by email rather than posting them here. Posting here would seem likely to add to the already confusing site search engine's by producing largely duplicative entries. Or should we use CVS?
Best regards,
Paul
Comment #3
nancydruDrafts: yes, we should probably do that by email. You have my address already.
Bug reports: Hmm, it's easier to track issues one-by-one. It might also be nice to distribute the docs with the module (CVS) in addition to having them in the handbooks. On the other had it might be nice to have them all in one place (single issue). Does anyone else have a preference?
I'm sorry to hear that, Paul. I know how it can be because my mother is now being counted in hours.
Comment #4
Marbux commentedIt's hard to lose a parent. I lost both of mine in the early 90s. I still get the urge to give them a telephone call at least once a day and have a huge hole in my very being that will never be filled. One of the surprising things you might be on the watch for was the sometimes almost overwhelming anger I felt at first because my parents left me.
On the documentation bug reports, I'll post them as separate issues and maintain an index of them in the first post of this thread for now. We can always change that approach later.
On distributing the documentation, it seems to make more sense to me to just have a link to it in the Readme or an application shortcut to the documentation distributed with the module. That way, folks will be encouraged to rely on the most up-to-date version of the documentation.
Best regards,
Paul
Comment #5
nancydruWell, I've been her almost sole care-giver for 2½ years. I don't think I'll feel that anger as much as I might at my family for having me give up my career and then end up with virtually no support.
That approach is fine. The link is in the README.txt file now.
Comment #6
nancydruhttp://drupal.org/node/241377
http://drupal.org/node/237582
Also, something about reports of problems with PHP 4 (especially 4.3.x).
Comment #7
nancydruBumping this to remind us both...
Comment #8
gobinathmClosing the issue. It was inactive for a long time & it's related to a Drupal Version which is not supported anymore