Closed (fixed)
Project:
Drupal.org CVS applications
Component:
new project application
Priority:
Normal
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
15 Aug 2010 at 22:56 UTC
Updated:
30 Dec 2018 at 09:12 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
mdorman commentedComment #2
avpadernoHello, and thanks for applying for a CVS account. I am adding the review tags, and some volunteers will review the code, pointing out what it needs to be changed.
As per requirements, the motivation message should be expanded to contain more features of the proposed project. For themes, it should include also a screenshot of the theme, and (when possible) a link to a working demo site using the proposed theme; for modules, it should include also a comparison with the existing solutions.
Comment #3
mdorman commentedModule Description:
This module allows for multiple site owners to utilize a domain and CDN for all core JavaScript files. By serving these shared files from a single domain and CDN end users will gain significant caching as they go from one Drupal site to another. In addition, the shared domain will serve the files from a CDN to geographically locate the responses from
a server nearby.
As an example rather than serving the /misc/jquery.js file from your local server, or even a private CDN domain after installing this module you're file will be served from:
http://ajax.googleapis.com/ajax/libs/jquery/1.2.6/jquery.min.js
Other core files, that are specific to Drupal will be available based on your version of Drupal which is determined by the module. For example the /misc/drupal.js file will now be served here if you were using version 6.17:
http://j.cmscdn.com/drupal/6.17/misc/drupal.js
This module is not a replacement for the http://drupal.org/project/cdn module, however can work along side that one if you feel it is necessary.
Comment #4
avpadernoThank you for your reply.
Comment #5
mdorman commentedI'm uploading an updated module based on feedback I've seen in other module submissions. This version is a fully functional version with the correct domain and works with 6.16, 6.17, 6.18. I will include all other 6.X versions before final release.
Looking forward to the feedback.
-Matt
Comment #6
mdorman commentedI wanted to add a little more background to this issue to see if I can get some feedback of whether or not this module has potential to get approved. I'd like to continue development on porting this to D7 and possibly even D5, but without a project page with an issue list it's hard to get the necessary testing done.
This module will make performance issues relating to aggregation far less important as it pulls all core JS, and eventually CSS out of local aggregation and allows them to be served externally. Here are the related D7 issues:
http://drupal.org/node/769226
http://drupal.org/node/630100
http://drupal.org/node/721400
http://drupal.org/node/101227
Comment #7
meba commentedFrom security point, there is nothing wrong with the module. From usability point, I don't really see a point of it. It redirects your misc/*.js files to j.cmscdn.net without any possibility to change that domain. What happens when module author decides not to run this domain anymore? Sites will be broken.
Comment #8
mdorman commentedVery valid point about if j.cmscdn.net goes away, your site goes down. However, the same can be said for any other module that connects you to a service. The goal of this module is to allow less technical site owners and those hosting in shared environments to have the benefits of serving Core files from an external CDN to gain end user and server performance gains.
That being said, having manual as well as automated fail overs back to local is a good recommendation. The support of the free service will later be supplemented by paid services for more specialized/unique caching requirements.
I hope this alleviates some of your concerns, this will also be listed on the project page as a note.
Comment #9
mdorman commentedUploading the latest version of the module, which adds the following:
One known issue is an incompatibility with jquery_update.
Comment #10
avpadernoWhen a hook is not necessary, it should not be declared.
Hook implementation comments should be like the following one:
Thank you for your contribution! I am going to update your account.
These are some recommended readings to help with excellent maintainership:
You can find more contributors chatting on the IRC #drupal-contribute channel. So, come hang out and stay involved.
Thank you, also, for your patience with the review process.
Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
I thank all the dedicated reviewers as well.
Comment #13
avpadernoComment #14
avpaderno