<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>3509</bug_id>
          
          <creation_ts>2012-11-28 20:12:17 +0000</creation_ts>
          <short_desc>Need better Yocto Project Documentation Components</short_desc>
          <delta_ts>2014-10-07 15:39:43 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>5</classification_id>
          <classification>Infrastructure</classification>
          <product>Bugzilla</product>
          <component>bugzilla</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard>17 June 2014: IN PROGRESS REVIEW</status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>Future</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Scott Rifenbark">srifenbark</reporter>
          <assigned_to name="Michael Halstead">mhalstead</assigned_to>
          <cc>infras.bug.watcher</cc>
    
    <cc>Infras.watcher</cc>
    
    <cc>sgw</cc>
    
    <cc>srifenbark</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>No (bug/feature does not impact docs)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>27808</commentid>
    <comment_count>0</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2012-11-28 20:12:17 +0000</bug_when>
    <thetext>we need a general classification of &quot;Documentation&quot;, which I think we have and then the documentation components need to break out into the available manuals:

* Reference Manual
* Quick Start
* Kernel Architecture Manual
* BSP Guide
* Development Manual
* Application Developer&apos;s Guide
* Mega-manual
* general

This way when you find a bug against a YP manual you can specifically identify the exact manual. We could use &quot;general&quot; for documentation problems that can&apos;t be sourced to a specific manual (e.g. new features, stuff that spreads across multiple manuals, etc.)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>29725</commentid>
    <comment_count>1</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2013-02-11 20:52:11 +0000</bug_when>
    <thetext>the components for the YP documentation set have changed:

* ref-manual - Yocto Project Reference Manual
* yocto-project-qs - Yocto Project Quick Start
* kernel-dev - Yocto Project Linux Kernel Development Manual
* profile-manual - Yocto Project Profiling and Tracing Manual
* bsp-guide - Yocto Project Board Support Package (BSP) Developer&apos;s Guide
* adt-manual - Yocto Project Application Developer&apos;s Guide
* mega-manual - (no title for this document)

We need a component for each of these manuals so bugs can be filed against them individually.  We also need a case where we file a bug against the documentation in general with no associated manual.  

Scott</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>29727</commentid>
    <comment_count>2</comment_count>
    <who name="Michael Halstead">mhalstead</who>
    <bug_when>2013-02-11 21:08:04 +0000</bug_when>
    <thetext>I&apos;ll add mega-manual. Is the development manual no longer needed? Is profile-manual is a component of the developer manual or ADT/SDK docs?

* profile-manual - Yocto Project Profiling and Tracing Manual
* mega-manual - (no title for this document)

Do you still need a category for general documentation bugs?


These five are represented. I&apos;ll update the descriptions where needed. Visit https://bugzilla.yoctoproject.org/enter_bug.cgi?classification=Documentation to see them all at once.

* ref-manual - Yocto Project Reference Manual
* yocto-project-qs - Yocto Project Quick Start
* kernel-dev - Yocto Project Linux Kernel Development Manual
* bsp-guide - Yocto Project Board Support Package (BSP) Developer&apos;s Guide
* adt-manual - Yocto Project Application Developer&apos;s Guide</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>29728</commentid>
    <comment_count>3</comment_count>
    <who name="Michael Halstead">mhalstead</who>
    <bug_when>2013-02-11 21:36:50 +0000</bug_when>
    <thetext>I&apos;ve added a general section. https://bugzilla.yoctoproject.org/describecomponents.cgi?product=General%20Docs 

And a mega-manual product
https://bugzilla.yoctoproject.org/describecomponents.cgi?product=Mega%20Manual

I&apos;m adding version information now.


These questions are still relevant. 
Is the development manual no longer needed? Is profile-manual is a component of the developer manual or ADT/SDK docs?

* profile-manual - Yocto Project Profiling and Tracing Manual</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>29735</commentid>
    <comment_count>4</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2013-02-12 00:24:51 +0000</bug_when>
    <thetext>Michael, 

