Contributions CVS Cleanup
Kjartan - March 29, 2006 - 15:33
Since the contrib CVS is starting to get relativly full again here is the list of modules/themes that haven't been updated or had any stable releases for a while. These will get moved to the Attic in CVS to make it easier to find what is currently active projects. We will also move all files in the sandboxes that haven't been touched in a year or more to the Attic as well.
If anyone spots any mistakes post a comment and we will clean it up.
Modules and themes with no 4.5.x, 4.6.x 4.7.x, releases, and not updated since 2005-09-30 (~6 months)
| File | Releases | Last Modified | ||||||
|---|---|---|---|---|---|---|---|---|
| admnotify.module | 4.3.x | 2004-10-01 | ||||||
| akvaforum.module | 2005-02-02 | |||||||
| announcement.module | 2005-09-05 | |||||||
| anyfilter.module | 4.3.x | 2003-11-10 | ||||||
| archive.module | 2005-04-17 | |||||||
| asciimath.module | 2005-06-12 | |||||||
| auction.module | 2004-10-01 | |||||||
| am.module | 2005-09-23 | |||||||
| binder.module | 2005-04-27 | |||||||
| blogadmin.module | 4.4.x | 2004-07-04 | ||||||
| blog_archive.module | 2005-03-29 | |||||||
| bloggerauth.module | 2005-01-26 | |||||||
| blog_theme.module | 2005-05-07 | |||||||
| bunchsubmit.module | 2005-08-19 | |||||||
| cafepress.module | 2004-10-01 | |||||||
| chat.module | 2005-07-28 | |||||||
| debate.module | 2005-08-09 | |||||||
| discography.module | 2005-05-06 | |||||||
| download.module | 2004-10-01 | |||||||
| foodmiles.module | 2005-07-30 | |||||||
| resource.module | 2005-07-30 | |||||||
| edit_template.module | 4.4.x | 2004-10-01 | ||||||
| emailfilter.module | 2005-03-13 | |||||||
| encheferizer.module | 2005-08-19 | |||||||
| eventrepeat.theme | 2005-09-13 | |||||||
| faqsuggest.module | 2005-04-20 | |||||||
| fbu.module | 2005-08-28 | |||||||
| filtercache.module | 4.4.x | 2004-09-18 | ||||||
| firefox_counter.module | 2005-04-05 | |||||||
| flickrauth.module | 2004-10-01 | |||||||
| flickr_block.module | 2005-08-06 | |||||||
| friendlist.module | 2004-10-01 | |||||||
| profile_node.module | 4.4.x | 2004-05-06 | ||||||
| groups.module | 4.3.x | 4.4.x | 2005-03-23 | |||||
| handango.module | 2004-12-29 | |||||||
| ical.module | 2005-04-27 | |||||||
| image_browse.module | 2004-10-01 | |||||||
| image_thread.module | 2005-08-18 | |||||||
| image_url_filter.module | 2005-02-25 | |||||||
| importpage.module | 4.4.x | 2005-03-29 | ||||||
| inactive_user.module | 4.4.x | 2004-09-15 | ||||||
| lanparty.module | 4.4.x | 2004-10-01 | ||||||
| libdb.module | 2004-12-01 | |||||||
| livesearch.module | 2005-03-18 | |||||||
| logsearch.module | 2005-06-05 | |||||||
| ma_blogit.module | 2005-01-18 | |||||||
| ma_bzip2.module | 2005-01-09 | |||||||
| ma_gzip.module | 2005-01-12 | |||||||
| mail_archive.module | 2005-02-10 | |||||||
| mass_url.module | 2004-11-24 | |||||||
| media.module | 2005-08-12 | |||||||
| mime_registry.module | 2004-11-24 | |||||||
| moblog.module | 2005-01-29 | |||||||
| navigation.module | 4.4.x | 2004-11-24 | ||||||
| navlinks.module | 2004-11-24 | |||||||
| navtable.module | 4.3.x | 2003-12-19 | ||||||
| netnews.module | 2005-09-09 | |||||||
| node_aggregator.module | 2004-06-17 | |||||||
| node_image.module | 4.3.x | 4.4.x | 2005-07-31 | |||||
| nodeperm_role.module | 2005-02-27 | |||||||
| oldwarning.module | 2004-10-06 | |||||||
| opml_import.module | 2005-04-20 | |||||||
| pirate.module | 2005-09-16 | |||||||
| popup.module | 4.3.x | 2003-12-04 | ||||||
| primary_links.module | 2005-05-01 | |||||||
| privacy_book.module | 2005-07-14 | |||||||
| publish.module | 2005-08-12 | |||||||
| question.module | 2005-08-20 | |||||||
| queue.module | 4.1.x | 4.2.x | 2005-04-24 | |||||
| matching.module | 2005-08-30 | |||||||
| recorder.module | 4.1.x | 4.2.x | 2004-03-10 | |||||
| revision.module | 2004-10-16 | |||||||
| ride.module | 4.2.x | 4.3.x | 2004-10-01 | |||||
| s5_book.module | 2005-09-20 | |||||||
| security.module | 2005-08-28 | |||||||
| shamu.module | 4.4.x | 2005-03-02 | ||||||
| shoutbook.module | 2005-04-07 | |||||||
| sidebar.module | 4.1.x | 4.2.x | 4.3.x | 4.4.x | 2004-10-01 | |||
| simpletest_xmlrpc.module | 2005-08-24 | |||||||
| snippets.module | 2005-03-02 | |||||||
| spam_mtblacklist.module | 2005-02-03 | |||||||
| spam_mtblacklist.module | 2005-01-27 | |||||||
| spellcheck.module | 4.3.x | 4.4.x | 2004-10-01 | |||||
| static.module | 2005-04-18 | |||||||
| stats_plot.module | 2004-08-11 | |||||||
| style.module | 4.2.x | 4.3.x | 2004-10-01 | |||||
| ftpchannel.module | 2005-08-28 | |||||||
| tag.module | 2004-07-04 | |||||||
| taggame.module | 2004-08-10 | |||||||
| task.module | 2005-09-07 | |||||||
| taxnav.module | 4.3.x | 2004-10-01 | ||||||
| taxonomy_similar.module | 2005-05-18 | |||||||
| teaser.module | 2004-12-30 | |||||||
| tec.module | 2004-10-01 | |||||||
| tellafriend.module | 2005-02-03 | |||||||
| term_access.module | 4.4.x | 2004-05-28 | ||||||
| texfilter.module | 2005-06-30 | |||||||
| upload.module | 4.4.x | 2004-07-11 | ||||||
| vocabulary_list.module | 4.4.x | 2004-11-06 | ||||||
| wallpaper.module | 2004-10-01 | |||||||
| waypath.module | 2004-10-01 | |||||||
| flexiblock.module | 2005-07-23 | |||||||
| wireframe.module | 2005-08-24 | |||||||
| zippy_images.module | 2005-05-11 | |||||||
| bluerobot.theme | 4.1.x | 4.2.x | 4.4.x | 2004-08-18 | ||||
| gworks.theme | 4.3.x | 2004-02-07 | ||||||
| xtemplate.theme | 4.4.x | 2004-04-27 | ||||||
| ivy.theme | 2004-06-27 | |||||||
| marvin_2k.theme | 4.4.x | 2004-08-11 | ||||||
| personal.theme | 4.3.x | 2004-02-21 | ||||||
| polder.theme | 4.1.x | 4.2.x | 4.3.x | 2003-11-10 | ||||
| simple.theme | 2004-07-01 | |||||||
| stylebox.theme | 4.1.x | 4.2.x | 4.3.x | 4.4.x | 2004-08-19 | |||
Six months seems too short
Six months seems too short of a time for me - if Drupal 4.7 took more than a year to come out, then we should at least let modules have the same amount of time to update themselves. I'd push it to 12 months.
http://www.disobey.com/
http://www.gamegrene.com/
Developer of Drupal's Game API
Agreed
There do seem to be some useful modules that never received a 4.6 tag. Let's not make the community suffer because the maintainer forgot this tag. I would think 12 months is reasonable. When was 4.6 released exactly? Perhaps that should be the cut off.
Forgot? Perhaps the
Forgot? Perhaps the maintainer decided not to port is the much more likely situation. So if you volunteer to test, update and maintain the module, then volunteer to take it over.
Steps are
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
Branches v. Tags
Perhaps I should have been more clear: there was some confusion over whether to use branches or tags in CVS to indicate the release status of code. I don't remember what the outcome was, but I do remember that many people had used the wrong method to mark versions of their code.
If Developer X used a tag to mark his code, and he should have used a tag, I'd hate to see his code removed.
I can see some value in
I can see some value in that, but is it likely that any module that was coded for CVS 12-6 months ago would actually work with 4.7 when it gets released?
Remember, if the module had a 4.5 or 4.6 release it wont get Atticed no matter if it was 2 years ago the last modification took place. Also it is relativly simple to restore the code from the attic in case someone wants to do further development.
--
Kjartan
Pirate
T' Pirate module should now be tagged for 4.6 and I plan on testin' it in 4.7 and taggin' it as such. Yarr!
consolidation
Any chance of merging it with encheferizer.module for the sake of Swedish muppets everywhere?
+1 For a merged novelty
+1 For a merged novelty filter
And while you're at it...
... could you write us a pig-latin filter? l33t would also be nice.
- Robert Douglass
-----
My Drupal book: Building Online Communities with Drupal, phpBB and WordPress
Contributions CVS Cleanup
We might need separate cvs folders as follows:
4.6.x-cvs
4.7.x-cvs
Apache is bandwidth limited, PHP is CPU limited, and MySQL is memory limited.
Related?
I'm not sure if this is related, please forgive me if not and point me to the right place to post.
As of today, 30/3/2006 all the modules in the 4.6 download area appear to be tagged with their latest release being today.
For example, pathauto claims to have last been updated today, but if I download the .tar.gz none of the files match the new timestamp.
Has some sort of refresh happened that's tagged all these modules like this? It's now impossible to easily tell how old a module really is.
Tim
Edit: Sorry, this should have been a reply to the article, not to the specific comment I replied to.
This is a great idea. I'd
This is a great idea. I'd like to see this happen, because there are a lot of modules that will work with 4.6 but aren't being actively developed, or haven't had their forms API updated. It would also give a heads up for package maintainers to update their modules.
How can we make sure this happens ? Should we start a thread where we testing the CVS modules to see if they work with 4.6 are updated to 4.7. Also some people might want to develop for 4.6 still and have their modules be in the CVS vs. listed as done.
less is more, more or less
good to see cvs being cleaned up. If something really is useful, someone will care enough to do something about it.
loose the crud I say.
what is the deadline?
I've looked through about half of the modules. Most are snippets/junk/duplicate/stubs.
However, there are one or two that interest me. What is the cut-off date?