[prev in list] [next in list] [prev in thread] [next in thread] 

List:       python-dev
Subject:    Re: [Python-Dev] Thoughts fresh after EuroPython
From:       Tarek_Ziadé <ziade.tarek () gmail ! com>
Date:       2010-07-26 23:18:17
Message-ID: AANLkTinB63Td4Qw9mP0bxo=KGZb1r5=j9yGB2DPxogBU () mail ! gmail ! com
[Download RAW message or body]

On Mon, Jul 26, 2010 at 11:57 PM, "Martin v. Löwis" <martin@v.loewis.de> wrote:
>> Basically, I think what you'd like to have is Martin saying "I'm going to
>> work on this feature", in addition to "I implemented this feature now"
>> afterwards.  That shouldn't be too hard.
>
> I'm not very good at blogging (more specifically, I never blog).
>
> People interested in following even the tinyest changes to PyPI should
> watch the commit list; it is unlikely that I will post each and every
> change to catalog-sig.
>
> People are then free to blog about the changes as they please (and I
> would appreciate any help I can get in announcing changes).

I think what would be good is to have you discussing the  "I'm going
to work on this feature"
at the ML before it's started. And not discovering it randomly at PyPI
or the commit list,
leading to a heated discussion or a poll.

I would classify the changes in three kinds:

- minor: a new feature, a UI bugfix etc
- important: a new feature that changes a lot the end-user experience
(like the rating system)
- major: a change to the APIs (HTTP/XML-RPC)

I think you should briefly present your plans for important or major
changes in catalog-SIG
prior to starting them, so we can discuss them.

Regards
Tarek

-- 
Tarek Ziadé | http://ziade.org
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-dev%40progressive-comp.com

[prev in list] [next in list] [prev in thread] [next in thread]