Where should infrastructure information go?
We are increasingly developing sets of infrastructure (docker files, CI scripts, etc) for developing, using and deploying yt. Where should we catalog this info? Should we continue updating the infrastructure ytep, or find a different/new place, perhaps auto-deployed? How can we increase discoverability of this info?
We could always start issuing additional yteps if the changes are significant enough. We could also update the relevant docs: installation, development, etc. On Tue, Oct 6, 2015 at 12:36 PM, Matthew Turk <matthewturk@gmail.com> wrote:
We are increasingly developing sets of infrastructure (docker files, CI scripts, etc) for developing, using and deploying yt. Where should we catalog this info? Should we continue updating the infrastructure ytep, or find a different/new place, perhaps auto-deployed? How can we increase discoverability of this info?
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Cameron Hummels NSF Postdoctoral Fellow Department of Astronomy California Institute of Technology http://chummels.org
That could work. Maybe Kacper should just push updates directly for that ytep? On Tue, Oct 6, 2015, 12:39 PM Cameron Hummels <chummels@gmail.com> wrote:
We could always start issuing additional yteps if the changes are significant enough. We could also update the relevant docs: installation, development, etc.
On Tue, Oct 6, 2015 at 12:36 PM, Matthew Turk <matthewturk@gmail.com> wrote:
We are increasingly developing sets of infrastructure (docker files, CI scripts, etc) for developing, using and deploying yt. Where should we catalog this info? Should we continue updating the infrastructure ytep, or find a different/new place, perhaps auto-deployed? How can we increase discoverability of this info?
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Cameron Hummels NSF Postdoctoral Fellow Department of Astronomy California Institute of Technology http://chummels.org _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
I think these sort of updates don't need detailed review. Substantive changes sure, but not merre technical changes. That said, I'm not sure a YTEP is a good place for e.g. a dockerfile. Maybe we just need an infrastructure repo? On Tue, Oct 6, 2015 at 2:55 PM, Matthew Turk <matthewturk@gmail.com> wrote:
That could work. Maybe Kacper should just push updates directly for that ytep?
On Tue, Oct 6, 2015, 12:39 PM Cameron Hummels <chummels@gmail.com> wrote:
We could always start issuing additional yteps if the changes are significant enough. We could also update the relevant docs: installation, development, etc.
On Tue, Oct 6, 2015 at 12:36 PM, Matthew Turk <matthewturk@gmail.com> wrote:
We are increasingly developing sets of infrastructure (docker files, CI scripts, etc) for developing, using and deploying yt. Where should we catalog this info? Should we continue updating the infrastructure ytep, or find a different/new place, perhaps auto-deployed? How can we increase discoverability of this info?
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Cameron Hummels NSF Postdoctoral Fellow Department of Astronomy California Institute of Technology http://chummels.org _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Well, I was thinking of it as more of a catalog of infra, not the dockerfiles themselves. I think I was unclear in my initial email. On Oct 6, 2015 12:59 PM, "Nathan Goldbaum" <nathan12343@gmail.com> wrote:
I think these sort of updates don't need detailed review. Substantive changes sure, but not merre technical changes.
That said, I'm not sure a YTEP is a good place for e.g. a dockerfile. Maybe we just need an infrastructure repo?
On Tue, Oct 6, 2015 at 2:55 PM, Matthew Turk <matthewturk@gmail.com> wrote:
That could work. Maybe Kacper should just push updates directly for that ytep?
On Tue, Oct 6, 2015, 12:39 PM Cameron Hummels <chummels@gmail.com> wrote:
We could always start issuing additional yteps if the changes are significant enough. We could also update the relevant docs: installation, development, etc.
On Tue, Oct 6, 2015 at 12:36 PM, Matthew Turk <matthewturk@gmail.com> wrote:
We are increasingly developing sets of infrastructure (docker files, CI scripts, etc) for developing, using and deploying yt. Where should we catalog this info? Should we continue updating the infrastructure ytep, or find a different/new place, perhaps auto-deployed? How can we increase discoverability of this info?
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Cameron Hummels NSF Postdoctoral Fellow Department of Astronomy California Institute of Technology http://chummels.org _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
I somehow completely missed this email. I can't even remember what was happening 6 days ago, but this is a discussion worth having. I think we do need better documentation of our infrastructure, both in narrative form and probably a repository of relevant files. Matt, if you have some ideas, maybe you could lay something out in more detail? On Tue, Oct 6, 2015 at 9:08 PM, Matthew Turk <matthewturk@gmail.com> wrote:
Well, I was thinking of it as more of a catalog of infra, not the dockerfiles themselves. I think I was unclear in my initial email. On Oct 6, 2015 12:59 PM, "Nathan Goldbaum" <nathan12343@gmail.com> wrote:
I think these sort of updates don't need detailed review. Substantive changes sure, but not merre technical changes.
That said, I'm not sure a YTEP is a good place for e.g. a dockerfile. Maybe we just need an infrastructure repo?
On Tue, Oct 6, 2015 at 2:55 PM, Matthew Turk <matthewturk@gmail.com> wrote:
That could work. Maybe Kacper should just push updates directly for that ytep?
On Tue, Oct 6, 2015, 12:39 PM Cameron Hummels <chummels@gmail.com> wrote:
We could always start issuing additional yteps if the changes are significant enough. We could also update the relevant docs: installation, development, etc.
On Tue, Oct 6, 2015 at 12:36 PM, Matthew Turk <matthewturk@gmail.com> wrote:
We are increasingly developing sets of infrastructure (docker files, CI scripts, etc) for developing, using and deploying yt. Where should we catalog this info? Should we continue updating the infrastructure ytep, or find a different/new place, perhaps auto-deployed? How can we increase discoverability of this info?
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Cameron Hummels NSF Postdoctoral Fellow Department of Astronomy California Institute of Technology http://chummels.org _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
participants (4)
-
Britton Smith -
Cameron Hummels -
Matthew Turk -
Nathan Goldbaum