[Bug 459088] New: Review Request: protobuf - Protocol Buffers - Google's data interchange format

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: Review Request: protobuf - Protocol Buffers - Google's data interchange format

https://bugzilla.redhat.com/show_bug.cgi?id=459088

           Summary: Review Request: protobuf - Protocol Buffers - Google's
                    data interchange format
           Product: Fedora
           Version: rawhide
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: medium
          Priority: medium
         Component: Package Review
        AssignedTo: nobody at fedoraproject.org
        ReportedBy: shamardin at gmail.com
         QAContact: extras-qa at fedoraproject.org
                CC: notting at redhat.com, fedora-package-review at redhat.com
   Estimated Hours: 0.0
    Classification: Fedora


Spec URL: http://shamardin.googlepages.com/protobuf.spec
SRPM URL: http://shamardin.googlepages.com/protobuf-2.0.0-0.1.beta.fc8.src.rpm
Description:

Protocol Buffers are a way of encoding structured data in an efficient
yet extensible format. Google uses Protocol Buffers for almost all of
its internal RPC protocols and file formats.

Protocol buffers are a flexible, efficient, automated mechanism for
serializing structured data – think XML, but smaller, faster, and
simpler. You define how you want your data to be structured once, then
you can use special generated source code to easily write and read
your structured data to and from a variety of data streams and using a
variety of languages. You can even update your data structure without
breaking deployed programs that are compiled against the "old" format.

Project homepage: http://code.google.com/p/protobuf/

This is my first package for Fedora and I am seeking for a sponsor.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.