[Pharo-project] Alternative to MC for upload?
Hello all, I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community. In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me. Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool? Bill
On Feb 5, 2012, at 12:30 PM, Schwab,Wilhelm K wrote:
Hello all,
I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community.
In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me.
Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool?
The best thing to do is create a repository on squeak source and publish the code there with a clear license. You can just copy the packages in there.
Bill
Stef, Sure, but my concern is that, in the past, I had a simple packing mistake (I assume I was at fault) expose code that I had not intended to release. There was no harm that time, but I would really rather do *anything* other than let MC write my code to the repository. I'd settle for FTP access or a gofer solution, just so long as I know exactly which files are going to upload. I don't make the rules, but I did sign the non-disclosure agreements and MUST respect them. Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Stéphane Ducasse [stephane.ducasse@inria.fr] Sent: Sunday, February 05, 2012 7:41 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload? On Feb 5, 2012, at 12:30 PM, Schwab,Wilhelm K wrote:
Hello all,
I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community.
In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me.
Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool?
The best thing to do is create a repository on squeak source and publish the code there with a clear license. You can just copy the packages in there.
Bill
I do not really understand your problem. either your code is public and you can publish it to a repository where people can have a look or your code is private and you do not publish it. The fact that this is mc or not is orthogonal or I miss something Stef On Feb 5, 2012, at 2:01 PM, Schwab,Wilhelm K wrote:
Stef,
Sure, but my concern is that, in the past, I had a simple packing mistake (I assume I was at fault) expose code that I had not intended to release. There was no harm that time, but I would really rather do *anything* other than let MC write my code to the repository. I'd settle for FTP access or a gofer solution, just so long as I know exactly which files are going to upload. I don't make the rules, but I did sign the non-disclosure agreements and MUST respect them.
Bill
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Stéphane Ducasse [stephane.ducasse@inria.fr] Sent: Sunday, February 05, 2012 7:41 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload?
On Feb 5, 2012, at 12:30 PM, Schwab,Wilhelm K wrote:
Hello all,
I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community.
In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me.
Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool?
The best thing to do is create a repository on squeak source and publish the code there with a clear license. You can just copy the packages in there.
Bill
Stef, The only thing you are missing is that I (presumably) made a mistake that once broke a barrier between public code and things that I had not intended to release. The "spill" was code that was not worthy of release (otherwise harmless), but it could have just as easily have been something that is "somebody else's intellectual property." It is that latter mistake that I don't ever want to make, so I would like to be specific about the files I push. Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Stéphane Ducasse [stephane.ducasse@inria.fr] Sent: Sunday, February 05, 2012 8:06 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload? I do not really understand your problem. either your code is public and you can publish it to a repository where people can have a look or your code is private and you do not publish it. The fact that this is mc or not is orthogonal or I miss something Stef On Feb 5, 2012, at 2:01 PM, Schwab,Wilhelm K wrote:
Stef,
Sure, but my concern is that, in the past, I had a simple packing mistake (I assume I was at fault) expose code that I had not intended to release. There was no harm that time, but I would really rather do *anything* other than let MC write my code to the repository. I'd settle for FTP access or a gofer solution, just so long as I know exactly which files are going to upload. I don't make the rules, but I did sign the non-disclosure agreements and MUST respect them.
Bill
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Stéphane Ducasse [stephane.ducasse@inria.fr] Sent: Sunday, February 05, 2012 7:41 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload?
On Feb 5, 2012, at 12:30 PM, Schwab,Wilhelm K wrote:
Hello all,
I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community.
In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me.
Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool?
The best thing to do is create a repository on squeak source and publish the code there with a clear license. You can just copy the packages in there.
Bill
On 2012-Feb-5, at 8:13 , Schwab,Wilhelm K wrote:
The only thing you are missing is that I (presumably) made a mistake that once broke a barrier between public code and things that I had not intended to release. The "spill" was code that was not worthy of release (otherwise harmless), but it could have just as easily have been something that is "somebody else's intellectual property." It is that latter mistake that I don't ever want to make, so I would like to be specific about the files I push.
I thought you should be able to access www.squeaksource.com using WebDAV, but at least guest access doesn't work. There must be one of the protocols that WebDAV uses that the monticello server that I presume powers ss doesn't support, because the converse certainly works, I have a local WebDAV that MC is quite happy with. If you had webdav you could move over files (and possibly delete old files you didn't want there). ../Dave
Dave, Thanks for the suggestion. It also occurs to me that Pharo *has* to contain the upload code, so I might simply be able to isolate and script it to push only what I specify. I just need an idiot proof safe solution. Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Dave Mason [dmason@mason-rose.ca] Sent: Sunday, February 05, 2012 8:41 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload? On 2012-Feb-5, at 8:13 , Schwab,Wilhelm K wrote:
The only thing you are missing is that I (presumably) made a mistake that once broke a barrier between public code and things that I had not intended to release. The "spill" was code that was not worthy of release (otherwise harmless), but it could have just as easily have been something that is "somebody else's intellectual property." It is that latter mistake that I don't ever want to make, so I would like to be specific about the files I push.
I thought you should be able to access www.squeaksource.com using WebDAV, but at least guest access doesn't work. There must be one of the protocols that WebDAV uses that the monticello server that I presume powers ss doesn't support, because the converse certainly works, I have a local WebDAV that MC is quite happy with. If you had webdav you could move over files (and possibly delete old files you didn't want there). ../Dave
Schwab,Wilhelm K wrote:
Hello all,
I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community.
In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me.
Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool?
Bill
I feel I've misread your question - but my first thought is that different packages can be stored in different Repository Types. So the heart surgery stuff would be saved to only local "directory" repositories while the more general stuff would be saved to the public "http" repositories. More generally, an interesting feature would be being able to tag both packages and repositories with a license type (eg MIT, MyCommericalLicense, OtherCompanyNDA) and the system constrain you to saving packages in compatible repositories. As an extension, some ideas for tool support might be: + being able to strip "all non-MIT" code out of an image + using a different background colour when editing non-MIT code cheers, ben
Ben, Constraints would be useful. Again, I don't dare botch this - it's silly but, there is "force of law" and all that. Failing a screening system like you describe, I would literally settle for an ability to make a repository and then just FTP specific files that I have saved locally and browsed for content. I'd be less scared if I hadn't been surprised in the past... I probably create some of my own troubles by my naming conventions, which are my attempt at making it easy to catch my code with a wide net so I don't lose work. That same wide net worked against me with net repositories. Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Ben Coman [btc@openInWorld.com] Sent: Sunday, February 05, 2012 8:05 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload? Schwab,Wilhelm K wrote:
Hello all,
I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community.
In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me.
Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool?
Bill
I feel I've misread your question - but my first thought is that different packages can be stored in different Repository Types. So the heart surgery stuff would be saved to only local "directory" repositories while the more general stuff would be saved to the public "http" repositories. More generally, an interesting feature would be being able to tag both packages and repositories with a license type (eg MIT, MyCommericalLicense, OtherCompanyNDA) and the system constrain you to saving packages in compatible repositories. As an extension, some ideas for tool support might be: + being able to strip "all non-MIT" code out of an image + using a different background colour when editing non-MIT code cheers, ben
I think your concern is admirable. Businesses are sometimes shy of open source (more the GPL than MIT) for similar concerns. Providing tools to manage those concerns "might" enhance respectability in the eyes of those potential business users, but there are probably more important things for the limited resources to focus on at the moment. Schwab,Wilhelm K wrote:
Ben,
Constraints would be useful. Again, I don't dare botch this - it's silly but, there is "force of law" and all that.
Failing a screening system like you describe, I would literally settle for an ability to make a repository and then just FTP specific files that I have saved locally and browsed for content. I'd be less scared if I hadn't been surprised in the past...
I guess a possible workflow for a poor-man's-version would be to hack the <Save> button in Monticello Browser so that it only works with local directory repositories (or less harshly, issues a warning for non-local repositories). Then uploading to a remote repository is a two step process requiring manual use the <Copy> button in the Repository Browser. To each pertinent class/method add "License: NDA1" to the comment. Hack the <Copy> button in the Repository Browser to scan the selected mcz for the "License" string before presenting the list of remote repositories. Alternatively, further hack the Save process to scan the newly created mcz for a "License" taint and rename it to reflect that (although that may have unintended consequence on tracking ancestors).
I probably create some of my own troubles by my naming conventions, which are my attempt at making it easy to catch my code with a wide net so I don't lose work. That same wide net worked against me with net repositories.
Bill
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Ben Coman [btc@openInWorld.com] Sent: Sunday, February 05, 2012 8:05 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload?
Schwab,Wilhelm K wrote:
Hello all,
I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community.
In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me.
Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool?
Bill
I feel I've misread your question - but my first thought is that different packages can be stored in different Repository Types. So the heart surgery stuff would be saved to only local "directory" repositories while the more general stuff would be saved to the public "http" repositories.
More generally, an interesting feature would be being able to tag both packages and repositories with a license type (eg MIT, MyCommericalLicense, OtherCompanyNDA) and the system constrain you to saving packages in compatible repositories. As an extension, some ideas for tool support might be: + being able to strip "all non-MIT" code out of an image + using a different background colour when editing non-MIT code
cheers, ben
You give me a little too much credit: I'm SCARED of their lawyers :) Beyond that, I also respect the deals we made and it is only correct to honor them. Note that one or two of the agreements are just plain silly, but we entered them in good faith. ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Ben Coman [btc@openInWorld.com] Sent: Sunday, February 05, 2012 8:55 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload? I think your concern is admirable. Businesses are sometimes shy of open source (more the GPL than MIT) for similar concerns. Providing tools to manage those concerns "might" enhance respectability in the eyes of those potential business users, but there are probably more important things for the limited resources to focus on at the moment. Schwab,Wilhelm K wrote:
Ben,
Constraints would be useful. Again, I don't dare botch this - it's silly but, there is "force of law" and all that.
Failing a screening system like you describe, I would literally settle for an ability to make a repository and then just FTP specific files that I have saved locally and browsed for content. I'd be less scared if I hadn't been surprised in the past...
I guess a possible workflow for a poor-man's-version would be to hack the <Save> button in Monticello Browser so that it only works with local directory repositories (or less harshly, issues a warning for non-local repositories). Then uploading to a remote repository is a two step process requiring manual use the <Copy> button in the Repository Browser. To each pertinent class/method add "License: NDA1" to the comment. Hack the <Copy> button in the Repository Browser to scan the selected mcz for the "License" string before presenting the list of remote repositories. Alternatively, further hack the Save process to scan the newly created mcz for a "License" taint and rename it to reflect that (although that may have unintended consequence on tracking ancestors).
I probably create some of my own troubles by my naming conventions, which are my attempt at making it easy to catch my code with a wide net so I don't lose work. That same wide net worked against me with net repositories.
Bill
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Ben Coman [btc@openInWorld.com] Sent: Sunday, February 05, 2012 8:05 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload?
Schwab,Wilhelm K wrote:
Hello all,
I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community.
In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me.
Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool?
Bill
I feel I've misread your question - but my first thought is that different packages can be stored in different Repository Types. So the heart surgery stuff would be saved to only local "directory" repositories while the more general stuff would be saved to the public "http" repositories.
More generally, an interesting feature would be being able to tag both packages and repositories with a license type (eg MIT, MyCommericalLicense, OtherCompanyNDA) and the system constrain you to saving packages in compatible repositories. As an extension, some ideas for tool support might be: + being able to strip "all non-MIT" code out of an image + using a different background colour when editing non-MIT code
cheers, ben
On 02/05/2012 12:30 PM, Schwab,Wilhelm K wrote:
Hello all,
I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community.
In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me.
Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool?
Perhaps I am daft - but why don't you use either local directories for those packages or a private ftp server (like I do)? I use pure-ftpd which is really nice because it can easily map specific users to specific "home directories". regards, Göran
You're not daft; I'm simply looking for suggestions; yours counts :) ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Göran Krampe [goran@krampe.se] Sent: Sunday, February 05, 2012 12:12 PM To: pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload? On 02/05/2012 12:30 PM, Schwab,Wilhelm K wrote:
Hello all,
I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community.
In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me.
Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool?
Perhaps I am daft - but why don't you use either local directories for those packages or a private ftp server (like I do)? I use pure-ftpd which is really nice because it can easily map specific users to specific "home directories". regards, Göran
Hi, For private code I began by using an ftp repository then switched to a WebDAV server, With a private WebDAV server you can use Monticello, Gofer etc as though you are using squeak-source - though without a front-end. If you want a front-end there is squeak-source 3 [1] Nick [1] http://ss3.gemstone.com/ss/ss3.html/Overview On 5 February 2012 18:03, Schwab,Wilhelm K <bschwab@anest.ufl.edu> wrote:
You're not daft; I'm simply looking for suggestions; yours counts :)
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [ pharo-project-bounces@lists.gforge.inria.fr] on behalf of Göran Krampe [ goran@krampe.se] Sent: Sunday, February 05, 2012 12:12 PM To: pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload?
On 02/05/2012 12:30 PM, Schwab,Wilhelm K wrote:
Hello all,
I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community.
In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me.
Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool?
Perhaps I am daft - but why don't you use either local directories for those packages or a private ftp server (like I do)?
I use pure-ftpd which is really nice because it can easily map specific users to specific "home directories".
regards, Göran
In honor of Stef, let's make this *really* simple. The pieces for what I want to do MUST exist; I just don't see how to make it happen. So let's say I have GiveThisToStef.mcz on my drive, and I have checked, and rechecked that it is clean and releasable. Can I use an FTP client or some other command line tool to put that in the in box? That way, the code will be where everyone wants it (vs. just attached to email here), and I won't have to worry about what MC might be doing that I didn't anticipate. I know MC can do the whole thing - trouble is it once did something I didn't expect, and I can't have that (legal exposure). I want a clear wall that I deliberately penetrate when I have something to share - it's that simple. Bill ________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Nick Ager [nick.ager@gmail.com] Sent: Monday, February 06, 2012 2:04 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload? Hi, For private code I began by using an ftp repository then switched to a WebDAV server, With a private WebDAV server you can use Monticello, Gofer etc as though you are using squeak-source - though without a front-end. If you want a front-end there is squeak-source 3 [1] Nick [1] http://ss3.gemstone.com/ss/ss3.html/Overview On 5 February 2012 18:03, Schwab,Wilhelm K <bschwab@anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> wrote: You're not daft; I'm simply looking for suggestions; yours counts :) ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr> [pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr>] on behalf of Göran Krampe [goran@krampe.se<mailto:goran@krampe.se>] Sent: Sunday, February 05, 2012 12:12 PM To: pharo-project@lists.gforge.inria.fr<mailto:pharo-project@lists.gforge.inria.fr> Subject: Re: [Pharo-project] Alternative to MC for upload? On 02/05/2012 12:30 PM, Schwab,Wilhelm K wrote:
Hello all,
I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community.
In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me.
Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool?
Perhaps I am daft - but why don't you use either local directories for those packages or a private ftp server (like I do)? I use pure-ftpd which is really nice because it can easily map specific users to specific "home directories". regards, Göran
Schwab,Wilhelm K wrote:
In honor of Stef, let's make this *really* simple. The pieces for what I want to do MUST exist; I just don't see how to make it happen.
So let's say I have GiveThisToStef.mcz on my drive, and I have checked, and rechecked that it is clean and releasable. Can I use an FTP client or some other command line tool to put that in the in box?
If that inbox was a ftp repository then you would be able to use a separate ftp client to upload to it. However most of the current repositories your want to deal with are http repositories that wont work with your ftp client. You might try curl (http://linux.about.com/od/commands/l/blcmdl1_curl.htm) and play around with authentication schemes to find one that matches squeaksource. However just to double-check... I understand your not wanting to use the <Save> button to store directly to a remote repository because it is hard to undo accidents. However have you specifically discounted the <Copy> button on the Repository Inspector. Try this proposed workflow... 1. In Monticello Browser, in the left-pane select your package. In the right-pane select the local-package-cache. 2. Unzip the created GiveThisToStef.1.mcz and undertake due-diligence-scan for NDA code. If all okay.... 3. In Monticello Browser, in the right-pane select your local-package-cache, click the <Open> button. 4. Select the GiveThisToStef.1.mcz. Click the <Copy> button. Select the remote repository to upload to. This seems to provide everything with you need to avoid surprises.
That way, the code will be where everyone wants it (vs. just attached to email here), and I won't have to worry about what MC might be doing that I didn't anticipate.
I know MC can do the whole thing - trouble is it once did something I didn't expect, and I can't have that (legal exposure). I want a clear wall that I deliberately penetrate when I have something to share - it's that simple.
Bill
________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Nick Ager [nick.ager@gmail.com] Sent: Monday, February 06, 2012 2:04 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload?
Hi,
For private code I began by using an ftp repository then switched to a WebDAV server, With a private WebDAV server you can use Monticello, Gofer etc as though you are using squeak-source - though without a front-end. If you want a front-end there is squeak-source 3 [1]
Nick
[1] http://ss3.gemstone.com/ss/ss3.html/Overview
On 5 February 2012 18:03, Schwab,Wilhelm K <bschwab@anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> wrote: You're not daft; I'm simply looking for suggestions; yours counts :)
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr> [pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr>] on behalf of Göran Krampe [goran@krampe.se<mailto:goran@krampe.se>] Sent: Sunday, February 05, 2012 12:12 PM To: pharo-project@lists.gforge.inria.fr<mailto:pharo-project@lists.gforge.inria.fr> Subject: Re: [Pharo-project] Alternative to MC for upload?
On 02/05/2012 12:30 PM, Schwab,Wilhelm K wrote:
Hello all,
I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community.
In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me.
Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool?
Perhaps I am daft - but why don't you use either local directories for those packages or a private ftp server (like I do)?
I use pure-ftpd which is really nice because it can easily map specific users to specific "home directories".
regards, Göran
Ok, this copy button thing is a new idea. Will investigate... I'm also going to look at MC code for the part that does the actual save. There must be a way to script that to do exactly what I want - no worries and code where it should be. Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Ben Coman [btc@openInWorld.com] Sent: Monday, February 06, 2012 3:35 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload? Schwab,Wilhelm K wrote:
In honor of Stef, let's make this *really* simple. The pieces for what I want to do MUST exist; I just don't see how to make it happen.
So let's say I have GiveThisToStef.mcz on my drive, and I have checked, and rechecked that it is clean and releasable. Can I use an FTP client or some other command line tool to put that in the in box?
If that inbox was a ftp repository then you would be able to use a separate ftp client to upload to it. However most of the current repositories your want to deal with are http repositories that wont work with your ftp client. You might try curl (http://linux.about.com/od/commands/l/blcmdl1_curl.htm) and play around with authentication schemes to find one that matches squeaksource. However just to double-check... I understand your not wanting to use the <Save> button to store directly to a remote repository because it is hard to undo accidents. However have you specifically discounted the <Copy> button on the Repository Inspector. Try this proposed workflow... 1. In Monticello Browser, in the left-pane select your package. In the right-pane select the local-package-cache. 2. Unzip the created GiveThisToStef.1.mcz and undertake due-diligence-scan for NDA code. If all okay.... 3. In Monticello Browser, in the right-pane select your local-package-cache, click the <Open> button. 4. Select the GiveThisToStef.1.mcz. Click the <Copy> button. Select the remote repository to upload to. This seems to provide everything with you need to avoid surprises.
That way, the code will be where everyone wants it (vs. just attached to email here), and I won't have to worry about what MC might be doing that I didn't anticipate.
I know MC can do the whole thing - trouble is it once did something I didn't expect, and I can't have that (legal exposure). I want a clear wall that I deliberately penetrate when I have something to share - it's that simple.
Bill
________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Nick Ager [nick.ager@gmail.com] Sent: Monday, February 06, 2012 2:04 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload?
Hi,
For private code I began by using an ftp repository then switched to a WebDAV server, With a private WebDAV server you can use Monticello, Gofer etc as though you are using squeak-source - though without a front-end. If you want a front-end there is squeak-source 3 [1]
Nick
[1] http://ss3.gemstone.com/ss/ss3.html/Overview
On 5 February 2012 18:03, Schwab,Wilhelm K <bschwab@anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> wrote: You're not daft; I'm simply looking for suggestions; yours counts :)
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr> [pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr>] on behalf of Göran Krampe [goran@krampe.se<mailto:goran@krampe.se>] Sent: Sunday, February 05, 2012 12:12 PM To: pharo-project@lists.gforge.inria.fr<mailto:pharo-project@lists.gforge.inria.fr> Subject: Re: [Pharo-project] Alternative to MC for upload?
On 02/05/2012 12:30 PM, Schwab,Wilhelm K wrote:
Hello all,
I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community.
In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me.
Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool?
Perhaps I am daft - but why don't you use either local directories for those packages or a private ftp server (like I do)?
I use pure-ftpd which is really nice because it can easily map specific users to specific "home directories".
regards, Göran
http://lmgtfy.com/?q=webdav+command-line http://stackoverflow.com/questions/1205101/command-line-utility-for-webdav-u... On 6 February 2012 07:59, Schwab,Wilhelm K <bschwab@anest.ufl.edu> wrote:
In honor of Stef, let's make this *really* simple. The pieces for what I want to do MUST exist; I just don't see how to make it happen.
So let's say I have GiveThisToStef.mcz on my drive, and I have checked, and rechecked that it is clean and releasable. Can I use an FTP client or some other command line tool to put that in the in box?
That way, the code will be where everyone wants it (vs. just attached to email here), and I won't have to worry about what MC might be doing that I didn't anticipate.
I know MC can do the whole thing - trouble is it once did something I didn't expect, and I can't have that (legal exposure). I want a clear wall that I deliberately penetrate when I have something to share - it's that simple.
Bill
------------------------------ *From:* pharo-project-bounces@lists.gforge.inria.fr [ pharo-project-bounces@lists.gforge.inria.fr] on behalf of Nick Ager [ nick.ager@gmail.com] *Sent:* Monday, February 06, 2012 2:04 AM
*To:* Pharo-project@lists.gforge.inria.fr *Subject:* Re: [Pharo-project] Alternative to MC for upload?
Hi,
For private code I began by using an ftp repository then switched to a WebDAV server, With a private WebDAV server you can use Monticello, Gofer etc as though you are using squeak-source - though without a front-end. If you want a front-end there is squeak-source 3 [1]
Nick
[1] http://ss3.gemstone.com/ss/ss3.html/Overview
On 5 February 2012 18:03, Schwab,Wilhelm K <bschwab@anest.ufl.edu> wrote:
You're not daft; I'm simply looking for suggestions; yours counts :)
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [ pharo-project-bounces@lists.gforge.inria.fr] on behalf of Göran Krampe [ goran@krampe.se] Sent: Sunday, February 05, 2012 12:12 PM To: pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload?
On 02/05/2012 12:30 PM, Schwab,Wilhelm K wrote:
Hello all,
I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community.
In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me.
Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool?
Perhaps I am daft - but why don't you use either local directories for those packages or a private ftp server (like I do)?
I use pure-ftpd which is really nice because it can easily map specific users to specific "home directories".
regards, Göran
curl -T GiveThisToStef.mcz http://www.squeaksource.com/PharoInbox On 6 February 2012 08:35, Nick Ager <nick.ager@gmail.com> wrote:
http://lmgtfy.com/?q=webdav+command-line
http://stackoverflow.com/questions/1205101/command-line-utility-for-webdav-u...
On 6 February 2012 07:59, Schwab,Wilhelm K <bschwab@anest.ufl.edu> wrote:
In honor of Stef, let's make this *really* simple. The pieces for what I want to do MUST exist; I just don't see how to make it happen.
So let's say I have GiveThisToStef.mcz on my drive, and I have checked, and rechecked that it is clean and releasable. Can I use an FTP client or some other command line tool to put that in the in box?
That way, the code will be where everyone wants it (vs. just attached to email here), and I won't have to worry about what MC might be doing that I didn't anticipate.
I know MC can do the whole thing - trouble is it once did something I didn't expect, and I can't have that (legal exposure). I want a clear wall that I deliberately penetrate when I have something to share - it's that simple.
Bill
------------------------------ *From:* pharo-project-bounces@lists.gforge.inria.fr [ pharo-project-bounces@lists.gforge.inria.fr] on behalf of Nick Ager [ nick.ager@gmail.com] *Sent:* Monday, February 06, 2012 2:04 AM
*To:* Pharo-project@lists.gforge.inria.fr *Subject:* Re: [Pharo-project] Alternative to MC for upload?
Hi,
For private code I began by using an ftp repository then switched to a WebDAV server, With a private WebDAV server you can use Monticello, Gofer etc as though you are using squeak-source - though without a front-end. If you want a front-end there is squeak-source 3 [1]
Nick
[1] http://ss3.gemstone.com/ss/ss3.html/Overview
On 5 February 2012 18:03, Schwab,Wilhelm K <bschwab@anest.ufl.edu> wrote:
You're not daft; I'm simply looking for suggestions; yours counts :)
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [ pharo-project-bounces@lists.gforge.inria.fr] on behalf of Göran Krampe [ goran@krampe.se] Sent: Sunday, February 05, 2012 12:12 PM To: pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload?
On 02/05/2012 12:30 PM, Schwab,Wilhelm K wrote:
Hello all,
I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community.
In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me.
Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool?
Perhaps I am daft - but why don't you use either local directories for those packages or a private ftp server (like I do)?
I use pure-ftpd which is really nice because it can easily map specific users to specific "home directories".
regards, Göran
That looks like a winner. I'll try a test when I'm really awake. Sorry to be dense, but I'm trying to help w/o doing anything awful in the process. Thanks! Bill ________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Nick Ager [nick.ager@gmail.com] Sent: Monday, February 06, 2012 3:38 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload? curl -T GiveThisToStef.mcz http://www.squeaksource.com/PharoInbox On 6 February 2012 08:35, Nick Ager <nick.ager@gmail.com<mailto:nick.ager@gmail.com>> wrote: http://lmgtfy.com/?q=webdav+command-line http://stackoverflow.com/questions/1205101/command-line-utility-for-webdav-u... On 6 February 2012 07:59, Schwab,Wilhelm K <bschwab@anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> wrote: In honor of Stef, let's make this *really* simple. The pieces for what I want to do MUST exist; I just don't see how to make it happen. So let's say I have GiveThisToStef.mcz on my drive, and I have checked, and rechecked that it is clean and releasable. Can I use an FTP client or some other command line tool to put that in the in box? That way, the code will be where everyone wants it (vs. just attached to email here), and I won't have to worry about what MC might be doing that I didn't anticipate. I know MC can do the whole thing - trouble is it once did something I didn't expect, and I can't have that (legal exposure). I want a clear wall that I deliberately penetrate when I have something to share - it's that simple. Bill ________________________________ From: pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr> [pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr>] on behalf of Nick Ager [nick.ager@gmail.com<mailto:nick.ager@gmail.com>] Sent: Monday, February 06, 2012 2:04 AM To: Pharo-project@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> Subject: Re: [Pharo-project] Alternative to MC for upload? Hi, For private code I began by using an ftp repository then switched to a WebDAV server, With a private WebDAV server you can use Monticello, Gofer etc as though you are using squeak-source - though without a front-end. If you want a front-end there is squeak-source 3 [1] Nick [1] http://ss3.gemstone.com/ss/ss3.html/Overview On 5 February 2012 18:03, Schwab,Wilhelm K <bschwab@anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> wrote: You're not daft; I'm simply looking for suggestions; yours counts :) ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr> [pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr>] on behalf of Göran Krampe [goran@krampe.se<mailto:goran@krampe.se>] Sent: Sunday, February 05, 2012 12:12 PM To: pharo-project@lists.gforge.inria.fr<mailto:pharo-project@lists.gforge.inria.fr> Subject: Re: [Pharo-project] Alternative to MC for upload? On 02/05/2012 12:30 PM, Schwab,Wilhelm K wrote:
Hello all,
I have a fair amount of code that I can't/don't dare release because it involves intellectual property that I do not own, and access under non-disclosure agreements (some of which are silly, but need to be respected regardless). None of that code it is relevant to you (unless you do heart surgery at home), but I need to keep it separate from things like GSL, PLplot, FFI tweaks, etc., that should interest the community.
In the past, I've saved to http repositories and been surprised at things (fortunately, nothing toxic) that were released w/o my intent. Squeak Source long since lost the code in question, but it put a fear of MC in me.
Is there a way to use gofer or something else to send specific .mcz files that I want to make available? Some other tool?
Perhaps I am daft - but why don't you use either local directories for those packages or a private ftp server (like I do)? I use pure-ftpd which is really nice because it can easily map specific users to specific "home directories". regards, Göran
participants (6)
-
Ben Coman -
Dave Mason -
Göran Krampe -
Nick Ager -
Schwab,Wilhelm K -
Stéphane Ducasse