Developer collaboration control system

Patent metadata

Field	Value
Publication number	US-2020201625-A1
Application number	US-201816228415-A
Country	US
Kind code	A1
Filing date	Dec 20, 2018
Priority date	Dec 20, 2018
Publication date	Jun 25, 2020
Grant date	—

Abstract

A method includes transmitting a first copy of a committed version of source code to a first client device and a second copy of the committed version of the source code to a second client device and receiving, from the first client device, a selection of a presentation type that specifies access privileges to changes made by a first user associated with the first client device to the first copy of the committed version. The method further includes receiving, from the first client device, first changes to a part of the source code of the first copy of the committed version and transmitting the first changes and instructions for real-time presentation of the first changes in accordance with the selected presentation type. The method further includes storing the first changes in a first record of changes that is associated with a first user of the first client device.

First claim

What is claimed is:

1 . A method comprising:
transmitting, by a server device, a first copy of a committed version of source code to a first client device and a second copy of the committed version of the source code to a second client device for real-time collaborative editing of the source code on a source control platform; receiving, from the first client device, a selection of a first presentation type from a plurality of presentation types, wherein each of the plurality of presentation types specify, for one or more other users of the source control platform, corresponding access privileges to source code changes made by a first user associated with the first client device to the first copy of the committed version of the source code, wherein the first presentation type specifies first access privileges to the source code changes and a second presentation type specifies second access privileges to the source code changes, wherein the second access privileges of the second presentation type are different from the first access privileges of the first presentation type; receiving, from the first client device, first source code changes to a part of the source code of the first copy of the committed version; transmitting, to the second client device, the first source code changes and instructions for real-time presentation of the first source code changes with the second copy of the committed version at the second client device in accordance with the first presentation type; and storing the first source code changes in a first record of changes that is associated with the first user of the first client device.

2 . The method of claim 1 further comprising:
receiving, from the first client device, a commit request that identifies at least some source code changes in the first record of changes and requests that the identified source code changes of the first record of changes be committed to the committed version of the source code stored at a repository of the source control platform;
responsive to receiving the commit request, committing the identified source code changes of the first record of changes to the committed version of the source code stored at the repository to generate a new committed version of the source code; and
transmitting a first copy of the new committed version of the source code to the first client device and a second copy of the new committed version of the source code to the second client device for the real-time collaborative editing of the source code.

3 . The method of claim 1 , further comprising:
receiving, from the first client device, a selection of a first publication type from a plurality of publication types, wherein the plurality of publication types specify, for the one or more other users of the source control platform, execution privileges to the source code changes made by the first user to the first copy of the committed version of the source code; and responsive to receiving the selection of the first publication type, transmitting first instructions for the execution privileges to the second client device that cause the second client device to propagate the first source code changes to the second copy of the committed version at the second client device, wherein the first instructions for the execution privileges cause the first source code changes to be propagated to the second copy to allow the second copy of the committed version comprising the first source code changes to be prepared for execution at the second client device.

4 . The method of claim 1 further comprising:
receiving, from the first client device, a selection of a second publication type from a plurality of publication types, wherein the plurality of publication types specify, for the one or more other users of the source control platform, execution privileges to the source code changes made by the first user to the first copy of the committed version of the source code; and
responsive to receiving the selection of the second publication type, transmitting second instructions for the execution privileges to the second client device that prevent the second client device from propagating the first source code changes to the second copy of the committed version at the second client device, wherein the second instructions for the execution privileges cause the first source code changes to be prohibited from propagating to the second copy to prevent the first source code changes to be prepared for execution with the second copy of the committed version at the second client device.

5 . The method of claim 1 , wherein transmitting of the instructions for the real-time presentation of the first source code changes with the second copy of the committed version at the second client device in accordance with the first presentation type causes the second client device to display a visual indication of a portion of the source code of the second copy of the committed version that includes the first source code changes without displaying content of the first source code changes.

6 . The method of claim 5 , wherein transmitting of the instructions for the real-time presentation to the second client device further causes the second client device to display a graphical element that is selectable to display the content of the first source code changes.

7 . The method of claim 1 , wherein transmitting of the instructions for the real-time presentation of the first source code changes with the second copy of the committed version at the second client device in accordance with the first presentation type causes the second client device to display content of the first source code changes in a portion of the second copy of the committed version in real-time and prohibits a second user of the second client device from editing the portion of the second copy of the committed version that includes the first source code changes.

8 . The method of claim 1 , wherein the transmitting of the instructions for the real-time presentation of the first source code changes with the second copy of the committed version at the second client device in accordance with the first presentation type causes the second client device to display content of the first source code changes in real-time and to allow a second user of the second client device to edit a portion of the second copy of the committed version that includes the first source code changes.

9 . The method of claim 1 , further comprising:
determining a location of additional source code that is related to the first source code changes in the part of the source code of the first copy of the committed version, wherein a portion of the source code comprises the part of the source code receiving the first source code changes and the additional source code, wherein the instructions for the real-time presentation of the first source code changes with the second copy of the committed version at the second client device identify the portion of the source code.

10 . A method comprising:
receiving, by a first client device from a server device, a first copy of a committed version of source code for real-time collaborative editing of the source code on a source control platform; receiving first user input indicative of a selection of a first presentation type from a plurality of presentation types, wherein each of the plurality of presentation types specify, for one or more other users of the source control platform, corresponding access privileges to source code changes made by a first user associated with the first client device to the first copy of the committed version of the source code, wherein the first presentation type specifies first access privileges to the source code

Assignees

• Roblox Corp

Inventors

• Kryzhanovsky Michael
• Berg Tyler

Classifications

• G06Q10/103

  Workflow collaboration or project management · CPC title

• G06F8/30 Primary

  Creation or generation of source code · CPC title

• G06F8/71 Primary

  Version control (security arrangements therefor G06F21/57); Configuration management · CPC title

• G06F8/31 Primary

  Programming languages or programming paradigms · CPC title