search

w3c / modern-tooling

Work of the modern tooling task force
http://w3c.github.io/modern-tooling/
MIT License
44 stars 39 forks source link

Persistence #7

Open swickr opened 9 years ago

swickr commented 9 years ago

We should expand on where we need persistence; e.g.

  1. Design issues and discussion
  2. Evidence of IPR commitments
  3. ...

and how we'll achieve it where we deem it necessary.

darobin commented 9 years ago

I have a paragraph on persistence under External Tools integration. I don't know if we need to specifically list the cases in which it applies. My thinking is that we need the data to be available to us in any case (otherwise it really is lock-in) and so we should act as if anything that happens in an external tool could in fact require persistence (which we can provide only when the data is available). WDYT?

timbl commented 9 years ago

Anything which is part of the discourse and the process should be persistent for posterity. So all chat, all states of all documents. Could we exclude anything? Well, the result of running a validator on something does not have to be saved in all it gory detail for example. But preserve all chats and the states of all pads, wiki, documents in general as they develop.

ericprud commented 9 years ago

Related, I have a hunch that replies to at least this list git list don't get distributed, much less archive. This is a test of that hypothesis, cc'ing w3t-archive@w3.org for verification.

Reply to this email directly or view it on GitHub: https://github.com/w3c/modern-tooling/issues/7#issuecomment-89594557

-ericP

office: +1.617.599.3509 mobile: +33.6.80.80.35.59

(eric@w3.org) Feel free to forward this message to any list for any purpose other than email address distribution.

There are subtle nuances encoded in font variation and clever layout which can only be seen by printing this message on high-clay paper.

darobin commented 9 years ago

On 04/04/2015 18:19 , ericprud wrote:

Related, I have a hunch that replies to at least this list git list don't get distributed, much less archive. This is a test of that hypothesis, cc'ing w3t-archive@w3.org for verification.

I'm not sure what you mean by git list, this isn't a mailing list :) It is distributed.

Discussions are archived, but on a third party site which does the trick in the short term but not beyond that. That's why the report plans for the extraction and persistence of that information.

Robin Berjon - http://berjon.com/ - @robinberjon