FAQ
Edit report at http://pear.php.net/bugs/bug.php?id=16413&edit=1

ID: 16413
Updated by: brett.bieber@gmail.com
Reported By: daniel dot oconnor at gmail dot com
Summary: Usability: Bug reporting
Status: Open
Type: Feature/Change Request
Package: pearweb
Package Version: CVS
PHP Version: Irrelevant
Roadmap Versions:
New Comment:

please yes.


Previous Comments:
------------------------------------------------------------------------

[2009-07-07 04:48:31] doconnor

Description:
------------
Filing a bug in PEAR is painful if you don't start in the right place
(ie, package homepage).

The bugs page is painful too. Way too long.

The desire to have less bug reports of low quality can be better dealt
aside from putting people through a 7 page document.


Suggestions for a new bug report, ui:
http://www.flickr.com/photos/clockwerx/3696740984/
http://www.flickr.com/photos/clockwerx/3696740950/

Current:
http://www.flickr.com/photos/clockwerx/3696739232/

------------------------------------------------------------------------

Search Discussions

  • Brett Bieber at Jul 7, 2009 at 1:48 pm
    Edit report at http://pear.php.net/bugs/bug.php?id=16413&edit=1

    ID: 16413
    Updated by: brett.bieber@gmail.com
    Reported By: daniel dot oconnor at gmail dot com
    Summary: Usability: Bug reporting
    Status: Open
    Type: Feature/Change Request
    Package: pearweb
    Package Version: CVS
    PHP Version: Irrelevant
    Roadmap Versions:
    New Comment:

    The only thing I see missing is how to file a documentation bug or a
    website bug. Will the users know to enter 'Documentation' or pearweb for
    the package name?


    Previous Comments:
    ------------------------------------------------------------------------

    [2009-07-07 15:44:41] saltybeagle

    please yes.

    ------------------------------------------------------------------------

    [2009-07-07 04:48:31] doconnor

    Description:
    ------------
    Filing a bug in PEAR is painful if you don't start in the right place
    (ie, package homepage).

    The bugs page is painful too. Way too long.

    The desire to have less bug reports of low quality can be better dealt
    aside from putting people through a 7 page document.


    Suggestions for a new bug report, ui:
    http://www.flickr.com/photos/clockwerx/3696740984/
    http://www.flickr.com/photos/clockwerx/3696740950/

    Current:
    http://www.flickr.com/photos/clockwerx/3696739232/

    ------------------------------------------------------------------------
  • Mike at Jul 9, 2009 at 1:30 pm
    Edit report at http://pear.php.net/bugs/bug.php?id=16413&edit=1

    ID: 16413
    Updated by: mike@silverorange.com
    Reported By: daniel dot oconnor at gmail dot com
    Summary: Usability: Bug reporting
    Status: Open
    Type: Feature/Change Request
    Package: pearweb
    Package Version: CVS
    PHP Version: Irrelevant
    Roadmap Versions:
    New Comment:

    Good idea and good mockups. I think some of the content on the current
    page should stay; specifically, the bug reporting tips link, and the
    link to file web or doc bugs.

    Does PEAR have a particular blessed JS framework? I could help out with
    the auto-complete stuff in the mockup.


    Previous Comments:
    ------------------------------------------------------------------------

    [2009-07-07 15:46:20] saltybeagle

    The only thing I see missing is how to file a documentation bug or a
    website bug. Will the users know to enter 'Documentation' or pearweb for
    the package name?

    ------------------------------------------------------------------------

    [2009-07-07 15:44:41] saltybeagle

    please yes.

    ------------------------------------------------------------------------

    [2009-07-07 04:48:31] doconnor

    Description:
    ------------
    Filing a bug in PEAR is painful if you don't start in the right place
    (ie, package homepage).

    The bugs page is painful too. Way too long.

    The desire to have less bug reports of low quality can be better dealt
    aside from putting people through a 7 page document.


    Suggestions for a new bug report, ui:
    http://www.flickr.com/photos/clockwerx/3696740984/
    http://www.flickr.com/photos/clockwerx/3696740950/

    Current:
    http://www.flickr.com/photos/clockwerx/3696739232/

    ------------------------------------------------------------------------
  • Daniel Oconnor at Jul 13, 2009 at 9:25 am
    Edit report at http://pear.php.net/bugs/bug.php?id=16413&edit=1

    ID: 16413
    Updated by: daniel.oconnor@gmail.com
    Reported By: daniel dot oconnor at gmail dot com
    Summary: Usability: Bug reporting
    Status: Open
    Type: Feature/Change Request
    Package: pearweb
    Package Version: CVS
    PHP Version: Irrelevant
    Roadmap Versions:
    New Comment:

    Round 2:
    http://www.flickr.com/photos/clockwerx/3716470586/

    Retains the links / doc bug functionality (but minimizes its
    importance)


    Previous Comments:
    ------------------------------------------------------------------------

    [2009-07-09 15:28:13] gauthierm

    Good idea and good mockups. I think some of the content on the current
    page should stay; specifically, the bug reporting tips link, and the
    link to file web or doc bugs.

    Does PEAR have a particular blessed JS framework? I could help out with
    the auto-complete stuff in the mockup.

    ------------------------------------------------------------------------

    [2009-07-07 15:46:20] saltybeagle

    The only thing I see missing is how to file a documentation bug or a
    website bug. Will the users know to enter 'Documentation' or pearweb for
    the package name?

    ------------------------------------------------------------------------

    [2009-07-07 15:44:41] saltybeagle

    please yes.

    ------------------------------------------------------------------------

    [2009-07-07 04:48:31] doconnor

    Description:
    ------------
    Filing a bug in PEAR is painful if you don't start in the right place
    (ie, package homepage).

    The bugs page is painful too. Way too long.

    The desire to have less bug reports of low quality can be better dealt
    aside from putting people through a 7 page document.


    Suggestions for a new bug report, ui:
    http://www.flickr.com/photos/clockwerx/3696740984/
    http://www.flickr.com/photos/clockwerx/3696740950/

    Current:
    http://www.flickr.com/photos/clockwerx/3696739232/

    ------------------------------------------------------------------------
  • Daniel Oconnor at Jul 14, 2009 at 1:57 am
    Edit report at http://pear.php.net/bugs/bug.php?id=16413&edit=1

    ID: 16413
    Updated by: daniel.oconnor@gmail.com
    Reported By: daniel dot oconnor at gmail dot com
    Summary: Usability: Bug reporting
    -Status: Open
    +Status: Closed
    Type: Feature/Change Request
    Package: pearweb
    Package Version: CVS
    PHP Version: Irrelevant
    -Assigned To:
    +Assigned To: doconnor
    Roadmap Versions:
    New Comment:

    -Status: Open
    +Status: Closed
    -Assigned To:
    +Assigned To: doconnor
    This bug has been fixed in CVS.

    If this was a documentation problem, the fix will appear on
    pear.php.net by the end of next Sunday (CET).

    If this was a problem with the pear.php.net website, the change should
    be live shortly.

    Otherwise, the fix will appear in the package's next release.

    Thank you for the report and for helping us make PEAR better.

    Fixed in [284046]


    Previous Comments:
    ------------------------------------------------------------------------

    [2009-07-13 11:23:39] doconnor

    The following patch has been added/updated:

    Patch Name: bug.php
    Revision: 1247480619
    URL:
    http://pear.php.net/bugs/patch-display.php?bug=16413&patch=bug.php&revision=1247480619&display=1

    ------------------------------------------------------------------------

    [2009-07-13 11:22:52] doconnor

    Round 2:
    http://www.flickr.com/photos/clockwerx/3716470586/

    Retains the links / doc bug functionality (but minimizes its
    importance)

    ------------------------------------------------------------------------

    [2009-07-09 15:28:13] gauthierm

    Good idea and good mockups. I think some of the content on the current
    page should stay; specifically, the bug reporting tips link, and the
    link to file web or doc bugs.

    Does PEAR have a particular blessed JS framework? I could help out with
    the auto-complete stuff in the mockup.

    ------------------------------------------------------------------------

    [2009-07-07 15:46:20] saltybeagle

    The only thing I see missing is how to file a documentation bug or a
    website bug. Will the users know to enter 'Documentation' or pearweb for
    the package name?

    ------------------------------------------------------------------------

    [2009-07-07 15:44:41] saltybeagle

    please yes.

    ------------------------------------------------------------------------

    The remainder of the comments for this report are too long. To view
    the rest of the comments, please view the bug report online at
    http://pear.php.net/bugs/bug.php?id=16413

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppear-bugs @
categoriesphp
postedJul 7, '09 at 1:47p
activeJul 14, '09 at 1:57a
posts5
users3
websitepear.php.net

People

Translate

site design / logo © 2022 Grokbase