RidgeRun Developer Manual: Difference between revisions
No edit summary |
mNo edit summary |
||
Line 1: | Line 1: | ||
<seo title=" RidgeRun Developer Manual | Developer Manual | RidgeRun" titlemode="replace" | <seo title=" RidgeRun Developer Manual | Developer Manual | RidgeRun" titlemode="replace" metakeywords="GStreamer, ridgerun,ridgerun developer,ridgerun manual,ridgerun developer manual,ridgerun guide,ridgerun standards,ridgerun development, ridgerun development guide,ridgerun development manual" metadescription="RidgeRun Developer Manual is a wiki guide with the details about the software development standards, tools, process and practises followed by the RidgeRun R&D team."></seo> | ||
<br> | <br> |
Latest revision as of 10:18, 9 March 2023
WORK IN PROGRESS. Please Contact RidgeRun OR email to support@ridgerun.com if you have any questions. |
RidgeRun Developer Manual RidgeRun Developer Manual. |
| ||||||||||||||||||
RidgeRun Developer's Manual is written with the intention of helping to understand different procedures and professional practices that the software engineering team in RidgeRun follows. Most of this wiki consists of a collection of standards and tools that are employed during the development of the projects in which different RidgeRun engineering teams are involved (R&D and customer's projects).
| |||||||||||||||||||
RidgeRun Developer Manual Overview | |||||||||||||||||||
RidgeRun Developer Manual is a wiki guide with details about the software development standards, tools, process, and practices followed by the RidgeRun R&D team. Get started with RidgeRun Developer Manual by clicking the button below!
|