Paying For Privacy?

#1

Post by precium » Wed, Sep 25, 2013, 9:20 PM UTC

Re: Paying For Privacy?

#2

Post by cheshire137 » Wed, Sep 25, 2013, 9:40 PM UTC

My team uses pull requests extensively. The master branch is considered good, clean, production-ready code. Anything you want to get into production gets there by way of a pull request. Want to add a feature? Fix a bug? Make a branch, do your thing, and create a pull request against master. The rest of the team reviews your code in the pull request; the comments in a pull request are an excellent feature. My job would be ridiculously harder without pull requests.

Re: Paying For Privacy?

#3

Post by ehm_may » Wed, Sep 25, 2013, 9:49 PM UTC

I pay github for the same reason I pay heroku. It just works and I don't have to do anything. That is why they exist. Sure you can set up your own git server, but what do you do when it goes down?

Re: Paying For Privacy?

#4

Post by Scriptor » Wed, Sep 25, 2013, 9:52 PM UTC

cheshire137 wrote: post #2

My team uses pull requests extensively. The master branch is considered good, clean, production-ready code. Anything you want to get into production gets there by way of a pull request. Want to add a feature? Fix a bug? Make a branch, do your thing, and create a pull request against master. The rest of the team reviews your code in the pull request; the comments in a pull request are an excellent feature. My job woul…

Right, I thought one of the big benefits about pull requests was that it let other devs easily view the diffs before merging a change in, not to mention making it easier for people to discuss the changes. I guess if you don't want to do that then it's easier to just pass around patches and merge.

Re: Paying For Privacy?

#5

Post by zdw » Wed, Sep 25, 2013, 9:53 PM UTC

I keep a lot of personal/private data in git repos. I'd rather have this data on my own hardware or servers I admin, can audit, can apply unusual SSH security policy to, etc. gitolite and gitlab are great Github replacements for this purpose.

That said, I still use github (or bitbucket, etc.) when I want to share code - it's still the best place to do that.

I just don't need their private service, which appears to be the same case as the author.

Re: Paying For Privacy?

#6

Post by shocks » Wed, Sep 25, 2013, 9:55 PM UTC

ehm_may wrote: post #3

I pay github for the same reason I pay heroku. It just works and I don't have to do anything. That is why they exist. Sure you can set up your own git server, but what do you do when it goes down?

The same thing you do when GitHub goes down...

PANIC and flock to HN to comment on a minor outage!!! - wait, no. git is a distributed system. You continue as you were and nothing changes.

Re: Paying For Privacy?

#7

Post by zrail » Wed, Sep 25, 2013, 9:55 PM UTC

Watch out with the sending email directly from an EC2 instance. You don't really have a fixed IP so rDNS isn't going to work very well, and that's still a front-line filter for a lot of big email providers.

Re: Paying For Privacy?

#8

Post by lelandbatey » Wed, Sep 25, 2013, 9:56 PM UTC

cheshire137 wrote: post #2

My team uses pull requests extensively. The master branch is considered good, clean, production-ready code. Anything you want to get into production gets there by way of a pull request. Want to add a feature? Fix a bug? Make a branch, do your thing, and create a pull request against master. The rest of the team reviews your code in the pull request; the comments in a pull request are an excellent feature. My job woul…

Exactly, the benefit of Github is exactly what it says on the tin:

    "Build software better, together."

Or, like it says on my Github mug:

    "Github: social coding."

Seriously, if it's just you the self hosting your git repos is much easier, cheaper, and you'll have a better handle on how git actually works. However, if you're on a team or dealing with other people, the collaborative features of Github are awesome.

Once again, the correct answer is "use the right tool for the job."

Re: Paying For Privacy?

#9

Post by plorkyeran » Wed, Sep 25, 2013, 9:56 PM UTC

Scriptor wrote: post #4

cheshire137 wrote: post #2

My team uses pull requests extensively. The master branch is considered good, clean, production-ready code. Anything you want to get into production gets there by way of a pull request. Want to add a feature? Fix a bug? Make a branch, do your thing, and create a pull request against master. The rest of the team reviews your code in the pull request; the comments in a pull request are an excellent feature. My job woul…

Right, I thought one of the big benefits about pull requests was that it let other devs easily view the diffs before merging a change in, not to mention making it easier for people to discuss the changes. I guess if you don't want to do that then it's easier to just pass around patches and merge.

Viewing changes in a pull request is no easier than viewing the changes in a patchset (or rather, if it is you're using the wrong tools). For an established team, a PR-based workflow and a mailing list based workflow (where you mail patchsets to the mailing list and discuss them there) are not very different, but PRs are a lot friendlier to outside contributors.

Re: Paying For Privacy?

#10

Post by toomuchtodo » Wed, Sep 25, 2013, 9:57 PM UTC

zrail wrote: post #7

Watch out with the sending email directly from an EC2 instance. You don't really have a fixed IP so rDNS isn't going to work very well, and that's still a front-line filter for a lot of big email providers.

If you are an Amazon EC2 user, you can get started with Amazon SES for free. You can send 2,000 messages for free each day when you call Amazon SES from an Amazon EC2 instance directly or through AWS Elastic Beanstalk. Many applications are able to operate entirely within this free tier limit.

http://aws.amazon.com/ses/pricing/

You could also use Mailgun, mandrillapp.com, etc. I believe they all provide at least 10-12K emails/month for free, by calling a RESTful web api.