Enhancement: Sharing whole project instead of current file

[pxlrbt]

Description

Current implementation only shares current project. It would be more useful if I could share the whole project so two persons can work on different files. Ideally jumping to the file by clicking an avatar.

Is anything like this planned for the future?

[alrz]

Had a similar idea, something like "code conference": basically, allows you to share a read-only workspace to others. Would like to know if this is practical. Thanks.

[pxlrbt]

I was not only thinking about a "read-only" workspace, but also the possibility to edit other files. But maybe more fine-grained control would be interesting like: Read/Write; One File/Multiple Files/Whole project.

[VariableClass]

👍

[dennisvandehoef]

A colleague and I tested it, and it was the first thing we mentioned as "needed to be useful", but we also agreed that it would be enough to "only" share the open tabs. I mean, I have the same code base on my computer, so i can use that to find out which extra file is needed, and I can ask him to open it. In case security might be a big issue against it. ;)

[alrz]

@dennisvandehoef Good point. But it wouldn't be the case if the workspace is read-only. The tabs being changed should be distinguishable anyways, but at the same time you should be able to explore other files if you want. This is the desirable setting for a "code conference" use case.

[pxlrbt]

@dennisvandehoef Thats why it would be good to have finer control. So you can set up read-only or write only to certain files. So you can choose your own security level.

For example a use case for browsing the whole project would be helping someone with his project, or looking for some bugs, so you down have to setup the code yourself. Would make it easier than setting up a Codepen every time.

[jasonrudolph]

Thanks for taking the time to share this idea! :bow: Repository-wide sharing and/or multi-file sharing is indeed something we'd like to provide in the future.

As we prioritize future work, we'll be looking at feedback issues like this one to determine where we can deliver the most benefit with the available engineering resources (i.e., full-time Atom engineers, community maintainers, and new contributors). In the meantime, if this is a feature that would bring you joy in your daily workflow, adding a :+1: emoji reaction to the issue body is a great way to let us know.

[jasonrudolph]

:wave: Good news for people interested in collaborating on multiple files simultaneously: Teletype v0.3.0 adds preliminary support for hosts to share multiple simultaneous files with guests. Guests are free to navigate among the files shared by the host, and guests can edit those files independently of the file that the host is currently viewing/editing.

(demo gif)

This update is the first step toward implementing RFC-001. Note that RFC-001 focuses on the host sharing their workspace, which is a bit different than the host sharing an entire project. (See Rational and alternatives in RFC-001). We're interested in Teletype allowing a host to share an entire project at some point in the future. In the meantime though, we anticipate that sharing a workspace will address many of the use cases that developers have in mind when wanting to share an entire project.

If you're interested in tracking the progress on RFC-001, feel free to subscribe to the tracking issue for updates. 👌

[0n11san]

@jasonrudolph , is this update part of the main release now or is it a beta we have to dl ?

[jasonrudolph]

@0n11san: All Teletype releases are currently considered to be "beta" releases. This update is included in Teletype v0.3.0 and newer. If you already have Teletype installed, Atom should prompt you to update to the latest version (currently v0.5.0).

[AGkitchen]

Hi. After testing Teletype a bit and looking into this issue/reading the above comments, here's my 2 squid: The most important way for me to be able to share is definitely to share the PROJECT FOLDER in its entirety. There is little utility in having to ping someone to nav over to a file so you can see it again, while hoping they never timeout. While sharing many files over Telemetry, any problem means I need to go click a bunch of tabs in a row. So the best way to handle security/selective sharing in this case it seems would be to use something like a GITIGNORE, and just list any patterns or filters for who you'd like to not see what.

[sancarn]

@AGkitchen Before a full permission system (like GITIGNORE) is setup, it makes sense to me that a simple 'stepping stone' would be to simply allow the guest to see the project tree, and request that files should be opened in the host's editor.

Later a role system could be implemented on top of this base functionality.

Here's how I see the development of this feature request:

• Allow guests to see the host's active project - Most important because if needed a guest can request a host (verbally or through a chat client) to open a file.
• Allow users to request a file to be opened (right click --> request teletype connection). Allow host to accept and open files on acceptance.
• Hiding the requested file's editor pane (unless the host desires to view it of course).
• Allow host to give guest permanent access: "allow once", "allow always", "ignore once", "ignore always"
• Allow host to save settings locally for a specific project (in a ".teletype/config.json" file in either the project folder or the .atom root folder.)
• Allow hosts to assign roles to guests, have the roles determine what files the guest has access to.

[ameliaikeda]

Been using teletype extensively at work with other devs on a new project, and while it's fantastic, the thing we'd really need in order to be even nearly as productive as in-person pairing is having access to the whole project. We're working on golang projects, and the ability to quickly jump between packages is ridiculously important!

[webtheo]

Is there any update? I think this is very important!

[BlueskyFR]

Being able to share an entire project is very important AND dangerous. When the "share" button is pressed, the user should be prompted whether he wants to share only the current file or the entire project. This means that git only becomes a way to have a backup as all the work is done using P2P! This would simply be amazing.

Any update on this by the way?

[ghost]

Will there be a function to permanently share the file to editors, similar to the way Google Drive works? This way, the host does not have to be online for guests to edit. Is there another way to do this?

Thanks!

[mikefrederick]

Unfortunately this has myself and my team using VSCode + VS Live Share as we pair quite heavily. I miss atom :(. Do you need help contributing to this feature? Is there a way we can be given some direction or thoughts as to the route that might be taken?

[scoutchorton]

Will there be a function to permanently share the file to editors, similar to the way Google Drive works? This way, the host does not have to be online for guests to edit. Is there another way to do this?

Thanks!

I would like this. I think possibly having a server version of Teletype would be a good implementation. Possibly have a backend of SFTP, have some handshake to connect to a project on a server, and have all the regular teletype features from there.

Me and a friend are working on a project, but we have to push to Git when we're dealing with programming flaws. Personally, I don't feel like Git should be used this way with many, many commits, but maybe I'm wrong! It would be nice to share an entire folder (like Google Drive), and be able to simultaneously edit the project.

Interesting idea to keep in mind...

[dhdbtkd]

It would be nice to share an entire folder (like Google Drive), and be able to simultaneously edit the project.

[bnebeker]

Is it on the roadmap to have the project view on the sidebar as well, or just the ability for the host to open files and the guest to see only the opened files in new tabs? I can see his code when he opens it, but my project view is blank. Would be helpful to have access to all files in the project, with some sort of host approval of course.

cc @jmwoloso

[BlueskyFR]

The project seems almost abandoned. You can take a look at VSCode's Liveshare which works really well. Moreover (and sadly), Atom generally almost doesn't receive any new update while VSCode does.

[bnebeker]

Dang - not a fan of VSCode but will give it a shot. Thanks!

[BlueskyFR]

Dang - not a fan of VSCode but will give it a shot. Thanks!

I was thinking the same thing at the beginning too! But you can install the Atom keybindings extension on VSCode for example, and there is way more extensions (and more maintained!) as well! I strongly advise anyone reading this to give VSCode a try while Atom stays in its current state (not gaining any new features).

[sancarn]

Hey @pxlrbt is there any reason why you closed this issue? If you're getting annoyed about notifications on the thread you can unsubscribe from the issue itself, instead of closing it...

[BlueskyFR]

Yes this issue is still unresolved! Why are you closing it?

[pxlrbt]

Sorry it seemed as this won't be implemented. But you're right. Unsubscribing is the better solution.