public inbox for gentoo-python@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Johan Bergström" <bugs@bergstroem.nu>
To: gentoo-python@lists.gentoo.org
Subject: [gentoo-python] Lets re-ignite the python eclass discussion
Date: Wed, 7 Dec 2011 22:45:58 +0100	[thread overview]
Message-ID: <832DA3CABDFF4D0EB6C8D911C9C47EB6@bergstroem.nu> (raw)

Hey, 

I just wanted to let you know that our document that used to live at http://typewith.me/NNW7iB4jyL now lives at http://piratepad.net/gxpXCcNNvv. This is due to typewith.me migrating (dropping history) to etherpad lite. Unfortunately etherpad lite doesn't allow you to use monospaced fonts. Ouch.

So, I moved the document. Changes between platforms include validating markdown and switching to a 80 character width (and noting it in the introduction).

Anyway. For those of you that hasn't been part of this, we're (a couple of cool katz) are trying to form a document outlining our thoughts on what the next generation eclass could look like. This does in no way state that we're unhappy with the current, or aim to replace it.

Instead of discussing on IRC or in mailing lists, this kind of collaboration should end up in somewhat close to a specification. Hopefully this makes the document usable during our journey, not just at the end. Since piratepad/typewithme has full history - should you be interested in adding your thoughts, please add where appropriate. The only rule is adding a name so history is actually trackable. Open ended questions can be added at the bottom.

So, what are you waiting for? :-)

http://piratepad.net/gxpXCcNNvv

Take care now,
Johan




                 reply	other threads:[~2011-12-07 21:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=832DA3CABDFF4D0EB6C8D911C9C47EB6@bergstroem.nu \
    --to=bugs@bergstroem.nu \
    --cc=gentoo-python@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox