October 2006 - Development - lists.drupal.org

Re: [development] Contrib module clean up - Status report
by Michelle Cox 29 Oct '06

29 Oct '06

Just wanted to let people know that something has come up and I won't be able to work on this until Wednesday. Michelle

1 0

Contrib module clean up - Status report
by Michelle Cox 28 Oct '06

28 Oct '06

I've started at Z and gone through W with the page filter set to "all". I tagged, !--break'd, and cleaned up where I could. These are the remaining issues I see with the modules in those letters: zippy images - Only release is cvs. Needs a better description Z39.50 Search - Last release is 4.6. Ystock - Last release is 4.6. xstatistics - Needs a better description but I don't get the module well enough to write it. workspace - Description makes good teaser, but could use more meat on main page worklog - Has a 4.7 version but default is cvs workflow - Has a 4.7 version but default is cvs worldfilter - Has a 4.7 version but default is cvs wiki404 - Only release is cvs. Last update Apr 2006. Could use a better desc. if it's not abandoned. whatsrelated - Last release is 4.6. Defaults to cvs. wgHTML - Last release is 4.6. weight - Description says "Module now works with both 4.6 and 4.7 (CVS) versions of Drupal." cvs is default. 4.6 version not listed. Weekly node listing - Has 4.7 version but 4.6 is default Webserver Auth - Has 4.7 version but 4.6 is default WebMedia - Only release is cvs. Screenshots require logging in to view. Weblink - Desc says "This module is discontinued after CVS/HEAD" Last version is 4.6. Possibly change that note to be clearer with versions? webcomic - Has a 4.7 version but default is cvs Weather - cvs default. 4.5 only other version. Demo page not found. Project owner email is listed as drupal-devel(a)drupal.org waypath - Only release is cvs. Last update Apr 2006 A lot of them need the default download changed. I didn't do that because I felt that's something the maintainer should do in case there's a reason it's set as it is. Some of the modules haven't been updated since 4.6 or before. If these have been abandoned, I suggest putting a note as such in the description. If you see any of your modules here, I'd appreciate it if you could either make the change or let me know why it shouldn't be changed. When I get through all the letters, I'll see what modules still have issues and contact the maintainers directly. Thanks, Michelle

5 4

Re: [development] Contrib module clean up - Status report
by Michelle Cox 27 Oct '06

27 Oct '06

On 10/26/2006 4:58:37 PM, Chris Kennedy (chrisken(a)mail.utexas.edu) wrote: > How difficult would it be to patch project.module to display the date of > the last commit and/or release on the teaser page for each module, next > to the "Download", "Find out more" links (or next to the module title)? > > The last release date is shown on the full project page already so it > seems like automating this functionality would be best, rather than a > one-time update. I will volunteer to code a patch if it would be helpful > and/or if Derek is busy. I like this idea. On IRC just a bit ago, Derek said "i'll be gone until at least friday night, maybe not until early next week". I don't know if that includes gone from email, too, but thought I'd mention it in case he doesn't respond. Michelle

2 1

Re: [development] Contrib module clean up - Status report
by Michelle Cox 27 Oct '06

27 Oct '06

On 10/26/2006 4:48:39 PM, Gerhard Killesreiter (gerhard(a)killesreiter.de) wrote: > In most cases the reason probably is "maintainer forgot to set it". Feel > free to change it to the latest release, it can easily be changed back. Ok, will do. > It is always difficult to guess wether a module is truly abondoned. I > myself have modules that don't > yet have a 4.7 release since I don't use > them myself and there aren't > enough patches. > > But if for example the latest commit is like one year ago on the 4.6 > branch and nothing on HEAD since then, it is safe to assume it > won't be > updated any time soon and maybe never. Adding a note about this will > save people from wasting their time with it. Feel free to add such > notes, they can also easily be removed. Add something like "this module > hasn't > been updated in a long time and the author isn't very resresponsive. >It is possible the module is abondoned. The management." That will take a little investigating in each one, so I'll go back through and do that once I've gotten the rest taken care of. Thanks. Michelle

1 0

can't add DRUPAL-5 tag
by Peter Wolanin 26 Oct '06

26 Oct '06

A quick question re: using CVS. I just updated a module, but I'm getting an error whan I try to apply the DRUPAL-5 tag: $ cvs tag DRUPAL-5 ** ERROR: invalid tag for this directory: ** contributions/modules/og_mandatory_group cvs tag: Pre-tag check failed cvs [tag aborted]: correct the above errors first! for some of my module's i have avoided branching them until the next core is branched, and was planning to do that again. Can the DRUPAL-5 tag only be applied as a branch tag? thanks, -Peter

3 2

Re: [development] Counting .info files [Was: Documenting contribs]
by Michelle Cox 26 Oct '06

