Vision

The Developer Tools portion of MAP will provide MIT software developers and IT project managers with an integrated and supported system for managing, building, and deploying code.

Backlog

  • Developers can integrate their integrated development environment into source control.
  • Developers from outside MIT can participate in MIT projects via direct access to source control and all the other tools developed as part of this program.
  • A developer can easily find information and get support for these systems and services.
  • A developer can go to a web site that will guide him to the service he is looking for.
  • IT project managers can browse the source for their projects over the web.
  • IT project managers can get analysis reports in human readable format.
  • Teams can publically publish their open-source projects on the web. They can expose only the branches of code they want, undictated by code-management best practices.
  • Developers can be assured that no one outside of the core developer-support team will have access to their secure repositories.
  • Access to server-based applications is easy for a developer through one managed account, not through the separate, local username and password mechanism with which each product comes.
  • Application Administrators do not have to manage a list of separate "root" or "admin" user accounts for each installation of each developer-tools product.
  • A DLC can request their own instance of our developer tools system that will run on a Server Operations hosted environment.
    • Constraint: This will come as an installable package to be managed by local DLC technical staff. IPS cannot scale to providing hands-on support of local installations.
  • Touchstone is the preferred method of web authentication for web-based tools.
    • There are implications for non-web tools that I (sml) do not fully understand yet.
  • MIT Developers can get a MyEclipse distribution with integration with developer tools already set up.
  • No labels