[haiku-web] Re: updated developer's permissions
- From: "Jorge G. Mare" <koki@xxxxxxxxxxxxx>
- To: haiku-web@xxxxxxxxxxxxx
- Date: Sun, 29 Nov 2009 19:37:22 -0800
Matt Madia wrote:
On Mon, Nov 30, 2009 at 01:16, Jorge G. Mare <koki@xxxxxxxxxxxxx> wrote:
Urias McCullough wrote:
Well, not speaking for him specifically - I wouldn't have understood
why the "Dev" role wasn't meant to be assigned to developers either...
So, its very name is misleading.
Yes, the fact that several developers had a role "Dev" seemed to imply
that developers are intended to have it. Many developers on the drupal
site had only the basic permissions, which are granted to all
authenticated users.
Based on that, I saw no reason for any preliminary discussion. I saw
it simply as a matter of inconsistency that developed over time.
Basically, you made the wrong assumption out of ignorance of why that
role was there.
I can understand the assumption that Matt made, but I also think he has
already given too much access to too many people that may not understand
what they are doing.
Which permissions do you not trust our developers with?
No single person here has the authority to change permissions. Period.
So it's not what I (or you) think, but what all of us think, and that's
exactly what should have been discussed. Assigning new permissions has
ramifications, so it should done on a whim by the assumption of a single
person who does not understand those ramifications.
Once it's agreed upon, I'm willing to implement modifying the permissions.
It's the other way around Matt: if you want to change permissions, you
ask first.
So, please revert this change right away, because if you don't, I will.
But besides all this reasoning, what is so hard about the concept of prior
consultation? Why is it so hard to ask before do, especially when you don't
know what you are doing like in this case?
For something that is an error, I see no reason for preliminary
discussion. I performed the correction and notified this list. This is
a standard procedure in committing code, editing content on the
website (even when it is submitted by another person), and elsewhere
in our community.
You corrected nothing; all you did was give permissions to people that
are not supposed to have them in the first place, and you did that based
on wrong assumptions and your own unilateral decision. That is the problem.
If you want to give the developers the ability to add/change content, I
agree. But then start a thread to the effect so that we can discuss what
the best approach would be; this is not for you to decide alone,
particularly being that you know close to nothing about how Drupal works
and are not familiarized with how our system is setup.
Whereas you Jorge, have performed structural changes to the site
without prior consultation nor discussion.
For example changing the behavior of the top news entry to not display
the author(this was later reverted after the fact upon inquiry from
Axel), removing the GSoC/HCD 2009 sidebars (but more importantly its
contents), and changing the url of the community/gsoc2009/ pages
(without at least creating redirect urls) are some examples that come
to mind.
I do not recall any discussion before they were implemented nor
notifications after the fact. Please understand that I'm merely
pointing out examples to demonstrate that you Jorge, also forget about
(or simply do not abide by) the concept of prior consultation from
time to time.
So, a little consistency on your part would be appreciated.
I think it's you who forgets. In the process of upgrading the website to
the new theme and Drupal version for the alpha 1 release, I put up a
test website online many weeks before the actual migration , so that
everyone could review the changes and provide input, which a lot of
people actually did. The upgraded website was also live online for about
one full week before the alpha 1 release for everyone to review.
If you thought something was wrong with what I had done, you should have
spoken out then, not try to use this against me now several months later
on something totally unrelated.
Regards,
Jorge/aka Koki
-----------------------------------------------------------------------
haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List
Other related posts:
