Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
32 lines (32 sloc) 1.04 KB
amazon_s3_presentation_url amazon_s3_video_url author categories comments date image layout session_id session_track slideshare_presentation_url speakers title youtube_video_url attached_documents tag
None
None
connect
yvr18
true
2018-09-16 09:00:00+00:00
featured file_name path
true
YVR18-SWG01.png
/assets/images/featured-images/YVR18-SWG01.png
resource-post
YVR18-SWG01
Security, SWG-Hack
None
biography company job-title name speaker-image
Heading Security Working Group in Linaro.
Linaro
Principal Engineer
Joakim Bech
JoakimBech.JPG
YVR18-SWG01 Hacking: Documentation in OP-TEE
None
session

Currently the OP-TEE documentation is spread among different gits and op-tee.org? I would like to have a discussion how to shape up our documentation a bit. Markdown vs rst? Sphinx is a good candidate, but require that all docs is under the same root.

You can’t perform that action at this time.