David Crossley wrote:
I also adopted that screen for Forrest. Try adding or
editing an issue to see the new layout.
These are great improvements - thanks David.
Ross
The last couple of days some Cocoon people have been
helping to better configure Jira.
http://marc.theaimsgroup.com/?t=11334797645
The Cocoon issue entry/edit screen has been enhanced
with better prompts to explain each field.
I also adopted that screen for Forrest. Try adding or
editing an i
Gav wrote:
>
> Although I doubt I'll be able to contribute much,
> I would like to look in on IRC
> and see whats being said and just say Hello really.
That is one of the main reasons, we can become
more familiar with each other.
> I am in Australia, I can be on from 7PM my time which is 12P
Ross Gardler wrote:
> David Crossley wrote:
> >Ross Gardler wrote:
> >
> >>Is it worth us identifying when we expect to be online during the day?
> >>I'm not talking about a commitment, it's just that we may be able to
> >>maximise benefit by trying to get online in groups.
> >
> >I for one will
- Original Message -
From: "Ross Gardler" <[EMAIL PROTECTED]>
To:
Sent: Monday, August 29, 2005 9:23 PM
Subject: Re: Forrest Tuesday (Was: Bug Days (Was Re: better use of Jira for
Forrest))
| David Crossley wrote:
| > Ross Gardler wrote:
| >
| >>Is it
David Crossley wrote:
Ross Gardler wrote:
Is it worth us identifying when we expect to be online during the day?
I'm not talking about a commitment, it's just that we may be able to
maximise benefit by trying to get online in groups.
I for one will do blocks throughout the whole day.
I will
Ross Gardler wrote:
>
> Is it worth us identifying when we expect to be online during the day?
> I'm not talking about a commitment, it's just that we may be able to
> maximise benefit by trying to get online in groups.
I for one will do blocks throughout the whole day.
I will certainly be ther
Ferdinand Soethe wrote:
David Crossley wrote:
I would like to deal with "Internal structure is XHTML2"
and the associated issues.
+1
So far there has been plenty of agreement for this. Clearly (at least in
my mind) this work will be done in Forrest:views not in skins, is my
mind correct
Ferdinand Soethe wrote:
David Crossley wrote:
I would like to deal with "Internal structure is XHTML2"
and the associated issues.
+1
Though simplifying Forrest directory structure is a close second on my
list ...
That is part of the config thing, I have this in mind for the second
Ross Gardler wrote:
> The *implementation* of the move to XHTML2 would be eased considerably
> by refactoring our sitemaps to use the locationmap.
Why is that? In my limited understanding lm allows to specify the
location of a resource in more sophisticated ways, where is the
connection?
>
David Crossley wrote:
> I would like to deal with "Internal structure is XHTML2"
> and the associated issues.
+1
Though simplifying Forrest directory structure is a close second on my
list ...
--
Ferdinand Soethe
Diwaker Gupta wrote:
On Saturday 27 August 2005 10:33 pm, David Crossley wrote:
I would like to deal with "Internal structure is XHTML2"
and the associated issues.
+1
The *implementation* of the move to XHTML2 would be eased considerably
by refactoring our sitemaps to use the locationmap.
On Saturday 27 August 2005 10:33 pm, David Crossley wrote:
> I would like to deal with "Internal structure is XHTML2"
> and the associated issues.
+1
> Do others have better suggestions?
>
> Perhaps just dealing with the Jira backlog would keep
> us amused, i.e. the Issue Tracker is this month's
Diwaker Gupta wrote:
> David Crossley wrote:
> >
> > Each meeting could either just concentrate on getting Jira
> > under control or have a special topic like a group effort
> > to move the core to use xhtml2.
>
> More generally, we could identify a particular area to work on before hand.
> That
Juan Jose Pablos wrote:
> David Crossley wrote:
> >
> >The other thing that we need to do is to log the session.
> >I will do that locally this time, unless someone knows
> >how to do a logger bot. We can put the result into
> >our events SVN.
>
> I can setup a eggdrop bot to listen in whatever ir
David Crossley wrote:
The other thing that we need to do is to log the session.
I will do that locally this time, unless someone knows
how to do a logger bot. We can put the result into
our events SVN.
I can setup a eggdrop bot to listen in whatever irc channel that you want.
On Thursday 18 August 2005 7:05 am, David Crossley wrote:
> In our earlier discussions, we agreed that we don't
> want to have the channel as a permanent means of
> communication. So i looked into how to restrict it.
> Just start a new channel at the beginning of the
> day with name like for-09 and
David Crossley wrote:
Ross Gardler wrote:
Cyriaque Dupoirieux wrote:
David Crossley a ?crit :
David Crossley wrote:
We need to be continually cleaning up our Jira issue tracker.
There is a lot of clutter and it means that we cannot have a
good view of our situation.
The remainder of thi
Ross Gardler wrote:
> Cyriaque Dupoirieux wrote:
> >David Crossley a ?crit :
> >>David Crossley wrote:
> >>>We need to be continually cleaning up our Jira issue tracker.
> >>>There is a lot of clutter and it means that we cannot have a
> >>>good view of our situation.
> >>
> >>The remainder of this
Ross Gardler wrote:
> Steven Noels wrote:
> >Ross Gardler wrote:
> >
> >>We, the Forrest team, believe that we have now updated all our
> >>documentation to point at the new issues tracker at apache.org Could
> >>we ask that you place a redirect in your .htaccess to point visitors
> >>to the coc
On Sat, 2005-06-04 at 12:32 +0200, Nicola Ken Barozzi wrote:
> Ross Gardler wrote:
> ...
> > May I also take this opportunity to thank Outerthought and Cocoondev.org
> > on behalf of the Apache Forrest project for hosting our issue tracker
> > for so long.
>
> Yes, a warmhearted thanks to Steven
Ross Gardler wrote:
...
May I also take this opportunity to thank Outerthought and Cocoondev.org
on behalf of the Apache Forrest project for hosting our issue tracker
for so long.
Yes, a warmhearted thanks to Steven, Jeff, and all involved. It has
really been of help.
--
Nicola Ken Barozzi
Steven Noels wrote:
On 04 Jun 2005, at 10:11, Ross Gardler wrote:
We, the Forrest team, believe that we have now updated all our
documentation to point at the new issues tracker at apache.org Could
we ask that you place a redirect in your .htaccess to point visitors
to the cocoondev.org issue
On 04 Jun 2005, at 10:11, Ross Gardler wrote:
We, the Forrest team, believe that we have now updated all our
documentation to point at the new issues tracker at apache.org Could
we ask that you place a redirect in your .htaccess to point visitors
to the cocoondev.org issue tracker to the new a
We, the Forrest team, believe that we have now updated all our
documentation to point at the new issues tracker at apache.org Could we
ask that you place a redirect in your .htaccess to point visitors to the
cocoondev.org issue tracker to the new apache.org tracker at:
http://issues.apache.org
Cyriaque Dupoirieux wrote:
David Crossley a écrit :
David Crossley wrote:
We need to be continually cleaning up our Jira issue tracker.
There is a lot of clutter and it means that we cannot have a
good view of our situation.
The remainder of this old thread led to a bit of a cleanup.
It also
Cyriaque Dupoirieux wrote:
> David Crossley a ?crit :
> >
> >It also led to a brilliant idea about a regular bug day
> >which we should instigate soon.
>
> When will we decide the regular bug day ?
How about we decide now.
I reckon once per month. Perhaps we can do it
more often if it works.
Wh
David Crossley a écrit :
David Crossley wrote:
We need to be continually cleaning up our Jira issue tracker.
There is a lot of clutter and it means that we cannot have a
good view of our situation.
The remainder of this old thread led to a bit of a cleanup.
It also led to a brilliant idea a
David Crossley wrote:
> We need to be continually cleaning up our Jira issue tracker.
> There is a lot of clutter and it means that we cannot have a
> good view of our situation.
The remainder of this old thread led to a bit of a cleanup.
It also led to a brilliant idea about a regular bug day
wh
Dave Brondsema wrote:
> Quoting Ross Gardler <[EMAIL PROTECTED]>:
> > Dave Brondsema wrote:
> > > Quoting David Crossley <[EMAIL PROTECTED]>:
> > >
> > >
> > >>Done. That clarifies the Roadmap.
> > >>
> > >>Do any people out in the Forrest dev community
> > >>know other things that we can do
Quoting Ross Gardler <[EMAIL PROTECTED]>:
> Dave Brondsema wrote:
> > Quoting David Crossley <[EMAIL PROTECTED]>:
> >
> >
> >>Done. That clarifies the Roadmap.
> >>
> >>Do any people out in the Forrest dev community
> >>know other things that we can do to improve our use
> >>of Jira? Or po
Dave Brondsema wrote:
Quoting David Crossley <[EMAIL PROTECTED]>:
Done. That clarifies the Roadmap.
Do any people out in the Forrest dev community
know other things that we can do to improve our use
of Jira? Or point to projects that use it well.
Many projects periodically do a "bug day
Quoting David Crossley <[EMAIL PROTECTED]>:
> Done. That clarifies the Roadmap.
>
> Do any people out in the Forrest dev community
> know other things that we can do to improve our use
> of Jira? Or point to projects that use it well.
>
Many projects periodically do a "bug day" where e
Done. That clarifies the Roadmap.
Do any people out in the Forrest dev community
know other things that we can do to improve our use
of Jira? Or point to projects that use it well.
--David
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
What i am proposing now is an extra step. Remove the option
"HEAD version" entirely from Jira. I think it is superfluous.
Sorry - I'm reading too fast this morning.
If a bug is introduced into head (i.e. wasn't in the previous release)
Ross Gardler wrote:
> David Crossley wrote:
> >What i am proposing now is an extra step. Remove the option
> >"HEAD version" entirely from Jira. I think it is superfluous.
>
> Sorry - I'm reading too fast this morning.
>
> If a bug is introduced into head (i.e. wasn't in the previous release)
>
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
We need to be continually cleaning up our Jira issue tracker.
There is a lot of clutter and it means that we cannot have a
good view of our situation.
We recently defined a stack categories. That helps to provide
other ways to browse t
Ross Gardler wrote:
> David Crossley wrote:
> >We need to be continually cleaning up our Jira issue tracker.
> >There is a lot of clutter and it means that we cannot have a
> >good view of our situation.
> >
> >We recently defined a stack categories. That helps to provide
> >other ways to browse th
David Crossley wrote:
We need to be continually cleaning up our Jira issue tracker.
There is a lot of clutter and it means that we cannot have a
good view of our situation.
We recently defined a stack categories. That helps to provide
other ways to browse the outstanding issues.
Today i removed the
We need to be continually cleaning up our Jira issue tracker.
There is a lot of clutter and it means that we cannot have a
good view of our situation.
We recently defined a stack categories. That helps to provide
other ways to browse the outstanding issues.
Today i removed the 0.6.1 release versi
40 matches
Mail list logo
