> Finally, it is my hope that the end result of this effort is that the walls
> between projects that people see as much harder barriers than they really
> are will become more porous, with both people and code flowing more freely
> between them. Much talk has been given to people getting commit rights to
> this subproject based on their contributions to another subproject, but the
> converse also needs to be true. If someone is working on a XML mapper used
> by multiple subprojects, perhaps it might make sense for that person to
> maintain the project specific wrappers for this function contained in each.
> The project lead for Rhino is a committer to BSF and maintains his own
> wrapper.
That would be an excelent idea.
And people maintaining the build file for a project should get access to
the project.xml file from gump, people developing taglibs in a project
should get commit access in taglibs project so they can develop it in the
common place ( they're going to do it anyway ), people developing ant
tasks of common interest should be able to add it in optional/ with
minimal effort.
We have mechanisms to prevent un-wanted code - any commiter can -1 a
change, and CVS makes it easy to roll back.
But if we can't agree on lowering the walls even on the library, I'm not
very optimistic about the rest of it.
Costin