I forgot the development manual:

* dev-manual - Yocto Project Development Manual

Profile manual is a new manual as is the kernel-dev manual.  The old kernel manual (kernel-manual) will be gone for 1.4.  

The adt-manual still exists but has a different title - Yocto Project Application Developer&apos;s Guide.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>38382</commentid>
    <comment_count>5</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2013-10-31 17:54:20 +0000</bug_when>
    <thetext>Michael, 

Documentation components are now the following:

* Reference Manual
* Quick Start
* Linux Kernel Development Manual
* BSP Guide
* Development Manual
* Application Developer&apos;s Guide
* Profile and Tracing Manual
* Mega-manual
* General

Can we get these categories under documentation?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>38393</commentid>
    <comment_count>6</comment_count>
    <who name="Michael Halstead">mhalstead</who>
    <bug_when>2013-10-31 18:45:11 +0000</bug_when>
    <thetext>* Reference Manual (https://bugzilla.yoctoproject.org/describecomponents.cgi?product=Reference)

* Quick Start (https://bugzilla.yoctoproject.org/describecomponents.cgi?product=Quick%20Start)

* Linux Kernel Development Manual this is currently called Kernel Development manual. Do we need to rename it? (https://bugzilla.yoctoproject.org/describecomponents.cgi?product=Kernel%20Development)

* BSP Guide, renamed (https://bugzilla.yoctoproject.org/describecomponents.cgi?product=BSP%20Guide)

* Development Manual, renamed (https://bugzilla.yoctoproject.org/describecomponents.cgi?product=Development%20Manual)

* Application Developer&apos;s Guide is part of ADT Docs. Does it need a separate listing? (https://bugzilla.yoctoproject.org/describecomponents.cgi?product=ADT%20Docs)

* Profile and Tracing Manual, renamed (https://bugzilla.yoctoproject.org/describecomponents.cgi?product=Profile%20and%20Tracing%20Manual)

* Mega-manual (https://bugzilla.yoctoproject.org/describecomponents.cgi?product=Mega%20Manual)

* general (https://bugzilla.yoctoproject.org/describecomponents.cgi?product=General%20Docs)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>38404</commentid>
    <comment_count>7</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2013-10-31 20:50:35 +0000</bug_when>
    <thetext>Kernel Development Manual is fine.  No need to rename that.

What else is part of ADT Docs?  All I know about is the Application Developer&apos;s Guide.  The old manual was call the ADT manual, which is moot.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>43999</commentid>
    <comment_count>8</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2014-06-17 08:11:30 +0000</bug_when>
    <thetext>Michael, 

We probably need one now for the BitBake User Manual as it is published alongside the YP documentation.  The only other issue with this is that ADT manual.  There should only be a single manual.  Application Developer&apos;s Guide.  This should not be a part of &quot;ADT Docs&quot;  We don&apos;t need an &quot;ADT Docs&quot; category.

Thanks, 
Scott</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>46072</commentid>
    <comment_count>9</comment_count>
    <who name="Michael Halstead">mhalstead</who>
    <bug_when>2014-10-03 01:42:32 +0000</bug_when>
    <thetext>I&apos;ve added the BitBake User Manual product and component.

I can&apos;t remove or hide ADT Docs while there are open bugs assigned there. I can rename it though. Would that work?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>46125</commentid>
    <comment_count>10</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2014-10-06 15:34:45 +0000</bug_when>
    <thetext>Michael, 

I think we are good on this now.  All the manuals are covered and the description of the &quot;ADT Docs&quot; notes that it is the application development manual, which is the real title.  I suppose if you wanted to and it was not too much trouble you could rename &quot;ADT Docs&quot; to &quot;ADT Manual&quot;. 

Thanks, 
Scott</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>46176</commentid>
    <comment_count>11</comment_count>
    <who name="Michael Halstead">mhalstead</who>
    <bug_when>2014-10-07 15:39:43 +0000</bug_when>
    <thetext>Rename complete.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>