Documentation Roadmaps and Community Networking for Developers on Large Projects

• US 20100325613A1
• Filed: 06/18/2009
• Published: 12/23/2010
• Est. Priority Date: 06/18/2009
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Cheung, Lik, Bush, Christopher L.
• Granted Patent: US 8,458,657 B2
• Time in Patent Office: Days
• US Class Current: 717/120
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

A version control system includes a mechanism for a learning roadmap based on information available from a source repository. More particularly, the mechanism generates an easily understandable timeline of a project and a directory of developers based on information available in the version control system that contains the source content of a project. The timeline for the project may be tied to the directory of developers. Under each date in the timeline, a list of developers and their roles and commits may be listed.

Claims

1. A method, in a data processing system, for automating a learning roadmap based on information available from a version control system, the method comprising:

receiving a commit for a project with associated metadata, wherein the metadata comprises contact information for a developer providing the commit;

adding the commit with associated metadata to a content repository for the project;

generating a developer directory based on metadata in the content repository; and

generating a timeline based on metadata in the content repository.

2. The method of claim 1, wherein generating the developer directory comprises:

identifying a developer with a highest number of commits as a primary contact for the project.

3. The method of claim 1, wherein generating a developer directory comprises:

identifying a developer with a highest number of commits having a given commit type as a primary contact for the given commit type.

4. The method of claim 1, wherein generating a developer directory comprises:

identifying a developer with a highest number of commits for a given programming language as a primary contact for the given programming language.

5. The method of claim 1, wherein the timeline provides for a given date range a list of developers and corresponding roles and commits.

6. The method of claim 1, wherein generating the timeline comprises:

generating a custom timeline relating to a given programming language.

7. The method of claim 1, wherein the timeline is linked to the developer directory.

8. The method of claim 1, wherein adding the commit with associated metadata to the content repository comprises:

identifying a primary contact;

routing the commit to the primary contact;

determining whether the primary contact approves the commit; and

responsive to the primary contact approving the commit, adding the commit with associated metadata to the content repository.

9. A computer program product comprising a computer recordable medium having a computer readable program recorded thereon, wherein the computer readable program, when executed on a computing device, causes the computing device to:

receive a commit for a project with associated metadata, wherein the metadata comprises contact information for a developer providing the commit;

add the commit with associated metadata to a content repository for the project;

generate a developer directory based on metadata in the content repository; and

generate a timeline based on metadata in the content repository.

10. The computer program product of claim 9, wherein generating the developer directory comprises:

identifying a developer with a highest number of commits as a primary contact for the project.

11. The computer program product of claim 9, wherein generating a developer directory comprises:

identifying a developer with a highest number of commits having a given commit type as a primary contact for the given commit type.

12. The computer program product of claim 9, wherein generating a developer directory comprises:

identifying a developer with a highest number of commits for a given programming language as a primary contact for the given programming language.

13. The computer program product of claim 9, wherein the timeline provides for a given date range a list of developers and corresponding roles and commits.

14. The computer program product of claim 9, wherein adding the commit with associated metadata to the content repository comprises:

identifying a primary contact;

routing the commit to the primary contact;

determining whether the primary contact approves the commit; and

responsive to the primary contact approving the commit, adding the commit with associated metadata to the content repository.

15. An apparatus, comprising:

a processor; and

a memory coupled to the processor, wherein the memory comprises instructions which, when executed by the processor, cause the processor to;

receive a commit for a project with associated metadata, wherein the metadata comprises contact information for a developer providing the commit;

add the commit with associated metadata to a content repository for the project;

generate a developer directory based on metadata in the content repository; and

generate a timeline based on metadata in the source repository.

16. The apparatus of claim 15, wherein generating the developer directory comprises:

identifying a developer with a highest number of commits as a primary contact for the project.

17. The apparatus of claim 15, wherein generating a developer directory comprises:

identifying a developer with a highest number of commits having a given commit type as a primary contact for the given commit type.

18. The apparatus of claim 15, wherein generating a developer directory comprises:

identifying a developer with a highest number of commits for a given programming language as a primary contact for the given programming language.

19. The apparatus of claim 15, wherein the timeline provides for a given date range a list of developers and corresponding roles and commits.

20. The apparatus of claim 15, wherein adding the commit with associated metadata to the content repository comprises:

identifying a primary contact;

routing the commit to the primary contact;

determining whether the primary contact approves the commit; and

responsive to the primary contact approving the commit, adding the commit with associated metadata to the content repository.