Re: [campsite-dev] Switching from Mantis to Trac
  • It's all a bit fragmented though, isn't it. Three different places to
    look for information: doxygen/phpdoc + docmint + trac.
    Couldn't we consolidate those somehow? Maybe put the dev docs into
    docmint, for example?

    JP

    Paul Baranowski wrote:

    >John Pye wrote:
    >
    >
    >>>We're going to be using it for developer documentation. User
    >>>documentation is covered by DocMint.
    >>>
    >>>
    >>What about Doxygen and PHP Documentor?
    >>
    >>
    >
    >This is for API documentation only - there is more to developer
    >documentation than just API though. How to get started developing,
    >architecture documents, best practices, coding style, etc.
    >
    >Paul
    >
    >
    >
    >

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • 3 Comments sorted by
  • At 14:32 10.08.2005, you wrote:
    >Maybe put the dev docs into
    >docmint, for example?

    no. don't even start this discussion.

    Micz Flor - micz@mi.cz

    content and media development http://mi.cz
    ------------------------------------------------------------------
    http://www.campware.org -- http://www.redall.de -- http://suemi.de
    ------------------------------------------------------------------

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • This is a multipart message in MIME format.
    --=_alternative 0057C8D385257059_=
    Content-Type: text/plain; charset="us-ascii"

    John,

    I'm happy with us growing together with Trac. We'll help them make it
    better. The Timeline and Roadmap features make it worth our while already.
    We will think of nifty ways of showcasing that better on the Campware.org
    site. The rest of the features will catch up. Just get out of those John
    Howard set ways of yours Smile) (sorry, apologees, that was low)

    And regarding remembering your preferences, try playing with settings.
    There it can remember your session ID, so you may be able to dig up
    something useful.

    Best,

    Sava




    Paul Baranowski
    10/08/2005 11:15 AM
    Please respond to campsite-dev


    To: campsite-dev@campware.org
    cc:
    Subject: Re: [campsite-dev] Switching from Mantis to Trac


    This from someone who wanted ViewCVS + Wiki + Mantis, instead of Trac.

    Smile Just giving you a hard time.

    In the year 2013, we could make a plugin for docmint that records
    changes into the trac timeline.

    As for PHPdoc, we only need a link from the wiki.

    - Paul


    John Pye wrote:
    > It's all a bit fragmented though, isn't it. Three different places to
    > look for information: doxygen/phpdoc + docmint + trac.
    > Couldn't we consolidate those somehow? Maybe put the dev docs into
    > docmint, for example?
    >
    > JP
    >



    --=_alternative 0057C8D385257059_=
    Content-Type: text/html; charset="us-ascii"



    John,



    I'm happy with us growing together with Trac. We'll help them make it better. The Timeline and Roadmap features make it worth our while already. We will think of nifty ways of showcasing that better on the Campware.org site. The rest of the features will catch up. Just get out of those John Howard set ways of yours Smile) (sorry, apologees, that was low)



    And regarding remembering your preferences, try playing with settings. There it can remember your session ID, so you may be able to dig up something useful.



    Best,



    Sava









    Paul Baranowski <paul@paulbaranowski.org>

    10/08/2005 11:15 AM

    Please respond to campsite-dev


           

            To:        campsite-dev@campware.org

            cc:        

            Subject:        Re: [campsite-dev] Switching from Mantis to Trac






    This from someone who wanted ViewCVS + Wiki + Mantis, instead of Trac.



    Smile  Just giving you a hard time.



    In the year 2013, we could make a plugin for docmint that records

    changes into the trac timeline.



    As for PHPdoc, we only need a link from the wiki.



    - Paul





    John Pye wrote:

    > It's all a bit fragmented though, isn't it. Three different places to

    > look for information: doxygen/phpdoc + docmint + trac.

    > Couldn't we consolidate those somehow? Maybe put the dev docs into

    > docmint, for example?

    >

    > JP

    >






    --=_alternative 0057C8D385257059_=--

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • Hi All,

    To be honest, I'm for switching to the Sourceforge tools. I always considered
    this kind of tools as something what should keep me away from the boring
    development things and keep my time and concentration on the software
    development. When I see all that time spent on the tools analysis,
    installation, hosting and maintenance (not to mention time needed to learn
    how to use it), I would prefer the Sourceforge tools. In six months, you'd
    find some SuperTrac or some SuperSubVersion and It'd be never ending story.
    In case of the Sourceforge tools, the only time I would need to spend is to
    learn (incrementally) new features once a while.

    Let's leave mailing lists on our server and put all other things on the
    Sourceforge. There is no poet/writer on the world who cares about his pencil
    like you do about your tools.

    Let's concentrate on the poetry... Smile

    Nenad


    On Wednesday 10 August 2005 14:32, John Pye wrote:
    > It's all a bit fragmented though, isn't it. Three different places to
    > look for information: doxygen/phpdoc + docmint + trac.
    > Couldn't we consolidate those somehow? Maybe put the dev docs into
    > docmint, for example?
    >
    > JP
    >
    > Paul Baranowski wrote:
    > >John Pye wrote:
    > >>>We're going to be using it for developer documentation. User
    > >>>documentation is covered by DocMint.
    > >>
    > >>What about Doxygen and PHP Documentor?
    > >
    > >This is for API documentation only - there is more to developer
    > >documentation than just API though. How to get started developing,
    > >architecture documents, best practices, coding style, etc.
    > >
    > >Paul

    ------------------------------------------
    Posted to Phorum via PhorumMail