Fixed Price: $1,000 - $5,000
| Posted: Sep 26, 2015 | Closed |
We are looking for a technical writer who can go through and write our technical API documentation and add tutorials, examples in the style of [obscured] /tutorials/01-GettingStarted for our products (EMOTIV EPOC/+ and Insight). Our products can be found at [obscured] Current documentation at [obscured] /emotiv We'd like the API documentation created using markdown on a Github repository so we can host the documentation easily, but also for open collaboration with our developer community. Github comes with a very nice Issue Tracker that people use quite often.
Hourly Rate: Not Sure
| Duration: 1-2 weeks
| Posted: Oct 04, 2012 | Closed |
The aim of this project is to review a class found in the Orcomp library on github ( [obscured] /Orcomp/Orcomp). The class in question can be found in Orcomp/Extensions/TaskCollectionExtensions.cs As part of this project you will need to: - Fork the Orcomp library and create a new branch called "CleanTaskCollectionExtensions" - Then fix the code in the TaskCollectionExtensions file so that it passes stylecop with no warnings. - This will require you to familiarize yourself with the code and write the necessary XML documentation. (You can find general documentation for the code at [obscured] /2012/05/task-levels.html) - Create an activity diagram using plantUML to represent the TryToMakeTasksComply() method (You can use [obscured] /projects/plantumlqeditor/ to assist you) - Fix the Unit tests in Orcomp/Extensions/TaskCollectionExtensionsTests.cs to be clearer and better structured. - Provide a code review of the TaskCollectio...