Pass ownership of sql-bricks-postgres

[Suor]

As I understand you don't intend to maintain sql-bricks-postgres. But I am. I don't like forks in such cases since they create confusion. So what do you think of passing repo ownership to me?

I am writing it here cause you are not watching sql-bricks-postgres.

[prust]

@Suor: Thank you for being willing to maintain sql-bricks-postgres!

I agree about forks creating confusion. Instead of transferring ownership, I deleted the CSNW\sql-bricks-postgres repo, which makes your repo the primary one (no longer a fork). Transferring ownership from an organization to an individual looks tricky and it looks like you would have had to delete your fork first, before I could transfer it.

With the main sql-bricks-postgres repository being under "Suor", you get more visibility as the maintainer and it's no longer under CSNW, since CSNW employees aren't maintaining it.

I'll add links to https://github.com/Suor/sql-bricks-postgres to the core sql-bricks readme and the documentation and I'll @mention everyone who has expressed an interested in postgres in a sql-bricks issue or pull request.

I transferred ownership of https://www.npmjs.org/package/sql-bricks-postgres to you, so you can edit the sql-bricks-postgres package.json to point to your repository instead of mine and do an "npm publish" to make it public.

[prust]

FYI: @nickschwab, @makebytes, @EmileSpecs, @alekbarszczewski: In #43 I removed postgres-specific clauses (LIMIT, OFFSET, RETURNING, USING) from the core SQLBricks library and put them in a separate sql-bricks-postgres library. I then transferred ownership to @Suor (see above).

To access postgres-specific clauses, just require('sql-bricks-postgres'). More details at https://github.com/Suor/sql-bricks-postgres. Now you can add postgres-specific clauses to your hearts' content and @Suor will merge them :smiley:.

If you're interested, don't forget to like and watch https://github.com/Suor/sql-bricks-postgres.