- Development - lists.drupal.org

"Accepted" status for issues
by Dmitri Gaskin 13 Mar '09

13 Mar '09

Hey Development, What about adding a "Accepted" status for issues, kind of in between "active" and "has a patch" - we recognize it's a bug, we're working to fix it, or we like this feature, we're going to implement it. What are your thoughts? Dmitri

7 8

modify the "add comment" in links
by Aldo Martinez Selleras 13 Mar '09

13 Mar '09

how can i change the link title "Add comment" for Reply, but only for forum and blog posts?? must be with theme() ??? thanks in advanced -- ---------------------- Aldo Martinez Selleras Especialista en Telematica CITMATEL GND Camaguey Tel: 53 32 291661 Linux User #364356

9 17

contrib categorisation
by robert crowther 13 Mar '09

13 Mar '09

Listen, if anyone wants to suggest a better thread title, please do so! Anyhow, the 'Duplicated Modules' thread has moved in this direction (one suggestion being that duplicate modules would be more easily avoided if modules were categorised more freely and finely) ...and the 'An Alternative to Common Thinking' thread has moved in this direction, as leaning towards natural selection (if I might draw that analogy without upsetting anyone. If I have, I do apologise, but I hope you understand the process I am trying to summon) ...whereas at the moment we have an exciting and spontaneous enthusiasm from the fertile ground of Drupal core. But it would be nice to move this part of the discussion aside, I feel? Hence the new subject line. Look, I simply glance at dev to keep tabs on things. But I do recall something about this being talked over before. So I'm sure there is discussion I am not party to. RE: Walt Daniels - I've never seen Tagadelic (told you I'm not current) but a quick look tells me you most certainly get my drift. SoundSnap has a number of features (many I like), - A rough overall vocabulary - Sub categories Terms. Don't know who provides these. - A tagging system Now I assume this is free-tagging by contributors. But it works very well. I use it all the time for cross checking. Whether these categorisations are actively checked for synonyms or not, I don't know. I assume that people think carefully about their tagging though, otherwise their contribution will not show. - A star rating system. Now I hardly ever use this, as I may want a 'spitfire takeoff', not a 'spitfire flyby' (if I looked up aircraft). But I might use... - Download count - List sorting I never use it. As with EBay, where I slam everything onto 'Ending Soonest' (though I do use 'Auctions' and 'Buy-it-now' tabs) - Comments Hardly ever use them, because... - Try before download and finally - Search box suggestions e.g. 'telephone' might suggest 'ring'/'booth'/'operator'. Don't know how SoundSnap regulate this, but the suggestions are clearly pertinent, even inspiring. Differences (between Soundsnap and Contrib) Soundsnap is actively vetted for content. Don't see how this changes the argument, but there you are. You can sum up a sound sample on one line. Actually, I don't see why you can't sum up a module on one line, but there you go... Similarities Errm, I think SoundSnap is Drupal. Just guessing, from the interface and all. The base information is probably on a similar scale to contrib. SoundSnap claim about 100,000 samples. Anyway, they achieve highly effective searching over a large base. I imagine, given their content, the searches are pulverising and fine grained... in short, very intensive. Further thoughts The current Drupal system provides SOME of this anyhow. The main missing bits seem to be, - A thumpingly big front end. - Some sub-classification on the front end. - Tagging. - A suggestive search. - Knowing which bits SoundSnap actively administer, and what that would cost in the Drupal contrib environment. And maybe - Encouraging people to produce one or two line distillations of module descriptions. I love the idea of a try-before-buy feature. The only analogy I can think of is to more actively encourage screenshots. This may work in an EBay fashion - you get no interest without that little picture in on the left... Right, and now I feel somewhat embarrassed that I'm not going to do this, ...well, not now anyhow... so, over to the list, Rob

2 1

Duplicated modules
by Karoly Negyesi 12 Mar '09

12 Mar '09

Hi, OK all you wiseasses, now you pissed me off enough to bring these issues into wider public, so tell me what to do in these situations. 1) There is a Drupal module, older than my boots, gets a much needed rewrite by two guys. Comes a third one, and he is, of course, welcome to the party. There is a discussion of what we do and what we not to do. Come next day, said third guy does what we all three agreed not do. Following a debate, he packs his toys and starts a new project. Said third guy contributes heavily to Drupal project for extremely long but quality and quantity does not always correlate. 2) I hand off privatemsg to another maintainer. He wants to go in a direction which neither me nor someone else even higher in the Drupal hierarchy agrees with. We all three come to a happy conclusion and the new maintainer does not go there. Time passes, and another guy, notorious for starting a parallel project, does exactly the thing we agreed on not to do and despite he says it was just experiment with the new Drupal 6 code, the project lives on. NK PS. the project moderation queue would undo Drupal because people would take their not-accepted projects off site. php nuke follows. PS2. 'mob rule' applied to code does not work. Your precious drupalmodules.com which I opposed from day one is an excellent example. captcha rated #2 , cck and views not even in #10, give me a break, this is broken,.

