element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
    About the element14 Community
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      •  Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Raspberry Pi
  • Products
  • More
Raspberry Pi
Raspberry Pi Forum troubleshooting topics zooms past 1000 (now 6000)
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Raspberry Pi to participate - click to join for free!
Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 35 replies
  • Subscribers 708 subscribers
  • Views 4668 views
  • Users 0 members are here
Related

troubleshooting topics zooms past 1000 (now 6000)

e14 Contributor
e14 Contributor over 14 years ago

http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=10869

 

In my experience, when you have around 10 known issues, you can

discuss the status of each of them in a 1 hour weekly meeting.  You can

easily notice when two are duplicates of each other, and combine them.

You can keep track of which ones have been reproduced, and which

need further information in order to reproduce.  You can keep track of

who is assigned to work each issue, and in what order they should work

them.  You can remember from week to week what the issues are about,

without having to spend all your time coming up to speed again on each

issue.  You can ask whether each issue presents an opportunity to

improve the documentation, or to improve the QA process.  You can

ask to review in detail the proposed fix for each problem, until you are

satisfied that the fix actually solves the problem without creating other problems.

You can ask whether each problem was caused by a fault in the tools used,

or the process used, and if so, whether to make improvements in those.

You can notice when multiple problems relate to the same component,

and perhaps decide to redesign that component rather than continually

patch it.  You can thoughtfully decide whether to deliver a fix as an urgent

update, or wait to deliver it in the next general release.  You can develop

regression tests to prevent the same or similar problems from ever being

shipped again.  And when a problem is fixed and the fix delivered, you

can move it off your agenda.

 

When you have about 100 known issues, it becomes much more

difficult to do the same tasks.  You can try to prioritize and focus on

just the top 10, but then the others suffer.  When you have about 1000

known issues, it becomes impossible to manage, and you will completely

lose track of which issues are duplicates of others, which are fixed, and

which are urgent.  If you release a product update, you will have no idea

what to say in the release notes.

  • Sign in to reply
  • Cancel
Parents
  • e14 Contributor
    e14 Contributor over 14 years ago

    Hindsight is a wonderful thing. You have to wonder how many of those issues are caused by two or three design decisions that, in hindsight, were very poor.

    It's easy for us to criticise now, but I wonder if I'd have made similar choices to hit the $25 mark.

     

    All said though, it's the response to any issues that paints a much clearer picture of any organisation - and that applies to everyone, not just the RPF.  There are some UK xDSL providers that make the RPF look positively wonderful image

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • jamodio
    jamodio over 14 years ago in reply to e14 Contributor

    I don't think that we are trying to criticise, we are just reviewing, testing, analyzing, reporting and trying to have an open discussios on issues that could be fixed or improved to make the R-pi and its users experience much better.

     

    Based on the volumes we are talking, even before they realized that demand was much much higher than anticipated, the $25 target, and the credit card size, are just BS. What's the difference between a $25 product that has design and reliability issues to a $28 that works properly ?

     

    As far as I remember, the community was not invited or welcomed during the hardware design process, not even preliminary schematics were available, errors like the one I found wrongly connecting the VDDCORE pin of the LAN9512 to the 1V8 line could have been corrected before mass production, after going through alpha and beta boards, distributing boards among people I find surprising that there are so many issues being reported, some of which could be hazardous to kids.

     

    The $25/$35 is really a joke, when you factor in that you need to buy a keyboard, a mouse if you want to work in graphics mode, a power supply or several of them you need to try to make sure they work and don't blow up your TV, a collection of SD cards to figure which one works with your Pi, a powered USB hub (of which some were reported not to work properly) if you want to have some extra stuff or even power hungry USB devices connected to the Pi, the HDMI cable, and if you don't have one, a monitor. Plus if you want to provide some protection to the board, a case.

     

    What one really can criticise now, is that it does seem that there is no intention to listen, acknowledge and correct the problems.

     

    -J

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • morgaine
    morgaine over 14 years ago in reply to jamodio

    Indeed.  And since the engineering process starts with identifying problems, that process is effectively dead for the community as far as the hardware is concerned.  It's interesting that the software guys at RPF don't have that mental block.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • e14 Contributor
    e14 Contributor over 14 years ago in reply to jamodio

    criticise was maybe the wrong word... What we're doing though is analysing their decisions in hindsight and thinking we'd have done something better/differently. Morgaine got it right on the CSI/DSI connectors - we really don't know what the design criteria were and they're not about to tell us. 

    You're absolutely correct that $28 for something that works perfectly is better. But is it better if it fails the unknown (to us) design criteria ?

     

    What one really can criticise now, is that it does seem that there is no intention to listen, acknowledge and correct the problems.

    Which is exactly what I was getting at, their reaction to the problems is terrible.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • e14 Contributor
    e14 Contributor over 14 years ago in reply to morgaine

      It's interesting that the software guys at RPF don't have that mental block.

    It's much harder for the software guys to have that block. Especially when someone posts a patch to fix it image

    I do find it interesting that a number of significant software improvements have come from outside the RPF, and that it is encouraging to see them incorporated into the 'official' releases.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • e14 Contributor
    e14 Contributor over 14 years ago in reply to morgaine

      It's interesting that the software guys at RPF don't have that mental block.

    It's much harder for the software guys to have that block. Especially when someone posts a patch to fix it image

    I do find it interesting that a number of significant software improvements have come from outside the RPF, and that it is encouraging to see them incorporated into the 'official' releases.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
  • jamodio
    jamodio over 14 years ago in reply to e14 Contributor

    Well, that's exactly how the GNU community is supposed to work, and there is no need to debate if it is effective or not, just look at how Linux evolved since its early inception.

     

    -J

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube