How to document the Relearn tools without becoming tool-centric?
Focus on the effect of the tools? what learning processes are facilitated by the tools themselves?


What tool do we use to document the Relearn tools?
Also on a meta level : what do we do with the distribution/accessibility/potential updates to the archive (so, new tools in the coming years).

xmpp

things that could be included:

tools that we could use to document:

Will this tool documentation be an archive?
Will this tool documentation be part of the documentation of Relearn?

*Miglena's physical git workshop

PADS
http://complex.local/etherdump/xmpp_carousel.diff.html
http://complex.local/etherdump/local_network_carousel.diff.html
http://complex.local/etherdump/local_network.diff.html
http://192.168.73.188:9001/p/tool_carousel
http://complex.local/etherdump/complex.local.diff.html


LINKS
https://github.com/ether/etherpad-lite/wiki/How-to-deploy-Etherpad-Lite-as-a-service
http://www.reganmian.net/blog/2014/10/03/supporting-idea-convergence-through-pedagogical-scripts/
https://pypi.python.org/pypi/etherpad_lite/
https://github.com/graphiclunarkid/etherpad-saver
https://gitlab.constantvzw.org/aa/etherdump/tree/master/etherdump/commands

our ETHERPAD API key
ced8c0068ef893d1a47f900560226a65e16ef4f1905f777399ea86c870930e03

python -m etherpad_lite -p apikey=ced8c0068ef893d1a47f900560226a65e16ef4f1905f777399ea86c870930e03



A simple helper function to execute Etherpad API calls, and properly format the return message:
def run_etherpad(path, **params):
    params['apikey'] = settings.ETHERPAD_API
    data = urlencode(dict(params)).encode('ascii')
    url = ("%s/api/1.2.10/%s" % (settings.ETHERPAD_URL, path))
    r = json.loads(urlopen(url, data).read().decode('utf-8'))
    return(r)


http://etherpad.org/doc/v1.3.0/#index_api_methods

createPad padID=testingstuff text="Lorem ipsum dolor sit amet."