[yt-dev] Where should infrastructure information go?

[Matthew Turk]

That could work. Maybe Kacper should just push updates directly for that
ytep?

On Tue, Oct 6, 2015, 12:39 PM Cameron Hummels <chummels at 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 at 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 at 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 at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spacepope.org/pipermail/yt-dev-spacepope.org/attachments/20151006/95aee343/attachment.htm>