On 01/17/2013 04:01 AM, Andreas Tille wrote: > Hi Adam, > > thanks for your ITP. I'd (strongly) recommend using a less generic > name. Why not sticking to the upstream choice "sosreport"? > > BTW, after reading the description twice I totally fail to tell what > this package might really do. After reading the very short description > on the github page I wonder how this might fit together at all. > > For instance please define or give examples for things like > "organisations", "plugins", "report", "software packages" because I > somehow have the feeling that these terms are used in different context > than I'm usually doing. > > Kind regards > > Andreas. > > On Wed, Jan 16, 2013 at 11:27:07PM -0500, Adam Stokes wrote: >> Package: wnpp >> Severity: wishlist >> Owner: Adam Stokes <adam-sto...@ubuntu.com> >> >> * Package name : sos >> Version : 2.3.1 >> Upstream Author : Adam Stokes <adam-sto...@ubuntu.com> >> * URL : https://github.com/sosreport/sosreport >> * License : GPL2+ >> Programming Lang: Python >> Description : This set of tools is designed to provide information to >> support organizations >> >> This set of tools is designed to provide information to support >> organizations in an extensible manner, allowing third parties, package >> maintainers, >> and anyone else to provide plugins that will collect and report information >> that is useful for supporting software packages. > >
* Package name : sosreport Version : 2.3.1 Upstream Author : Adam Stokes <adam-sto...@ubuntu.com> * URL : https://github.com/sosreport/sosreport * License : GPL2+ Programming Lang: Python Description : A tool for taking a snapshot of a system's properties at given point of time. This set of tools provides end users with the ability to take a snapshot of their system customizable and _automated_ through plugins. A snapshot of a system consists of but not limited too Filesystem layout, installed packages, application configurations. Additional mechanisms are available to print out reports based on rulesets that allow end users to preemptively check for existing bug reports based on analyzed logs and common configurations. One of the common use cases for this application is when an end user is working with another person in an attempt to troubleshoot an issue and that person would like to see an overall layout of the end user's current system with any relevant application configurations/logs. This application proves to be very beneficial in large organizations/enterprises where you may have a technical team that provides support for any number of customers/clients/end users. Sosreport is also multi-distribution aware which already provides support for Fedora and Debian/Ubuntu. Sosreport also differs from applications such as abrt and apport which tend to concentrate more on detecting and analyzing application crashes. Thank you Adam -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50f868a4.5000...@canonical.com
