======================================
#opendaylight-meeting: TWS weekly call
======================================


Meeting started by Madhu at 17:06:02 UTC.  The full logs are available
at
http://meetings.opendaylight.org/opendaylight-meeting/2014/tws_weekly_call/opendaylight-meeting-tws_weekly_call.2014-08-18-17.06.log.html
.



Meeting summary
---------------

* Project level Helium docs  (Madhu, 17:06:28)
  * mlemay leading the discussion on Docs  (Madhu, 17:07:09)
  * LINK:
    https://s3.amazonaws.com/uploads.hipchat.com/32585/219117/2MRpGfCwURCnGDk/TWS%20-%20Docs%20%26%20DLUX.pptx
    mlemay 's PPT  (Madhu, 17:07:43)
  * mlemay says if you have any installation-specific isntructions,
    projects will have to add that (not in flow chart)  (tbachman,
    17:12:06)
  * audience fo operations guide is a sysadmin  (tbachman, 17:14:03)
  * audience for developer guide is SW developers  (tbachman, 17:14:11)
  * artifact is a feature of your project (e.g . did you create a GUI
    extension).  (tbachman, 17:15:01)
  * these docs are for non-project users/consumers.  This is why REST
    APIs are in the Developer Facing artifacts… these developers should
    be considered not part of the ODL development community, but instead
    developers that will leverage ODL when programming their network
    applications.  (phrobb, 17:15:08)
  * Carol Sanders asks about what’s on the wiki - how does that relate
    to docs artifact?  (tbachman, 17:19:23)
  * Q: How will we keep docs in the structured docs be kept in sync with
    wiki?  A:  Wiki is for community and is more fluid.  The structured
    docs are for users/consumers  (phrobb, 17:19:41)
  * mlemay says that the wiki is really an internal documentation
    mechanism, as it changes all the time  (tbachman, 17:19:42)
  * the material in the docs repo are considered source files that are
    managed in the same release process as the rest of the ODL projects.
    (phrobb, 17:21:29)
  * LINK: screenshot of the doc project file structure
    https://www.dropbox.com/s/1bkl4yf68ttcs07/Screenshot%202014-08-18%2013.22.30.png
    (networkstatic, 17:24:41)
  * LINK:
    https://www.dropbox.com/s/1bkl4yf68ttcs07/Screenshot%202014-08-18%2013.22.30.png
    <= screenshot of the doc project file strucure  (tbachman, 17:25:32)

* dlux modularity  (tbachman, 17:30:55)
  * Projects no longer have to go into DLUX project and submit their
    changes to the project  (tbachman, 17:31:32)
  * Projects can now create their own things and have it picked up by
    the DLUX UI  (tbachman, 17:31:54)
  * Projects start by creating a module extension  (tbachman, 17:32:13)
  * LINK: mlemay add a dlux module wiki
    https://wiki.opendaylight.org/view/OpenDaylight_dlux:Create_and_add_a_module
    (networkstatic, 17:32:51)
  * LINK:
    https://wiki.opendaylight.org/view/OpenDaylight_dlux:Create_and_add_a_module
    wiki page explaining how to add a module in dlux  (tbachman,
    17:33:40)
  * projects create a Resources JAR with all the javascript, which can
    be in a single bundle or separate JARs  (tbachman, 17:34:38)
  * the Resources JAR is unpacked into a separate Module Bundle.
    (tbachman, 17:35:08)
  * the Module Loader from the DLUX project is where a project’s module
    is registered  (tbachman, 17:35:35)
  * A project’s static files must be registered with the HTTPService
    (tbachman, 17:35:56)
  * new project UIs show up as separate folders in a navigation pane in
    the left of the UI  (tbachman, 17:40:13)
  * There’s a question outstanding for how/when to sunset the old GUI in
    favor of DLUX  (tbachman, 17:46:38)
  * LINK:
    https://jenkins.opendaylight.org/dlux/job/dlux-merge/35/org.opendaylight.dlux$dlux-web/
    <= bundle that can be included to bring up
    localhost:8080/dlux/index.html DLUX UI  (tbachman, 17:51:36)



Meeting ended at 17:53:38 UTC.



People present (lines said)
---------------------------

* tbachman (37)
* networkstatic (19)
* Madhu (11)
* phrobb (6)
* odl_meetbot (5)
* alagalah (1)



Generated by `MeetBot`_ 0.1.4