With:
$ sed -i 's/[[:space:]]*$//' README.md
fixing some trailing whitespace that snuck in with ca0803d1
(Additional language for conformance statement, 2016-04-06, #374).
Future occurrences should be caught by git-validation, which checks
for whitespace issues since [1,2].
[1]: https://github.com/vbatts/git-validation/pull/7
[2]: https://github.com/vbatts/git-validation/pull/9
Signed-off-by: W. Trevor King <wking@tremily.us>
Weekly call is for all OCI projects and per discussion on today's call,
updates to indicate the call is for all OCI projects (rather than having
multiple calls.)
And updates time zone description from PST/PDT to Pacific time
Signed-off-by: Rob Dolin <RobDolin@microsoft.com>
Proposed additional conformance language to support future certification work (cribbed from https://tools.ietf.org/html/rfc2616).
Signed-off-by: Stephen R. Walli <stephen.walli@gmail.com>
This is style information, even though it's about the spec and not
about the behavior covered by the spec. The Go-pointer rule is also
about more peripheral stuff though, and the README has a lot of stuff
in it, so it seems like a better fit after the move.
Signed-off-by: W. Trevor King <wking@tremily.us>
The only reference was removed in 15a43acd (ReadMe: Replace BlueJeans
with UberConference, 2016-02-24, #326).
Signed-off-by: W. Trevor King <wking@tremily.us>
Update the Table of Contents section of the ReadMe.md to match the order
of the merged MarkDown files in the printable HTML and PDF outputs
Signed-off-by: Rob Dolin <RobDolin@microsoft.com>
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
Reverting 7232e4b1 (specs: introduce the concept of a runtime.json,
2015-07-30, #88) after discussion on the mailing list [1]. The main
reason is that it's hard to draw a clear line around "inherently
runtime-specific" or "non-portable", so we shouldn't try to do that in
the spec. Folks who want to flag settings as non-portable for their
own system are welcome to do so (e.g. "we will clobber 'hooks' in
bundles we run") are welcome to do so, but we don't have to have
to split the config into multiple files to do that.
There have been a number of additional changes since #88, so this
isn't a pure Git reversion. Besides copy-pasting and the associated
link-target updates, I've:
* Restored path -> destination, now that the mount type contains both
source and target paths again. I'd prefer 'target' to 'destination'
to match mount(2), but the pre-7232e4b1 phrasing was 'destination'
(possibly due to Windows using 'target' for the source?).
* Restored the Windows mount example to its pre-7232e4b1 content.
* Removed required mounts from the config example (requirements landed
in 3848a238, config-linux: specify the default devices/filesystems
available, 2015-09-09, #164), because specifying those mounts in the
config is now redundant.
* Used headers (vs. bold paragraphs) to set off mount examples so we
get link anchors in the rendered Markdown.
* Replaced references to runtime.json with references to config.json.
[1]: https://groups.google.com/a/opencontainers.org/forum/#!topic/dev/0QbyJDM9fWY
Subject: Single, unified config file (i.e. rolling back specs#88)
Date: Wed, 4 Nov 2015 09:53:20 -0800
Message-ID: <20151104175320.GC24652@odin.tremily.us>
Signed-off-by: W. Trevor King <wking@tremily.us>
Lets call out some users directly and give them titles. Then define what
they is trying to do.
Signed-off-by: Brandon Philips <brandon.philips@coreos.com>
So we have something to cite to avoid rehashing established decisions.
Provide some motivation and links to the backing discussion so folks
can re-open these if they have new information that wasn't covered in
the original decision.
Like the glossary (18734986, glossary: Provide a quick overview of
important terms, 2015-08-11, #107), I've used subsection titles for
each entry to get link anchors.
Signed-off-by: W. Trevor King <wking@tremily.us>
And link them to the more detailed specification.
Subsection titles for the entries will be obnoxiously spacious, but
the other alternatives seem worse:
a. An HTML definition list (<dl>) would have nice default styling, but
it's annoying to write raw HTML. And we would have needed
something like:
<dt name="bundle">Bundle</dt>
<dd>
A [directory structure](bundle.md) that is...
</dd>
to get Markdown-style links in the defintion itself.
b. A Markdown list (* ...) would have reasonable default styling, but
there's no Markdown syntax for adding anchors to the entries. And
a glossary is much less useful if you can't link to a specific
entry.
Signed-off-by: W. Trevor King <wking@tremily.us>
In #opencontainers after today's meeting, here's the source for the
change from Google Hangouts to BlueJeans:
12:01 < wking> Is the BlueJeans approach going to be our standard
procedure? If so, I can file a PR updating our weekly-meeting docs
(which still talk about YouTube and Google Hangouts)
12:03 < mrunalp> wking: Yeah, I think so.
12:04 < wking> ok. And it's just going to "push the BlueJeans link to
IRC and the list before the meeting"? Or does BlueJeans have stable
channel URLs or similar?
12:05 < mrunalp> wking: The URL that we used today is stable.
Signed-off-by: W. Trevor King <wking@tremily.us>
On Mon, Aug 10, 2015 at 09:38:50AM -0700, Mrunal Patel wrote [1]:
> There is a limit of 10 participants per hangout. So, I will
> broadcast it at the time when it starts and people who aren't
> invited could view the stream and discuss on IRC.
On Mon, Aug 10, 2015 at 09:53:59AM -0700, Mrunal Patel wrote [2]:
> I think the youtube channel should work as the broadcast link
> https://www.youtube.com/channel/UC1wmLdEYmwWcsFg7bt1s5nw
The IRC channel location is from opencontainers/web@f693390f (updated
content, 2015-06-21).
[1]: https://groups.google.com/a/opencontainers.org/d/msg/dev/Cy5uFI_ySpg/E1FnYUmfDwAJ
From: Mrunal Patel
Subject: Re: Discussions and Notes
Date: Mon, 10 Aug 2015 09:38:50 -0700
Message-ID: <CANEZBD7K=8+i7RaTAkg_0XLUSQrZLykGR0bxce-JtErO8KAQ1Q@mail.gmail.com>
Cc: dev <dev@opencontainers.org>, ...
[2]: https://groups.google.com/a/opencontainers.org/d/msg/dev/Cy5uFI_ySpg/X4RQEx2gDwAJ
From: Mrunal Patel
Subject: Re: Discussions and Notes
Date: Mon, 10 Aug 2015 09:53:59 -0700
Message-ID: <CANEZBD7snSro5GXYc6QRuk3+KnR0WAeFThfQXvOcnx3t9jNXag@mail.gmail.com>
Cc: dev <dev@opencontainers.org>, ...
Signed-off-by: W. Trevor King <wking@tremily.us>
On Wed, Aug 05, 2015 at 11:57:59AM -0700, Mrunal Patel wrote [1]:
> We could also have guests on the hangout if they have some important
> topic to present. We can decide that on the topics being discussed
> in the mailing list.
On Sat, Aug 08, 2015 at 08:23:21AM -0400, Vincent Batts wrote [2]:
> We said the topics would be proposed on this list. Discussion notes have
> been shared as a Google doc so far. I'm not opposed to markdown notes, but
> initially that just seems like an repo to me.
More generally, the topic of feedback loops came up in the 2015-08-05
meeting [3,4] (after 26:02 in the video), and the consensus was to
start discussion anything that seemed worth discussion on the mailing
list ("conversations and discussions should be on
dev@opencontainers.org mailing-list first, conversations and
discussions should be on dev@opencontainers.org" [3]). That doesn't
speak to agenda-formation specifically, but it makes an official
policy of discussing most things on the mailing list, and the two
posts I quote above extend that general approach to agenda formation.
While touching this paragraph, I also re-wrapped it to match
README.md#markdown-style.
[1]: https://groups.google.com/a/opencontainers.org/d/msg/dev/JsXgi4kxkBg/Gw7GvPodDgAJ
From: Mrunal Patel
Subject: Re: Hangout link for today
Date: Wed, 5 Aug 2015 11:57:59 -0700
Message-ID: <CANEZBD6Zs5Ht8dgkvSHRHQGaVLms_kSGqCV00AJD6eFLm9hR4w@mail.gmail.com>
Cc: dev <dev@opencontainers.org>, …
[2]: https://groups.google.com/a/opencontainers.org/d/msg/dev/41jZ9Qe7R5c/ZInajC_0DgAJ
From: Vincent Batts
Subject: Re: Open Container Weekly Meeting - Aug 5, 2015
Date: Sat, 8 Aug 2015 08:23:21 -0400
Message-ID: <CAN6Zp5yFX8yLG3b-82SAq7AmCxVpoy1tyt0K1ijFqSsCjKPRpg@mail.gmail.com>
Cc: dev <dev@opencontainers.org>, …
[3]: https://docs.google.com/document/d/1a5UW7MRLVaUDEjuQmRudYMZcPV0bBtPD2QEOLT_3zi0/edit?usp=sharing
[4]: https://plus.google.com/events/cqfpicicbnra9mv6kvpj0mb24u4
Signed-off-by: W. Trevor King <wking@tremily.us>
Qiang Huang
Abhijeeth Nuthan
Vincent Batts
Rob Dolin (MSFT)
Mrunal Patel
W. Trevor King
Stephen Walli
Michael Crosby
Vish Kannan
Brandon Philips
Mike Brown
Zefan Li
Vincent Batts