Re: [PROPOSAL] Zeta Components (issue tracker)

2010-04-21 Thread Daniel Kulp
On Wednesday 21 April 2010 6:38:09 am Tobias Schlitt wrote > I read on the infra pages, that our website is required to be generated > static HTML content. This is fine for us, since the desired systems does > basically do this. But I wounder how really dynamic stuff is handeled > here? E.g. having

Re: [PROPOSAL] Zeta Components (issue tracker)

2010-04-21 Thread Christian Grobmeier
> we talked a bit about the issue tracker stuff and came to the conclusion > that we'd go with Jira. The point of having issues central in ASF infra > is quite striking and we agree here, that we don't want issues to be > tracked on an external server. Thats good, b/c infra responded and they are

Re: [PROPOSAL] Zeta Components (issue tracker)

2010-04-21 Thread Tobias Schlitt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On 04/21/2010 12:43 PM, Daniel S. Haischt wrote: > actually blogs are done using apache roller as you may figure from the > below URL. > On Wed, Apr 21, 2010 at 12:40 PM, Bertrand Delacretaz > wrote: >> On Wed, Apr 21, 2010 at 12:38 PM, Tobias

Re: [PROPOSAL] Zeta Components (issue tracker)

2010-04-21 Thread Daniel S. Haischt
actually blogs are done using apache roller as you may figure from the below URL. On Wed, Apr 21, 2010 at 12:40 PM, Bertrand Delacretaz wrote: > On Wed, Apr 21, 2010 at 12:38 PM, Tobias Schlitt wrote: >> ...I read on the infra pages, that our website is required to be generated >> static HTML co

Re: [PROPOSAL] Zeta Components (issue tracker)

2010-04-21 Thread Bertrand Delacretaz
On Wed, Apr 21, 2010 at 12:38 PM, Tobias Schlitt wrote: > ...I read on the infra pages, that our website is required to be generated > static HTML content. This is fine for us, since the desired systems does > basically do this. But I wounder how really dynamic stuff is handeled > here? E.g. havin

Re: [PROPOSAL] Zeta Components (issue tracker)

2010-04-21 Thread Tobias Schlitt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, we talked a bit about the issue tracker stuff and came to the conclusion that we'd go with Jira. The point of having issues central in ASF infra is quite striking and we agree here, that we don't want issues to be tracked on an external server