Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
as per a discussion on the devel list, the newly created "version2" module definitely needs a different/better name.
Comments
Comment #1
douggreen CreditAttribution: douggreen commentedPlease rename version2 to "projectreleasemonitor"... whew... what a long name, but it's descriptive! With all the attention on the name, I'm a little afraid to make up a cute name at this point. Should there be underscores in the name?
While I've been developing for Drupal for about 6 months, I'm still learning the Drupal way. I new I'd get flamed for the name, but thought I'd get more kudo's for providing something that is very useful today.
Comment #2
kbahey CreditAttribution: kbahey commentedThis is too long.
modulemonitor or moduleversions is better, and more descriptive since that is what it does.
Comment #3
douggreen CreditAttribution: douggreen commentedI was planning on adding support for themes, so project seems more appropriate. What does the Drupal community feel about? I know we have cck. "Project Monitor" or "/Module Monitor" would imply something that monitors module run states -- which is not what this does. "Project Monitor" works for me, though. "Module Version" seems way off -- versioning is only a means to an end. Could I have "Project Monitor" / "projectmonitor"?
Comment #4
douggreen CreditAttribution: douggreen commentedoops, too much editing... What does the Drupal community feel about abbreviated project names? I know we have cck. Personally I don't like them, and think I'll retract this question.
Comment #5
RobRoy CreditAttribution: RobRoy commentedI think since this monitors the status of Modules, having that in the name is good. "Module status" or "module monitor" is good enough for me and much more descriptive than version2 ;)
Comment #6
douggreen CreditAttribution: douggreen commentedI'd prefer "Project Monitor", because I want to add support for themes.
Comment #7
RobRoy CreditAttribution: RobRoy commentedSounds good to me too. Nice modules Doug, look forward to checking them out.
Comment #8
anantagati CreditAttribution: anantagati commentedProject Monitor sounds good.
Comment #9
douggreen CreditAttribution: douggreen commentedI'm sorry that the concensus seems to be settling in on another name, but the more I play with this, I think it should be called "Release Monitor".
I am pretty close to having a new version ready. This new version starts to move away from CVS in 5.0, but still works like I'd want in 4.7. There's a new option in 5 to display cvs information or not, and the default is set to not.
Can we can settle on a name soon so I can release this? I currently don't have CVS write access to this module.
Just to be clear, as the developer of this module, my preference is "Release Monitor".
Comment #10
RobRoy CreditAttribution: RobRoy commentedI think that's the most descriptive name yet. Do it Doug!
Comment #11
dww"releasemonitor" sounds good. i was just waiting for a little dust to settle before i took any action. ;)
i'll rename the stuff in cvs, fix up the project node and release nodes. however, this won't happen until tomorrow (thursday), since it's late, i've got some work for my day job to deal with yet tonight, and i need sleep. but, i'll take care of this tomorrow... i know you want to make progress.
thanks for the contribution! these are exactly the sorts of tools i was hoping people would start to build now that the new release system is in place.
cheers,
-derek
Comment #12
dwwok, everything is renamed to "releasemonitor" in CVS as appropriate. the old "version2" stuff is completely gone now. please do a fresh checkout, like so: "cvs checkout contributions/modules/releasemonitor" and you'll see all the old revision history is there.
i also updated the appropriate files in the project node, and renamed the 5.x-1.x-dev release node (and tarball).
i delete the 4.7.x-1.0 release completely, since it was bogus, and not going to work anyway.
all the hooks in this module are now broken. you get to rename "version2" to "releasemonitor" in all your files and commit those as appropriate. you should move the DRUPAL-4-7--1-0 tag once you've got something working again, and make a new release for that.
let me know if you have any questions or problems from here.
cheers,
-derek
Comment #13
douggreen CreditAttribution: douggreen commentedthanks - btw, when I went to close this issue, the "Component" changed, "cvs" was no longer an issue, and I had to select another one.
Comment #14
dwwthat's because the projects for d.o maintainence stuff have been split: http://drupal.org/node/107131