[Inpycon] Issue / Task Tracking for Pycon India

Dhananjay Nene dhananjay.nene at gmail.com
Tue Feb 15 09:42:27 CET 2011


On Tue, Feb 15, 2011 at 1:45 PM, Dhananjay Nene <dhananjay.nene at gmail.com>wrote:

> On Tue, Feb 15, 2011 at 1:15 PM, Noufal Ibrahim <noufal at gmail.com> wrote:
>
>>
>> Regardless of which tool you use for issue tracking, one thing I must
>> *heavily* emphasise is that the mailing list (and a bunch of wiki pages)
>> should be the main vehicles for coordination, discussion and decision
>> making.
>>
>
> Sure, I shall try to set up a "hose-pipe" from the task tracking into the
> mailing list. Please be prepared for some low level fine grained emails as
> well (eg. task got reassigned from A to B).
> While I might have to send a few (hopefully no more than 5)
> trial/registration messages to this mailing list. I trust that can be
> overlooked. Even the messages will have a reply-to pointing to the specific
> ticket id which will get incorporated as comments against the specific
> ticket (example : pycon-india-2011+<ticket_number>@tickets.assembla.com).
> What we need to ensure is that mails originating from
> pycon-india-2011 at alerts.assembla.com (which is how the mails will be
> sourced) be allowed to be posted to this mailing list. I hope except for
> minor inconveniences in the brief transition things should continue to be
> comfortable for all.
>
> The hosepipe to this mailing list is turned on and as far as I can tell,
all ticket activities will get streamed to this mailing list. The mailing
list administrators will need to enable
pycon-india-2011 at alerts.assembla.comas a valid source email id in case
there are any email id based validations
at source. Replying to these emails directly should also directly update the
ticket data by inserting the content as comments (though be careful if you
are not directly replying to a reply/forward of the mail that came from
assembla - in which case the reply-to would've been set to someone else).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/inpycon/attachments/20110215/1994c10a/attachment.html>


More information about the Inpycon mailing list