On Wed, 2010-09-29 at 20:28 +0200, Martin Hejl wrote: > Hi Mike, > > >> To me it sounds (if we want to stay in line with the terms of use with > >> SF), that we either do that (but then, what actually _is_ a "binary > >> releases made via our File Release System or any other project resource" > > > > Martin, > > The SF policy applies to the FRS only. If you release a binary, you have > > to release source that will allow building that binary. > If that's the case, that's good (since it means less tarballs are > required). I was just unsure about the "or any other project resource" > in the sentence: > > "SourceForge.net requires that source code releases be made via our File > Release System for any binary releases made via our File Release System > or any other project resource." > > Since we're somewhat abusing CVS by storing our (binary) packages in > there, it could be argued that CVS is one of those "other project > resource[s]".
Martin, If you recall, our current use of CVS was initiated by SF Staff. It was a workaround for changes to their service offerings for hosted projects. These legacy workarounds are no longer necessary. > But as I said - I'm not a lawyer, and I try to stay away from > reading/interpreting legalese if I can. > > By the way - are you aware of a way to automate the process of uploading > something into FRS, apart from using some form of screen-scraping the SF > website? > Never having used the FRS in any shape or form, I'm afraid I don't know > much about it - other than hearing from a couple of project admins (from > other SF projects) that it's awkward to use. But that was several years > ago, so things might have changed. There have been major changes to the FRS in the last couple of years. Sub-directory support, shell interface, etc. http://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download > Martin > > P.S. I don't have time to get back into actively working on LEAF any > time soon - but I might find the time to provide some "helper tools" to > make sticking to the SF policies easier to those who are actively > working on LEAF. I can't promise anything though - I'm afraid I can't > commit to anything at the moment, since I just don't know how busy > things might be a week from now. Do what you can, when you can. No pressure. -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
