changes to contrib repository?
Has there been some change to the contributions repository? I tried to commit some changes to a module iIm developing and I got the following error message: ** Access denied: pwolanin does not have permission to commit files in: ** contributions/sandbox/pwolanin/chemical ** Please contact the owner of this project and request to be added ** as a CVS maintainer, see http://drupal.org/node/63634. running "cvs login" and supplying my password again made no difference., nor di checkout out a new copy. -Peter
Peter Wolanin wrote:
Has there been some change to the contributions repository? I tried to commit some changes to a module iIm developing and I got the following error message:
** Access denied: pwolanin does not have permission to commit files in: ** contributions/sandbox/pwolanin/chemical
Yeah, there has been a change wrt sandboxes. Sandboxes were intended to allow for the development of core patches, but usually got used for a lot of different stuff. That's why as of now people need to apply for a sandbox. Hope somebody can explain this better. :p Cheers, Gerhard
Yeah, there has been a change wrt sandboxes.
Sandboxes were intended to allow for the development of core patches, but usually got used for a lot of different stuff. That's why as of now people need to apply for a sandbox.
And when I said this is a stupid rule because sandboxes are good for example alpha quality stuff or whatever useful code that's just pushed out in the name of sharing I got two answers: a) create and host your own repository, it's not hard. -- I would rather not even comment this one, I have no polite answer to this one. b) maybe we need to have a forge-like something -- yes we still need. Example. I had written a module which let people to tag users. I never had the time to really maintain it but several months later someone found it, ported it to 4.7... I have --and I think was not alone-- learned how to write node access modules from JonBon's primitve modules which were never intended to be released. I am working with Robert Douglass on memcached sessions and both of us has his memcached code in his sandbox. What will come out of this work is not yet clear but it's crystal clear that without a place to share, our work would be hindered. What about this rule: "sandboxes are to be used for code that benefits the Drupal community"? Regards, NK
I really couldn't agree more, and was quite unhappy with the discussion the last time around. I think the sandbox should be a sandbox. A place to play with Drupal code. Nobody likes being told how to play in their sandbox. -Robert Karoly Negyesi wrote:
Yeah, there has been a change wrt sandboxes.
Sandboxes were intended to allow for the development of core patches, but usually got used for a lot of different stuff. That's why as of now people need to apply for a sandbox.
And when I said this is a stupid rule because sandboxes are good for example alpha quality stuff or whatever useful code that's just pushed out in the name of sharing I got two answers:
a) create and host your own repository, it's not hard. -- I would rather not even comment this one, I have no polite answer to this one. b) maybe we need to have a forge-like something -- yes we still need.
Example. I had written a module which let people to tag users. I never had the time to really maintain it but several months later someone found it, ported it to 4.7... I have --and I think was not alone-- learned how to write node access modules from JonBon's primitve modules which were never intended to be released. I am working with Robert Douglass on memcached sessions and both of us has his memcached code in his sandbox. What will come out of this work is not yet clear but it's crystal clear that without a place to share, our work would be hindered.
What about this rule: "sandboxes are to be used for code that benefits the Drupal community"?
Regards,
NK
Quoting Karoly Negyesi <karoly@negyesi.net>:
Yeah, there has been a change wrt sandboxes.
Sandboxes were intended to allow for the development of core patches, but usually got used for a lot of different stuff. That's why as of now people need to apply for a sandbox.
I am coming into this conversation late because I'm new to the list so I am trying to understand the issues. I can foresee that if every maintainer were allowed to create whatever package in the sandbox that a resource issue could quickly ensue. Is this the reason for the decision for "people need to apply for a sandbox"? Disallowing new creations would be a good control but if maintainers already had code in their previously allowed sandbox I would think a grandfathering technique for the existing modules would be good to prevent this kind of grief.
And when I said this is a stupid rule because sandboxes are good for example alpha quality stuff or whatever useful code that's just pushed out in the name of sharing I got two answers:
Not necessarily stupid just not convenient for those already using the sandbox. If resource issues are present or close to being present then this decision makes sense. If it was a matter of I own the ball so you play by my changed rules or I take the ball and go home then I'll need to think about my proactiveness in using and promoting Drupal. Drupal is one of the better CMS packages I have found and I've been looking for a long time. I dislike seeing this political issue as the first item I receive from joining the list.
a) create and host your own repository, it's not hard. -- I would rather not even comment this one, I have no polite answer to this one.
I will take the liberty to comment. If Drupal is having resource issues perhaps we should take a look at what we need to do to help Drupal to have more resources. I don't see anywhere that Drupal is backed by some institution so where are resources coming from? Again, the response to "create and host your own repository, it's not hard" sounds as if Drupal is having resource issues. Based on other projects I think the contribution maintainers have been pretty lucky to have had this type of service anyway.
b) maybe we need to have a forge-like something -- yes we still need.
There are many and we probably don't need another one besides where is the funding coming from? If the Drupal Community leads supported this then I'm all for it. One of the things I see happening is the naming and categorization of modules. There are already conflicting modules existing which may be a good thing in some eyes but if some unknowing user installs and activates both then what happens to his system? I think that more control of contributed modules supported and distributed by Drupal is needed. I don't think that everyone with access to CVS should be allowed to create whatever module they need. A module application process would be good with a review of the description of the module and if the module is similar to some other module already existing that requestors be pointed to the existing module and asked to cooperate with the current maintainers to extend it.
Example. I had written a module which let people to tag users. I never had the time to really maintain it but several months later someone found it, ported it to 4.7... I have --and I think was not alone--
Great, so how did this person port it to 4.7? Certainly this person didn't have access to write to the CVS. Did he not just submit a patch?
learned how to write node access modules from JonBon's primitve modules which were never intended to be released. I am
I am still learning how to write Drupal code but I've submitted already many patches for 5.0 to various modules. I've never seen JonBon's primitive modules but I haven't yet started creating new things. I'm more interested in what already exists. There are nearly a hundred modules.
working with Robert Douglass on memcached sessions and both of us has his memcached code in his sandbox. What will come out of this work is not yet clear but it's crystal clear that without a place to share, our work would be hindered.
But if Robert Douglass didn't have a sandbox on Drupal's CVS don't you think you could have come up with some method to share the code? SF hands out project access to many would be project requests and you could use their CVS or SVN services. You could even install Drupal as the web CMS interface for your module. Now don't get me wrong, I'm just suggesting an alternative to the if you had to do it differently scenario. I do like the fact that Drupal acts much like a pulled together community and every thing is in one place including the development sandbox.
What about this rule: "sandboxes are to be used for code that benefits the Drupal community"?
Sounds good. So I guess I need to apply for sandbox access; perhaps you can to. What is the URI for the form to apply? Earnie http://for-my-kids.com -- -- ****************************************************************************** * The user of this server has agreed to allow the use of a trailer in the * * mail that he sends for advertising purposes. This advertisment is added * * by the server and is not in the control of the user of our services. * ****************************************************************************** Toshiba Satellite P105-S6114 Notebook http://give-me-an-offer.com/offers/computers/laptop/toshiba PlayStation 3 Auctions http://give-me-an-offer.com/offers/auctions/au1 Samsung HP-S4253 42" High Definition Plasma TV http://give-me-an-offer.com/offers/tv/plasma
Earnie Boyd wrote:
I will take the liberty to comment. If Drupal is having resource issues perhaps we should take a look at what we need to do to help Drupal to have more resources.
This is not about resources. This is about proper use of allocated resources. Take a tour of the sandboxes and look at which code will comply with the usage rules. It is only a small part of it. Even my sandbox does not fully comply, I think.
-- ******************************************************************************
* The user of this server has agreed to allow the use of a trailer in the * * mail that he sends for advertising purposes. This advertisment is added * * by the server and is not in the control of the user of our services. * ******************************************************************************
Can you pretty please use another mail provider? We won't tolerate the use of our mail archive as somebody else's advertising resource. Cheers, Gerhard
Quoting Gerhard Killesreiter <gerhard@killesreiter.de>:
Earnie Boyd wrote:
I will take the liberty to comment. If Drupal is having resource issues perhaps we should take a look at what we need to do to help Drupal to have more resources.
This is not about resources. This is about proper use of allocated resources. Take a tour of the sandboxes and look at which code will comply with the usage rules. It is only a small part of it. Even my sandbox does not fully comply, I think.
I'm all for enforcing rules.
-- ****************************************************************************** * The user of this server has agreed to allow the use of a trailer in the * * mail that he sends for advertising purposes. This advertisment is added * * by the server and is not in the control of the user of our services. * ******************************************************************************
Can you pretty please use another mail provider? We won't tolerate the use of our mail archive as somebody else's advertising resource.
Like what yahoo.com or or google's gmail? Just trying to make a buck or two. At least the server is using Drupal. :) Earnie http://give-me-an-offer.com P.S.: For this mail the trailer is missing. It doesn't mean that I won't add it back in for future mail. I use IMP for many identities. Unfortunately I can't control the trailer per identity.
Earnie Boyd wrote:
Quoting Gerhard Killesreiter <gerhard@killesreiter.de>:
Earnie Boyd wrote:
I will take the liberty to comment. If Drupal is having resource issues perhaps we should take a look at what we need to do to help Drupal to have more resources.
This is not about resources. This is about proper use of allocated resources. Take a tour of the sandboxes and look at which code will comply with the usage rules. It is only a small part of it. Even my sandbox does not fully comply, I think.
I'm all for enforcing rules.
-- ****************************************************************************** * The user of this server has agreed to allow the use of a trailer in the * * mail that he sends for advertising purposes. This advertisment is added * * by the server and is not in the control of the user of our services. * ******************************************************************************
Can you pretty please use another mail provider? We won't tolerate the use of our mail archive as somebody else's advertising resource.
Like what yahoo.com or or google's gmail? Just trying to make a buck or two. At least the server is using Drupal. :)
Earnie http://give-me-an-offer.com
P.S.: For this mail the trailer is missing. It doesn't mean that I won't add it back in for future mail. I use IMP for many identities. Unfortunately I can't control the trailer per identity.
Your posts will be moderated untill you fix your attitude. Cheers, Gerhard
"Gerhard Killesreiter" wrote:
P.S.: For this mail the trailer is missing. It doesn't mean that I won't add it back in for future mail. I use IMP for many identities. Unfortunately I can't control the trailer per identity.
Your posts will be moderated untill you fix your attitude.
Swift. Firm. Decisive. Excellent. -- inkfree press
Gerhard wrote:
Can you pretty please use another mail provider? We won't tolerate the use of our mail archive as somebody else's advertising resource.
Cheers to Gerhard for pointing this out. It is the viral quality of this kind of "free email" that makes it so insidious. "Earnie Boyd" wrote:
Like what yahoo.com or or google's gmail? Just trying to make a buck or two.
Yeah, and I think the point Gerhard was making is exactly this: You're continuing to use other people's resources to make your "buck or two". Also, your comment totally belies your little "disclaimer" which suggests that you can _not_ control this advertising placement. The fact is, you _can_ control it -- you can use a real email service and stop trying to make your buck or two on other people's resources. It is not hard to calculate how many extra bytes of data you require other people to use just to read your little "buck or two" ads. Every time a person downloads email, they must also then pay to download your ad. You make money by causing other people to spend it. You really should use your money-sucking email for your business email and NOT use it for your private email. This way, you can cause your customers, clients and others to spend their money to continually download your ads, but you won't subject your anonymous 'friends' to this surcharge.
At least the server is using Drupal. :)
Is that supposed to be some kind of appeal to let you continue polluting the Drupal storage space (email is stored) with your ads? Is the cute little smiley supposed to blind us all to the real costs that you cause others to incur, just so you can make "a buck or two"? It does not assuage the real concern...nor does it eliminate the real cost. Perhaps we should start charging you to read your email? Or, perhaps the Drupal project could bill you for the storage bytes used by your extra crappy ads? -- inkfree press
participants (6)
-
Earnie Boyd -
Gerhard Killesreiter -
inkfree press -
Karoly Negyesi -
Peter Wolanin -
Robert Douglass