You have a privilege to create a quiz (QnA) related to this subject and obtain creativity score...
Plan and Status Tracking
Ivan:
We currently do not have a working prototype of any kind, so an issue tracker is not our foremost priority. When we do start testing, though, we want the testers to report discovered issues and track them in some well-organized fashion. Same goes for feature requests.
BitBucket has a built-in Jira-like issue tracker with good Wiki integration. I am familiar with Jira, so that would be my obvious choice, but I am open to other ideas as well.
Jeff:
It is useful to establish agile process with planning and status reporting. We are not there yet, but moving to the point where we can list a set of tasks with specific discussions on status and obstacles at least once a week.
This is the placeholder.
I would like to start with the first task on DATA, provided as the link above. This is a common task.
>> 80. Technology >> Semantic Notes >> ITS-MF discussion >> Archive-PT1 >> Discussion on Development Process >> Development Documentation