That's it, I'm unsubscribing from this developer's mailing list. It's become a complete waste of my time when I continually read things like "that's not development, that's support, but you're going to have to write a custom module using these hooks…" Later all. -- Joel Farris Transparatech.com "There are no mysteries here." On May 9, 2012, at 5:59 AM, Earnie Boyd wrote:

On Wed, May 9, 2012 at 5:49 AM, Andreas Laesser <andreas.laesser@tugraz.at> wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi @all

is there a proper way to display/hide entries on the user profile site?

Spezial case: If I (as a drupal user) post an News/Event entry it appears on my profile site under "Related Content" as "News". (This is ok if I post only one news item per week, but if you post 10/day this will exceed.) I want to hide this entry (and maybe some others) for all users...

Does anyone can provide me a way to do this so that drupal stays still updatable?

This question is not related to development and is a support question. Please follow-up on the support@drupal.org list.

There are theme methods to hide this as well as a custom module using hook_form_alter or hook_form_FORM_ID_alter.

-- Earnie -- https://sites.google.com/site/earnieboyd

Wouldn't be better have a clear distinction of lists like core-dev@ / contrib-dev@ / support@ ? Il 09/05/2012 19:33, Cameron Eagans ha scritto:

Ditto. These lists aren't useful at all. Unsubscribing from both. --

On Thu, May 10, 2012 at 5:43 AM, Todd Bloom <todd.bloom@me.com> wrote:

Honestly, I don't get why there's a fuss about it. How much volume does this list get specifically dedicated to core development, any way?

Did I say "core" development? No, I did not, we've succumbed to the fact that core developers no longer visit this list. We have agreed that this list is to be used by module developers for questions about module development issues. The OP did not speak about development in any way but instead about use.

It's not like it's a high volume list. It's not like it's a big deal to answer questions that someone might have even though it's not specifically related to core development.

The support list isn't "high volume" either. But that isn't the issue. The issue is a segregation for archive purposes. If we just willy-nilly use the list without dedicated purpose what's the point of having a list named development versus one named support? How will a user seeking information know he can depend on a list named development to discuss development issues? We self-police the list so that we can have distinction in the purpose of the list for the benefit of those seeking information. -- Earnie -- https://sites.google.com/site/earnieboyd

Which is why the confusion is cleared up. I like having two different lists, personally. They have similar, but quite different purposes. I don't know that I read the 'this is for the support list' response as snarky at all, and the response was still helpful. As mentioned, it's a self-policing list, and I appreciate that the intention is here to help. Requesting those that help and have set up the helping process to specifically help under what you deem as the best method seems counterproductive. I saw no problem at all with the response email, nor with the development list. Just my view on it. Keep up the good work, all! And thanks for all the free help! Joel From: development-bounces@drupal.org [mailto:development-bounces@drupal.org] On Behalf Of Todd Bloom Sent: Thursday, May 10, 2012 8:12 AM To: development@drupal.org Subject: Re: [development] How to change user profile entries Why even have two lists at all, then? It just seems counter productive to bicker about which list something should be on and just answer the question.  I can't imagine the "archives" of this list being heavily searched for answers, considering how hidden the UI is. On the forums, sure, I could see directing a user to the right place but not here. I feel that the more Drupal grows the more it will lose the sense of community. I mean, seriously - the question was pretty clearly not a "how do I" question and something that would have needed programming to accomplish. And, even if it was outside of the lists scope, why give a completely snarky and unhelpful reply? "Development" is pretty wide open - quite frankly, the question *was* about development of Drupal.  There's a difference between keeping people clear about the topics of mailing lists and just plain being rude. Given that Drupal.org doesn't really even know *what* they want these lists to be, I could see where the confusion lies. I mean, on the mailing-lists page of drupal.org, it lists it as being for core developers. On the mailman page, it lists it as being for "whoever". Some people mention that it's for module developers. Regards, Todd On May 10, 2012, at 05:26 AM, Earnie Boyd <earnie@users.sourceforge.net> wrote: On Thu, May 10, 2012 at 5:43 AM, Todd Bloom <todd.bloom@me.com> wrote:

Honestly, I don't get why there's a fuss about it. How much volume does this list get specifically dedicated to core development, any way?

Did I say "core" development? No, I did not, we've succumbed to the fact that core developers no longer visit this list. We have agreed that this list is to be used by module developers for questions about module development issues. The OP did not speak about development in any way but instead about use.

It's not like it's a high volume list. It's not like it's a big deal to answer questions that someone might have even though it's not specifically related to core development.

