[Inpycon] Assembla and discussions

[Dhananjay Nene]

On Tue, Feb 15, 2011 at 3:45 PM, JAGANADH G <jaganadhg at gmail.com> wrote:

>
> It should be a "Decide website software" item and the actual details of
>>> what to use, who will host etc. should be an email thread here.
>>>
>>> This is my personal view but I think it'll work better than way.
>>>
>>> Ok. Unless there is a contrary opinion, we will use the mailing list for
>> issues and assembla for task tracking
>>
>> Dhananjay
>>
>> The assembla tickets trying to *re invent the wheel* . Tasks like create a
> new mailing list, new web site etc are not required. The
> inpycon at python.org is the volunteer mailing list and we have a good nice
> web site. I think this can be customized for 2011 .
>
> Planing includes analysis of existing reusable components too
>

I was documenting these as issues to be resolved. Based on feedback, I've
already responded we could restrict assembla to task tracking and will not
use it for issue tracking. However I am not sure of the "analysis of
existing" comment.

a. The matter of website was raised on the mailing list. I just documented
that as a matter to be discussed. I even specifically stated that I could
not see any reason to not continue with status quo.
b. At no point in time the mailing list itself was also questioned. What was
questioned on one of the issues is whether the mailing list should be
subjected to fine granularity updates which are likely once we put task
tracking in place. Even the issue of an alternative mailing list
specifically acknowledged that the potential overlap with the mailing list
and that that would need to be sorted out. For now it seems like we shall
continue to use the current mailing list for all volunteer communication too
- something that I am entirely comfortable with.
c. What I was and am keen on is to have a tracking system in place. This is
so that there is a clearly visible list of items that we need to focus on
and that we do not drop items accidentally from the todo list. Also people
should get a clearly visible information about important elements in the
progress of a task in a consolidated manner. Moreover if there is slippage,
we should have a mechanism to get alerted and feel alarmed about it as well.
Many of these are not feasible on a mailing list. Obviously there were
matters related to the integration of the task tracking and the mailing list
- matters which I believe we have made reasonable progress in terms of
resolving and we shall continue to do so as feasible.

Dhananjay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/inpycon/attachments/20110215/57aea49d/attachment.html>