Enable Metrics and Version Control API modules to show lines of code changed

[GoogleCodeExporter]

Changes in the code base can show whether or not a module is being
maintained, or if it is receiving a lot of development and is perhaps unstable.

The following steps will enable typical site admins to see how many lines
of code have changed in a module

    *

      The Version Control API currently records the number of lines changed
in each commit of code.  This information is in the database but not
available via the API.  The first task is to add code to this module so
that other modules can get information about.
          o Design the function signature.  What information will the
function need to return the data?  Can some of the variables be optional? 
If they are optional, what should the function do when they are excluded?
          o Write a query that will use the data in the function to find
the information in the database and return it.  Be sure to use the Drupal
Database API so that your queries will be secure.
          o Consider what kind of return value makes sense for this
function.  An array?  A single number? 
    * Review the Metrics module's system for adding measurements and add
code that integrates the function you created in the first part of the task
into the Metrics module
    * Provide patches for both of these changes to the issue queue for each
module

The final deliverable is a pair of patches to the Metrics and Version
Control API modules that exposes the information in an API and includes
that information into the Metrics module

Resources:

    * Version Control API http://drupal.org/project/versioncontrol
    * Project Metrics Module http://drupal.org/project/metrics
    * Database Interaction page in the Secure Code handbook
http://drupal.org/node/101496 

Estimated time:

  3 days

Original issue reported on code.google.com by webchick...@gmail.com on 19 Nov 2007 at 8:08

[GoogleCodeExporter]

I claim this task.

Original comment by cor...@gmail.com on 30 Nov 2007 at 9:24

[GoogleCodeExporter]

Oooo, nice! :) Go, corsix!

Original comment by webchick...@gmail.com on 30 Nov 2007 at 3:21

• Changed state: Claimed
• Added labels: ClaimedBy-corsix

[GoogleCodeExporter]

Great, corsix.  If you have any questions or problems feel free to post them 
here
and/or contact me http://drupal.org/user/36762/contact

Original comment by greg.kna...@gmail.com on 30 Nov 2007 at 3:42

[GoogleCodeExporter]

I'm hereby unclaiming this task. Once I get versioncontrol, versioncontrol_cvs 
and
CVS installed and co-operating, I will reclaim, if nobody else has claimed by 
then.

Original comment by cor...@gmail.com on 1 Dec 2007 at 6:50

[GoogleCodeExporter]

OK, thanks for letting us know. Re-opening.

Original comment by addi.be...@gmail.com on 1 Dec 2007 at 7:00

• Changed state: Open
• Removed labels: ClaimedBy-corsix

[GoogleCodeExporter]

That seems reasonable.  I'm working on getting those tables for whomever does 
work on
this task.

Part of the task here is to design the API.  Perhaps you could work on that part
prior to getting the tables?  There is a lot of work in designing a good API 
and the
part that actually queries the table could be commented out until we know the 
exact
structure/substance of the data.

Original comment by greg.kna...@gmail.com on 1 Dec 2007 at 9:36

[GoogleCodeExporter]

Personally, I like to see what data _could_ be exposed by the API, and how 
things fit
together before thinking about the API itself.

A set of tables with the data already in them is alot easier than fighting CVS 
:)

Original comment by cor...@gmail.com on 1 Dec 2007 at 10:45

[GoogleCodeExporter]

I guess we continue here http://drupal.org/node/197212

Original comment by greg.kna...@gmail.com on 5 Dec 2007 at 7:30

[GoogleCodeExporter]

Ok, got a copy of versioncontrol(_cvs) tables with data in them, and therefore:

I claim this task.

Original comment by cor...@gmail.com on 7 Dec 2007 at 2:44

[GoogleCodeExporter]

Ok Corsix, the task is yours.  Please use the Drupal issue at
http://drupal.org/node/197212 to communicate your progress.

Original comment by acli...@gmail.com on 7 Dec 2007 at 2:52

• Changed state: Claimed
• Added labels: ClaimedBy-corsix, DrupalIssue-197212

[GoogleCodeExporter]

Original comment by webchick...@gmail.com on 8 Dec 2007 at 5:06

• Added labels: DueDate-2007-12-14

[GoogleCodeExporter]

Patches have been marked RTBC

Original comment by cor...@gmail.com on 10 Dec 2007 at 10:58

[GoogleCodeExporter]

jpetso marked this as RTBC at http://drupal.org/node/197212, so I'm setting this
issue as closed.  Great job.  Keep up the good work!

Original comment by acli...@gmail.com on 10 Dec 2007 at 11:11

• Changed state: Closed
• Removed labels: DueDate-2007-12-14

[GoogleCodeExporter]

Mirroring final patches here, as per section 12 of the rules ("All Entries 
(code and
otherwise) must be submitted and published on the Project Hosting site as 
specified
in Section 6, a publicly accessible location on the Google Code site.")

Original comment by cor...@gmail.com on 11 Dec 2007 at 11:10

Attachments:

• ghop30_versioncontrol_3.patch
• ghop30_versioncontrol_cvs_3.patch
• ghop30_versioncontrol_project_3.patch

[GoogleCodeExporter]

Original comment by acli...@gmail.com on 21 Jan 2008 at 3:55

• Added labels: AdminChecked