{
  "$type": "site.standard.document",
  "canonicalUrl": "https://khattamicah.xyz/posts/index",
  "path": "/posts/index",
  "publishedAt": "2021-01-01T00:00:00.000Z",
  "site": "at://did:plc:tc67mguo6vvlgqpw54mez6jv/site.standard.publication/3mdrjsb2bdk2p",
  "textContent": "When selecting tools for use by the collectives I worked with in India, we had to consider the following factors due to the unique context and limited resources available:\n\nExport Capabilities: \n- [ ] Does the tool allow for easy export of data or content?\nCompatibility with Other Tools: \n- [ ] Do the export options work well with other tools commonly used by the collectives?\nSelf-Hosting: \n- [ ] If the collective has its own server, can the tool be self-hosted? \n- [ ] Is there someone available to maintain and experiment with it?\nDevice and Screen Compatibility: \n- [ ] Is the tool usable on multiple devices and different screen sizes?\nCollaboration Features: \n- [ ] Can the tool facilitate collaborative work among team members?\nAffordability: \n- [ ] Is the tool relatively free or affordable for Indian collectives, with a monthly cost of less than 200-300 INR?\nOpen Source: \n- [ ] If the usage involves sensitive data, is the tool open source, providing transparency and security?\nInput Variety: \n- [ ] Can the platform support different types of input, such as voice, text, and other formats?\nInput Delivery Options: \n- [ ] Can the tool enable input delivery through various means, like phone calls for voice-based inputs?\nEfficiency vs. Accessibility: \n- [ ] If there are multiple tools available, one being faster but more opaque, and another being slower but more accessible, which trade-off is more important based on the specific needs and limitations of the collective?\nLong Term Stability\n- [ ] Is there some sort of way that the project itself fails in the long-term either by acquisition, abandonment or commercialisation\nCoherence for Collaborators\n- [] Does it make sense with the larger context of our work to our team internally and to our collaborators\n\n---\n{{< card type=\"info\" title=\" Why This Checklist Exists\" >}}\n\nConsiderations for the checklist were driven by the unique characteristics of the work environment in India -- limited resources for maintenance, challenges related to connectivity and device capabilities, language and interface simplicity requirements, the importance of open visibility for learning and collaboration, and the limited technical expertise of collaborators.\n{{< /card >}}",
  "title": "Selecting tools for Indian Collectives"
}