Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Saturday June 02 2018, @02:14PM   Printer-friendly
from the good-business-or-something-else dept.

https://www.cnbc.com/amp/2018/06/01/microsoft--github-acquisition-talks-resume.html

Microsoft held talks in the past few weeks to acquire software developer platform GitHub, Business Insider reports.

One person familiar with the discussions between the companies told CNBC that they had been considering a joint marketing partnership valued around $35 million, and that those discussions had progressed to a possible investment or outright acquisition. It is unclear whether talks are still ongoing, but this person said that GitHub's price for a full acquisition was more than Microsoft currently wanted to pay.

GitHub was last valued at $2 billion in its last funding round 2015, but the price tag for an acquisition could be $5 billion or more, based on a price that was floated last year.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 4, Touché) by tomp on Saturday June 02 2018, @06:02PM (2 children)

    by tomp (996) on Saturday June 02 2018, @06:02PM (#687766)

    It's way harder than googling a tutorial. Safe to assume you can't be bothered to set up your own Git server either.

    Starting Score:    1  point
    Moderation   +2  
       Touché=2, Total=2
    Extra 'Touché' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   4  
  • (Score: 3, Disagree) by JoeMerchant on Saturday June 02 2018, @07:05PM (1 child)

    by JoeMerchant (3937) on Saturday June 02 2018, @07:05PM (#687785)

    Tutorial for Ubuntu:

    sudo apt-get install git

    mkdir repo.git

    cd repo.git

    git init --bare

    and, if you haven't disabled the default ssh server, your repo is live and ready to use. There are, of course, several hundred nuanced security considerations - all left as an exercise for the reader. Basically: if you're going to start giving people access to your machine via the ssh server - handle your ssh server with all due care. Personally, I like creating a git user with the git (no command line access) shell and only exposing ssh access to that, and requiring my outside users to give me their public ssh key so I can add them to the /home/git/.ssh/authorized_keys file - hopefully the git user's shell access is limited enough that my repo users can't monkey with the authorized_keys file, hmmm.....

    --
    🌻🌻 [google.com]