Re: [PROPOSAL] Zeta Components (issue tracker)
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 a blog is possible with static HTML, but what about > comment functionality? A lot of projects use confluence to generate their static sites. Some examples: http://cxf.apache.org/ http://camel.apache.org/ http://directory.apache.org etc... Confluence does allow comments, but your export template would need to be setup to add a "comment" link that maps onto the confluence comment features. In anycase, I did want to through that option out there. -- Daniel Kulp dk...@apache.org http://dankulp.com/blog - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Zeta Components (issue tracker)
> 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 not so happy with another tool > For the CI we will mostly likely want to setup Hudson inside ASF and > will most probably setup Arbit for it on an external server. More CI > cannot hurt, can it? ;) I think so :--) > 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 a blog is possible with static HTML, but what about > comment functionality? The mentioned blog url does support comments Christian > > Regards, > Toby > - -- > Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 > a passion for php http://schlitt.info/opensource > Member of the eZ Components project http://components.ez.no > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAkvO1ZEACgkQ5bO3TcRivBThIQCgrdkAjAbxxsYS3vEKCrSHcnO1 > sBcAn3G26zmBZw9HhJodn6c3k5R2klJO > =fPJv > -END PGP SIGNATURE- > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Zeta Components (issue tracker)
-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 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 a blog is possible with static HTML, but what about >>> comment functionality?... >> Projects can have blogs with comments under http://blogs.apache.org/ >> >> For other dynamic stuff, projects can use zones: >> http://www.apache.org/dev/solaris-zones.html ok, then we need to deal with this in some way. Details can be figured out later, I guess. ;) Regards, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource Member of the eZ Components project http://components.ez.no -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvO1ycACgkQ5bO3TcRivBRCdgCfVxE4i84ROhYp7Mirk3K0C+nS n0AAoLGQOsWB40NHNkvGpjEV65kJXC2b =blV+ -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Zeta Components (issue tracker)
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 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 a blog is possible with static HTML, but what about >> comment functionality?... > > Projects can have blogs with comments under http://blogs.apache.org/ > > For other dynamic stuff, projects can use zones: > http://www.apache.org/dev/solaris-zones.html > > -Bertrand > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Zeta Components (issue tracker)
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. having a blog is possible with static HTML, but what about > comment functionality?... Projects can have blogs with comments under http://blogs.apache.org/ For other dynamic stuff, projects can use zones: http://www.apache.org/dev/solaris-zones.html -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Zeta Components (issue tracker)
-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. For the CI we will mostly likely want to setup Hudson inside ASF and will most probably setup Arbit for it on an external server. More CI cannot hurt, can it? ;) I updated our proposal in the wiki accordingly: http://wiki.apache.org/incubator/ZetaComponentsProposal 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 a blog is possible with static HTML, but what about comment functionality? Regards, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource Member of the eZ Components project http://components.ez.no -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvO1ZEACgkQ5bO3TcRivBThIQCgrdkAjAbxxsYS3vEKCrSHcnO1 sBcAn3G26zmBZw9HhJodn6c3k5R2klJO =fPJv -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
