[publican-list] [Bug 447825] New: Need a plugin for the ovirt brand for oVirt docs

[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 report.




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

           Summary: Need a plugin for the ovirt brand for oVirt docs
           Product: Red Hat Enterprise Linux 5
           Version: 5.2
          Platform: All
               URL: http://ovirt.org
        OS/Version: Linux
            Status: NEW
          Severity: medium
          Priority: medium
         Component: publican
        AssignedTo: jfearn at redhat.com
        ReportedBy: sburgess at redhat.com
         QAContact: mhideo at redhat.com
                CC: publican-list at redhat.com


>From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.12) Gecko/20080213 Red Hat/1.5.0.12-11.el5_1 Firefox/1.5.0.12

Description of problem:
Please create a plugin for the ovirt brand. Please see the website ovirt.org for the colours etc. Email trail below:

Susan Burgess wrote:
> Hi Mike and Perry,
>
> Thanks for clearing that up.
> Mike, so I will raise a ticket for Andy to create  the ovirt brand plugin for publican.
>
> and the ovirt doc will have this licensing model:
> --------
> http://opencontent.org/openpub/
>
> Under Section VI: License Options
>
> "B. To prohibit any publication of this work or derivative works in whole or in part in standard (paper) book form for commercial purposes unless prior permission is obtained from the copyright holder."
>
> That's it, the community can do what they desire, even create commercial derivatives. They simply cannot print it (and translations) and sell paper versions in bookstores without RH's permission.


Raise a bug against the publican package requesting a new brand. Andy will take it from there in terms of the assets he needs to collect from the ovirt team and report back once the package is complete.


> -------------------
>
> Thanks
> Susan
>
> Perry N. Myers wrote:
>> Michael Hideo Smith wrote:
>>> Perry N. Myers wrote:
>>>> Mike,
>>>>
>>>>
>>>> Susan has been working on documentation (a usage/installation guide) and the doc is taking shape nicely.  The doc right now is Red Hat branded and has the Red Hat documentation license on it (which according to Susan is the OPL with an additional restriction placed on it stating that you must ask permission before using the documentation in your own product)
>>>>
>>>
>>> http://opencontent.org/openpub/
>>>
>>> Under Section VI: License Options
>>>
>>> "B. To prohibit any publication of this work or derivative works in whole or in part in standard (paper) book form for commercial purposes unless prior permission is obtained from the copyright holder."
>>>
>>> That's it, the community can do what they desire, even create commercial derivatives. They simply cannot print it (and translations) and sell paper versions in bookstores without RH's permission.
>>
>> That seems reasonable and I don't have any issues with it.
>>
>>>> (If my understanding of this is incorrect, please correct me)
>>>>
>>>> We would like to be able to include the material that Susan has worked on on the ovirt.org site and as part of the online help embedded in the oVirt RPMs.  But we're concerned about having Red Hat branded documentation on a project that is not really owned by Red Hat.  Susan says the Red Hat docs license is OSI certified.  If this is true, then that license should be fine.  But if it is not, we would also be concerned about hosting docs with a non-OSI license on an open source project.
>>>>
>>>> What we were thinking would make the most sense would be to use the oVirt logos on ovirt.org to create an ovirt branding for our community documentation.  And then for the product release we could simply rebrand the ovirt.org documentation with the standard Red Hat templates.  (Aside from logos and color schemes, most likely all of the screen shots will need to be replaced as well since the application will likely be reskinned for the Red Hat product)
>>>>
>>>
>>> I agree that an ovirt brand/badging would be best suited for the .org side. We have that functionality. let us know if you want us to create an ovirt brand plugin for publican to handle this.
>>
>> Yes, we would like an ovirt brand plugin.  The color scheme/logos can just be taken from the ovirt.org website.  If are other things you need for creating this branding, let us know.
>>
>> Thanks!
>>
>> Perry
>


Version-Release number of selected component (if applicable):


How reproducible:
Always


Steps to Reproduce:
N/A

Actual Results:
N/A

Expected Results:
Need a different brand

Additional info:
I've put it as a medium bug, but I need it by the 6th June please.

-- 
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, or are watching someone who is.