From sac-owner Fri Jan 25 08:11:34 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0PGBY5E012562 for ; Fri, 25 Jan 2008 08:11:34 -0800 (PST) Received: from newsunmail1brm.central.sun.com (localhost [127.0.0.1]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m0PGBYDb046750 for ; Fri, 25 Jan 2008 09:11:34 -0700 (MST) Received: (from noaccess@localhost) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/Submit) id m0PGBYjm046749 for one-pager-not-2b-used-directly; Fri, 25 Jan 2008 09:11:34 -0700 (MST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m0PGBY56046740 for <@sunmail2sca.sfbay.sun.com:one-pager@sun.com>; Fri, 25 Jan 2008 09:11:34 -0700 (MST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JV700M39JNAAM00@brm-avmta-1.central.sun.com> for one-pager@sun.com (ORCPT one-pager@sun.com); Fri, 25 Jan 2008 09:11:34 -0700 (MST) Received: from gmp-eb-mail-1.sun.com ([192.18.6.21]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JV700GRCJN8QPE0@brm-avmta-1.central.sun.com> for one-pager@sun.com (ORCPT one-pager@sun.com); Fri, 25 Jan 2008 09:11:33 -0700 (MST) Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe2.eu.sun.com [192.18.6.11]) by gmp-eb-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m0PGBWFw017826 for ; Fri, 25 Jan 2008 16:11:32 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JV700M01J06DI00@fe-emea-10.sun.com> (original mail from Petr.Jiricka@Sun.COM) for one-pager@sun.com (ORCPT one-pager@sun.com); Fri, 25 Jan 2008 16:11:32 +0000 (GMT) Received: from petr-jirickas-computer-3.local ([195.70.135.234]) by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JV700DMCJN4TT10@fe-emea-10.sun.com> for one-pager@sun.com (ORCPT one-pager@sun.com); Fri, 25 Jan 2008 16:11:29 +0000 (GMT) Date: Fri, 25 Jan 2008 17:12:22 +0100 From: Petr Jiricka Subject: [2008/052]NetBeans 6.0 Ruby features Sender: Petr.Jiricka@sun.com To: one-pager@sun.com Message-id: <479A0A66.3020701@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) Status: RO Content-Length: 8099 Template Version: @(#)onepager.txt 1.29 04/11/15 SMI This information is Copyright 2008 Sun Microsystems, Inc. 1. Introduction 1.1. Project/Component Working Name: NetBeans 6.0 Ruby features 1.2. Name of Document Author/Supplier: Petr Jiricka (petr.jiricka@sun.com) 1.3. Date of This Document: January 25, 2007 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: NetBeans PAC 1.4.2. The ARC(s) you expect to review your project: WSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Jim.Parkinson@Sun.COM 1.4.4. The name of your business unit: Software/Tools 1.5. Email Aliases: 1.5.1. Responsible Manager: petr.jiricka@sun.com 1.5.2. Responsible Engineer: petr.jiricka@sun.com 1.5.3. Marketing Manager: Judith.Lilienfeld@Sun.COM 1.5.4. Interest List: dev@ruby.netbeans.org 2. Project Summary 2.1. Project Description: This is the initial release of the Ruby tooling for NetBeans, delivered as a part of the NetBeans 6.0 release in December 2007. It includes support for developing software in the Ruby languages, including the Ruby on Rails web framework. 2.2. Risks and Assumptions: NetBeans 6 ARC review is divided several ARC cases corresponding to NetBeans 6 components. So this case only covers a part of the NetBeans 6 release. 3. Business Summary 3.1. Problem Area: The project provides tooling for development of Ruby software, including the Ruby on Rails framework. Development targets both the native Ruby runtime and the JRuby runtime, which allows running Ruby software on top of the Java platform. For Rails applications, popular Ruby servers such as WEBrick and Mongrel are supported, and foundation is established that will allow supporting GlassFish for Rails deployment in the future. 3.2. Market/Requester: Ruby is one of the high priority areas to be addressed by the NetBeans 6.0 release. It is a new segment of developers, which extends the reach of the NetBeans development tool to a completely new audience, and significantly contributes to the NetBeans adoption goal expressed in terms of active NetBeans users. 3.3. Business Justification: Extend the reach of the NetBeans tool and the Sun platform beyond the traditional Java developers' market, by addressing a new segment of developers. 3.4. Competitive Analysis: The main competitors in the Ruby area are Aptana/RadRails Eclipse-based IDE, IntelliJ IDEA, the TextMate editor and Ruby in Steel based on the Microsoft Visual Studio. 3.5. Opportunity Window/Exposure: As the Ruby tools market is relatively immature, Sun has an excellent opportunity to have the best Ruby IDE and win over the majority of Ruby developers. Also, as Sun controls the JRuby project through the main contributors to JRuby, and is working on the JRuby integration with the GlassFish application server, Sun has the potential to be the preferred vendor for Ruby applications built on top of the Java platform. Right now, we are on track to materialize this goal. 3.6. How will you know when you are done?: See the CTQs and "Project Boundary and Summary", which are a part of PLC documentation of the project. 4. Technical Description: 4.1. Details: Ruby features are implemented as a separate component ("cluster") of the NetBeans IDE. They only depend on the base parts of the NetBeans IDE, and do not require the unrelated features, such as Java development features, UML, Java EE, Mobility, Visual Web and similar. The Ruby features do interoperate with technology-independent features, such as database support, versioning, XML etc. NetBeans bundles the JRuby implementation of Ruby; at the same time it interoperates with the native Ruby implementations included in many operating systems, including Solaris and Mac OS X. 4.2. Bug/RFE Number(s): We plan to address all P1 and P2 bugs and most P3 bugs to meet the release quality criteria. 4.3. In Scope: See section 3.1 4.4. Out of Scope: Out of the box GlassFish deployment will be targetted in a future release. Also, as this is an initial release, the team will only target the most important features, not second tier features. 4.5. Interfaces: Ruby features will depend on the general IDE interfaces provided by the common clusters of the IDE. The Ruby modules do not expose any interfaces to other features included in the IDE. However, it contains some generic infrastructure elements that appear to be useful in other contexts than just Ruby development, so these are candidates to be factored out and made more generally available in the future version of the IDE. For the list of all NetBeans APIs, see this list: http://www.netbeans.org/download/dev/javadoc/ 4.6. Doc Impact: The new Ruby features will be documented. See also the Documentation Plan, that is a part of PLC documentation. 4.7. Admin/Config Impact: The product does not have a separate administration part. 4.8. HA Impact: Not applicable. 4.9. I18N/L10N Impact: All new and modified code will be internationalized and localized. 4.10. Packaging & Delivery: Packaging and delivery is changing dramatically. Please see the NetBeans installer ARC case for a detailed description. There is a special Ruby distribution of NetBeans, which contains only the Ruby features (and the technology-agnostic features), but not the Java-based development etc. Next, Ruby features are a part of the "all in one" download/distribution of NetBeans. 4.11. Security Impact: This proposal does not have impact on any security aspects of NetBeans. 4.12. Dependencies: Requires JRuby 1.0.x 5. Reference Documents: PLC documentation for NetBeans 6.0 http://jupiter.czech.sun.com/wiki/view/Netbeans/NB60 Main pages for the Ruby project http://wiki.netbeans.org/Ruby Other related ARC cases http://jupiter.czech.sun.com/wiki/view/Netbeans/NB6ARCCases 6. Resources and Schedule: 6.1. Projected Availability: Q4 CY 2007 6.2. Cost of Effort: See PLC Phase 2 materials at http://jupiter.czech.sun.com/wiki/view/Netbeans/NB60IntegratedProgramPlan#4_3_Resources_required_to_suppor 6.3. Cost of Capital Resources: Dtto 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: TBD 6.4.3. Type of CPT Review and Approval expected: TBD 6.4.4. Project Boundary Conditions: See PLC documentation here: http://jupiter.czech.sun.com/wiki/view/Netbeans/NB60IntegratedProgramPlan#7_Product_Team_Contract_owner_Iv 6.4.5. Is this a necessary project for OEM agreements: N/A 6.4.6. Notes: 6.4.7. Target RTI Date/Release: Ongoing throughout the NetBeans 6.0 release cycle until the FCS date. 6.4.8. Target Code Design Review Date: Q3 CY 2007. We do ongoing design reviews and user interface reviews for individual subcomponents. 6.4.9. Update approval addition: N/A 6.5. ARC review type: FastTrack 7. Prototype Availability: 7.1. Prototype Availability: Q2 CY 2007 7.2. Prototype Cost: No separate estimate for the prototype was done.