- Development - lists.drupal.org

Re: [development] Getting both better internal and external APIs intoDrupal 7
by Michelle Cox 30 Dec '07

30 Dec '07

On 12/30/2007 10:46:35 AM, Wim Mostrey (drupal(a)mostrey.be) wrote: > I don't think bio is a good candidate for this, if the plan is to > replace the profile module. Bio does not allow to put fields in the user > registration form, which in my opinion is a required functionality for > core. From my experience node profile does the cleanest of this (to make > it core-worthy the node family dependency would need to be dropped of > course). I have used both nodeprofile and bio and they are both good modules but I think recent changes to bio make it just a bit better. As noted elsewhere, bio now has the ability to put fields on the registration page. Better yet, it has the ability to _selectively_ put them there, not just dump the whole node there. Plus, nodeprofile has two module dependencies. Bio is a lighter solution. I like both modules and nodeprofile is the way to go if you want multiple node profiles for sure. But if anything would be considered for core, I would recommend bio as it is a lot lighter weight. Michelle

1 0

Re: [development] Op-ed: Posting FUD/flame bait to the front page is unproductive, disrespectful, an abuse
by Michelle Cox 30 Dec '07

30 Dec '07

On 12/29/2007 10:58:29 PM, Caleb Gilbert (caleb.gilbert(a)gmail.com) wrote: > ...and is not an appropriate thing to do for people with Drupal.org > frontpage rights. I agree completely. Which is why I demoted it to begin with. For the record, I have always maintained (despite the lies he posts on the thread) that he was in his rights to post the discussion. If he has concerns, he should ask. I don't want anyone to ever be afraid to speak their mind. The _only_ thing I have ever objected to was the promotion to the front page. I see the front page as a "brochure" where you post positive things about Drupal for the benefit of new people. It is _not_ the place for controversial posts that will have new people wondering just what sort of community they are getting into. I was asked by killes a while ago to look after the front page and since then haven't had to do very much. On the whole, the 90ish people with rights to promote do a good job. The only thing I've demoted up to this point is some local group events back when we were first settling on a policy for events on the front page. And I had no backlash from that. This is the first time a maintainer has flamed me for demoting something and then went behind my back and re-promoted it, even knowing that other admins agreed with me and it wasn't a unilateral action on my part. Personally, I don't see this as a breakdown of the system but simply an individual abusing his rights. The frontpage is pretty common sense, IMO. Put up things that will bring people to Drupal and announcements the community needs to know about. It should be a happy place, not a flame fest. Ask yourself, if you were new to Drupal and saw this post, would you turn around and not come back? Common sense is all that's needed. If you are unsure, file an issue or hop on IRC and converse with other admins. I'm even going to go so far and say I feel that promoting your own post is fine if it's something that belongs there. I don't think him promoting his own post was really the problem. It was him promoting his own opinionated, controversial post and then repromoting it after it was discussed and demoted that was the problem. There's a big difference between that and, say, Gábor writing up a release announcement and posting it. So I think promoting your own benign post is fine but, for goodness sake, if it gets demoted for some reason, don't just repromote it without discussing it. Again, it all comes down to common sense. As long as we all use it, the front page will be fine. Ok, off my soapbox. :) Michelle

3 2

Getting both better internal and external APIs into Drupal 7
by Dmitri G 30 Dec '07

30 Dec '07

Hello, list. I saw Dries' blog post about the State of Drupal presentation, and I looked through the presentation (for those of you who haven't seen this, it's at http://buytaert.net/state-of-drupal-presentation-september-2007) There is a list, titled "Drupal 7 killer release". It contains 11 items, three of them developer items. Two of them, #9 and #10, are about better APIs. You might scream at me for this, but I think having better APIs would be best solved by converting everything (users, comments, terms) to nodes. However, nodes are too heavy. They have a big hit on performance. My proposed/ideal solution would be to make the node more light-weight. Put fields (CCK-style) and access in it, and that's it (no title, body, extra fieldsets). Beyond that, each type can customize everything. Furthermore, things like content types would be moved specifically into the thing that used to be called nodes. This requires putting CCK or something like CCK in core. While these together may be beyond the scope of a single release, they would bring more power into Drupal, and bring uniformity with them. Back to APIs. To successfully implement them, nearly everything would need to turn into fields. That includes modules like event - it just needs to add fields to a node. The import/export API only needs to deal with nodes fields (since everything is made of nodes and fields), unlike the one done in SoC. The web services need to do the same. Only very complex data types/additions need to implement a hook_webservices or hook_importexport (or maybe we can combine them). Please respond with your criticisms! dmitrig01