18 26

Re: [development] An alternative to common thinking in 5- > 6migration
by robert crowther 12 Mar '09

12 Mar '09

And after Earl, how about a voice from the small fry? I had an idea for a module. That was half a year ago now. I knew nothing about Drupal and PHP. I don't even know about how programming culture works. After a helpful comment on dev (so how about being kind to frustrated people who stumble onto here?) I got going. My module is low profile because I want it to be. It's not ready for the big time. It is proof of concept. I try to make it clear to anyone who stumbles onto the work just what it can and can not do. This story works both ways, I guess. I'm exactly the kind of person some people would like to clear out. And other people would like to encourage, in the hope that 1 in 9 of the efforts might hit something good. Following David Meltzer yesterday, who sees a couple of basic arguments on separate threads.... I don't have time to read through all of this, There is another way of avoiding duplicates, besides review. If the cataloguing was good, you'd see the duplicates fast. And if cataloguing was good, you get minor efforts, such as my own, further down the pile. When I started my module, I searched Drupal modules and came up with 9 - 12 other modules, all in separate places. It took me hours. Not an adverse criticism folks, I'd rather contrib was big than small. And I'm another person who will not be applying myself to this right now (though there is a thought). Me, I'd rather make suggestions http://www.soundsnap.com/ Now that is a search facility I like. Rob

2 1

Re: [development] Duplicated modules
by As If Productions 12 Mar '09

12 Mar '09

At 05:45 AM 3/11/2009, Ivan Sergio Borgonovo wrote: >What I'd find useful would be >- better categorisation system and better search system on categories Big +1 on that. >- a flag to check if a module provides an API or is just an application >- an activity index (average lines of code changed/time) >- a issue queue index Regular +1 on those. >Maybe we could let people (other than the maintainers) to >"categorise" the project. Best idea I've heard yet. Ivan, I want to have a beer with you. >I really don't see duplication as a problem. Ditto. In fact I appreciate it. It's finding the one you need that is the problem. The way I see it, this problem requires a taxonomical/navigational solution, not a paradigm shift in methodology. It would have to be an ongoing task/project in its own right, but IMHO it's one that could easily be supported by less-than-hardcore developers. LVX TF --- As If Productions http://www.asifproductions.com Interactive Worlds and Immersive Obsessions

5 4

arg_separator
by Dave Cohen 12 Mar '09

12 Mar '09

Is there a reason for this in drupal's default settings.php? ini_set('arg_separator.output', '&');

2 1

Failed to install HEAD
by Dave Cohen 11 Mar '09

11 Mar '09

I'm trying to submit a patch which changes a form in install.php. Because of that change the test bot always fails with "Failed to install HEAD". At least I'm guessing that's why, the error message really gives no explanation. Is there something I can include in the patch to make the test bot succeed? The patch is here: http://drupal.org/node/394282 Thanks, -Dave

4 4

sandbox projects
by Jim Taylor 10 Mar '09

10 Mar '09

