Wouldn't this be a good time to discuss other types of URLs?
Eg:
* Documentation
* CI status (in the many different flavors)
* Issue tracker
* Forum/mailing list
* Support place
After all, there's nothing special about docker images - every project is
going to have a different special thing at s
On 3 February 2015 at 11:08, Nick Coghlan wrote:
> Microsoft actually support Linux containers on Azure and are working with
> Docker to support Windows containers on Windows. Everybody gets containers!
> :)
Cool, can't wait :-) At the moment, the Docker install for Windows
includes VirtualBox an
On 3 Feb 2015 19:10, "Paul Moore" wrote:
>
> On 1 February 2015 at 03:54, Nick Coghlan wrote:
> > I agree that from an implementation perspective, this could just be a
> > new recommended URL in the project URLs metadata (e.g. "Reference
> > Container Images"). If folks don't think the idea sound
On 1 February 2015 at 03:54, Nick Coghlan wrote:
> I agree that from an implementation perspective, this could just be a
> new recommended URL in the project URLs metadata (e.g. "Reference
> Container Images"). If folks don't think the idea sounds horrible,
> I'll make that update to the PEP 459 d
On 3 Feb 2015 18:36, "Ionel Cristian Mărieș" wrote:
>
> Wouldn't this be a good time to discuss other types of URLs?
>
> Eg:
>
> * Documentation
> * CI status (in the many different flavors)
> * Issue tracker
> * Forum/mailing list
> * Support place
>
> After all, there's nothing special about doc
On 3 February 2015 at 16:01, Marcus Smith wrote:
>
>> As a possible interim approach to improving the situation, what do you
>> think of my writing up a "Binary distribution for Linux" advanced
>> topic? That could cover not only containers, but also the technique of
>> "bundle a /opt virtualenv i
> As a possible interim approach to improving the situation, what do you
> think of my writing up a "Binary distribution for Linux" advanced
> topic? That could cover not only containers, but also the technique of
> "bundle a /opt virtualenv in a platform binary package" as well as
> actually creat
On 2 February 2015 at 03:04, Marcus Smith wrote:
>
>> I agree that from an implementation perspective, this could just be a
>> new recommended URL in the project URLs metadata (e.g. "Reference
>> Container Images"). If folks don't think the idea sounds horrible,
>> I'll make that update to the PEP
> I agree that from an implementation perspective, this could just be a
> new recommended URL in the project URLs metadata (e.g. "Reference
> Container Images"). If folks don't think the idea sounds horrible,
> I'll make that update to the PEP 459 draft.
>
wouldn't this just be a use case for a cu
On 1 February 2015 at 11:01, Donald Stufft wrote:
> Do you expect some automated tool to take advantage of this link?
>
> In other words, what’s the benefit over just having a link to the docker
> container in the long_description or in the metadata 2.0 project urls?
I agree that from an implemen
> On Jan 31, 2015, at 7:43 PM, Nick Coghlan wrote:
>
> One of the recurring problems folks mention here is how to deal with
> the complexities of handling Linux ABI compatibility issues.
>
> That's a genuinely hard problem, and not one that *anyone* has solved
> well - it's one of the reasons b
One of the recurring problems folks mention here is how to deal with
the complexities of handling Linux ABI compatibility issues.
That's a genuinely hard problem, and not one that *anyone* has solved
well - it's one of the reasons being an independent software vendor
for Linux in general (rather t
12 matches
Mail list logo