26 Oct '06

On 10/26/2006 2:24:01 PM, Thomas Barregren (thomas(a)webbredaktoren.se) wrote: > Ok. It was just wishful thinking. :-) Nothing wrong with wishes. Having projects notify their maintainers when their descriptions are changed is actually a pretty decent feature request. I suggest filing an issue so the idea doesn't get lost in the archives. > I can understand that [not manually notifying every little change]. The > purpose with my original post on this subject > was actually to express my approval of your work. Thanks :) > I may have misunderstood the terminology here. But since we were talking > about module description, I thought maintainer meant the maintainer of > the module. I am the maintainer of RoleAssign > <http://drupal.org/project/roleassign>, but I havn't access to previous > versions of the description I have written. I guess you need site maintainer access to view revisions. Unfortunately Drupal's permissions aren't very fine grained so I don't think it's possible to give module maintainers access without getting it across the site. But there are revisions there behind the scenes, so all you need to do is ask if you want something reverted. A bit of a PITA, I know, but best I can suggest with the current infrastructure. General FYI - If your module (haven't got that far yet) has a decent description with no more than a few lines before the  tag, and is tagged with the appropriate category(ies), it's unlikely to be messed with anyway. :) Michelle

1 0

Re: [development] Counting .info files [Was: Documenting contribs]
by Michelle Cox 26 Oct '06

26 Oct '06

On 10/26/2006 4:28:57 AM, Thomas Barregren (thomas(a)webbredaktoren.se) wrote: > If we are encouraging people to edit each others module description (or > handbook pages for that matter), I would very much like to see an > opportunity to register for an e-mail upon change, very much like how it > works on Wikipedia. In that way, a maintainer (or any other interested) > would automatically be informed every time a change is made. That is > particularly important to make it possible to see small changes which > otherwise could go undetected for a long period of time. I don't think this is possible with the current infrastructure. I'm emailing the maintainers if I make major changes that they'll want to review. I'm not emailing every one I'm adding a break tag to, though. > I also would > like to see reversion management of the pages, again very much like how > it works on Wikipedia. What do you other guys say? There are revisions built in. If the maintainer doesn't like the changes, it can be reverted. Michelle

2 1

Re: [development] Counting .info files [Was: Documenting contribs]
by Michelle Cox 26 Oct '06

26 Oct '06

On 10/26/2006 3:31:39 AM, Derek Wright (drupal(a)dwwright.net) wrote: > as the person most likely to write any code that takes .info files > and replaces project descriptions with them, i guess i should speak > to this... > > i have no intention of doing anything like this anytime soon for a > variety of reasons: Thanks for clarifying this. I suspect I was misunderstanding what Moshe wrote in an earlier email. Michelle

1 0

input formats
by zis 26 Oct '06

26 Oct '06

Hey everyone, This is my first contribution to the list; i have a porpostion i want to make, it would be nice to have it included.. I think an important feature that should be available, is to be able to assign input formats by node types. Let me give you an example, let's say we have a site with a forum section and a stories section.. all members can submit stories and post in the forum. I want the posts in the forum to have bbcode and other filters.. let's say an input format called "Forum posts" On the other hands i want the stories to be submitted with the "Filtered HTML" filter.. There currently is no way of assigning input formats to node types.. It shouldn't be too difficult to implement. Each content type configuration page can have a section with a filter selection and weighting.. and there would be a overall site default that could be overridden by the content type specific filters... I hope i made my self clear.. waiting for your feedback. zis

5 5

Re: [development] Counting .info files [Was: Documenting contribs]
by Michelle Cox 26 Oct '06

26 Oct '06

On 10/25/2006 8:34:18 PM, inkfree press (inkfree(a)gmail.com) wrote: > I mistakenly connected the idea of ".info" to the current 4.7.x module > list, > and swung the conversation slightly away from meaningful. I knew that .info was meant for 5.x, but (nearly) all these project pages that are currently for 4.7 modules will be for 5.x modules soon. I was afraid they would undo everything I'm doing. I didn't get a direct answer to my question, but the wording of related posts made it sound like that's not the case. So I went ahead and got started with Z. I'm only up to X so far... I tend to bounce between projects a lot. I'll keep working my way up the module list a little bit at a time. If you want to start at the top and work down, we'll meet at the middle. :) At this point, I'm only fixing up formatting, adding a break tag, categorizing if necessary, and other minor edits. I'm not tackling the related to/prerequisites, yet, unless they are already part of the description as in the case of zip code. If I hit a module that needs more work than I can do right now, I'll make a note of it and come back. Module maintainers, feel free to jump in and clean up your own. That'll get me through the list faster. ;) Michelle

2 1