There are two goals of the Eclipse Process Framework Project:
2022-01-26 00:38:09 by administrator, took 12 seconds.| Information 21 |
| Metrics 67 |
| Attributes 17 |
| Recommendations 6 |
| Quality Model |
| Mnemo | Value | |
|---|---|---|
| BZ_URL | https://bugs.eclipse.org/bugs//buglist.cgi?product=EPF | |
| GIT_URL | git://git.eclipse.org/gitroot/epf/org.eclipse.epf.features.git | |
| MLS_USR_CAT_URL | https://api.eclipse.org/forums/category/1 | |
| MLS_USR_DESC | Eclipse Process Framework (EPF) | |
| MLS_USR_NAME | EPF | |
| MLS_USR_URL | https://www.eclipse.org/forums/index.php/f/49/ | |
| PMI_BUGZILLA_COMPONENT | ||
| PMI_BUGZILLA_CREATE_URL | https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EPF | |
| PMI_BUGZILLA_PRODUCT | EPF | |
| PMI_BUGZILLA_QUERY_URL | https://bugs.eclipse.org/bugs/buglist.cgi?product=EPF | |
| PROJECT_DESC | <p>There are two goals of the Eclipse Process Framework Project:</p> <ul><li> To provide an extensible framework and exemplary tools for software process engineering - method and process authoring, library management, configuring and publishing a process.</li> <li> To provide exemplary and extensible process content for a range of software development and management processes supporting iterative, agile, and incremental development, and applicable to a broad set of development platforms and applications</li> </ul><h3> Extensible software process engineering framework</h3> <p>The framework consists of the following two components:</p> <ul><li> Meta-model: Method content and processes will be structured based on a formal meta-model. This meta-model will be documented with a comprehensive meta-model specification using MOF, UML diagrams, as well as an associated XML schema. The initial version of this meta-model has been derived from IBM's Unified Method Architecture (UMA, reference to UMA specification download to be added soon). UMA is an evolution of the current OMG industry standard <a href="http://www.omg.org/docs/formal/05-01-06.pdf">Software Process Engineering Meta-model (SPEM) v1.1</a> integrating concepts from IBM Rational Unified Process, IBM Global Services, and IBM Rational Summit Ascendant. IBM and other OMG partners are working on making UMA, with improvements suggested by partners, to become <a href="http://www.omg.org/cgi-bin/doc?ad/2004-11-4">SPEM 2.0</a>. Two versions of draft specifications have already been submitted to the OMG as of November 2005. The initial exemplary tool implementation for EPF will be based on the <a href="http://www.omg.org/cgi-bin/doc?ad/05-05-06">first draft submission</a>. As SPEM 2.0 stabilizes, it is expected to update the EPF to the final specification. The meta-model will be extensible through the usage of custom attributes and custom process elements as well as normal EMF extensibility mechanisms.</li> <li> Core extensible process tooling framework - Basic functionality and extension point APIs will be provided to allow 1) method authoring, 2) process authoring, 3) library management, and 4) configuring and publishing. Each of these domains is described in more details below, under exemplary tools.</li> </ul><p>An initial implementation of the process engineering framework is offered for contribution by IBM. It will require some modification to be made extensible, following the SPEM 2.0 extensibility mechanisms.</p> <h3> Exemplary tools</h3> <p>The following exemplary tools provide the following capabilities:</p> <ul><li> Method Authoring - Best practices can be captured as a set of reusable method building blocks as defined in the meta-model; roles, work products, tasks, and guidance, such as templates, guidelines, examples, and check lists. Relationships between method elements can be defined through forms. A rich-text editor allows you to document method elements, and graphical views present diagrams showing relevant relationships. Reuse is facilitated by allowing you to create a method element as a derivative of another method element through various inheritance-type of relationships. This allows you to e.g. specify that a Systems Architect has similar responsibilities to a Software Architect by expressing the differences, reusing everything that is common.</li> <li> Process Authoring - Reusable process building blocks can be organized into processes along a lifecycle dimension by defining e.g. Work Breakdown Structures (WBSs), and when in the lifecycle to produce what work products in which state. The tool allows you to construct reusable chunks of processes through so called capability patterns. A capability pattern may for example define how to define, design, implement and test a scenario or a user story, and this pattern can now be reused in a variety of processes. The tool also allows you to define delivery processes, which are end-to-end processes. Structural information can often be edited with graphical as well as non-graphical editors.</li> <li> Library Management and Content Extensibility - An XMI-based library enables persistency and flexible configuration management as well as content interchange for distributed client-server implementations. Method and process content can be packaged into content plug-ins and content packages allowing simple distribution, management and extensibility of content. A plug-in can be produced describing how content in other plug-ins should be extended. As content plug-ins are added to your content library, the tool will resolve dependencies between process elements.</li> <li> Configuring and Publishing - A process configuration can be created by selecting a set of content plug-ins and content packages. Optionally, an exemplary process configuration can be used as a starting point, and content plug-ins and content packages added or removed from this exemplary configuration. As an example, you may start with a generic exemplary process suitable for small collocated teams, and add content plug-ins containing specific guidance for each of Eclipse, JUnit, J2EE, and IBM Rational RequisitePro. The delivery processes associated with a configuration can be further customized. As the configuration is published, the tool resolves the many relationships that may exist between process elements in the selected plug-ins and packages, and generates a set of html pages with links representing relationships between process elements to make the resulting Web site easy to navigate. The resulting Web site is viewable via a web browser, without the need for a Web server. This will allow users on all platforms to view the published process.</li> </ul><p>An initial implementation of these features is offered for contribution by IBM. See proposal artifacts at the end of this proposal. This initial contribution needs to be matured, and refactored to address the added extensibility of the process engineering framework.</p> <h3> Exemplary and extensible process content</h3> <p>Our intention is to enable the ecosystem to build software best practices. Some of these best practices may be contributed to Eclipse as exemplary uses of EPF, while others may be commercial process offerings. A key value proposition with the Process Framework is the ability and intent to support a wide spectrum of development styles to accommodate both established practices as well as new ones as they are introduced. The scope of the open source content will be kept small initially, to enable us to build a stable set of high-quality base content, focusing on core development activities; requirements, analysis & design, implementation, testing, change management, and project management. It is however crucial, that the framework and the base content can be extended to scale to support content covering the entire IT Lifecycle Management domain, including software, systems and product development, business engineering, operations and systems management, governance and portfolio management.</p> <ul><li> IBM is offering for contribution the Basic Unified Process (BUP, a very light weight adaptation of RUP with influences from Scrum. This content exists in draft format, but needs to be completed and evolved based on contributions from other project members. The content may also need to be refactored to enable a broad set of processes to be created from it through content extensions. See <a href="http://www.eclipse.org/proposals/beacon/Basic%20Unified%20Process.pdf">BUP whitepaper</a>and demo of the BUP prototype (BUP.avi). Also see a demo of a variant of Basic Unified Process with Scrum influences (BUP+Scrum.avi). Several other companies such as <a href="http://www.ambysoft.com/">Ambysoft</a>, <a href="http://www.bearingpoint.com/">BearingPoint</a>, <a href="http://www.capgemini.com/">Capgemini</a>, <a href="http://www.covansys.com/">Covansys</a>, <a href="http://www.ivarjacobson.com/">Ivar Jacobson International</a>, <a href="http://www.numbersix.com/">Number Six</a>, and <a href="http://www.ubc.ca/">University of British Columbia</a> will also create other content extensions</li> <li> Other project members, including <a href="http://www.objectmentor.com/">Object Mentor</a>, <a href="http://www.bedarra.com/">Bedarra Research Lab</a>, <a href="http://www.rallydev.com/index.jsp">Rally Software Development</a> and <a href="http://www.ambysoft.com/">Ambysoft </a>will collaborate to contribute a Basic Agile process which covers other key ideas and processes from the Agile Development community, including Agile Modeling, Extreme Programming and Scrum</li> </ul><p>More exemplary and extensible processes will be created as committers express interest and contributions are proposed. See demo of process authoring capabilities in the EPF prototype (Authoring.avi).</p> <h3> Target Users of the Process Framework</h3> <p>For a perspective of how different types of organizations may leverage the Process Framework, see whitepaper titled <a href="http://www.eclipse.org/proposals/beacon/Who%20will%20benefit%20from%20Eclipse%20Process%20Framework.pdf">Who will benefit from Process Framework</a></p> | |
| PROJECT_DOC_URL | http://www.eclipse.org/epf/general/developers_documentation.php | |
| PROJECT_DOWNLOAD_URL | http://www.eclipse.org/epf/downloads/downloads.php | |
| PROJECT_GETTINGSTARTED_URL | http://www.eclipse.org/epf/general/getting_started.php | |
| PROJECT_ID | technology.epf | |
| PROJECT_MAIN_URL | http://www.eclipse.org/epf | |
| PROJECT_MLS_DEV_URL | https://dev.eclipse.org/mailman/listinfo/epf-dev | |
| PROJECT_MLS_USR_URL | http://www.eclipse.org/forums/eclipse.technology.epf | |
| PROJECT_NAME | Eclipse Process Framework Project | |
| PROJECT_PLAN_URL | http://www.eclipse.org/epf/plan/epf_1-5-1-8_project_plan.xml | |
| PROJECT_SCM_URL | https://git.eclipse.org/r/plugins/gitiles/epf/org.eclipse.epf.wiki |
| Name | Mnemo | Description | Value | Indicator |
|---|---|---|---|---|
| Governance documentation | DOC_GOV | Is there a documentation explaining how decisions are made? | 1 | 5 |
| Board transparency | GOV_BOARD_PUBLIC | Are the minutes of the board publicly available? | 1 | 5 |
| ITS Authors | ITS_AUTHORS | Number of different authors who created issues during the lifetime of the project. | 222 | |
| ITS authors last month | ITS_AUTHORS_1M | Number of authors who created issues during last month. If today is 2017-02-01 then the range is from 2017-01-01 to 2017-02-01. | 0 | 1 |
| ITS authors last week | ITS_AUTHORS_1W | Number of authors who created issues during last week. If today is Wed. 2017-02-01 then the range is from Wed. 2017-01-25 to Wed. 2017-02-01. | 0 | |
| ITS authors last year | ITS_AUTHORS_1Y | Number of authors who created issues during last year. If today is 2017-02-01 then the range is from 2016-02-01 to 2017-02-01. | 1 | |
| ITS issues created last month | ITS_CREATED_1M | Number of issues created during last month. If today is 2017-02-01 then the range is from 2017-01-01 to 2017-02-01. | 0 | |
| ITS issues created last week | ITS_CREATED_1W | Number of issues created during last week. If today is Wed. 2017-02-01 then the range is from Wed. 2017-01-25 to Wed. 2017-02-01. | 0 | |
| ITS issues created last year | ITS_CREATED_1Y | Number of issues created during last year. If today is 2017-02-01 then the range is from 2016-02-01 to 2017-02-01. | 1 | |
| ITS diversity ratio | ITS_DIVERSITY_RATIO_1Y | The ration of bugs divided by the number of submitters, over a period of one year. | 1 | 1 |
| ITS Total issues | ITS_ISSUES_ALL | Number of issues registered in the database, whatever their state is. | 3220 | |
| ITS Open issues | ITS_OPEN | Number of issues with a state 'open' at the time of analysis. | 328 | |
| ITS Old open issues | ITS_OPEN_OLD | Number of dead issues, i.e. issues that are in state open and have not been updated for a long time (one year). | 0 | |
| ITS Open issues (%) | ITS_OPEN_PERCENT | Percentage of open issues compared to the overall number of issues registered in the system. | 10 | |
| ITS Pending issues | ITS_OPEN_UNASSIGNED | Number of issues in state open with no assignee (i.e. pending). | 0 | |
| ITS issues updated last month | ITS_UPDATED_1M | Number of issues updated during last month. If today is 2017-02-01 then the range is from 2017-01-01 to 2017-02-01. | 0 | 1 |
| ITS issues updated last week | ITS_UPDATED_1W | Number of issues updated during last week. If today is Wed. 2017-02-01 then the range is from Wed. 2017-01-25 to Wed. 2017-02-01. | 0 | |
| ITS issues updated last year | ITS_UPDATED_1Y | Number of issues updated during last year. If today is 2017-02-01 then the range is from 2016-02-01 to 2017-02-01. | 1 | |
| User ML Authors | MLS_USR_AUTHORS | The total number of different identities found in the User mailing list. | 347 | |
| User ML Authors one month | MLS_USR_AUTHORS_1M | The total number of different identities found in the User mailing list during last month. | 0 | 1 |
| User ML Authors one week | MLS_USR_AUTHORS_1W | The total number of different identities found in the User mailing list during last week. | 0 | |
| User ML Authors one year | MLS_USR_AUTHORS_1Y | The total number of different identities found in the User mailing list during last year. | 2 | |
| User ML diversity ratio | MLS_USR_DIVERSITY_RATIO_1Y | The ration of posts divided by the number of authors, over a period of one year. | 2 | 2 |
| User ML Posts | MLS_USR_POSTS | The total number of posts found in the User mailing list. | 1187 | |
| User ML Posts one month | MLS_USR_POSTS_1M | The total number of posts found in the User mailing list during last month. | 0 | 1 |
| User ML Posts one week | MLS_USR_POSTS_1W | The total number of posts found in the User mailing list during last week. | 0 | |
| User ML Posts one year | MLS_USR_POSTS_1Y | The total number of posts found in the User mailing list during last year. | 5 | |
| User ML Threads | MLS_USR_THREADS | The total number of threads (one question followed by zero or more answers) found in the User mailing list. | 1187 | |
| User ML Threads one month | MLS_USR_THREADS_1M | The total number of threads (one question followed by zero or more answers) found in the User mailing list during last month. | 0 | 1 |
| User ML Threads one week | MLS_USR_THREADS_1W | The total number of threads (one question followed by zero or more answers) found in the User mailing list during last week. | 0 | |
| User ML Threads one year | MLS_USR_THREADS_1Y | The total number of threads (one question followed by zero or more answers) found in the User mailing list during last year. | 1 | |
| Dependency check | OSS_DEP_CHECK | Analysis of dependencies to identify old, vulnerable dependencies, as provided by tools like dependency-check or JFrog/Nexus. | 1 | 5 |
| Escalation procedure | OSS_ESCALATE | Is there an easy and visible way for anybody to report toxic behaviour or unfair practices? | 1 | 5 |
| Inclusion initiative | OSS_INCLUSION | Is there a formal procedure to help people join and benefit from the community, whoever they are? | 1 | 5 |
| Access information | PROJECT_ACCESS_INFO | Is the access info (downloads, update sites..) correctly filled in the PMI records? | 1 | 3 |
| CI access | PROJECT_CI_ACCESS | Is the continuous integration info correctly filled in the PMI records? | 0 | 4 |
| CI information | PROJECT_CI_INFO | Is the continuous integration info correctly filled in the PMI records? | 0 | 4 |
| DL access | PROJECT_DL_ACCESS | Is the access info (downloads, update sites..) correctly filled in the PMI records? | 1 | 5 |
| DL information | PROJECT_DL_INFO | Is the access info (downloads, update sites..) correctly filled in the PMI records? | 1 | 5 |
| Doc access | PROJECT_DOC_ACCESS | Is the documentation info correctly filled in the PMI records? | 1 | 5 |
| Docs information | PROJECT_DOC_INFO | Is the documentation info correctly filled in the PMI records? | 4 | 5 |
| Getting started | PROJECT_GETTINGSTARTED_INFO | Is the documentation info correctly filled in the PMI records? | 1 | 5 |
| ITS access | PROJECT_ITS_ACCESS | Is the bugzilla info correctly filled in the PMI records? | 0 | 4 |
| ITS information | PROJECT_ITS_INFO | Is the bugzilla info correctly filled in the PMI records? | 5 | 5 |
| MLS access | PROJECT_MLS_ACCESS | Is the communication channel for the team info correctly filled in the PMI records? | 1 | 5 |
| MLS information | PROJECT_MLS_INFO | Is the communication channel for the team info correctly filled in the PMI records? | 1 | 4 |
| Number of releases | PROJECT_REL_VOL | The number of releases recorded in the PMI. | 5 | 4 |
| SCM access | PROJECT_SCM_ACCESS | Is the source_repo info correctly filled in the PMI records? | 1 | 5 |
| SCM information | PROJECT_SCM_INFO | Is the source_repo info correctly filled in the PMI records? | 1 | 4 |
| SCM authors | SCM_AUTHORS | Total number of identities found as authors of commits in source code management repository. | 5 | |
| SCM authors one month | SCM_AUTHORS_1M | Total number of identities found as authors of commits in source code management repositories dated during the last month. | 0 | 1 |
| SCM authors one week | SCM_AUTHORS_1W | Total number of identities found as authors of commits in source code management repositories dated during the last week. | 0 | |
| SCM authors one year | SCM_AUTHORS_1Y | Total number of identities found as authors of commits in source code management repositories dated during the last year. | 0 | |
| SCM Branches | SCM_BRANCHES | Number of branches as returned by `git branch --all`. | 13 | |
| SCM Commits | SCM_COMMITS | Total number of commits in source code management repositories. | 29 | |
| SCM Commits one month | SCM_COMMITS_1M | Total number of commits in source code management repositories dated during the last month. | 0 | 1 |
| SCM Commits one week | SCM_COMMITS_1W | Total number of commits in source code management repositories dated during the last week. | 0 | |
| SCM Commits one year | SCM_COMMITS_1Y | Total number of commits in source code management repositories dated during the last year. | 0 | |
| SCM committers | SCM_COMMITTERS | Total number of identities found as committers of commits in source code management repository. | 5 | |
| SCM committers one month | SCM_COMMITTERS_1M | Total number of identities found as committers of commits in source code management repositories dated during the last month. | 0 | |
| SCM committers one week | SCM_COMMITTERS_1W | Total number of identities found as committers of commits in source code management repositories dated during the last week. | 0 | |
| SCM committers one year | SCM_COMMITTERS_1Y | Total number of identities found as committers of commits in source code management repositories dated during the last year. | 0 | |
| SCM diversity ratio | SCM_DIVERSITY_RATIO_1Y | The ration of commits divided by the number of authors, over a period of one year. | 0 | 1 |
| SCM Changed Lines | SCM_MOD_LINES | Total number of changed lines (added, removed, changed) in source code management repositories. | 9627 | |
| SCM Changed Lines one month | SCM_MOD_LINES_1M | Total number of changed lines (added, removed, changed) in source code management repositories dated during the last month. | 0 | 1 |
| SCM Changed Lines one week | SCM_MOD_LINES_1W | Total number of changed lines (added, removed, changed) in source code management repositories dated during the last week. | 0 | |
| SCM Changed Lines one year | SCM_MOD_LINES_1Y | Total number of changed lines (added, removed, changed) in source code management repositories dated during the last year. | 0 |
| Name | Mnemo | Description | Value | Confidence |
|---|---|---|---|---|
| Activity | QM_ACTIVITY | The activity of the project's ecosystem, as measured on the mailing lists and configuration management system. | 1.0 | 4 / 5 |
| Collaboration | QM_AGG_COLLAB | Are the required pieces of basic documentation available? | 5.0 | 1 / 4 |
| Decisions | QM_AGG_DECISIONS | How public and open is the project's decision-making process? | 5.0 | 2 / 2 |
| Information | QM_AGG_DOC | Is the project well documented? | 4.5 | 6 / 6 |
| Engagement | QM_AGG_ENGAGEMENT | How the community is invited to participate, and how much is it heard when talking? | 1.3 | 3 / 4 |
| Ethics | QM_AGG_ETHICS | Is the project compliant regarding OSS' ethics? | 5.0 | 2 / 3 |
| Intellectual Property Management | QM_AGG_IP | How is intellectual property handled in the project? Is there an IP log? Are the project and the Eclipse Foundation safe regarding IP? | 5.0 | 1 / 2 |
| Openness | QM_AGG_OPENNESS | Is the project open and transparent? | 4.7 | 6 / 6 |
| OSS Core | QM_AGG_OSS_CORE | The conformance of the project to the core Open-Soure Software principles and good practices. | 4.8 | 15 / 19 |
| Diversity | QM_DIVERSITY | The diversity of the project's ecosystem, as measured on the mailing lists and configuration management system. | 1.0 | 3 / 3 |
| Documentation | QM_DOC | The maturity of code. | 4.2 | 4 / 4 |
| Ecosystem | QM_ECOSYSTEM | The sustainability of the ecosystem evolving around the project. | 1.9 | 15 / 17 |
| Process | QM_PROCESS | The maturity of the process used to run the project. | 3.8 | 9 / 11 |
| Eclipse Maturity | QM_QUALITY | The overall Maturity of the project. | 3.5 | 39 / 47 |
| Build and Release Management | QM_REL_ENG | Does the project apply best practices regarding Build and Release management? | 4.0 | 1 / 2 |
| Configuration Management | QM_SCM | The maturity of the project regarding access and usage of the configuration management system. | 2.0 | 3 / 3 |
| Support | QM_SUPPORT | The amount of knowledge provided when someone asks for support. | 1.0 | 3 / 3 |
| Type | Severity | Description |
|---|---|---|
| PMI_EMPTY_WIKI | High | The wiki URL is missing in the PMI. It helps people understand and use the product and should be filled. |
| PMI_EMPTY_UPDATE | High | The update site URL is empty in the PMI. People need it if they want to use the product, and it should be filled. |
| PMI_EMPTY_CI | High | The Hudson CI engine URL [https://git.eclipse.org/r/plugins/gitiles/epf/org.eclipse.epf.wiki] in the PMI is empty. |
| Plugin | Description | URL |
|---|---|---|
| Bugzilla | bugzilla_components.csv The list of components that have at least one bug registered against them (CSV). |
/projects/technology.epf/Bugzilla/bugzilla_components.csv |
| Bugzilla | bugzilla_evol.csv The evolution of issues created and authors by day (CSV). |
/projects/technology.epf/Bugzilla/bugzilla_evol.csv |
| Bugzilla | bugzilla_issues.csv The list of issues, with fields 'id, summary, status, assignee, reporter, due_date, created_at, updated_at' (CSV). |
/projects/technology.epf/Bugzilla/bugzilla_issues.csv |
| Bugzilla | bugzilla_issues_open.csv The list of open issues, with fields 'id, summary, status, assignee, reporter, due_date, created_at, updated_at' (CSV). |
/projects/technology.epf/Bugzilla/bugzilla_issues_open.csv |
| Bugzilla | bugzilla_issues_open_unassigned.csv The list of open and unassigned issues, with fields 'id, summary, status, assignee, reporter, due_date, created_at, updated_at' (CSV). |
/projects/technology.epf/Bugzilla/bugzilla_issues_open_unassigned.csv |
| Bugzilla | bugzilla_milestones.csv The list of milestones that have at least one bug targeted for (CSV). |
/projects/technology.epf/Bugzilla/bugzilla_milestones.csv |
| Bugzilla | bugzilla_versions.csv The list of software versions that have at least one bug registered against them (CSV). |
/projects/technology.epf/Bugzilla/bugzilla_versions.csv |
| Bugzilla | import_bugzilla.json The original file of current information, downloaded from the Bugzilla server (JSON). |
/projects/technology.epf/Bugzilla/import_bugzilla.json |
| Bugzilla | metrics_bugzilla.csv The list of metrics with their values (CSV). |
/projects/technology.epf/Bugzilla/metrics_bugzilla.csv |
| Bugzilla | metrics_bugzilla.json The list of metrics with their values (JSON). |
/projects/technology.epf/Bugzilla/metrics_bugzilla.json |
| EclipseForums | eclipse_forums_forum.csv The forum description file as returned by Eclipse servers (CSV). |
/projects/technology.epf/EclipseForums/eclipse_forums_forum.csv |
| EclipseForums | eclipse_forums_posts.csv The list of posts for the forum as returned by Eclipse servers (CSV). |
/projects/technology.epf/EclipseForums/eclipse_forums_posts.csv |
| EclipseForums | eclipse_forums_threads.csv The list of threads for the forum as returned by Eclipse servers (CSV). |
/projects/technology.epf/EclipseForums/eclipse_forums_threads.csv |
| EclipseForums | import_eclipse_forums_forum.json The forum description file as returned by Eclipse servers (JSON). |
/projects/technology.epf/EclipseForums/import_eclipse_forums_forum.json |
| EclipseForums | import_eclipse_forums_posts.json The list of posts for the forum as returned by Eclipse servers (JSON). |
/projects/technology.epf/EclipseForums/import_eclipse_forums_posts.json |
| EclipseForums | import_eclipse_forums_threads.json The list of threads for the forum as returned by Eclipse servers (JSON). |
/projects/technology.epf/EclipseForums/import_eclipse_forums_threads.json |
| EclipsePmi | pmi.json The PMI file as returned by the Eclipse repository (JSON). |
/projects/technology.epf/EclipsePmi/pmi.json |
| EclipsePmi | pmi_checks.csv The list of PMI checks and their results (CSV). |
/projects/technology.epf/EclipsePmi/pmi_checks.csv |
| EclipsePmi | pmi_checks.json The list of PMI checks and their results (JSON). |
/projects/technology.epf/EclipsePmi/pmi_checks.json |
| GenericR | generic_r.pdf The PDF document generated from the R markdown file. |
/projects/technology.epf/GenericR/generic_r.pdf |
| Git | git_branches.csv List of branches of the Git repository, one by line (CSV). |
/projects/technology.epf/Git/git_branches.csv |
| Git | git_commits.csv List of all commits, with id, message, time, author, committer, and added, deleted and modifed lines (CSV). |
/projects/technology.epf/Git/git_commits.csv |
| Git | git_commits_evol.csv Evolution of number of commits and authors by day (CSV). |
/projects/technology.epf/Git/git_commits_evol.csv |
| Git | import_git.txt The original git log file as retrieved from git (TXT). |
/projects/technology.epf/Git/import_git.txt |
| Git | info_git.csv All information computed by the Git plugin (CSV). |
/projects/technology.epf/Git/info_git.csv |
| Git | metrics_git.csv Current metrics for the SCM Git plugin (CSV). |
/projects/technology.epf/Git/metrics_git.csv |
| Git | metrics_git.json Current metrics for the SCM Git plugin (JSON). |
/projects/technology.epf/Git/metrics_git.json |
| Plugin | Description | URL |
|---|---|---|
| Bugzilla | Bar plot of all components defined for project in Bugzilla (HTML) | /projects/technology.epf/Bugzilla/bugzilla_components.html |
| Bugzilla | Evolution of Bugzilla issues submission | /projects/technology.epf/Bugzilla/bugzilla_evol_summary.html |
| Bugzilla | Bar plot of all versions defined for project in Bugzilla (HTML). | /projects/technology.epf/Bugzilla/bugzilla_versions.html |
| EclipseForums | Timeline of posts | /projects/technology.epf/EclipseForums/eclipse_forums_plot.html |
| EclipseForums | Wordcloud of threads subjects (PNG) | /projects/technology.epf/EclipseForums/eclipse_forums_wordcloud.png |
| EclipseForums | Wordcloud of threads subjects (SVG) | /projects/technology.epf/EclipseForums/eclipse_forums_wordcloud.svg |
| Git | HTML export of Git authors evolution. | /projects/technology.epf/Git/git_evol_authors.html |
| Git | PNG export of Git SCM authors evolution. | /projects/technology.epf/Git/git_evol_authors.png |
| Git | SVG export of Git SCM authors evolution. | /projects/technology.epf/Git/git_evol_authors.svg |
| Git | HTML export of Git commits evolution. | /projects/technology.epf/Git/git_evol_commits.html |
| Git | PNG export of Git SCM commits evolution. | /projects/technology.epf/Git/git_evol_commits.png |
| Git | SVG export of Git SCM commits evolution. | /projects/technology.epf/Git/git_evol_commits.svg |
| Git | HTML export of Git SCM evolution summary. | /projects/technology.epf/Git/git_evol_summary.html |
| Git | HTML export of Git main metrics. | /projects/technology.epf/Git/git_summary.html |
| ProjectSummary | A badge to display current value of main quality attribute on an external web site (uses shields.io) | /projects/technology.epf/ProjectSummary/badge_attr_alambic.svg |
| ProjectSummary | A badge to display current value of main quality attribute on an external web site (uses shields.io) | /projects/technology.epf/ProjectSummary/badge_attr_root.svg |
| ProjectSummary | A HTML snippet that displays downloads for main data. | /projects/technology.epf/ProjectSummary/badge_downloads |
| ProjectSummary | A HTML snippet that displays a list of plugins for the project. | /projects/technology.epf/ProjectSummary/badge_plugins |
| ProjectSummary | A HTML snippet that displays the name and description of the project. | /projects/technology.epf/ProjectSummary/badge_project_main |
| ProjectSummary | A HTML snippet to display main quality attributes and their values. | /projects/technology.epf/ProjectSummary/badge_psum_attrs.html |
| ProjectSummary | A HTML snippet that displays main quality attributes. | /projects/technology.epf/ProjectSummary/badge_qm |
| ProjectSummary | A HTML snippet that displays the quality model visualisation. | /projects/technology.epf/ProjectSummary/badge_qm_viz |
| ProjectSummary | A HTML snippet to display main quality attributes and their values. | /projects/technology.epf/ProjectSummary/psum_attrs.html |
| Plugin | Name | URL |
|---|---|---|
| Bugzilla | Bugzilla | /projects/technology.epf/Bugzilla/bugzilla.html |
| EclipseForums | Eclipse Forums | /projects/technology.epf/EclipseForums/eclipse_forums.html |
| EclipsePmi | Eclipse PMI Checks | /projects/technology.epf/EclipsePmi/pmi_checks |
| Git | Git SCM | /projects/technology.epf/Git/git_scm.html |
| ProjectSummary | Badges | /projects/technology.epf/ProjectSummary/badges.html |
Last analysis was on 2022-01-26 00:38:09.
Page generated by Alambic 3.3.3-dev on Wed Jan 26 18:07:18 2022.
