Hi, I have no doubt about those all features will be good for the future of Subversion, from a technical point of view.
On the other hand, the underlaying message scares me. The message is clear: Apache can't drive the development process by itself and only Wandisco can do it in the right way and in timing. And I think that this exceeds Subversion project and undermines Apache's authority. Today is Wandisco and Subversion. Tomorrow could be Oracle or Microsoft doing the same with other project. I would not like see Apache become in a silly Software Factory. But of course, I have not enough knowledge about how Apache internally works and perhaps I'm saying a very great stupidness. So, my apologizes for that if that is the case. Pablo. On Tue, Dec 21, 2010 at 7:38 PM, David Richards <da...@wandisco.com> wrote: > [This is a one-off and we will not post this again on this list] > > Following the > announcement<http://www.wandisco.com/php/pr.php?rss=0&prdate=2010-12-20>by > WANdisco yesterday that we would undertake the work to fix / improve > branching and merging in Subversion; we are on the lookout for new > Subversion developers to complement our existing team. If you (or someone > you know) have what it takes feel free to email me or careers {a.t} > WAndisco . com. We are looking to hire a large number of new developers. > Also, contact us if you would just like to donate some of your own time. > > I would also say that this work will be completed both *for* and as *part > of* the *community*. I have tried to answer questions surrounding this on > my > blog<http://blogs.wandisco.com/2010/12/20/shaking-up-subversion-by-listening-to-the-user-community-and-then-committing-to-do-the-work/>. > Any questions or concerns feel free to email me directly. > > > Highlights of the proposed improvements include: > > - Enhanced Subversion merge performance, with features such as allowing > users to take all of the changes committed on one branch and replay them on > another > - Subversion rename tracking to eliminate tree conflicts during merges > when file names change > - Improve correctness of 'SVN blame - g' to make it possible to follow > complete merge history and trace authors of merged code > - Improve 'SVN import' to better manage branches. > - Make Authz architecture more granular similar to Unix filesystem > permissions. > - Repository-dictated configuration. > > > > > > -- > Regards, > > David Richards > President & CEO > WANdisco, Inc. > > http://www.wandisco.com > http://blog.wandisco.com/david/ > > > > Free Online Subversion Training > http://svn.wandisco.com/eTraining > > Join the Open Source Subversion Community > http://svn.wandisco.com/eCommunity > > Read our blogs! > http://blogs.wandisco.com/ > > Follow us on Twitter > http://svn.wandisco.com/eTwitter > > Join us on facebook! > http://svn.wandisco.com/eFacebook > > THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY, AND MAY BE > PRIVILEGED. If this message was misdirected, WANdisco, Inc. and its > subsidiaries, ("WANdisco") does not waive any confidentiality or privilege. > If you are not the intended recipient, please notify us immediately and > destroy the message without disclosing its contents to anyone. Any > distribution, use or copying of this e-mail or the information it contains > by other than an intended recipient is unauthorized. The views and opinions > expressed in this e-mail message are the author's own and may not reflect > the views and opinions of WANdisco, unless the author is authorized by > WANdisco to express such views or opinions on its behalf. All email sent to > or from this address is subject to electronic storage and review by > WANdisco. Although WANdisco operates anti-virus programs, it does not > accept responsibility for any damage whatsoever caused by viruses being > passed. >
