Mark em as experimental so ppl know we'll change them. Fairly common practice in frontend dev frameworks and Node.
On Wed, May 21, 2014 at 9:35 AM, Michal Mocny <mmo...@chromium.org> wrote: > Fair enough. I guess I expected for you to run across this experiment via > an outlet such as: "Hey guys, check out ___. You use it as such.. (docs > inline)", and not by casually reading the CLI docs some day. > > But anyway, Gorkem has volunteered to document it, and I guess having a > central place to update instructions as things change is good, so thats > that. > > -Michal > > > On Wed, May 21, 2014 at 10:28 AM, Ray Camden <rayca...@adobe.com> wrote: > > > If the intent is for us to test them, then they should be documented. If > I > > run across something and _don't_ see a doc, I get more upset about that > > then anything else. Just make it clear it is an experiment and it may > > change in the future. > > ________________________________________ > > From: mmo...@google.com <mmo...@google.com> on behalf of Michal Mocny < > > mmo...@chromium.org> > > Sent: Wednesday, May 21, 2014 9:24 AM > > To: dev > > Subject: Re: CLI implementation for the save and restore plugins > > > > In theory, but I think the point for now was that we aren't sure about > the > > syntax and semantics. We should probably reach out using various > channels > > to get users to try it and chime in, but its really early to start > > documenting lest users get upset when it breaks. > > > > > > On Wed, May 21, 2014 at 10:16 AM, Gorkem Ercan <gorkem.er...@gmail.com > > >wrote: > > > > > I was planning to add it when I got the "restore/save platforms" in > but I > > > can send an early PR. > > > -- > > > Gorkem > > > > >