5 7

Op-ed: Posting FUD/flame bait to the front page is unproductive, disrespectful, an abuse
by Caleb Gilbert 30 Dec '07

30 Dec '07

...and is not an appropriate thing to do for people with Drupal.orgfrontpage rights. If there is something that an individual wants to talk out with the active Drupal community it should be done on the mailing listing, in the forums, in irc, Planet Drupal, via email or other appropriate places which are NOT supposed to be reserved for ushering in newcomers. Of the hundreds of thousands of people who visit the front page, only a few hundred of them have enough inside knowledge of the Drupal community to have an educated opinion, so why not spare the vast majority of Drupal.org visitors from posts, which in their eyes, likely serves nothing but to undermine the legitimacy of Drupal, its community, and open source. Besides the practicalities of the situation it's also very disrespectful and a betrayal of trust to the people/project who granted the frontpage rights in the first place to do such a thing as posting personal agenda-type items to the frontpage. Here's hoping that individuals and the community-at-large tighten the reins around themselves/each other in order to avoid these personal-soapbox situations in the future (unless it's to evangelize Drupal, the community, or open source), because it seems to be having a profoundly negative effect on morale...

2 1

Op-ed: Posting FUD/flame bait to the front page is unproductive, disrespectful, an abuse
by Caleb Gilbert 30 Dec '07

30 Dec '07

For the record I had these thoughts (see previous message) when the post I'm referring to first went up, and after watching the commotion it has caused I continued to feel more strongly about it. Tonight after seeing sepeck's post I finally gave into saying something about it... <steps of soapbox, himself>

1 0

Re: [development] Updating drupal.org to Drupal 6 release candidate
by Chad Phillips -- Apartment Lines 29 Dec '07

29 Dec '07

project* needs more manpower help. specifically, help with the views conversion stuff would be great, and review/testing of issues listed at http://groups.drupal.org/node/7396 (some of which are holding up project's next release, which holds up other progress). when we get to the point in the roadmap where the 6.x port will happen, then any number of people could help w/ the grunt work there. if we can get a few more people to really start pitching in more time with things on the roadmap, then a port in the foreseeable future would be possible. without the extra help, there's only so much that dww, i, and the few others who pitch in regularly can do. basically, this is the same plea for help that we've been sending out for a long time now. :) hunmonk

1 0

Re: [development] Themes and modules have a new method for adding screenshots
by Michelle Cox 29 Dec '07

29 Dec '07

On 12/29/2007 5:53:17 AM, Yves CHEDEMOIS (yched.drupal(a)free.fr) wrote: > Michelle Cox a écrit : > > re: http://drupal.org/node/202856 > > > > You can now add screenshots to your modules and themes via image assist. > > That would be image_attach, right ? Whoops, yes. I've never used either of those before last night and got them mixed up. Sorry. Michelle

1 0

Good D6 test?
by Dries Buytaert 29 Dec '07

29 Dec '07

http://lstigile.wordpress.com/2007/12/27/cms_mysql/ -- Dries Buytaert :: http://www.buytaert.net/

2 1

Themes and modules have a new method for adding screenshots
by Michelle Cox 29 Dec '07

29 Dec '07

re: http://drupal.org/node/202856 You can now add screenshots to your modules and themes via image assist. There's a new fieldset, "attached images" with a spot to upload. A thumbnail is automatically created and placed on the project node. This takes the place of the old links on themes so please remove those. Everyone who has used their CVS account in the last year has been given the role with access to it. If you have any problems, please file an issue. Michelle

3 2

form protection?
by Alessandro Feijó 29 Dec '07

29 Dec '07

I'm manipulating dynamicaly the content of a Combobox It starts empty, I set the values with jQuery, and when I click Submit, an error say something like 'invalid content, contact your administrator' There is any protection to prevent content different from the original possible values to an <SELECT> ? Its hard to search for it, what keywords? :) Thanks Feijó

6 8