[development] Drupal's CVS policies... including 'foriegn' codein TinyMCE module?

Walt Daniels wdlists at optonline.net
Sun May 27 13:28:29 UTC 2007

+100 on this

It is trivial to implement just change the policy (but add a pretty please
permission somewhere in the process). 

-----Original Message-----
From: development-bounces at drupal.org [mailto:development-bounces at drupal.org]
On Behalf Of Derek Wright
Sent: Sunday, May 27, 2007 4:12 AM
To: development at drupal.org
Subject: Re: [development] Drupal's CVS policies... including 'foriegn'
codein TinyMCE module?

On May 26, 2007, at 9:29 PM, Boris Mann wrote:

> A patch to the project module / packaging scripts and/or an 
> architecture doc on how such a thing would be built would be more 
> useful.

(trying not to lose my temper...)

WTF?  are you people not getting or not reading my messages?  Gerhard seems
to have completely ignored my input on the discussion, and now you are,

how many times do i have to say it?

1) our existing policy is too strict, and should be relaxed under some

2) it would require a *MASSIVE* (wasted) effort to try to solve this problem
via modifying our packaging script.  please RTF previous email of mine for
details.  i will *NOT* accept patches that attempt to do this.  "won't fix"
on sight...

so, of all the many ways i've asked for help on project*, please do not try
to "help" by working on such a patch. ;)

also, given how much time and energy i've spent on the care and feeding of
our CVS repositories, i wish i was at least being taken seriously enough
that people read what i'm saying about this topic, and respected my views
enough to reply (even if you disagree, at least address the points i'm


No virus found in this incoming message.
Checked by AVG Free Edition. 
Version: 7.5.472 / Virus Database: 269.8.0/819 - Release Date: 5/26/2007
10:47 AM

More information about the development mailing list