The support list isn't "high volume" either. But that isn't the issue. The issue is a segregation for archive purposes. If we just willy-nilly use the list without dedicated purpose what's the point of having a list named development versus one named support? How will a user seeking information know he can depend on a list named development to discuss development issues? We self-police the list so that we can have distinction in the purpose of the list for the benefit of those seeking information. -- Earnie -- https://sites.google.com/site/earnieboyd

On 5/10/12 6:26 AM, Earnie Boyd wrote:

We self-police the list so that we can have distinction in the purpose of the list for the benefit of those seeking information.

While that's a great goal, is the approach of telling people they're on the wrong list actually working? Doesn't look like it. This blog post seems relevant: http://www.marco.org/2012/02/25/right-vs-pragmatic -- Scott Reynen Sliced Bread Labs

Actually it would be better to take it up on the actual issue for this on D.O. http://drupal.org/node/1163962 Jamie Holly http://www.intoxination.net http://www.hollyit.net On 5/10/2012 11:08 AM, Paolo Mainardi wrote:

Please stop spamming, continue the discussion in the appropriate place: http://drupal.org/irc

On Thu, May 10, 2012 at 4:58 PM, Scott Reynen <scott@slicedbreadlabs.com <mailto:scott@slicedbreadlabs.com>> wrote:

On 5/10/12 6:26 AM, Earnie Boyd wrote:

We self-police the list so that we can have distinction in the purpose of the list for the benefit of those seeking information.

While that's a great goal, is the approach of telling people they're on the wrong list actually working? Doesn't look like it. This blog post seems relevant:

http://www.marco.org/2012/02/25/right-vs-pragmatic

-- Scott Reynen Sliced Bread Labs

-- Paolo Mainardi

CTO Twinbit ILDN: http://www.ildn.net Blog: http://www.paolomainardi.com

-- Please consider the environment before printing this email --

On 05/10/12 22:58, Scott Reynen wrote:

On 5/10/12 6:26 AM, Earnie Boyd wrote:

...

We self-police the list so that we can have distinction in the purpose of the list for the benefit of those seeking information.

While that's a great goal, is the approach of telling people they're on the wrong list actually working? Doesn't look like it. This blog post seems relevant:

http://www.marco.org/2012/02/25/right-vs-pragmatic

I like it! However, I think that people will move to the "correct" list when they understand why it serves their interest better to do so. I am not well-known in Drupal, and probably never will be, but I have been helping people in much the same way people here do from the late 1990s with OS/2 and later with various releases of RHL, Fedora and CentOS. Mostly, I either ignored misplaced questions, or tried to give a fairly decent answer (or asked a few questions to get better information), and made the argument for asking their question on the "correct list." To my mind, Paolo and Jamie are completely off the mark. You can, and maybe should, regard these lists as a little like face-to-face meetings. The most important topics at any formal meetings go to conducting the meeting (procedural motions); when the process is determined then the meeting goes on with the real business (substantive motions). Discussing the conduct of this list elsewhere, especially an IRC channel, disenfranchises many of those with an interest in the discussion and outcome.

On 05/10/12 20:26, Earnie Boyd wrote:

On Thu, May 10, 2012 at 5:43 AM, Todd Bloom<todd.bloom@me.com> wrote:

...

Honestly, I don't get why there's a fuss about it. How much volume does this list get specifically dedicated to core development, any way?

Did I say "core" development? No, I did not, we've succumbed to the fact that core developers no longer visit this list. We have agreed that this list is to be used by module developers for questions about module development issues. The OP did not speak about development in any way but instead about use.

I don't know enough about Drupal to judge that, but I note that a part of the response was, "as well as a custom module using hook_form_alter or hook_form_FORM_ID_alter," and that suggests to me that the development list isn't entirely a bad choice.

...

It's not like it's a high volume list. It's not like it's a big deal to answer questions that someone might have even though it's not specifically related to core development.

The support list isn't "high volume" either. But that isn't the issue. The issue is a segregation for archive purposes. If we just willy-nilly use the list without dedicated purpose what's the point of having a list named development versus one named support? How will a user seeking information know he can depend on a list named development to discuss development issues? We self-police the list so that we can have distinction in the purpose of the list for the benefit of those seeking information.

First, I agree that the separation is important. If I think I'll be writing code, this list would be my first choice, and I fully understand that people who are prepared to answer questions about development aren't necessarily anxious to answer support questions. And I am sure there are lots of people well able to answer support questions haven't the skills to answer questions regarding coding. However, I don't see the distinction regarding archiving is valid. I, for one, use search engines extensively, and it makes not one jot of difference to me which list or forum my answers come from or even which site. What matters is that the answer can be found with the search terms I use.