Re: [development] Counting .info files [Was: Documenting contribs]
On 10/25/2006 8:34:18 PM, inkfree press (inkfree@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
On Oct 25, 2006, at 6:59 PM, Michelle Cox wrote:
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.
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: 1) the new release system is more important. 2) porting project* and friends to the 5.x API is more important. 3) .info files are still too new, and will probably be in flux for a few versions of core. before i (or anyone else) invests serious effort to do something like this, i'd like to see the .info files a little more well-established and mature. 4) i think the kinds of descriptions we'd want in the .info files and in the project pages are totally different. as someone pointed out, the .info files are specific to a given release, whereas the project node's description spans all releases and branches. moreover, the full project page text could potentially be large, and one of the points of the info file was to prevent running out of memory on the / admin/modules page (/admin/settings/modules in 5.x, i guess). i'd hate to see the .info files bloat so huge that we start running into this problem again. ;) 5) .info files are *entirely* specific to drupal code, and project.module needs to be useful to other sites, too. we probably will have a project_drupal_org.module in the near future to put the worst of our site-specific hacks into, but i'm not interested in making project.module significantly more specific to our usage than it already is. so, i'll boldly assert that this will NOT happen during 5.x, and possibly not ever. ;) cheers, -derek (your under-slept and sometimes friendly project.module maintainer) p.s. rock on michelle! +1 to just editing directly (and leaving a revision). thanks for improving drupal. ;)
participants (2)
-
Derek Wright -
Michelle Cox