Progress Open Source Software Exchange N E T - PowerPoint PPT Presentation

1 / 35
About This Presentation
Title:

Progress Open Source Software Exchange N E T

Description:

Check-in, check-out and versioning. Bugzilla Bug Tracking System ... are major pieces of the toolset (Procedure Editor, Dictionary, SmartObjects, etc. ... – PowerPoint PPT presentation

Number of Views:74
Avg rating:3.0/5.0
Slides: 36
Provided by: PSC93
Category:

less

Transcript and Presenter's Notes

Title: Progress Open Source Software Exchange N E T


1
Progress Open Source Software ExchangeNET
  • Ray Huey
  • Sr. Product Manager
  • 4GL Tools

2
POSSENET
  • What is Open Source?
  • What is its Value?
  • What is POSSENET?
  • Roadmap

3
Disclaimer
  • This presentation reflects Progress Softwares
    current plans.
  • Some information is subject to change.

4
What is Open Source?
  • Open Source software is source code that is
    available to anyone to use as is or to modify and
    use free of charge.
  • Source IDC Bulletin - Open Source
    Software Steve McClure Hadar Pedhazur

5
What is Open Source?
  • Key elements of the web's foundation depend on
    OSS
  • Linux (34 of Internet servers)
  • Apache (60 of HTTP web servers outside the
    firewall)
  • BIND (100 of web address resolution)
  • Sendmail (70 of Internet mail traffic)
  • Source D.H. Brown Associates
  • Why Open-Source Software Matters to End Users
  • Countering Locked-Up Data and Locked-In
    Obsolescence,
  • May 2000

6
What is Open Source?
  • Open source will displace 20 of licensing
    dollars by 2004.
  • 84 of IT managers at Global 2,500 companies
    indicate that open source has fostered innovation
    in the software industry.
  • 52 believe that the biggest effect of open
    source will be to force increased competition in
    the industry.
  • Source Forrester Report
  • Open Source Cracks the Code, August 2000

The largest crisis of the 21st Century for the
IT world will be the competition for people who
can do the work. Other issues of technology,
market, margin, etc. will pale in
comparison. Source H. Michael Boyd, Ph.D., IDC
7
What is Open Source?
  • Development Model
  • User community collaboration
  • Community guides product direction
  • Based on meritocracy
  • Increased output
  • Improved quality
  • License Model
  • Source code is freely available
  • Users can review, modify, and redistribute it
  • Many different licensing models to choose from

8
What is its Value?
  • Value to PSC
  • Many of the development tools are written in the
    4GL
  • There is a large, highly skilled community of
    users that understand the 4GL
  • Experienced users already modify the tools for
    their own use
  • Most of our revenue comes from licenses and
    support for deployed applications, not tools

9
What is its Value?
  • Value to PSC
  • We want to increase your rate of development and
    the quality of your applications
  • We want to make sure we are working on what is
    important to you
  • Open Source is a proven development model that
    benefits the entire community
  • There is a lot of positive buzz around Open
    Source

10
What is its Value?
  • All PSC 4GL Tools developers continue in their
    current roles
  • Future PSC 4GL Tools development will be done on
    the Open Source web site
  • PSC will commercialize and support the POSSENET
    source code
  • POSSENET will be kept as independent of PSC as
    possible
  • Initial PSC management of POSSENET will be
    extended to the community ASAP

11
What is its Value?
  • Value to Progress Community
  • What makes you successful?
  • Are you focused on your business unique value to
    your customers?
  • Would you save time if you could use tools
    implemented by others in your field of expertise?
  • Would it increase your sales if others used
    components you built and are the recognized
    expert in using?

12
What is its Value?
  • Value to Progress Community
  • Leverage your development resources through
    collaboration
  • Help your business by influencing the
    architecture of the development tools
  • Create more reliable applications using stable
    code tested by real users
  • Real world input will streamline migration paths
    and shorten learning curves

13
What is POSSENET?
  • Objectives
  • Location
  • Contents
  • License
  • Community
  • Release process

14
Objectives
  • To provide an environment to support
    collaboration in design and development of 4GL
    based tools
  • To improve the quality of the tools
  • To promote the adoption of a standard framework
    for 4GL tools development
  • To increase productivity by combining ideas and
    software from many people

15
Location
  • All POSSENET materials (code, documentation and
    e-mail) will reside on the Internet at
    www.possenet.org
  • Progress is working with CollabNet to construct
    and maintain a web site
  • The site will go live in December 2000
  • Once it goes live, anyone can access the site

16
Contents
  • Discussion threads for projects
  • Submit comments, ideas, specifications and code
  • CVS Code Management System
  • Check-in, check-out and versioning
  • Bugzilla Bug Tracking System
  • ADE/ADM bug reports will be moved to the site
  • All bugs will be tracked and fixed through the
    site
  • Build scripts to allow builds from the source code

17
Contents
  • The source code we already ship will be placed on
    www.possenet.org
  • Source code for all other 4GL ADE tools will be
    made available
  • Developer documentation for the code will be
    included

18
Contents
  • Already shipping
  • ADM2 SmartObjects
  • Data Dictionary
  • Procedure Editor
  • PROTools
  • WebTools
  • DataServer Utilities
  • Partitioning Tool
  • Performance Profilers
  • Sample Application
  • Doc Examples
  • And for the first time
  • AppBuilder
  • WebSpeed Workshop
  • Application Compiler
  • RESULTS
  • Translation Manager
  • Visual Translator

19
License
  • The POSSENET license will be based on the Mozilla
    Public License, version 1.1
  • http//www.mozilla.org/MPL/
  • Anyone can view and use the source code
  • Anyone can modify it as long as changes are also
    open source
  • Anyone can commercialize and support the code as
    long as the code stays open

20
Community
  • User
  • Developer
  • Contributor
  • Project Owner
  • Core Review Team

21
POSSENET User
  • Anyone who accesses the site
  • Access to the site will be unrestricted
  • Anyone can follow discussions, make comments,
    submit bug reports and download code
  • No-one will be able to check-in code to the site
    without approval

22
POSSENET Developer
  • Someone who contributes bug fixes or enhancements
    by e-mail
  • Anyone can do this within the discussion thread
    for a project
  • Such changes will be reviewed before being
    accepted and checked-in

23
POSSENET Contributor
  • Someone who has check-in privileges for a project
  • Contributors will initially be Progress employees
  • Over time, we expect that numerous people in the
    community will become contributors
  • POSSENET will be a meritocracy
  • privileges follow quality and substance of
    submissions

24
POSSENET Project Owner
  • Projects are major pieces of the toolset
    (Procedure Editor, Dictionary, SmartObjects,
    etc.)
  • Each project will have an owner, responsible for
    design and oversight of check-ins
  • Initial owners will be Progress employees
  • Ownership will be extended to the community over
    time
  • Once again, this will be a meritocracy

25
POSSENET Core Review Team
  • Oversees the POSSENET initiative
  • Helps set overall direction for POSSENET
  • Assures that the process is working
  • Provides guidance for project owners
  • Makes high-level technical decisions
  • Initially comprised of Progress employees
  • Will be expanded to include members of the
    community

26
POSSENET Core Review Team
  • Soliciting nominations from the community
  • Job description for CRT members mailed to
    posse_at_peg.com
  • Qualifications
  • Be willing and able to dedicate a significant
    amount of time
  • Track the happenings on POSSENET daily
  • Participate in CRT activities by e-mail and phone
  • Foster open discussions
  • CRT members serve for a specified period of time

27
Community
  • The largest benefit from open source may not be
    extra developers!
  • "Open source developments that have a strong core
    of developers but never achieve large numbers of
    contributors beyond that core will be able to
    create new functionality but will fail because of
    a lack of resources devoted to finding and
    repairing defects in the released code.
  • Source "A Case Study of Open Source Software
    Development The Apache Server",
  • Proceedings of ICSE 2000

28
Community
  • There's an order of magnitude reduction moving
    along each level
  • Case Study of Mozilla
  • 1 in 20 users send a bug report
  • 1 in 100 files more than 5 bug reports
  • 1 in 500 submits a patch
  • 1 in 2000 are core developers

29
Release process
  • Anyone can see, download, and run the code at any
    time
  • There will be regular baseline versions of the
    code
  • some degree of QA
  • documentation of fixes and features
  • The baselines will not be supported by PSC
  • The community will provide support through the
    POSSENET site

30
Release process
PSC Features Release
2.2 Baseline
2.1 Baseline
Project B
3.0 (New Features)
Project A
Project C
2.0 (New Features)
2.0 (Maintenance)
PSC 9.1B
1.0 (Maintenance)
Bug Fixes
PSC Maintenance Release
PSC Patch Release
1.1 Baseline
1.2 Baseline
31
Roadmap
  • In the short term, POSSENET will provide bug
    fixes and extensions to existing tools
  • In the long term, major new tools and
    initiatives will be developed under POSSENET
  • The goal is to provide a comprehensive framework
    with many common elements for building successful
    4GL applications

32
Roadmap
  • Potential POSSENET projects
  • Design and runtime repository
  • Authentication / Login
  • User and Group maintenance
  • Authorization and runtime security
  • Session and configuration management
  • Source Code Control interface
  • Reporting tools interface
  • Code generation and interface generation

33
For more information
  • Open Source
  • http//www.opensource.org
  • http//www.oreilly.com
  • Open Source Licenses
  • http//www.stromian.com/Open_Source_Licensing.htm
  • http//www.hecker.org/writings/setting-up-shop.htm
    l
  • Progress Community
  • posse_at_peg.com

34
For more information
  • The Cathedral and the Bazaar
  • http//www.tuxedo.org/esr/writings/cathedral-baza
    ar/
  • Open Source Projects
  • http//www.sourceforge.net
  • http//www.openoffice.org
  • http//www.mozilla.org
  • http//www.netbeans.org

35
(No Transcript)
Write a Comment
User Comments (0)
About PowerShow.com