| {"checks":{"bugzilla_create_url":{"desc":"Checks if the URL can be fetched using a simple get query.","results":["OK: Create <a href=\"https:\/\/bugs.eclipse.org\/bugs\/enter_bug.cgi?product=EPF\">URL<\/a> could be successfully fetched."],"value":"https:\/\/bugs.eclipse.org\/bugs\/enter_bug.cgi?product=EPF"},"bugzilla_query_url":{"desc":"Checks if the URL can be fetched using a simple get query.","results":["OK: Query <a href=\"https:\/\/bugs.eclipse.org\/bugs\/buglist.cgi?product=EPF\">URL<\/a> could be successfully fetched."],"value":"https:\/\/bugs.eclipse.org\/bugs\/buglist.cgi?product=EPF"},"build_url":{"desc":"Sends a get request to the given CI URL and looks at the headers in the response (200, 404..). Also checks if the URL is really a Hudson instance (through a call to its API).","results":["Failed: could not get CI URL []."],"value":""},"dev_list":{"desc":"Checks if the Dev ML URL can be fetched using a simple get query.","results":["OK: Dev ML <a href=\"https:\/\/dev.eclipse.org\/mailman\/listinfo\/epf-dev\">URL<\/a> could be successfully fetched."],"value":"https:\/\/dev.eclipse.org\/mailman\/listinfo\/epf-dev"},"documentation_url":{"desc":"Checks if the URL can be fetched using a simple get query.","results":["OK: Documentation <a href=\"http:\/\/www.eclipse.org\/epf\/general\/developers_documentation.php\">URL<\/a> could be successfully fetched."],"value":"http:\/\/www.eclipse.org\/epf\/general\/developers_documentation.php"},"download_url":{"desc":"Checks if the URL can be fetched using a simple get query.","results":["OK: Download <a href=\"http:\/\/www.eclipse.org\/epf\/downloads\/downloads.php\">URL<\/a> could be successfully fetched."],"value":"http:\/\/www.eclipse.org\/epf\/downloads\/downloads.php"},"forums":{"desc":"Checks if the Forums URL can be fetched using a simple get query.","results":["OK. Forum [eclipse.technology.epf] correctly defined.","OK: Forum [eclipse.technology.epf] <a href=\"http:\/\/www.eclipse.org\/forums\/eclipse.technology.epf\">URL<\/a> could be successfully fetched."],"value":"http:\/\/www.eclipse.org\/forums\/eclipse.technology.epf"},"gettingstarted_url":{"desc":"Checks if the URL can be fetched using a simple get query.","results":["OK: Documentation <a href=\"http:\/\/www.eclipse.org\/epf\/general\/getting_started.php\">URL<\/a> could be successfully fetched."],"value":"http:\/\/www.eclipse.org\/epf\/general\/getting_started.php"},"mailing_lists":{"desc":"Checks if the Mailing lists URL can be fetched using a simple get query.","results":["Failed: no mailing list defined."]},"plan_url":{"desc":"Checks if the URL can be fetched using a simple get query.","results":["OK: Plan <a href=\"http:\/\/www.eclipse.org\/epf\/plan\/epf_1-5-1-8_project_plan.xml\">URL<\/a> could be successfully fetched."],"value":"http:\/\/www.eclipse.org\/epf\/plan\/epf_1-5-1-8_project_plan.xml"},"proposal_url":{"desc":"Checks if the URL can be fetched using a simple get query.","results":["OK: Proposal <a href=\"http:\/\/www.eclipse.org\/proposals\/beacon\/\">URL<\/a> could be successfully fetched."],"value":"http:\/\/www.eclipse.org\/proposals\/beacon\/"},"releases":{"desc":"Checks if the releases have been correctly filled.","results":["Failed. Review for [1.5.1.6] type [1] is [none] on [2013-11-01 00:00:00].","OK. Review for [1.5.1] is 'success'.","OK. Review for [1.5.0] is 'success'.","OK. Review for [1.2.0] is 'success'."]},"source_repo":{"desc":"Checks if the Source repositories are filled and can be fetched using a simple get query.","results":["OK. Source repo [epf\/org.eclipse.epf.additional] type [git] path [\/gitroot\/epf\/org.eclipse.epf.additional.git].","OK: Source repo [epf\/org.eclipse.epf.additional] <a href=\"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.additional\">URL<\/a> could be successfully fetched.","OK. Source repo [epf\/org.eclipse.epf.archive] type [git] path [\/gitroot\/epf\/org.eclipse.epf.archive.git].","OK: Source repo [epf\/org.eclipse.epf.archive] <a href=\"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.archive\">URL<\/a> could be successfully fetched.","OK. Source repo [epf\/org.eclipse.epf.composer] type [git] path [\/gitroot\/epf\/org.eclipse.epf.composer.git].","OK: Source repo [epf\/org.eclipse.epf.composer] <a href=\"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.composer\">URL<\/a> could be successfully fetched.","OK. Source repo [epf\/org.eclipse.epf.design] type [git] path [\/gitroot\/epf\/org.eclipse.epf.design.git].","OK: Source repo [epf\/org.eclipse.epf.design] <a href=\"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.design\">URL<\/a> could be successfully fetched.","OK. Source repo [epf\/org.eclipse.epf.docs] type [git] path [\/gitroot\/epf\/org.eclipse.epf.docs.git].","OK: Source repo [epf\/org.eclipse.epf.docs] <a href=\"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.docs\">URL<\/a> could be successfully fetched.","OK. Source repo [epf\/org.eclipse.epf.features] type [git] path [\/gitroot\/epf\/org.eclipse.epf.features.git].","OK: Source repo [epf\/org.eclipse.epf.features] <a href=\"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.features\">URL<\/a> could be successfully fetched.","OK. Source repo [epf\/org.eclipse.epf.libraries] type [git] path [\/gitroot\/epf\/org.eclipse.epf.libraries.git].","OK: Source repo [epf\/org.eclipse.epf.libraries] <a href=\"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.libraries\">URL<\/a> could be successfully fetched.","OK. Source repo [epf\/org.eclipse.epf.nl-libraries] type [git] path [\/gitroot\/epf\/org.eclipse.epf.nl-libraries.git].","OK: Source repo [epf\/org.eclipse.epf.nl-libraries] <a href=\"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.nl-libraries\">URL<\/a> could be successfully fetched.","OK. Source repo [epf\/org.eclipse.epf.nl-src] type [git] path [\/gitroot\/epf\/org.eclipse.epf.nl-src.git].","OK: Source repo [epf\/org.eclipse.epf.nl-src] <a href=\"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.nl-src\">URL<\/a> could be successfully fetched.","OK. Source repo [epf\/org.eclipse.epf.plugins] type [git] path [\/gitroot\/epf\/org.eclipse.epf.plugins.git].","OK: Source repo [epf\/org.eclipse.epf.plugins] <a href=\"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.plugins\">URL<\/a> could be successfully fetched.","OK. Source repo [epf\/org.eclipse.epf.projects] type [git] path [\/gitroot\/epf\/org.eclipse.epf.projects.git].","OK: Source repo [epf\/org.eclipse.epf.projects] <a href=\"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.projects\">URL<\/a> could be successfully fetched.","OK. Source repo [epf\/org.eclipse.epf.prototype] type [git] path [\/gitroot\/epf\/org.eclipse.epf.prototype.git].","OK: Source repo [epf\/org.eclipse.epf.prototype] <a href=\"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.prototype\">URL<\/a> could be successfully fetched.","OK. Source repo [epf\/org.eclipse.epf.tests] type [git] path [\/gitroot\/epf\/org.eclipse.epf.tests.git].","OK: Source repo [epf\/org.eclipse.epf.tests] <a href=\"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.tests\">URL<\/a> could be successfully fetched.","OK. Source repo [epf\/org.eclipse.epf.wiki] type [git] path [\/gitroot\/epf\/org.eclipse.epf.wiki.git].","OK: Source repo [epf\/org.eclipse.epf.wiki] <a href=\"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.wiki\">URL<\/a> could be successfully fetched."],"value":"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.wiki"},"title":{"desc":"Checks if a name is defined for the project: !~ m!^\\s*$!","results":["OK"],"value":"Eclipse Process Framework Project"},"update_sites":{"desc":"Checks if the update sites can be fetched using a simple get query.","results":["Failed. No update site defined."]},"website_url":{"desc":"Checks if the URL can be fetched using a simple get query.","results":["OK: Website <a href=\"http:\/\/www.eclipse.org\/epf\">URL<\/a> could be successfully fetched."],"value":"http:\/\/www.eclipse.org\/epf"},"wiki_url":{"desc":"Sends a get request to the project wiki URL and looks at the headers in the response (200, 404..).","results":["Failed: no URL defined for wiki_url."]}},"id_pmi":"technology.epf","last_update":1627173532,"name":"Eclipse Process Framework Project","pmi":{"bugzilla":[{"component":"","create_url":"https:\/\/bugs.eclipse.org\/bugs\/enter_bug.cgi?product=EPF","product":"EPF","query_url":"https:\/\/bugs.eclipse.org\/bugs\/buglist.cgi?product=EPF"}],"build_description":[],"build_doc":[],"build_technologies":[],"build_url":[{}],"contrib_message":[],"contributors":[],"description":[{"format":"full_html","summary":"<p>There are two goals of the Eclipse Process Framework Project:<\/p>\r\n<ul>\r\n\t<li>\r\n\t\tTo provide an extensible framework and exemplary tools for software process engineering - method and process authoring, library management, configuring and publishing a process.<\/li>\r\n\t<li>\r\n\t\tTo 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>\r\n<\/ul>\r\n","value":"<p>There are two goals of the Eclipse Process Framework Project:<\/p>\r\n<ul>\r\n\t<li>\r\n\t\tTo provide an extensible framework and exemplary tools for software process engineering - method and process authoring, library management, configuring and publishing a process.<\/li>\r\n\t<li>\r\n\t\tTo 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>\r\n<\/ul>\r\n<h3>\r\n\tExtensible software process engineering framework<\/h3>\r\n<p>The framework consists of the following two components:<\/p>\r\n<ul>\r\n\t<li>\r\n\t\tMeta-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>\r\n\t<li>\r\n\t\tCore 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>\r\n<\/ul>\r\n<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>\r\n<h3>\r\n\tExemplary tools<\/h3>\r\n<p>The following exemplary tools provide the following capabilities:<\/p>\r\n<ul>\r\n\t<li>\r\n\t\tMethod 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>\r\n\t<li>\r\n\t\tProcess 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>\r\n\t<li>\r\n\t\tLibrary 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>\r\n\t<li>\r\n\t\tConfiguring 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>\r\n<\/ul>\r\n<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>\r\n<h3>\r\n\tExemplary and extensible process content<\/h3>\r\n<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>\r\n<ul>\r\n\t<li>\r\n\t\tIBM 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>\r\n\t<li>\r\n\t\tOther 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>\r\n<\/ul>\r\n<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>\r\n<h3>\r\n\tTarget Users of the Process Framework<\/h3>\r\n<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>\r\n"}],"dev_list":{"email":"WEF1HWTIwQlw18bF@AL+i1tm2YgpuzlxR","name":"epf-dev","url":"https:\/\/dev.eclipse.org\/mailman\/listinfo\/epf-dev"},"documentation":[],"documentation_url":[{"attributes":[],"title":null,"url":"http:\/\/www.eclipse.org\/epf\/general\/developers_documentation.php"}],"download_url":[{"attributes":[],"title":null,"url":"http:\/\/www.eclipse.org\/epf\/downloads\/downloads.php"}],"downloads":[],"downloads_message":[],"forums":[{"description":"The Eclipse Process Framework (EPF) aims at producing a customizable software process enginering framework, with exemplary process content and tools, supporting a broad variety of project types and development styles. Want to know more? Join this newsgroup and see the EPF home page.","name":"eclipse.technology.epf","url":"http:\/\/www.eclipse.org\/forums\/eclipse.technology.epf"}],"gettingstarted_url":[{"attributes":[],"title":null,"url":"http:\/\/www.eclipse.org\/epf\/general\/getting_started.php"}],"github_repos":[],"gitlab_repos":[],"id":[{"format":null,"safe_value":"technology.epf","value":"technology.epf"}],"ip_due_diligence_type":[],"licenses":[{"name":"Eclipse Public License 1.0","url":"http:\/\/www.eclipse.org\/org\/documents\/epl-v10.php"}],"logo":[{"alt":"","fid":"168","filemime":"image\/jpeg","filename":"process_eclipse_pos_logo_fc_sm.jpg","filesize":"4143","height":"144","rdf_mapping":[],"status":"1","timestamp":"1390584019","title":"","uid":"1974","uri":"public:\/\/process_eclipse_pos_logo_fc_sm.jpg","width":"144"}],"mailing_lists":[],"marketplace":[],"other_links":[],"parent_project":[{"id":"technology"}],"patent_license":[],"plan_url":[{"attributes":[],"title":null,"url":"http:\/\/www.eclipse.org\/epf\/plan\/epf_1-5-1-8_project_plan.xml"}],"pmi_url":"https:\/\/projects.eclipse.org\/json\/project\/technology.epf","proposal_url":[{"attributes":[],"title":null,"url":"http:\/\/www.eclipse.org\/proposals\/beacon\/"}],"related":[],"releases":[{"apis":[{"value":"0"}],"architecture":[],"communities":[],"compatibility":[{"format":"full_html","value":"<p>Compatible with previous releases.<\/p>\r\n"}],"conf_ui_guidelines":[{"value":"not_verified"}],"date":[{"date_type":"datetime","timezone":"America\/Montreal","timezone_db":"America\/Montreal","value":"2018-04-28 00:00:00"}],"deliverables":[{"format":"full_html","value":"<p>Update to Eclipse 4.2.2.<\/p>\r\n"}],"description":[{"format":"full_html","summary":"","value":"<p>Updated to Eclipse 4.2.2<\/p>\r\n"}],"endoflife":[],"environment":[{"format":"full_html","value":"<p>Window and Linux<\/p>\r\n"}],"i18n":[{"format":"full_html","value":"<p>N\/A<\/p>\r\n"}],"ip_due_diligence_type":[],"milestones":[{"date":"2018-04-28 00:00:00","description":"Final release","name":"M1"}],"noncode":[],"noteworthy":[],"parent_project":[{"id":"technology.epf"}],"review":{"state":[{}]},"screenshots":[],"security":[],"standards":[],"subprojects":[],"themes":[{"committed":"http:\/\/bugs.eclipse.org\/bugs\/buglist.cgi?query_format=advanced&classification=TECHNOLOGY&product=EPF&component=Tool&target_milestone=1.5.2&target_milestone=1.5.2 M1","deferred":"","description":"","name":"Update Eclipse","proposed":""}],"title":"1.5.2","type":[{"value":"3"}],"url":"https:\/\/projects.eclipse.org\/projects\/technology.epf\/releases\/1.5.2","usability":[]},{"apis":[{"value":"0"}],"architecture":[],"communities":[],"compatibility":[],"conf_ui_guidelines":[],"date":[{"date_type":"datetime","timezone":"America\/Montreal","timezone_db":"America\/Montreal","value":"2013-11-01 00:00:00"}],"deliverables":[],"description":[],"endoflife":[],"environment":[],"i18n":[],"ip_due_diligence_type":[],"milestones":[],"noncode":[],"noteworthy":[],"parent_project":[{"id":"technology.epf"}],"review":{"state":[{}]},"screenshots":[],"security":[],"standards":[],"subprojects":[],"themes":[],"title":"1.5.1.6","type":[{}],"url":"https:\/\/projects.eclipse.org\/projects\/technology.epf\/releases\/1.5.1.6","usability":[]},{"apis":[{"value":"0"}],"architecture":[],"communities":[],"compatibility":[{"format":"full_html","value":"<div>No incompatibilities have been introduced.<\/div>"}],"conf_ui_guidelines":[],"date":[{"date_type":"datetime","timezone":"America\/Montreal","timezone_db":"America\/Montreal","value":"2012-12-10 00:00:00"}],"deliverables":[{"format":"full_html","value":"<div>Deliverables include installable EPF composer build and the EPF practices library. The release work also includes updating the EPF web site with download bits, published, release notes, and updates to the EPF Wiki. <\/div>"}],"description":[{"format":"full_html","summary":null,"value":"<div>The approach for this project plan will be discussed at the Thurs July 12, 2012 EPF meeting. This is planned to be just a bug fix release, and will be made available on Dec 10, 2012. <\/div>"}],"endoflife":[],"environment":[{"format":"full_html","value":"<div>Win32 and Linux<\/div>"}],"i18n":[{"format":"full_html","value":"<div>None<\/div>"}],"ip_due_diligence_type":[],"milestones":[],"noncode":[],"noteworthy":[],"parent_project":[{"id":"technology.epf"}],"review":{"description":[],"end_date":[{"date_type":"datetime","timezone":"America\/Montreal","timezone_db":"America\/Montreal","value":"2010-09-29 00:00:00"}],"links":[{"attributes":[],"title":"Approved IP Log","url":"http:\/\/www.eclipse.org\/epf\/project-info\/project_log.csv"}],"project":[{"id":"technology.epf"}],"reference":[{"title":"1.5.1"}],"state":[{"value":"success"}],"title":"1.5.1 Release Review","top_level":[{"id":"technology"}],"type":[{"value":"release"}],"url":"https:\/\/projects.eclipse.org\/content\/1.5.1-release-review"},"screenshots":[],"security":[],"standards":[],"subprojects":[],"themes":[{"committed":"http:\/\/bugs.eclipse.org\/bugs\/buglist.cgi?query_format=advanced&classification=TECHNOLOGY&product=EPF&component=Tool&target_milestone=1.5.1.5&target_milestone=1.5.1.5 M1&target_milestone=1.5.1.5 M2&target_milestone=1.5.1.5 M3&target_milestone=1.5.1.5 M4&target_milestone=1.5.1.5 M5","deferred":null,"description":"<p>- Bug fixes only.<\/p>","name":"EPF Composer tooling capabilities","proposed":null},{"committed":"http:\/\/bugs.eclipse.org\/bugs\/buglist.cgi?query_format=advanced&classification=TECHNOLOGY&product=EPF&component=Content&target_milestone=1.5.1.5&target_milestone=1.5.1.5 M1&target_milestone=1.5.1.5 M2&target_milestone=1.5.1.5 M3&target_milestone=1.5.1.5 M4&target_milestone=1.5.1.5 M5","deferred":null,"description":"<p>- Bug fixes and minor content updates.<\/p>","name":"EPF Practices library","proposed":null}],"title":"1.5.1","type":[{}],"url":"https:\/\/projects.eclipse.org\/projects\/release\/1.5.1-2","usability":[]},{"apis":[{"value":"0"}],"architecture":[],"communities":[],"compatibility":[],"conf_ui_guidelines":[],"date":[{"date_type":"datetime","timezone":"America\/Montreal","timezone_db":"America\/Montreal","value":"2009-10-31 00:00:00"}],"deliverables":[],"description":[],"endoflife":[],"environment":[],"i18n":[],"ip_due_diligence_type":[],"milestones":[],"noncode":[],"noteworthy":[],"parent_project":[{"id":"technology.epf"}],"review":{"description":[],"end_date":[{"date_type":"datetime","timezone":"America\/Montreal","timezone_db":"America\/Montreal","value":"2008-08-13 00:00:00"}],"links":[{"attributes":[],"title":"Approved IP Log","url":"http:\/\/www.eclipse.org\/project-slides\/EPF_1.5_project_log.csv"},{"attributes":[],"title":"Review Documentation","url":"http:\/\/www.eclipse.org\/project-slides\/EPF_1-5_Release_Review.pdf"}],"project":[{"id":"technology.epf"}],"reference":[{"title":"1.5.0"}],"state":[{"value":"success"}],"title":"1.5.0 Release Review","top_level":[{"id":"technology"}],"type":[{"value":"release"}],"url":"https:\/\/projects.eclipse.org\/content\/1.5.0-release-review-5"},"screenshots":[],"security":[],"standards":[],"subprojects":[],"themes":[],"title":"1.5.0","type":[{}],"url":"https:\/\/projects.eclipse.org\/projects\/release\/1.5.0-7","usability":[]},{"apis":[{"value":"0"}],"architecture":[],"communities":[],"compatibility":[],"conf_ui_guidelines":[],"date":[{"date_type":"datetime","timezone":"America\/Montreal","timezone_db":"America\/Montreal","value":"2007-08-01 00:00:00"}],"deliverables":[],"description":[],"endoflife":[],"environment":[],"i18n":[],"ip_due_diligence_type":[],"milestones":[],"noncode":[],"noteworthy":[],"parent_project":[{"id":"technology.epf"}],"review":{"description":[],"end_date":[{"date_type":"datetime","timezone":"America\/Montreal","timezone_db":"America\/Montreal","value":"2007-07-25 00:00:00"}],"links":[{"attributes":[],"title":"Approved IP Log","url":"http:\/\/www.eclipse.org\/project-slides\/EPF_1-2_IP_Log.csv"},{"attributes":[],"title":"Review Documentation","url":"http:\/\/www.eclipse.org\/project-slides\/EPF_1-2_Release_Review.pdf"}],"project":[{"id":"technology.epf"}],"reference":[{"title":"1.2.0"}],"state":[{"value":"success"}],"title":"1.2.0 Release Review","top_level":[{"id":"technology"}],"type":[{"value":"release"}],"url":"https:\/\/projects.eclipse.org\/content\/1.2.0-release-review-8"},"screenshots":[],"security":[],"standards":[],"subprojects":[],"themes":[],"title":"1.2.0","type":[{}],"url":"https:\/\/projects.eclipse.org\/projects\/release\/1.2.0-16","usability":[]}],"scope":[{"format":"full_html","value":"<p>Throughout the software industry, there are a lot of great ideas and knowledge about how to effectively develop software. This knowledge may be centered around 1) technologies, such as J2EE, .NET, and various tool environments; 2) various specialty domains, such as how to do iterative and agile development, how to build secure software, how to best leverage service-oriented architectures, or how to do distributed development; and 3) various vertical industry knowledge, such as how to deal with straight-through processing in the financial world, or how to build embedded systems for the auto industry.<\/p>\r\n<p>The sources for all of these great ideas and knowledge include organizations doing software development, open source communities, the agile community, <a href=\"http:\/\/www.sei.cmu.edu\/collaborating\/spins\/\">Software Process Improvement Networks<\/a> (SPIN groups), product and technology companies, academia and software research groups, such as <a href=\"http:\/\/www.sei.cmu.edu\/\">SEI Carnegie Mellon<\/a>, <a href=\"http:\/\/www.ubc.ca\/\">University of British Columbia<\/a>, and <a href=\"http:\/\/sunset.usc.edu\/\">USC Center for Software Engineering<\/a>, a variety of methodologists and companies capturing industry best practices into various knowledge bases, literature, and processes. The problems with these process assets are:<\/p>\r\n<ul>\r\n\t<li>\r\n\t\t<strong>Integration<\/strong>: When different media, notations, language, and terminology are used to express process assets, integration of the process assets becomes difficult to achieve. Furthermore, lack of standard interfaces makes it hard to integrate these assets with; project & portfolio management tools, such as <a href=\"http:\/\/www-306.ibm.com\/software\/awdtools\/portfolio\/\">IBM Rational Portfolio Manager<\/a>, <a href=\"http:\/\/www.rallydev.com\">Rally's Agile Management Application<\/a> or <a href=\"http:\/\/www.microsoft.com\/office\/project\/prodinfo\/default.mspx\">Microsoft Project<\/a>; process management and support tools, such as <a href=\"http:\/\/www.jaczone.com\/product\/demonstration\/\">WayPointer<\/a> or <a href=\"http:\/\/www.osellus.com\/products\/iris_suite\/iris_suite.html\">IRIS<\/a>; or development environments such as the Eclipse platform.<\/li>\r\n\t<li>\r\n\t\t<strong>Redundant and Isolated Work:<\/strong> When process assets are developed with limited collaboration between different groups, some groups may take part in redundant work, reinventing the wheel rather than adding value to preexisting work or failing to leverage ideas towards accelerating innovation.<\/li>\r\n\t<li>\r\n\t\t<strong>Flexibility and Communication<\/strong>: When process assets are developed without a framework that allows for integration and customization, they may not be effectively communicated for a specific project or organization.<\/li>\r\n<\/ul>\r\n"}],"source_repo":[{"name":"epf\/org.eclipse.epf.additional","path":"\/gitroot\/epf\/org.eclipse.epf.additional.git","type":"git","url":"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.additional"},{"name":"epf\/org.eclipse.epf.archive","path":"\/gitroot\/epf\/org.eclipse.epf.archive.git","type":"git","url":"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.archive"},{"name":"epf\/org.eclipse.epf.composer","path":"\/gitroot\/epf\/org.eclipse.epf.composer.git","type":"git","url":"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.composer"},{"name":"epf\/org.eclipse.epf.design","path":"\/gitroot\/epf\/org.eclipse.epf.design.git","type":"git","url":"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.design"},{"name":"epf\/org.eclipse.epf.docs","path":"\/gitroot\/epf\/org.eclipse.epf.docs.git","type":"git","url":"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.docs"},{"name":"epf\/org.eclipse.epf.features","path":"\/gitroot\/epf\/org.eclipse.epf.features.git","type":"git","url":"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.features"},{"name":"epf\/org.eclipse.epf.libraries","path":"\/gitroot\/epf\/org.eclipse.epf.libraries.git","type":"git","url":"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.libraries"},{"name":"epf\/org.eclipse.epf.nl-libraries","path":"\/gitroot\/epf\/org.eclipse.epf.nl-libraries.git","type":"git","url":"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.nl-libraries"},{"name":"epf\/org.eclipse.epf.nl-src","path":"\/gitroot\/epf\/org.eclipse.epf.nl-src.git","type":"git","url":"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.nl-src"},{"name":"epf\/org.eclipse.epf.plugins","path":"\/gitroot\/epf\/org.eclipse.epf.plugins.git","type":"git","url":"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.plugins"},{"name":"epf\/org.eclipse.epf.projects","path":"\/gitroot\/epf\/org.eclipse.epf.projects.git","type":"git","url":"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.projects"},{"name":"epf\/org.eclipse.epf.prototype","path":"\/gitroot\/epf\/org.eclipse.epf.prototype.git","type":"git","url":"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.prototype"},{"name":"epf\/org.eclipse.epf.tests","path":"\/gitroot\/epf\/org.eclipse.epf.tests.git","type":"git","url":"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.tests"},{"name":"epf\/org.eclipse.epf.wiki","path":"\/gitroot\/epf\/org.eclipse.epf.wiki.git","type":"git","url":"https:\/\/git.eclipse.org\/r\/plugins\/gitiles\/epf\/org.eclipse.epf.wiki"}],"spec_working_group":[],"state":[{"value":"Regular"}],"tags":[],"team_project_sets":[],"techology_types":[],"title":"Eclipse Process Framework Project","update_sites":[],"url":"https:\/\/projects.eclipse.org\/projects\/technology.epf","website_url":[{"attributes":[],"title":null,"url":"http:\/\/www.eclipse.org\/epf"}],"wiki_url":[{}],"working_group":[]},"pmi_url":"https:\/\/projects.eclipse.org\/json\/project\/technology.epf"} |