Talk:MPDL NIMS Developer Meeting 2008-12-22

if i understand correctly, it is planned that NIMS maintains essentially a fork of pubman - i.e. no single code base is going to be used by pubman at MPDL and at NIMS. i think this would be a problematic state of affairs, in particular regarding the less-than-perfect support for merging offered by svn. my experience when working with branches in svn was that only frequent merging is going to keep things maintainable and from what i gathered, this is not the strategy here. so i recommend either to merge both branches frequently (i.e. not only after each release) or let NIMS work on the pubman trunk as well.--Robert 17:58, 22 December 2008 (UTC)


 * There is not yet any strategy defined or detailed planning on how we will approach NIMS development. At present NIMS is only working on language resource bundles for japanese language and there are no big merging issues in that respect. We are not yet in position to define any more concrete steps at present as we do not know what will be NIMS development and efforts yet. --Natasa 08:20, 23 December 2008 (UTC)
 * As for merge, we had problems with merging our own code as well, so this is exactly the problem we would like to avoid and that is heavy for sure. If more often merge would mean less trouble, then we would probably aproach it. --Natasa 08:20, 23 December 2008 (UTC)


 * in any case the risk of forking should be avoided.--Robert 11:04, 23 December 2008 (UTC)