søn, 18 10 2009 kl. 11:53 +0200, skrev Paul Sundvall: > Nice work! > I appreciate your efforts towards a per-package release system. The > layout is nice and the only thing that I think is wrong is the title of > the page, which I guess should be "Octave package: Image" and not > "Function Referene: image".
That's a bug. I'll fix it; thanks. > *does the package name has to be repeated in the yellow box as well as > on the top of the page? No, I guess not. Which one would be best to remove? > *can the green box display the latest version number, and have a smaller > text below with a link to older releases? (if there are is such > functionality). If there is something broken in a package version, I > think users will appreciate being able to easily find an older version. Adding a version number should be easy. Links to older releases is somewhat harder as I'm not sure we can automatically determine which of the previous releases we should link to. We could link to https://sourceforge.net/projects/octave/files/ but I'm not sure how much that helps. > *is it desirable/possible to have links to external packaging of the > octave packages? Like pointers to debian package, macports etc. C.f. > http://www.macports.org/ports.php?by=name&substr=octave-image and > http://packages.debian.org/sv/source/lenny/octave-image Again, this is not something that can be hard to determine automatically. I would guess that people that get their Octave-stuff from e.g. MacPorts would look there in the first place instead of looking at our site. Is that assumption correct? > *should there be a link to bugs for the package? For now, it can lead to > the bugs page http://octave.sourceforge.net/bugs.html but there will > maybe be a bug tracking system for the octave packages in the future. There has been talk about making a bug tracker for core Octave, but I don't remember discussing this for Octave-Forge. > *should we include a pointer to the repository? something like > http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/main/image/ I think potential contributors should be able to navigate the SVN themselves. So, _I_ think the 'SVN' link in the top menu should be enough. Søren ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
