Closed (won't fix)
Project:
Drupal.org CVS applications
Component:
new project application
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
5 Sep 2010 at 09:37 UTC
Updated:
31 Mar 2019 at 14:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
avpadernoComment #2
hymanroth commentedThanks for refusing my CVS account request.
Assuming you're interested, here's the module I wanted to share http://github.com/hymanroth/Path-Lockdown
Comment #3
hymanroth commentedComment #4
avpadernoHello, and thanks for applying for a CVS account.
Unfortunately, you didn't do what reported in http://drupal.org/cvs-application/requirements, which is the page where you found the link to apply for a CVS account; you didn't also followed what reported in the form where you entered the motivation of your application, which states:
The following message should have been shown to you:
Comment #5
hymanroth commentedI wrote a small and simple module which I find very useful. I wanted to give something back to the community by sharing it. That is all.
It says on drupal.org "Contributors are strongly encouraged to host at drupal.org rather than elsewhere (GitHub, BitBucket, your personal site, etc.)"
That is all I am trying to do.
If you had clicked on the link I supplied you would have read:
Why make it so difficult for people who want to give something back to the community?
Comment #6
jsr47 commentedNo one is making it difficult - just read the instructions provided, and follow them. There are lots of modules and themes to review by a team of volunteers - having a process makes things run more smoothly.
sorry, I should never do anything in the morning before coffee...
Comment #7
hymanroth commentedYou're right about the coffee.
Comment #8
avpadernoThe archive containing the proposed module has not been attached in a comment here.
Comment #9
hymanroth commentedArchive attached
Comment #10
jsr47 commentedDon't forget to reset the 'needs review' status when you make a change!
Comment #11
svendecabooterComments after browsing through the code a bit:
Comment #12
hymanroth commentedThanks for your comments svendecabooter.
I wrote the module for my own personal use, but since I find it really useful I thought I would share it.
It's very 'quick and dirty' - but it does do what it says on the tin.
I don't know if you've had the chance to run the module on an actual Drupal installation, but some of the results can be very revealing.
For example, ctools has three paths which are open to authenticated users: '/test', '/test2' and '/test3'.
This type of information could be useful to the security team.
I will fix up the comments and the func / var names in the next few days.
However, I don't have time to incorporate the settings UI or theme functionality you suggested.
The module is intended purely for developers, and so, while UI settings would be useful, they're probably not essential.
And since you can customize the output format from the settings file, there is no real need to go through theme().
I hope these two last issues are not deal breakers because that would be a pity.
If I had time I would implement all of your suggestions but I am, unfortunately, very, very busy.
Comment #13
avpadernoTheme functions should be used whenever there is HTML output; the use of theme functions don't depend from the presence of a configuration file. What is the vantage of using a theme function?
That is not the kind of reply I would expect from who is applying for a CVS account. If there is no much time to dedicate for a CVS application, then I wonder if there would be enough time to dedicate to the project, when users will report bug reports.
I am changing status as per comment by svendercabooter.
Comment #14
hymanroth commentedI give up. I can't say I didn't try.
Oh, and a quick message for kiamlaluno: pirla.
Comment #15
avpaderno@hymanroth: You should be also brave to say it in English, but I guess you will not do it.
Comment #16
avpaderno