==============================================
#fedora-meeting-2: Env and Stacks (2015-02-26)
==============================================


Meeting started by hhorak at 13:02:49 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-2/2015-02-26/env-and-stacks.2015-02-26-13.02.log.html
.



Meeting summary
---------------
* init process  (hhorak, 13:03:21)

* Removing 'scls' from %{_sysconfdir} and %{_localstatedir}  (hhorak,
  13:07:05)
  * LINK:
    https://www.redhat.com/archives/sclorg/2015-February/msg00032.html
    (hhorak, 13:07:30)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1066665#c8
    (hhorak, 13:10:27)
  * HELP:   (hhorak, 13:21:53)
  * AGREED: The preferred way for collections in Fedora is to use a
    directory under /opt/<vendor>, which allows to categorize content
    from one vendor (e.g. /opt/fedora/scls)  (hhorak, 13:30:18)
  * AGREED: to use scls for "directory for collections" rather than scl
    (hhorak, 13:40:09)

* Follow-ups: Dockerfiles recommended tips  (hhorak, 13:40:52)
  * having some docker.fedoraproject.org will be very beneficial
    (hhorak, 13:55:01)
  * IDEA: content should focus on "docker in Fedora" and developer
    workflow for container based deployments, not that on "what is
    Docker?"  (hhorak, 13:55:01)
  * IDEA: making DevAssistant fedora-dockerfiles aware would be quite
    neat  (hhorak, 13:55:30)

Meeting ended at 14:08:47 UTC.




Action Items
------------





Action Items, by person
-----------------------
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* phracek (62)
* ncoghlan (58)
* hhorak (46)
* bkabrda1 (30)
* ttomecek (24)
* juhp (22)
* zodbot (4)
* langdon (3)
* ttomecek1 (1)
* bkabrda (0)
* sicampbell (0)
* vpavlin (0)
* walters (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Reply via email to