| | 2 | |
| | 3 | To get work, a user goes to a particular Bossa-supplied page. |
| | 4 | There he sees a list of applications for which tasks are available |
| | 5 | and for which he is qualified, |
| | 6 | and links to courses for other applications. |
| | 7 | Online and offline applications are listed separately. |
| | 8 | Each application has an estimate of the time or other resources required to complete a job. |
| | 9 | |
| | 10 | Selecting an online application invokes the Bossa ''scheduler'' script, |
| | 11 | which selects a job instance suitable for the user, |
| | 12 | and redirects to its instance URL. |
| | 13 | |
| | 14 | Selecting an offline application invokes the Bossa scheduler, |
| | 15 | which selects a job and redirects to its instance-start URL. |
| | 16 | |
| | 17 | Team administrators are provided with an interface for getting |
| | 18 | offline jobs for the team. |
| | 19 | The scheduler allows a team to get instances only for applications |
| | 20 | for which some team member has the required skill. |
| | 21 | |
| | 22 | Users and teams are provided with an interface for seeing |
| | 23 | a list of pending offline jobs. |
| | 24 | They can indicate that one of them is completed; |
| | 25 | this takes them to the instance-complete URL for that job. |
