I now have a public link where what I have achieved to date can be viewed
This is far from complete and there is still loads to do. If you fancy
helping out then drop me a line.
It would be nice to get a decent PHP based Tracker and Wiki solution.
I have the Wiki working with Textile markup and a simple macro engine for
the Wiki. At the moment there is one for fetching tickets e.g.
{macro:bug}4{macro}
And one for formatting/displaying PHP code e.g.
{macro:php}
<?php
myFunction()
{
$a = $b
}
?>
{macro}
You can add/view tickets at the moment but that is it.
Everything else is under development :-)
http://rcastley.plus.com/ <http://rcastley.plus.com/>
- Robert
_____
From: Robert Castley
Sent: 21 January 2009 17:33
To: Karol Grecki; fw-general@lists.zend.com
Subject: RE: [fw-general] What do you use to manage your ZF projects?
Well ...
Depending on which way you look at it, I have stupidly decided to have a
stab at developing my own PHP based solution.
Using ZF ... of course!
My starting point is a direct copy of the sqlite database from trac, this
has already been modified to support projects :-)
I have the Wiki side of things all working thanks to my other attempt at a
project called ZFWiki.
I will report back when I have more information :-)
I have some screenshots at http://gallery.me.com/robert.castley#100086
<http://gallery.me.com/robert.castley#100086>
- Robert
-----Original Message-----
From: Karol Grecki [mailto:kgre...@gmail.com <mailto:kgre...@gmail.com> ]
Sent: 21 December 2008 22:42
To: fw-general@lists.zend.com
Subject: RE: [fw-general] What do you use to manage your ZF projects?
Everything is raised as tickets, there are different types like bug, task,
proposal etc.
You can organise them using milestones, components and versions.
I used milestones for projects because they have special meaning in Roadmap
view, but you can chose any of them and create appropriate reports using sql
syntax.
Anyway I feel your pain, I couldn't find anything meeting my requirements
either.
I even considered building it myself, using ZF of course :)
Karol
rcastley wrote:
>
> Hi Karol,
>
> How do you handle issue/bug tracking?
>
> In Bugzilla I can choose the Product and then the component etc.
>
> More research tonight has unveiled the following projects:
>
> 1) Redmine (seems to be like Trac but written in Ruby). Not used Ruby
> or Rails so not comfortable with this from a systems managament POV.
> See Item 3!
> 2) I used Gforge on the Mambo project, they now over an Advanced Version:
> http://gforgegroup.com/es/download.php
<http://gforgegroup.com/es/download.php>
> 3) Retrospectiva - but look at the 'Quick'???? Install guide:
> http://retrospectiva.org/wiki/Quick%20install
<http://retrospectiva.org/wiki/Quick%20install> . Now I know why I love
> PHP
> ;-)
>
> I think I am now getting myself down to Gforge AS or Trac.
>
> Why is nothing ever easy, eh?
>
> - Robert
>
> -----Original Message-----
> From: Karol Grecki [mailto:kgre...@gmail.com <mailto:kgre...@gmail.com> ]
> Sent: 21 December 2008 21:46
> To: fw-general@lists.zend.com
> Subject: Re: [fw-general] What do you use to manage your ZF projects?
>
>
> Robert
>
> I had the same problem over a year ago and settled for Trac. It
> doesn't support multiple projects but we use milestones for it e.g.
> "project A sprint 1".... It integrates really well with Subversion and
> there's a lot of plugins extending its functionality. It may still be
> your best bet if you don't find anything matching all your
> requirements.
>
> Karol
>
>
> rcastley wrote:
>>
>> Hi,
>>
>> Just curious here. I/we currently use Bugzilla & CVS, no formal
>> wiki but I do have a MediaWiki used for somethings.
>>
>> I am looking for a solution that fits all, so the obvious choices are
>> 'Trac'
>> like.
>>
>> My problem is that I need a solution that will support multiple projects.
>> (Trac doesn't score well in this area.)
>>
>> Bugzilla is used by multiple PHP, Java & C/C++ products. CVS is used
>> only by PHP developers the 'others' use VSS.
>> MediaWiki is used for 'sparse' documentation.
>>
>>
>> My gripes with the current setup:
>>
>> Bugzilla - v. slow and ugly but it fitted the bill at the time.
>> CVS - I like, no love, CVS but I know that there are better solutions
>> out there but am concerned about migration etc.
>> MediaWiki - Probably too much of an overkill for what we need and it
>> is not that easy to configured, extend etc.
>>
>> I now that the ZF team uses JIRA, Confluence etc but I have a budget
>> of £0/$0 :-) and don't qualify for the OS licenses.
>>
>> So ... I would be interested on the views of others of a 'one hat
>> fits all'
>> solution that can handle multiple projects.
>> The solution needs to offer Issues/Bug tracking and Wiki at a minimum.
>> Integration with SCM not important but if it does it great.
>>
>> I would prefer a PHP based solution but happy to consider others i.e.
>> Ruby,
>> Perl, Java etc.
>>
>> - Robert
>>
>
>
--
View this message in context:
http://www.nabble.com/What-do-you-use-to-manage-your-ZF-projects--tp21118310
p21120113.html
<http://www.nabble.com/What-do-you-use-to-manage-your-ZF-projects--tp2111831
0p21120113.html>
Sent from the Zend Framework mailing list archive at Nabble.com.
________________________________________________________________________
This email has been scanned for all known viruses by the MessageLabs Email
Security Service and the Macro 4 plc internal virus protection system.
________________________________________________________________________
________________________________________________________________________
This email has been scanned for all known viruses by the MessageLabs Email
Security Service and the Macro 4 plc internal virus protection system.
________________________________________________________________________
________________________________________________________________________
This email has been scanned for all known viruses by the MessageLabs Email
Security Service and the Macro 4 plc internal virus protection system.
________________________________________________________________________
________________________________________________________________________
This email has been scanned for all known viruses by the MessageLabs Email
Security Service and the Macro 4 plc internal virus protection system.
________________________________________________________________________
