On Fri, 22 Jan 2010 09:30:15 -0500, Barry Warsaw <ba...@python.org> wrote:
> On Jan 21, 2010, at 02:45 PM, R. David Murray wrote:
> email-ng is just the email package and contains some header module refactoring
> and a start on doctests for headers. The nice thing about using more doctests
> is that it can serve as the basis for improved documentation.
I will take a look at that, since I'm actively working on Header
right now. As for doctests...I agree that they are good for helping to
document the API, but IMO we are going to need more than that to get a
really good set of validation tests. I have some thoughts about that
that I'm experimenting with and will report back when I'm satisfied that
my idea is at least workable. (Whether it's a *good* idea remains to
be seen :)
> I'm sorry that it's so disorganized, but you seem to be pretty good at
> untangling nasty knots. :) Probably best to start with email6 and then just
> review the top few revisions in the other branches to see if there's anything
> useful in them.
No problem; at least you got started on it :)
> What you did isn't too bad actually. Whether it was the right thing to do
> depends on how we want to manage commit access to the email branch. I see no
> problem adding you to the ~python-dev team on Launchpad and creating the
> branch in the python project. That just means everyone in ~python-dev could
> commit to the branch (by default). I'd have no problem with that.
>
> Alternatively, we'd need to create a team for the python-email6 project so
> that folks other than just you have commit access to the branch. It's only a
> little more work that way, just because it's more things to set up, but it's
> not that big of a deal. So the question is: how locked down do you want to
> make this branch, and are there folks who would like to commit to this branch
> that shouldn't be added to ~python-dev?
My goal in using the DVCS is to make it easy for anyone to submit patches
for review, which I believe launchpad facilitates. ("Propose for merge",
right?) I don't want the branch locked too tightly, I'd rather
facilitate active contribution. So possibly making an email6 team is
better, but since I don't know what the consequences of adding someone to
~python-dev are, I don't know what would make it a bad thing for someone
to be added to it :).
> Either way, we have to remember to occasionally merge the py3k branch back
> into our branch so as to keep up on changes there.
Yes. That will probably be my job.
> >The sprint page doesn't list the core sprint yet. Any idea who is
> >organizing it this year?
>
> It might be me, but I'm not sure :). I think Brett is not going to attend the
> sprints so I'm slated to give the intro-to-sprinting talk. I'm not sure if
> that also means I've "volunteered" to organize the core sprint or not. I'll
> try to figure that out.
Well if you are we could try to hijack the whole core sprint to work on
email :)
Seriously, though, if I can be of assistance, let me know.
--David
_______________________________________________
Email-SIG mailing list
Email-SIG@python.org
Your options:
http://mail.python.org/mailman/options/email-sig/archive%40mail-archive.com
