|
Author
|
Message
|
|
Kai Duebbert
|
Thursday 16 October 2003 7:05:26 pm
Hi, How about giving some developers write access to SVN again? Then many bugs could be fixed immidiately instead having people complaining about bugs not being fixed. You could select only some developers who you know and who you can trust. I certainly would prefer fixing the bugs that I see in SVN instead of having to fill the bug list with small bugs. Are there license problems with that (probably solvable with agreements)? Kai
|
|
Bård Farstad
|
Thursday 16 October 2003 11:51:38 pm
Hi Kai, we could open the svn repository for selected developers. Technically there is no problem with this, however we would need every developer to sign an agreement that everyting they commit to the svn repository would need to be copyright eZ systems as. This is due to the dual licesing that we use, we need to have copyright of all the code. If some developers would agree to that we could open the svn repository for write access. --bård
Documentation: http://ez.no/doc
|
|
Paul Forsyth
|
Friday 17 October 2003 1:30:37 am
Write access could also be for contributions/projects, which wouldn't need to be under the dual license. How feasible is this given the past problems of svn? Even with the the new mirror Paul needs to perform sanity checks on his rsync'd copy before putting it onto pubsvn because of its instability. Should we instead try to work with places like sourceforge for things like this? paul
|
|
Bård Farstad
|
Friday 17 October 2003 2:01:59 am
Our current SVN server is not scaled for high traffic. I think an svn repository for extensions would be a good idèa. This could be a powertools package where we could have all contribution development. However we would need to have a new server for this. If someone from the community would like to maintain such a server we could probably provide the hardware. --bård
Documentation: http://ez.no/doc
|
|
Paul Borgermans
|
Friday 17 October 2003 2:22:43 am
Sourceforge or similar could be good idea. On the other hand, pubsvn.ez.no has all on board to host one or more extra source trees (if you would like to collaborate on GPL'ed-only contributions/extensions with svn). It would not be the place for bugfixes I think. I could add an ez publish based collaboration portal too over time (basic project management/forums/bug system). This all should be first approved by the ez crew of course. Any comments? -paul PS: The sanity checks are necessary because of transient states of the underlying berkeley database: even a read while rsyncing makes it "corrupt" for svn. It happened also with Google bots on pubsvn.ez.no, which forced me to let apache go down briefly during rsyncing the sanitized copy.
eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans
|
|
Paul Borgermans
|
Friday 17 October 2003 2:38:40 am
We were planning to set up a similar server for our projects anyway. So unless there aren't any other takers ... From what I can judge on current community development, that machine would not need to be a supercomputer cluster for the time being. Or do I underestimate the load/problems for a read-write svn server? The load on pubsvn.ez.no is very low, as well as the bandwidth consumed to the internet, so the same machine could be used? -paul
eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans
|
|
Bård Farstad
|
Friday 17 October 2003 2:48:23 am
Paul, I think this is a good idèa. You could create a new repository where developers could work on extensions for eZ publish. I would definetly support this. You need to make sure the the server is properly backed up though in case of a crash;) --bård
Documentation: http://ez.no/doc
|
|
Paul Borgermans
|
Friday 17 October 2003 3:02:22 am
OK Bård I'll do that. And backups aren't a problem, have a noisy Sun-DLT box taking daily care of that. Now those who want/need access email me pborgerm [at] sckcen [dot] be and I'll setup the accounts. I'll add more on this on pubsvn.ez.no next week -paul
eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans
|