Irssi for OpenSolaris [LSARC/2008/481 FastTrack timeout 08/05/2008]
shiying huang
Irene.Huang at sun.com
Mon Aug 11 17:17:23 PDT 2008
Close approved.
--Irene
On Mon, 2008-08-11 at 11:39, Irene Huang wrote:
> Contract signing does not block the ARC case. We're still working on the
> contract.
>
> If there's any comments on the updated proposal, please send an email
> within 24 hours. If not, I'll close this case then.
>
> Thanks
>
> --irene
>
> On Wed, 2008-08-06 at 11:20 +0800, Henry Zhang wrote:
> > Hi John,
> >
> > Updated..
> >
> > Thanks,
> > Henry
> >
> > John Plocher д:
> > > Henry Zhang wrote:
> > >> Below is the proposal, I added the libOpenSSL into interface list, and
> > >> the contract is ongoing....
> > >
> > >
> > >> 4.5. Interfaces:
> > >>
> > >> Imported Interfaces
> > >> Interface Stability Comments
> > >> ------------------- ----------- -----------------------------------
> > >>
> > >> libOpenSSL Uncommitted PSARC/2006/019/, contract is ongoing
> > >
> > > The interface stability of OpenSSL is either "External" (which maps to "Volatile"
> > > based on the rationale given) or "Contract Private", and not "Uncommitted".
> > >
> > > (The mail log for 2006/019 says " ...the interface was classified as External
> > > because of very unstable nature of OpenSSL interface, binary/API
> > > incompatibilites ... were to be expected.")
> > >
> > > -John
> > >
> > plain text document attachment (one-pager-irssi.txt)
> > Template Version: @(#)onepager.txt 1.29 04/11/15 SMI
> >
> > This information is Sun Proprietary/Confidential: Internal Use Only:
> > Engineering Need-to-Know
> >
> > 1. Introduction
> >
> > 1.1. Project/Component Working Name:
> >
> > Irssi
> >
> > 1.2. Name of Document Author/Supplier:
> >
> > Henry Zhang (hua.zhang at sun.com)
> >
> > 1.3. Date of This Document:
> >
> > 18/07/08
> >
> > 1.4. Name of Major Document Customer(s)/Consumer(s):
> >
> > 1.4.1. The PAC or CPT you expect to review your project:
> >
> > Solaris PAC
> >
> > 1.4.2. The ARC(s) you expect to review your project:
> >
> > LSARC
> >
> > 1.4.3. The Director/VP who is "Sponsoring" this project:
> >
> > Robert.Odea at Sun.Com
> >
> > 1.4.4. The name of your business unit:
> >
> > JDS Desktop Engineering, OPG
> >
> > 1.5. Email Aliases:
> > 1.5.1. Responsible Manager: leo.binchy at Sun.COM
> > 1.5.2. Responsible Engineer: hua.zhang at Sun.COM
> > 1.5.3. Marketing Manager: dan.roberts at sun.com
> > 1.5.4. Interest List: irssi at sun.com
> >
> > 2. Project Summary
> >
> > 2.1. Project Description:
> >
> > Irssi is a terminal based IRC client for UNIX systems.
> >
> >
> > 2.2. Risks and Assumptions:
> >
> > 1. INSTALL claim that there is some problem on Perl, Perl 5.004 doesn't work
> > by default, we'll need to edit src/perl/irssi-core.pl and remove all
> > lines with "delete_package" in them. We have 5.8 on Solaris, so can ignore
> > this issue.
> >
> >
> > 3. Business Summary
> >
> > 3.1. Problem Area:
> >
> > Irssi is a powerfull console-based irc client, making this tool ready to
> > provide an excellent communicating tool to those users who used to the
> > text mode IRC, and prefer this type of tool still.
> >
> >
> > 3.2. Market/Requester:
> >
> > JDS Desktop group
> >
> > 3.3. Business Justification:
> > Irssi is a very good text-based irc client, can be used in any terminal.
> > It can provide the intuitive and easy way for user to chat each other.
> > It also supports SILC and ICB protocols via plugins.
> > It's customizable, user can write perl scripts to add the new feature.
> >
> >
> > 3.4. Competitive Analysis:
> >
> > There are lots of IRC client in Unix world, e.g. ircii,
> > There are also the GUI IRC client, for example Xchat, Pidgin.
> >
> > 3.5. Opportunity Window/Exposure:
> >
> > It is expected that this project will be integrated into Nevada B100.
> >
> > 3.6. How will you know when you are done?:
> >
> > When it is ported to Nevada and runs correctly.
> >
> > The project will be complete when there are no stoppers, P1 or P2 bugs.
> >
> > 4. Technical Description:
> >
> > 4.1. Details:
> >
> > Irssi is a text-only IRC client for Unix-ish platforms, it's such an
> > easy and comfortable client to use, Irssi can range from a functional,
> > no-frills client to a highly-customized and automated client. It features
> > a text mode user interface, modularity, multi-server connectivity,
> > tab completion and a lot of automation.
> >
> > One of the many great features of Irssi is its Perl scripting support,
> > you can write your script, and lots of well implemented scripts can be
> > found on irssi’s script archive. Non-standard features are implemented
> > with these perl scripts, rather than in the core, so most non-standard
> > functionality is added through the use of perl scripts. At irssi.org/scripts,
> > there is a large database of these scripts available. To use them, download
> > the perl scripts to your ~/.irssi/scripts directory, then you can run them.
> >
> > Irssi is a modular IRC client that currently has only text mode user
> > interface, but 80-90% of the code isn't text mode specific, so other
> > UIs could be created pretty easily. Also, Irssi isn't really even IRC
> > specific anymore, there's already a working SILC (http://www.silcnet.org)
> > module available. Support for other protocols like ICQ could be created
> > some day too.
> >
> > In fact, there are some GUI IRC tool, e.g. Xchat, but someone still like
> > to use this terminal-based IRC, because it can be configured manually to
> > meet the different requirements, you can run lots of command to configure
> > your Irssi, you even can download or write some Perl scripts for some
> > special purpose.
> >
> > Features:
> > - Optional automation
> > - Multiserver friendy
> > - Channel automation
> > - Window content saving
> > - Tab completing anything
> > - Excellent logging
> > - Excellent ignoring
> > - Lastlog and scrollback handling
> >
> > 4.2. Bug/RFE Number(s):
> >
> > N/A
> >
> > 4.3. In Scope:
> >
> > The default functions and feature in core
> >
> > 4.4. Out of Scope:
> >
> > The new functions added by non-standard scripts
> >
> > 4.5. Interfaces:
> >
> > Imported Interfaces
> > Interface Stability Comments
> > ------------------- ----------- -----------------------------------
> >
> > libperl Uncommitted PSARC/2001/145
> > libOpenSSL Contract Private PSARC/2006/019/
> > GNOME Committed Platform Libraries Committed LSARC/2007/520 GTK+ library
> > GNOME 2.20
> >
> > Exported Interfaces Stability Comments
> > ------------------------- ------------- ---------------------------------
> >
> > /usr/bin/irssi Volatile
> > SUNWirssi Uncommitted Package name
> >
> > 4.6. Doc Impact:
> >
> > Man page exist already.
> >
> > 4.7. Admin/Config Impact:
> >
> > There are no changes to the system administration and configuration.
> >
> > 4.8. HA Impact:
> >
> > N/A
> >
> > 4.9. I18N/L10N Impact:
> >
> > Not to be needed
> >
> > 4.10. Packaging & Delivery:
> >
> > The new packages are:
> >
> > - SUNWirssi
> >
> >
> > 4.11. Security Impact:
> >
> > There is no additional security impact for Solaris.
> >
> > 4.12. Dependencies:
> >
> > Glib >=2.0
> > libperl
> >
> > 5. Reference Documents:
> >
> > Irssi main project page:
> > http://irssi.org
> >
> >
> > 6. Resources and Schedule:
> >
> > 6.1. Projected Availability:
> >
> > Expect to integrated into Nevada in build 100 in Q3 2008
> >
> > 6.2. Cost of Effort:
> >
> > Development 1.0 Engineers - 1 Months
> > Testing 0.5 Engineers - 1 Week
> > RE 0.5 Engineers - 1 Week
> >
> > 6.3. Cost of Capital Resources:
> >
> > N/A
> >
> > 6.4. Product Approval Committee requested information:
> >
> > 6.4.1. Consolidation or Component Name:
> >
> > JDS / OpenSolaris
> >
> > 6.4.3. Type of CPT Review and Approval expected:
> >
> > Standard
> >
> > 6.4.4. Project Boundary Conditions:
> >
> > None
> >
> > 6.4.5. Is this a necessary project for OEM agreements:
> >
> > No
> >
> > 6.4.6. Notes:
> >
> > N/A
> >
> > 6.4.7. Target RTI Date/Release:
> >
> > Nevada B100 - Sep. 2008
> >
> > 6.4.8. Target Code Design Review Date:
> >
> > Sep. 2008
> >
> > 6.4.9. Update approval addition:
> >
> > New project, no Solaris PAC approval yet
> >
> > 6.5. ARC review type:
> >
> > FastTrack
> >
> > 7. Prototype Availability:
> >
> > 7.1. Prototype Availability:
> >
> > Sep. 2008
> >
> > 7.2. Prototype Cost:
> >
> > 1 engineer
> > 1 QA
> > 1 RE
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20080812/0916c29d/attachment.html>
More information about the opensolaris-arc
mailing list