I'm curious is there is a handbook page on developing sandbox projects. A Google s/d.o search doesn't turn up much (saw mention of it on a recent thread and the one module I have contributed had a 3 years old attempt in there) -- Jim Taylor Rooty Hollow LLC, Owner jim(a)rootyhollow.com www.rootyhollow.com (614) 886-5530 Twitter: jalama Linkedin: http://www.linkedin.com/in/rootyhollow

2 1

Re: [development] Wasting time and effort - Here's a productive suggestion instead
by Dan Morrison 10 Mar '09

10 Mar '09

> From: Marcel Partap <mpartap(a)gmx.net> > >> PLEASE Look at that thread and you will see many others also against >> *enforcement* ( = manpower & acrimony) but for a generally useful >> community-based process. > So enforcement of coding style and not breaking tests is too large of > a price to pay, now i see. Coding style reviews are good, and can even happen automatically. That's trivial. There is even a process for running automated tests. Although you may find that almost no contrib modules HAVE tests. This is a non- automatable detail. Modules breaking tests is not an issue for users. However, neither of these have anything to do with the very real issue of DUPLICATION and overlap. >> Note, not a "core developer" gatekeeper team, > Even after me going to lengths doing 20 or so postings to explain and > reason what i have in mind, it's amazing people still misunderstand > what i propose. Is it me or them. The ONLY way to actually tell good code from bad code, and tell duplicates and redundancy is by informed developer review. That is the manpower needed. And as noted earlier, it needs to be skilled devs, not just popular vote. Which leads us to back to requiring housekeeping work by some non-existent cadre. >> but better visibility and feedback loop to resolve dupes. > Frigging exactly what i proposed. No. "Visibility" and feedback on proposed modules was was my suggestion last year. What I saw you propose in [Date: Sun, 08 Mar 2009 16:30:29 +0100] was bureaucracy, enforcement, automation, restrictions, vetos, and the belief that better code could be automated by : > what is possible is to come up with an algorithm that leads to > a statistically significant improvement on the sustainability and > correctness of decisions. I just gotta disagree that good, or more importantly - useful and unique - code can be judged by an algorithm in a way that will address the problem at hand. If you have such an algorithm handy, please suggest it as an addition to coder.module. > Why does that make me wonder > what sort of device would be required for making a human being to > constructively try to understand someone else's perspective and > subsequently reconsider their own position. :-) > > btw abundant opposition happened before in history to non-messiah > people which were more right than wrong. And so you completely miss the point. o_O Just because lots of experts disagree with you does NOT prove that you must be right. There are a heck of a lot more folk who were told they were wrong - and were wrong. Citing an exception only proves the (general) rule. Whether we are a meritocracy, a democracy, a timocracy or a dictatorship (benign or not), your campaign to make contributing to Drupal three times harder for everyone is just not getting any traction. Vast numbers of people already find CVS and patches a heck of an obstacle. I've had dozens of probably-OK patches die in the water because it there wasn't enough motivation for even one other valid developer to help push it through. Requiring a quorum of *10* votes as you proposed means that nothing would happen ever. If it was even conceivable that Drupal contrib became so draconic, it would force contributions into the "badlands" (see proposal http://drupal.org/node/307211) and possibly be divisive enough to justify a totally parallel repository of 'unvetted but free' code on another site. I (and many others) don't want to see that happen. *sigh* To end on another hopefully constructive suggestion, module voting and rating has ALWAYS been discussed and proposed, and is one of the key requested features the background of the d.o. redesign. If this comes though as providing a top list of recommended or even semi-official modules, that is a good thing. But such ranking or classification is NOT going to take the form of prohibiting people from contributing new innovation. You describe your elaborate voting system as one where not enough votes = no commit access. That may be what is turning everyone off. Voting for informational purposes, I think we could get behind. But making rules that will negatively affect the majority of developers and damage the community ... not popular. It may be possible to rework your proposal in a more practical way - but only if it enables the community by shepherding input, not as a bully cop that bans input by default. .dan.

1 0