On Sun, Apr 30, 2017 at 3:03 PM, Joseph Heller
<
joseph.h...@gmail.com> wrote:
> I just stumbled upon an issue I had encountered a year ago as well, and
> would like to share some thoughts on this here. All help appreciated, don't
> get me wrong, and I'm sure it will be resolved but I recalled some things
> missing the first time when I had the issue, which still seem to be missing
> now. It is things missing like: are there release notes,
> is there a bug
> tracker,
github:
https://github.com/beagleboard/
>differentiation between stable and unstable releases,
no diff, it's a rolling model..
> a wiki that's
> kept up-to-date,
it is, the issue is "3rd party" wiki's..
> and what happens if someone crucial is leaving the team?
He did. that's why we don't ship Angstrom by default..
Just to scare you more, i drive an hour every morning and night thru
dark country roads in north minnesota with lots of deer running around
to get to my Day Job.
Everything i use to build the debian image is on my github account. So
when i smack a 30 point buck or a moose, it should be easy for someone
else to pick up.
> Now that got me thinking: could it be that this is the underlying reason for
> issues like these in general? The reason for me to bring it up is that I'm
> actually wondering if spending my time and effort on the Beaglebone is the
> best investment, or that there's alternative solutions. The Beaglebone is
> known to be an SBC with a steep learning curve, but I did not expect to be
> spending time on the issues just mentioned. As an experiment, I have an
> outstanding order which I wonder if that suits me better in the long run if
> issues occur. So in that sense, this is feedback on something that looks to
> me as the weak spot of the Beaglebone. I truly think the board is a very
> good platform from hardware point of view, but it would be a pity if due to
> the issues mentioned it will not survive competition. My guess, and maybe
> the hard part, is that suggested improvements are not easily decided upon
> and implemented by the community - although here's my contribution by
> starting a discussion and sharing thoughts about it. It's more like defining
> a strategy and improving of the foundation by the core team, after which the
> community can benefit from it either as users or participants. Having a less
> well defined quality standpoint, is in a sense the other way round: despite
> the good intentions, have the community be confronted with issues, then try
> to solve them. Some frustration being vented here as well as you might have
> noted, but I guess that’s all in the game.
You can vent all you want, there's only one user on this forum that's
paid by Beagle Foundation/TI. The rest of use are just volunteer's
who spend our free time working on it, i usually just ignore venter's
unless they have a patch..
Ps, now go test, your bug is fixed:
https://rcn-ee.net/rootfs/bb.org/testing/2017-04-30/
Release notes will show up tomorrow on my lunch break .. ;)
Busy now, as I've got burgers to grill. ;)
Regards,
--
Robert Nelson
https://rcn-ee.com/