If you'd be more comfortable with a spreadsheet, then I'd say "go
ahead", and that you should use Google Spreadsheets with "public view"
turned on so that everybody can see it.
The issue tracker was used simply because we did not have a good way
to track the patches. The tracker does have the "attachment" feature,
which is handy (so you don't have to dig around the mailing list to
find the patch). I don't recall if Google Spreadsheets have
attachments. It probably does.
The tracker does allow for others to make edits, while you could share
the spreadsheet with other editors.
Personally, I believe it is your choice, and what makes things easier
for you to track these things. You *do* need to involve the other devs
and make it possible for them to know about outstanding patches. The
public spreadsheet works, along with (say) a weekly mailing of the
outstanding patches to the list. That said, I can defiitely see the
argument the other way: use the tracker for cooperative
editing/comments/etc.
Cheers,
-g
On Thu, Mar 12, 2009 at 15:01, Gavin 'Beau' Baumanis
<gavinb_at_thespidernet.com> wrote:
> Hi everyone,
>
> When I originally volunteered, one of my first ideas was to a create a
> public facing web page of some sort,
> Perhaps just scheduling the HTMLing and publication of a spreadsheet, that I
> would keep up to date with details along the lines of;
>
> Initial Post Date
> Latest Post Date
> Issue #,
> Voted,
> Merged,
> Backported etc...
>
> I thought I would use it for my own personal requirements in keeping in
> touch with patches (as per my role) and if anyone else found it useful to
> look at - well that's fine too.
> There's no "real" effort required in keeping it up to date and might well
> just stop a patch or two from falling into oblivion.
>
> I haven't actually done this though, because it seemed to be replicating the
> data housed in the issue tracker which Greg has pointed out..
>
> So I have just been keeping an eye on things through constant review of the
> @dev mailing list and using a few mail sorting rules.
> While I certainly pay "special" attention to any mail that has the [PATCH
> prefix - I review all @dev posts, just in case.
>
> I'm still happy to bring about the spreadsheet if people truly see it as
> being appropriate, otherwise I'll just keep on using the issue tracker as
> has been the "custom".
>
> Beau.
>
> On 12/03/2009, at 11:19 PM, Greg Stein wrote:
>
>> He may not have noticed because [PATCH] was not in the subject line
>> (we request that specifically for this reason)
>>
>> And unless things have changed since I was here last, the patches
>> should be hanging out in our issue tracker.
>>
>> Cheers,
>> -g
>>
>> On Thu, Mar 12, 2009 at 12:18, Stefan Sperling <stsp_at_elego.de> wrote:
>>>
>>> On Thu, Mar 12, 2009 at 10:40:59PM +1300, Alan Wood wrote:
>>>>
>>>> I was thinking that it would be nice to be able to see a 'pending
>>>> patches' list somewhere. I'm sure Gavin has something like this but
>>>> could it be made more accessible to all?
>>>
>>> That would certainly be nice!
>>>
>>> Stefan
>>>
>>>
>>
>> ------------------------------------------------------
>>
>> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1312600
>
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1313193
Received on 2009-03-12 15:44:55 CET