Opened 6 years ago

## #9177 new defect

Reported by: Owned by: gabriele.giammatteo@… lkraav normal TracPadPlugin normal 0.12

### Description

Dear all,

I'd like to rise again the TracPadPlugin idea of having a real-time collaborative environment embedded in Trac.

Now, a very nice feature of etherpad-lite is that pads can be easily embedded in any web page (see at the bottom of the announcement post for an example).

We can exploit this feature to make the TracPadPlugin embed in Trac pads coming from a running instance of the etherpad-lite. For instance each ticket page (e.g. /ticket/3) could have a pad embedded (e.g. http://myetherpadlite.example.org/p/trac-3) to let deveopers to collaborate on that ticket.

PROS:

• (seems to be) extremely easy to embed pads
• it would require just modification of the ui pages

CONS:

• it needs an etherpad-lite running instance
• pads' data is not stored in the trac db but in the etherpad-lite backend

What do you think? Anyone interested in keep investigating in this direction? I know Trac just from the user point of view and I haven't never developed any plugin/macro, so honestly I even do not know whether what i'm saying is feasible or not

Regards, Gabriele Giammatteo

### comment:1 Changed 6 years ago by lkraav

Absolutely, I've been keeping an eye on Etherpad-Lite for a little while now.

There are also Py bindings already.

In my view some sort of a workflow needs to be figured out how the collaboration happens, in what cases it is allowed, not allowed etc, and then a way to pipe results from pad editing back to trac db. I think all this is fully possible.

Find me on freenode (macmaN), Gabriele.

### comment:2 Changed 3 years ago by lkraav

http://togetherjs.com may be a feasible option to get something real going quickly

### Modify Ticket

Change Properties