We got the trackers as part of the sf.net project space, so they didn't require much effort to set up. Unfortunately, as you all know, they're also nontrivial to use; the package submissions tracker is notably annoying.
While we're figuring out an alternative, I would like to propose a few ideas. 1) If you're submitting a new revision to an existing package, send a message to fink-devel as well mentioning that fact and including a link to the tracker item. That way someone with commit access can run a quick diff on the files against the revision that is in Fink, and if the change is sufficiently trivial can add it without further ado. 2) For a new version of a package (or a new variant), follow the same procedure as above. If, once again, the changes are trivial, it can get expedited. If the changes are more substantial, some testing may be in order. Note: if a package is actually maintained by a person you may be better off contacting them directly rather than going through the tracker. 3) For new packages, it's probably still a good idea to solicit feedback on fink-devel as well. If you describe what the package does, somebody here might have an interest in trying it out. -- Alexander K. Hansen Fink Documenter (still) ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
