Open source was considered alongside closed source and the proprietary model. You have prompted me to consider:
open source the Subversion adaption layer
make the Rhapsody layer proprietary.
Why? To empower the user community to forwardly maintain the Subversion part of the integration, and encourage a commensurate contribution by Telelogic. Further, it will allow open source projects for integrating Rhapsody with other version control tools (e.g. CVS).
If there’s agreement, I could resubmit this as a master project with two sub-projects.
Add a comment
Before you add a comment you must be signed up – it takes about 30 seconds. Sign up now.
2 comments (oldest first)
Sounds really useful, and Telelogic don’t have a solution. But how about making it open source?
Thanks for the vote and the pledge, Shine.
Open source was considered alongside closed source and the proprietary model. You have prompted me to consider:
Why? To empower the user community to forwardly maintain the Subversion part of the integration, and encourage a commensurate contribution by Telelogic. Further, it will allow open source projects for integrating Rhapsody with other version control tools (e.g. CVS).
If there’s agreement, I could resubmit this as a master project with two sub-projects.
Add a comment
Before you add a comment you must be signed up – it takes about 30 seconds. Sign up now.