On Thu, Feb 19, 2009 at 10:17 PM, Stephen J. Turnbull
turnb...@sk.tsukuba.ac.jp wrote:
Overall, I recommend use of Google Docs for Python-Ideas level of
PEP drafts.
+1! I also like Google Sites for collaborative editing.
--
Cheers,
Leif
___
On Sat, Feb 21, 2009, rdmur...@bitdance.com wrote:
Not that I'm expecting to be working on PEPs any time soon, but just as a
different perspective, I would find the effort to open up Google docs to
be a much higher barrier to doing some editing tweaks than the dvcs case.
For me, the big
On 21-02-2009, Stephen J. Turnbull wrote:
Summary:
Google Docs is easy to use, featureful, and here now. Since AIUI the
PEPs eventually need to be hosted at python.org, I see Google Docs as
an immediate replacement for email transmission of early drafts of
PEPs, not as a permanent solution
-On [20090220 18:51], Guido van Rossum (gu...@python.org) wrote:
I still don't like wikis for this purpose very much -- a person
editing effectively grabs a lock on the whole file.
Imagine a Wiki with a cross-polination of Etherpad [1], that would resolve
that complaint.
[1] http://etherpad.com/
On Sat, 21 Feb 2009 at 01:12, Jeff Hall wrote:
Not that I'm expecting to be working on PEPs any time soon, but just as a
different perspective, I would find the effort to open up Google docs to
be a much higher barrier to doing some editing tweaks than the dvcs case.
For the DVCS, I'd just write
On Sat, Feb 21, 2009 at 6:25 AM, rdmur...@bitdance.com wrote:
On Sat, 21 Feb 2009 at 01:12, Jeff Hall wrote:
Not that I'm expecting to be working on PEPs any time soon, but just as a
different perspective, I would find the effort to open up Google docs to
be a much higher barrier to doing
On 21-02-2009, Guido van Rossum wrote:
On Sat, Feb 21, 2009 at 6:25 AM, rdmur...@bitdance.com wrote:
On Sat, 21 Feb 2009 at 01:12, Jeff Hall wrote:
Not that I'm expecting to be working on PEPs any time soon, but just as a
different perspective, I would find the effort to open up Google docs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 20, 2009, at 10:56 PM, Stephen J. Turnbull wrote:
(1) and (2) are obvious, I think, and I don't know how much (3) really
matters when the editors are a small group. But I was surprised by
how much (4), and (5) contributed to my experience
Stephen J. Turnbull schrieb:
FWIW, Google Docs is almost there. Working with Brett et al on early
drafts of PEP 0374 was easy and pleasant, and Google Docs gives
control of access to the document to the editor, not the Subversion
admin. The ability to make comments that are not visible to
Georg Brandl g.brandl at gmx.net writes:
The Python Wiki should also be considered:
* Comparing versions is easy, and versions are only saved on Save
* It supports reStructuredText, so there is no need for conversion
afterwards.
And it's vendor-neutral :-)
On Fri, Feb 20, 2009 at 3:21 AM, Antoine Pitrou solip...@pitrou.net wrote:
Georg Brandl g.brandl at gmx.net writes:
The Python Wiki should also be considered:
* Comparing versions is easy, and versions are only saved on Save
* It supports reStructuredText, so there is no need for conversion
On 20-02-2009, Guido van Rossum wrote:
On Fri, Feb 20, 2009 at 3:21 AM, Antoine Pitrou solip...@pitrou.net wrote:
Georg Brandl g.brandl at gmx.net writes:
The Python Wiki should also be considered:
* Comparing versions is easy, and versions are only saved on Save
* It supports
On Fri, Feb 20, 2009 at 10:02 AM, William Dode w...@flibuste.net wrote:
On 20-02-2009, Guido van Rossum wrote:
On Fri, Feb 20, 2009 at 3:21 AM, Antoine Pitrou solip...@pitrou.net wrote:
Georg Brandl g.brandl at gmx.net writes:
The Python Wiki should also be considered:
* Comparing versions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 20, 2009, at 1:16 PM, Guido van Rossum wrote:
Isn't it the good oportunity to try a DVCS ?
That was my original suggestion, yes, but Stephen Turnbull suggested
Google Docs instead.
I found Google docs to be both very helpful and very
Summary:
Google Docs is easy to use, featureful, and here now. Since AIUI the
PEPs eventually need to be hosted at python.org, I see Google Docs as
an immediate replacement for email transmission of early drafts of
PEPs, not as a permanent solution to PEP storage.
William Dode writes:
Isn't
On Sat, 21 Feb 2009 at 12:56, Stephen J. Turnbull wrote:
(4) automatic saves of intermediate work
-- at the tweak stage, the effort to save, commit, and push to a
DVCS outweighs the effort to tweak, costing a lot of polish IME
-- wikis don't do this, and I wonder whether people would
Not that I'm expecting to be working on PEPs any time soon, but just as a
different perspective, I would find the effort to open up Google docs to
be a much higher barrier to doing some editing tweaks than the dvcs case.
For the DVCS, I'd just write a little script that would (1) update (2)
[Aside to Guido: Oops, I think I accidentally sent you a contentless
reply. Sorry!]
As a suggestion, I think this is relevant to everybody who might be
writing a PEP, so I'm cross-posting to Python-Dev. Probably no
discussion is needed, but Reply-To is set to Python-Ideas.
On Python-Ideas,
On Thu, Feb 19, 2009 at 7:17 PM, Stephen J. Turnbull
turnb...@sk.tsukuba.ac.jp wrote:
On Python-Ideas, Guido van Rossum writes:
On Thu, Feb 19, 2009 at 2:12 AM, Greg Ewing wrote:
Fifth draft of the PEP. Re-worded a few things slightly
to hopefully make the proposal a bit clearer up
19 matches
Mail list logo
