Greetings folks!
I've been contacted by a CMU researcher who would like to interview
developers regarding dependency management.
The short version is this:
--
I'm collaborating with CMU colleagues on research about managing change
in an ecosystem context like Eclipse. We're looking to interview
Eclipse package or plugin developers who have had some experience with
maintaining packages where they've had to watch out for changes in the
packages they depend on, and/or had to be mindful of changes that might
affect packages dependent on them. They could be working either on the
Eclipse core packages, or on more peripheral plugins. We're interested
in knowing about their strategies for keeping up with change and for
managing the impact of change on the users of the API they expose.
--
I've explained our project structure, the concept of +1, +2, ...
dependencies and general rules for mapping bundle ids to projects.
If you're interested in participating in the research, please contact
Chris Bogart directly.
[email protected]
Thanks!
Wayne
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
EclipseCon Europe 2015 <http://www.eclipsecon.org/europe2015>
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
