plugin_manager

Project information

Project page on drupal.org: http://drupal.org/project/plugin_manager

Current status: Working on the backend functions while trying to figure out the best way to implement a repository of sorts.

Description

PluginManager is designed to retrieving a list of all modules and themes available for the version of Drupal in use in a setup. It then allows the administrator to automatically retrieve and install the modules and themes they desire.

Project schedule

May 26th: Start the project.
July 21th: Attempt to move focus to bug hunting.

Status updates

2008-05-27

Task summary: Posted mock screenshots to usability group for feedback (What did you get done this week?). Work on the backend functions required by the module (What's your plan for next week?).
Difficulties encountered (if any):
* None

2008-06-03

Task summary: I got feedback on the prototype screenshots and worked on the back end, successfully downloading and extracting a file from drupal.org using the engine. (What did you get done this week?). Work on the local uploader. (What's your plan for next week?).
Difficulties encountered (if any):
* None

Change Log:

• Committed file downloader (anon ftp only)
• Committed file extractor (requires tar)

2008-06-10

Task summary: I've been working on the basics for a repository index by extending the project module. (What did you get done this week?). I don't expect to get any work done this week. During the summer I have a total of one obligation: to direct Vacation Bible School at my church. That is this week, so I will hardly find time to check my email. After this I do not forsee having any slowdowns during the summer (What's your plan for next week?).

Difficulties encountered (if any):
* VBS Preperation
* Deciding whether to extend the functionality of http://updates.drupal.org/release-history/project-list/all or to add a new listing that contains all of the needed information.
Perhaps this issue can help? ~~greggles

Change Log:

*No commit at the moment. Working on a proper patch for the project module.

2008-06-17

Task summary: I was the director at my church's VBS this week. Thus, I was unable to spend any time on anything else. (What did you get done this week?). The plan for this next week is make the module use ftp to install the extracted files to their appropriate directories. (What's your plan for next week?).

Difficulties encountered (if any):

Change Log:

2008-06-24

Task summary: I changed the ftp code to use the php stream wrappers I also created the beginnings of a repository system of sorts. (What did you get done this week?). Install a theme using the system (downloading, unpacking and installation,) That and maybe sort modules by category. (What's your plan for next week?).

Difficulties encountered (if any):
This next week I expect to run into a little difficulty with repositories. There is (to the best of my knowledge) no location that holds dependencies, descriptions or screenshot urls for modules at d.o.

Change Log:
Added a repository system.
Added a listing of installable themes.
Changed the downloader to user streams.

2008-07-01

Task summary: I made file extraction to fall back on PEAR's Archive/Tar if the tar binary is unavailable. I almost finished getting manual installs to work. (What did you get done this week?). Finish making the system install a specified file. Clean up the install page.. (What's your plan for next week?).

Difficulties encountered (if any):
None

Change Log:
Made the system more compatible with Windows.
Setup most of manual installs.

2008-07-08

Task summary: The module is now able to install themes automatically. (What did you get done this week?). Allow for modules to be installed using the same method. (What's your plan for next week?).

Difficulties encountered (if any):
None

Change Log:
Removed the manual page.
Added a multistep form for installs.
Made installs work for themes.

2008-07-15

Task summary: Changed a little bit of the database design. (What did you get done this week?). Allow for modules to be installed using the same method. (What's your plan for next week?).

Difficulties encountered (if any):
None

Change Log:
Changed the database design a little.

2008-07-22

Task summary: Preparing for a test so that I can actually graduate. (What did you get done this week?). Fix issues present in the issue queue. (What's your plan for next week?).

Difficulties encountered (if any):
None

Change Log:
None

2008-07-29

Task summary: Rewrote the several sections of the code, allowing for multiple backends to be used to install the plugins, as well as the ability to retrieve plugins from sites other than d.o (What did you get done this week?). Fix ftp and ssh backends to work again after the other changes (What's your plan for next week?).

Difficulties encountered (if any):
None

Change Log:
Moved code to ftp.backend.
Added ssh.backend.
Broke install page (haven't been able to update it to use backends yet.)
Removed rule that downloads must be from d.o.

2008-08-05

Task summary: Fixed several problems with the ftp backend. Passed (I believe) my combinatorics final. (What did you get done this week?). Graduate. Oh, and have a working version of the plugin manager. (What's your plan for next week?).

Difficulties encountered (if any):
None

Change Log:
Fixed bugs in ftp.backend.

Todo:

• Internal file transfer system. (ftp, and possibly sftp and scp).
• File validation.
• Retrieve package list from drupal.org
• External file transfer system
• Prepare mock screenshots.

Deliverables

1. Be able to download themes and modules for a specified version of Drupal from drupal.org.
2. Be able to extract and upload the selected files to their appropriate directories.
3. Add to the Project module so that the system can verify the validity of the downloads against their appropriate MD5sums.