[GRASS-dev] Re: GRASS at GForge first steps - second encounter

[Maris Nartiss]

Hi,

I signed up to GForge to test new GRASS trackers. I submited two
patches to code patch tracker and here are my observations.

* In view issue page (i.e. [1]), please, add attribute "align=left" to
TD element containing user's submitted text. In some browsers it's
centred and it is NOT a browser bug but a correct interpretation of
CSS 2.1 spec - it inherits align parameter from first parent that HAS
such attribute set.

* I do not see all info that I entered when I was submiting patch.
Missing are CVS checkout date, GRASS version, GRASS component. They
should be visible when viewing issue.

* Issue browse mode lacks column "Last changed" and possibility to
sort by thath colum. IMHO it's really usefull to sort issues by
activity.

As I understand, new issue forwarding to -dev ML is not yet enabled.
Meanwhile could You clarify a bit for all dev's how patch handling
should be done using this new and wonderfull tool. I mean - how long
patch/bug should lie in tracker till it is considered that nobody
cares bout it and fallback mechanisms should be activated? Should
devel make a note to issue while he is inspecting patch (if it's not
oneliner or trivial)? Should there be some "areas of interest" defined
like Michael monitoring GUI related bugs/patches etc?


WBR,
Maris.

[1] http://wald.intevation.org/tracker/index.php?func=detail&aid=262&group_id=21&atid=205

2007/1/15, Maciej Sieczka <tutey at o2.pl>:
> Hi,
>
> In the past few weeks as time allowed I finished setting up the
> trackers at GForge.
>
> Before they are announced for users, I'm kindly asking
> developers to have a look at what was done and let me know if there
> is something that still needs a change or fix.
>
> Patches are for user submitted patches, if the user doesn't have CVS
> write access but wants to share his fix. They will also be used for
> patches which shouldn't go into CVS (yet), but we want to keep the
> track of them for later.
>
> When patch is submitted to a patches tracker, and nobody steps up to
> take care of the patch, there are first-contacts also, who will do a
> similar job here:
>
> As I don't have any programming skills, and my insight into GRASS
> website is poor, code and website experts are inevitable to evalute the
> submitted patches. For docs patches I'll try to help Martin as I can.
> Many thanks Guys!
>
> All trackers' new submitions will be automatically forwarded to
> grass-dev list. All the following traffic will be stored in the tracker
> and forwarded only to folks discussing the ticket. However, anybody can
> "monitor" (see GForge manual [6]) any ticket, or a whole tracker, to be
> forwaded all the related traffic.