On 22 July 2011 10:14, Søren Hauberg <[email protected]> wrote: >> > I believe that this could be better managed if users reported them >> > on the octave-forge bug tracker, which we do have at >> > http://sourceforge.net/tracker/?group_id=2888&atid=102888 >> >> Actually, I think the right fix is to merge with the Octave bug >> tracker in Savannah. We already get plenty of bug reports there for >> Octave-Forge packages, and we keep telling them, "that's not us, but a >> separate project!" which seems very wrong to me. We're the same people >> for the most part, we all care about core Octave and we all care at >> least about a few Octave-Forge packages, and we all have a comparable >> set of skills to work on Octave-Forge or Octave itself. >> >> We can keep using svn with Savannah, but I'd like to take the >> opportunity to do some cleanup and move Octave-Forge to hg: break it >> up into one hg repo per package plus another repo that contains them >> all as hg subrepos, plus any project metadata that may be necessary. >> As for bugtracking, all we would have to do is set a special >> Octave-Forge category in the Savannah (actually, this category already >> exists in Octave's bug tracker, but it's used to mean "not our >> problem!"). > > There are two separate issues here: > > 1. Where to report bugs, and > 2. where to develop code. > > Regarding the first issue, I agree with Jordi that it would be better if > we could use the Octave bug tracker as that would give users a single > point of entry. The current situation is a mess where users report > Octave-Forge problems to the Octave tracker and Octave problems to the > Octave-Forge mailing list. I guess we should talk to JWE about the > possibility of using the Octave tracker.
I agree here as well. I think we need a bug tracker, and if we can get one that moves us closer to octave, even better. > Regarding the issue of where code is developed (SVN vs Hg vs ???) then I > think we should deal with this independently of the bug tracker issue. > That being said, my impression is that a lot of development happens > outside the SVN repository and when a new release is made a lot of code > gets checked into SVN. So I don't think our current setup is working. I > must confess that I am not sure that the idea of using a single > repository for *all* packages actually works. If I want to work on > package X then I guess it is annoying that I have to check out the > entire Octave-Forge repository. The single repository seems to serve no > purpose now that we moved away from the monolithic releases. So perhaps > we should create a whole bunch of repositories? I believe you can do a partial checkout of the repo, limited to the package you want, with subversion. Just specify the path on the command > Regarding the type of the repository then I don't really care; for the > simple stuff I do, SVN, Hg, Git, ..., are all the same. A distributed revision control system such as hg/git/bzr should solve the problem of having the entire development of a release in one commit. If we are going to change the place where the development is made, there's one feature that I think it's handy. In places such as launchpad and github (the first uses bazaar, the second git), anyone can fork the project, make his changes with as many commits as they want (organization) and then make a pull request. A maintainer of the project can then accept or reject that request. I'm not suggesting moving to one of those sites, just pointing an advantage of distributed revision control systems. Octave users are programmers and I'm guessing some of them would be comfortable sending patches and fixing their bugs that way. >> The only problem is a few packages have non-free licenses, but they're >> rarely used or maintained, and I think all the non-free packages can >> be dropped. > > I think it is fine to drop the non-free packages; I'm not even sure they > compile any more, and I doubt they see much use anyway. If they're not free, I'm also in favor of dropping them if we move. However, we could maybe contact their originals authors and ask if they are willing to change the license first because we can't take them with us otherwise. Carnë ------------------------------------------------------------------------------ 10 Tips for Better Web Security Learn 10 ways to better secure your business today. Topics covered include: Web security, SSL, hacker attacks & Denial of Service (DoS), private keys, security Microsoft Exchange, secure Instant Messaging, and much more. http://www.accelacomm.com/jaw/sfnl/114/51426210/ _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
