From: thomas at tada.se (Thomas Hallgren) Date: Tue, 15 Jan 2013 12:36:28 +0100 Subject: [Pljava-dev] Source code move to Git In-Reply-To: <50F478FB.5030000@tada.se> References: <50F27A01.2090003@tada.se> <50F2FAEA.6090809@tada.se> <50F30C5A.9060407@tada.se> <8480FE88-E1AA-43EB-A5D1-6B155FA4BC55@me.com> <50F3D63B.3010203@tada.se> <50F478FB.5030000@tada.se> Message-ID: <50F53F3C.8000304@tada.se> A submission page has been added to the (not yet complete) wiki. Comments are welcome. https://github.com/tada/pljava/wiki/Contribution-guide - thomas On 2013-01-14 22:30, Thomas Hallgren wrote: > On 2013-01-14 19:16, Bear Giles wrote: >> I'm not sure what you need. I'm using the public google subversion >> server - I think the link is on the download page/tab/whatever. >> > I can find the code in your SVN repository for sure but I'm trying to > establish a process for submissions that will ensure that the correct > author gets credit while at the same time making the submission > traceable and easy. I plan to write a page where this process is > outlined soon enough but here's a short brief: > > 1. You ensure that you have an account at GitHub. > 2. You fork the tada/pljava repository at GitHub (just navigate to > that repository and click 'Fork'). This creates a fork named account name>/pljava. > 3. Create a local clone of that repository and add your examples to > the example module. > 4. Commit your changes to your local clone with an explanatory commit > comment. You can do several commits. > 5. Push the local clone (updates your fork at GitHub). This can also > be repeated. > 6. Submit a "pull request" at GitHub (in other words, ask tada/pljava > maintainers to merge your changes). This will automatically create an > issue with the tada/pljava repository where your commit(s) can be > reviewed and accepted. Once accepted, they are merged and will then > appear in the repository just as you entered them, with comments, > correct author, and all. > > Regards, > Thomas Hallgren > > >> >> On Mon, Jan 14, 2013 at 2:56 AM, Thomas Hallgren > > wrote: >> >> Hi Bear, >> >> I think examples like these are very valuable to the community. >> They are candidates for inclusion in our example module (we >> already have such a module). Would it be possible for you to >> provide them in the form of a pull request? >> >> Regarding the crypto stuff, also interesting. I'd love to see >> that too as a (separate) pull request. What JDK version is >> required for it to run? >> >> Regards, >> Thomas Hallgren >> >> >> On 2013-01-14 00:35, Bear Giles wrote: >>> P.S. the blog entries were at http://invariantproperties.com/ >>> >>> >>> On Sun, Jan 13, 2013 at 4:33 PM, Bear Giles >>> > wrote: >>> >>> Related to this - I created a project on google code a while >>> back that has a number of advanced examples for a series of >>> blog posts I wrote - things like user-defined types, >>> triggers, etc. I don't know if it makes sense to integrate >>> the examples into the main source tree (as an 'examples' >>> artifact), have it as a sibling project, or have it totally >>> independent. The project makes it clear that it was never >>> intended to be used as an actual library, it just contains >>> examples of how to use pl/java. >>> >>> https://code.google.com/p/postgresql-pljava-examples/ >>> >>> Also I might be able to devote a few cycles to improving the >>> crypto stuff. The motivation is that server-side crypto >>> means you could have a relatively unprivileged user perform >>> some tightly constrained functions. E.g., you may have a >>> database containing encrypted salaries but be willing to >>> provide an average salary. (Setting aside the crypto this is >>> actually a hard problem to solve since a series of careful >>> queries may reveal individual information. But at a minimum >>> you could have a function that makes sure there's at least a >>> dozen data points, decrypts them, then averages them.) >>> >>> The standard crypto extension provides a bit of this but we >>> really want to be able to toss BouncyCastle onto the jar >>> path. I've started playing with it but some key standard >>> Jave-SE classes are missing. >>> >>> >>> >>> On Sun, Jan 13, 2013 at 3:15 PM, Hal Hildebrand >>> > wrote: >>> >>> Oddly enough, I also created a maven plugin for pljava. >>> >>> Sent from my Tricorder >>> >>> On Jan 13, 2013, at 11:34 AM, Thomas Hallgren >>> > wrote: >>> >>> > On 2013-01-13 19:20, Thomas Hallgren wrote: >>> >> On 2013-01-13 18:10, Hal Hildebrand wrote: >>> >>> Is the break out of the maven modules acceptable? >>> >> >>> >> Yes, although I'd prefer if the module named 'jdbc' >>> was named 'plugin' or 'module' >>> > >>> > On second thought, 'plugin' is a bad name. We might >>> want to create a maven plug-in for pljava at some point. >>> What about 'server' to signify that this is the part >>> that runs in the server? >>> > >>> > - thomas >>> _______________________________________________ >>> Pljava-dev mailing list >>> Pljava-dev at pgfoundry.org >>> http://lists.pgfoundry.org/mailman/listinfo/pljava-dev >>> >>> >>> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: