Instead of coding directly into a etherpad instance or saving our work into an etherpad instance, how about we use Bzr and launchpad, and use IRC and etherpad as a way of communicating. This way we can work on our own branches of the code (a good advantage of the distributed version control) and use the code-review and merge tools within launchpad to merge our changes into the branch.
On 14 March 2010 21:14, Thomas Ibbotson <[email protected]> wrote: > On 14 March 2010 20:15, Alan Pope <[email protected]> wrote: > > > > Consider using our Etherpad instance instead of gobby. It's browser > > based and as such requires no software install. It's also cooler ;) > > > > http://pad.ubuntu-uk.org/ > > > > If you visit that page you'll get an automagically generated new > > document, just share the URL with people and you're off and running. > > > > If you want a friendly-named pad then add the page name on the end like > this:- > > > > http://pad.ubuntu-uk.org/pyweek2010 > > This page now exists. In terms of actually writing the code, I guess > we could have pages like: pyweek2010_main, pyweek2010_library etc. > given that we'll probably want more than one source file. > > > > > ..and it will prompt for new page creation. Then pass that URL around. > > As you suggested: http://pad.ubuntu-uk.org/pyweek2010 > > > > > Massive thanks to Dave Walker for setting it up and maintaining it. > > > Indeed :) > > -- > [email protected] > https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk > https://wiki.ubuntu.com/UKTeam/ >
-- [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
