1 / 12

Tool Development for an ELO-like Organization

Tool Development for an ELO-like Organization. What makes sense?. Tools: What makes sense?. Appropriate scale, goals Be specific to our community. Tools: What makes sense?. Appropriate scale, goals Not beyond our resources

ciara-bowen
Download Presentation

Tool Development for an ELO-like Organization

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Tool Development for an ELO-like Organization What makes sense?

  2. Tools: What makes sense? • Appropriate scale, goals • Be specific to our community

  3. Tools: What makes sense? • Appropriate scale, goals • Not beyond our resources • Not competing for users with large entities (commercial or open source) • Not trying to talk people out of using their current tools, but providing something else

  4. Tools: What makes sense? • Be specific to our community • In areas where tools exist, concentrate on how they can work for our constituents • For new development, do what others won’t

  5. Where tools exist • Test widely, contribute narrowly • Preference for open and free tools • What’s needed may not be technical

  6. Where tools exist • Test widely, contribute narrowly • e.g., what current emulation projects can help? • Is there one we should help improve?

  7. Where tools exist • Preference for open and free tools • Open source and free-as-in-beer • e.g., TidyLib vs. commercial, if both work (or if both would need significant contribution)

  8. Where tools exist • What’s needed may not be technical • A tool may exist, but be too expensive, and we can organizationally engineer access to it • A tool may exist, but be too difficult to use, and we can either engineer assistance or an improved interface

  9. Segue: what if no tools exist? • We should do what others won’t, even if we lobby them and/or help • Again, we should do things specific to our community

  10. What others won’t do • Elit beyond reading and writing • High risk, high gain projects

  11. What others won’t do • Elit beyond reading and writing • Tools for scholarship and education • Tools for preservation and archiving • Still build on work of others (e.g., Eclipse) • We have to do this, or it won’t happen — and our constituents will continue to try to function without appropriate tools

  12. What others won’t do • High risk, high gain projects • Elit creation tools (what if we could support a tool that tried to enable a new genre each year?) • Still build on work of others (extend existing commercial/open source tools or make research tools usable) • We don’t have to do this, but it would be exciting • Probably structure as subgrants

More Related