Yes, I'm familiar with it, and will add a mention of it on the project page. I created this new module because a client wanted a smaller image, and the ability to control it for specific hosts without editing the settings.php file. I felt the differences were enough to create a different module.
Thanks Dan. I've got a few questions regarding releases and documentation that I can't find the answers to; maybe I'm not looking in the right place. I'd appreciate any suggestions on where to look, or how to raise these as issues:
1) Some contrib modules have a "related modules" section in the right column of the project page. How are these added? Is that something I can do, do webmasters do it, is it automatic?
2) Also, there is often a "read documentation" link under "resources", that points to a handbook page. I believe that is created from the "documentation" field under "project resources" on the project page editor. What is best practice for creating the handbook page? I'd think it could be under a "developer modules" section, but can't find one. I saw that token has a docs page in handbook/modules/token, but imagecache uses just a page node. Are we striving for a hierarchical arrangement, where doc pages are under handbook?
3) What is best practice for attached images on a project page? Can there be more than one? Can they be deleted?
4) There is no recommended release when I try to download the module with drush by just project name, but under "administrate releases", I do see a recommended version, and it has been there for over 12 hours. Should I just wait, or should I report this? I seem to recall having this problem in the past for other modules too.
Sorry to bother you with these questions; I'm sure there must be a better procedure for dealing with them, but I'm not of where to ask. I do follow the webmasters mailing list, might it be the place?
1) AFAIK it's automatic. Not sure how it's calculated though.
2) Can point to a handbook page. I usually point it right at the CVS version of the README. Others link it offsite. Whatever works. Make your own at Contributed Module Documentation
3) Without Higher Drupal.org rights, there can be only one. No guidelines that I know of. yes you can replace it later. http://drupal.org/documentation-writers-guide
4) Apparently this is still a known bug on the very first release of a new project. I believe it can be fixed by adding an updated release (eg version +.1) over top of your existing one. If not, you'll have to ping the d.o webmaster crew re CVS. Do just raise an issue there, it's no biggie.
Comments
Comment #1
pglatz commentedYes, I'm familiar with it, and will add a mention of it on the project page. I created this new module because a client wanted a smaller image, and the ability to control it for specific hosts without editing the settings.php file. I felt the differences were enough to create a different module.
Comment #2
dman commentedCool. A cross reference to similar projects is enough to help people figure things out. That would be cool.
Comment #3
pglatz commentedThanks Dan. I've got a few questions regarding releases and documentation that I can't find the answers to; maybe I'm not looking in the right place. I'd appreciate any suggestions on where to look, or how to raise these as issues:
1) Some contrib modules have a "related modules" section in the right column of the project page. How are these added? Is that something I can do, do webmasters do it, is it automatic?
2) Also, there is often a "read documentation" link under "resources", that points to a handbook page. I believe that is created from the "documentation" field under "project resources" on the project page editor. What is best practice for creating the handbook page? I'd think it could be under a "developer modules" section, but can't find one. I saw that token has a docs page in handbook/modules/token, but imagecache uses just a page node. Are we striving for a hierarchical arrangement, where doc pages are under handbook?
3) What is best practice for attached images on a project page? Can there be more than one? Can they be deleted?
4) There is no recommended release when I try to download the module with drush by just project name, but under "administrate releases", I do see a recommended version, and it has been there for over 12 hours. Should I just wait, or should I report this? I seem to recall having this problem in the past for other modules too.
Sorry to bother you with these questions; I'm sure there must be a better procedure for dealing with them, but I'm not of where to ask. I do follow the webmasters mailing list, might it be the place?
Comment #4
dman commented1) AFAIK it's automatic. Not sure how it's calculated though.
2) Can point to a handbook page. I usually point it right at the CVS version of the README. Others link it offsite. Whatever works. Make your own at Contributed Module Documentation
3) Without Higher Drupal.org rights, there can be only one. No guidelines that I know of. yes you can replace it later. http://drupal.org/documentation-writers-guide
4) Apparently this is still a known bug on the very first release of a new project. I believe it can be fixed by adding an updated release (eg version +.1) over top of your existing one. If not, you'll have to ping the d.o webmaster crew re CVS. Do just raise an issue there, it's no biggie.
Comment #5
pglatz commentedThanks for your help, Dan, much appreciated!