Ok. I installed TortoiseSVN and got the repository URL from my project page. I was able to create a Docs directory with a small readme.txt file. I was able to then browse the repository and check out the files to a folder with the same name as the project.
So, as soon as I get the code cleaned up some more, I'll be ready to upload it. I will send out the SVN URL for the project when I am ready to let those interested start checking out and updating the code.
----- Original Message ----- From: "Andreas Stefik" <stefika@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx> Sent: Monday, June 28, 2010 7:14 PM Subject: Re: Using SourceForge
Jay, If you are trying to upload source files, the typical way is to use version control. In our case, for example, we use subversion. If you pull up your project and click the develop tab (not the develop tab on the homepage), it will have a subversion address listed for the project. Here's ours, for example: https://sourceforge.net/projects/sodbeans/develop Using subversion, GIT, or CVS, is, in my opinion, the best way to put source files up, as it allows other folks to make changes at a whim (if you allow it by admin -> membership). And, just as neat, sourceforge keeps stats on everything related to it, it's automatically integrated into Trac, and it is just generally really easy for everyone, since it is standard. As for choosing a version platform, I know some folks that really love CVS, others that love subversion, and others still that think that anything but GIT is the devil incarnate. Personally, I prefer subversion, as it gives one, unified, build number, across the projects, and you never have to muck around with file versioning (CVS), or just as frustrating, separate personal repositories which never seem to sync up right (Git or Mercurial). I've used all of them, and prefer subversion, but keep in mind that that's just my personal opinion. Now, if you are wanting to upload a release ready file, however, it's a bit different. There's two ways to do this: 1. Project admin -> File Manager If you go to the file manager, you can release files and these are automatically sent through all the sourceforge mirrors. However, the interface is pretty clunky and works very poorly for large files (it crashes). In the Sodbeans project, our files are often 200-300 megabytes, so we have to use system 2: 2. use rsync For large files, you need to use rsync from the command line. It's still pretty clunky, but this works really well. The command is something like the following: rsync -e ssh yourfile.exe username,projectname@xxxxxxxxxxxxxxxxxxx:/home/frs/project/pathtoyourproject/FolderYouWantItIn Generally speaking, if you are putting up largeish files, it would be wise to check Md5 checksums to be sure everything uploaded correctly. Every blue moon, one of the files we've uploaded has had a problem, so it's not a bad idea. Anyway, hope that helps. Personally, I'm excited to see what you folks have. I actually think we should consider collaborating on some of this code. Our team at Southern Illinois University already has working some code that integrates in a cross-platform, screen reader neutral way in Java, and it would be a shame if both our development teams ended up duplicating code unknowingly. Ours is somewhat NetBeans platform specific, as we are trying to make NetBeans more accessible, and there are enormous challenges in that as it is, but in practice we've spent a ton of time iterating through swing components, banging our head against the wall, and digging through debugger traces of swing code looking for how to "speak stuff" to the user. Cheers, StefikOn Mon, Jun 28, 2010 at 3:14 PM, Jay Macarty <jay.macarty2009@xxxxxxxxx> wrote:Question for anyone who has used SourceForge to host a project. I can't seemto determine the best way to upload files to the project. I was able toupload a single file using scp but not sure how is the best mechanism for us to collaborate on the java accessibility client so that people can downloadthe source, make contributions, and upload the changes. Also, just an FYI. I did recieve an answer back from the author of JNAsaying he would be more than happy for us to include JNA in our JAC project.__________ View the list's information and change your settings at //www.freelists.org/list/programmingblind
__________View the list's information and change your settings at //www.freelists.org/list/programmingblind
