Re: [fedora-arm] ARM summit at Plumbers 2011

2011-08-24 Thread Bill Gatliff
Luke:


Step back from the keyboard just a bit.  :)

It's true that the glass isn't completely full--- but it's pretty
darned full!  And we wouldn't be discussing the various GPL and other
violations that you cite were it not for the overwhelming successes of
Free Software, ARM, Linux, and Android.

We are well past debating the merits of Free Software et. al, which
itself is a huge milestone that we need to recognize.  Now it's time
to let the lawyers do their jobs.  And they will, because there are
tremendous sums of money at play.  Money that wouldn't be there if it
weren't for us developers.  But we need to stay out of their way,
while at the same time taking care to continue producing tangible
things that are worth fighting over.

As developers, we've won.  Deal with it.  Revel in it.  And then get over it.

I have observed all the hand-wringing regarding the state of ARM
Linux, and it's obvious to everyone that there is still work to be
done.  ARM isn't like PCs, and that's obviously inconvenient for Linus
but it's an essential part of ARM's success.  Russell King has been
overworked for a decade or more, attempting through sheer force of
human/developer will to keep ARM Linux from running off the rails.

As far as ARM Linux is concerned, I think we're dangerously close to
being smothered by our own success.   We have to learn to work
smarter, because we can't work any harder.  And I applaud Linaro and
the countless others for recognizing this problem and looking for ways
to resolve it.

I for one would love to participate in the ARM Summit, but I'm a sole
proprietor without an expense account to charge the travel costs to
and they are too large for me to carry personally.  I suspect I'm not
the only one in that situation.

The fact that there has been little response to the ARM Summit doesn't
mean that nobody cares or that the problems seem to large to solve.
It just means that we're going to have to find a different way to get
this work done.


b.g.
-- 
Bill Gatliff
b...@billgatliff.com


Re: Wrong link?

2006-05-24 Thread Bill Gatliff

Dave:



  Gerald, you've jumped to a false conclusion there; "was hijacked" should
read "has bitrotted".

  "Hijacked" is a pejorative term, and also historically and factually
inaccurate.  Objsw.com maintained the FAQ initially, but some time ago (around
2001 off the top of my head) it became clear that it had fallen into
disrepair, and Bill Gatliff, who was then and is now an active and valuable
contributing member of the crossgcc community, volunteered to take it over.
He then actively maintained it for several years and it was only when his
website got hacked and wiped out sometime last year that the link became out
of date.  He has been slow in getting his website rebuilt and hasn't put the
FAQ back up yet; which is why I've Cc'd him in on this thread.
  


Indeed, "bitrotted" is in fact a better description of what is happening.


  Bill, you need to make your intentions clear as to whether you are able and
willing to resume your maintainance duties.  Are you going to get the crossgcc
FAQ back up there?  If not, probably the best thing to do would be to replace
the paragraph with a reference to the mailing list ([EMAIL PROTECTED]) and
to Dan Kegel's crosstool and the related website.
  


Thanks for the kind words, Dave.  I am still quite committed to the 
crossgcc community, but I'm doing a lot of work behind the scenes as of 
late.


It's ironic that the security breach came through the Wiki software I 
had set up as a supplement to the FAQ.  A wiki that _nobody_ seemed to 
pay any attention to.  Ever.  Even when it was clear that many of the 
information needs of the crossgcc community were not being well met by a 
FAQ-type document.  Even when I had posted tutorials and detailed build 
procedures in the Wiki, which were really too detailed for a FAQ.


I don't think that a blanket link to crosstool is what is needed, 
because there is a lot of information that crossgcc'ers need that 
crosstool doesn't address, for example how to integrate newlib into an 
embedded system.  Crosstool doesn't even do newlib, in fact.


I'm happy to resume hosting the crossgcc document, but I don't have the 
time at the moment to give it a major overhaul--- which is what it 
needs.  And I hesitate to restore a document that is out of date.  And I 
still think a Wiki is the way to go, and I'm willing to donate a 
dedicated machine and a more secure Wiki installation towards that 
goal.  But since nobody contributed before, I don't have any reason to 
believe anyone will contribute now.  Which makes me wonder if anyone is 
using it, and I don't have the time to maintain a document that nobody 
reads.  We couldn't even get anyone to change the URL in the mailing 
list to point to the right place.


To summarize, I'm happy to re-post the FAQ but it is out of date and has 
been for some time.  It needs someone with the interest and time to 
update it.  Furthermore, I'm willing to donate resources to provide a 
Wiki, which I think is a better way to provide the information that 
people might be looking for.  But in both cases only if someone will 
actually use it.   Suggestions welcome.


At any rate, I would prefer the term "hijacked" not be used, since it is 
historically and factually inaccurate.




b.g.

--
Bill Gatliff
[EMAIL PROTECTED]



Re: Wrong link?

2006-05-24 Thread Bill Gatliff

Joe et al:



But the GCC project already has a Wiki, at

http://gcc.gnu.org/wiki

which is actively maintained by the developers.  I think it would be 
best to use that wiki, we'd have better odds that active developers

would keep it current if it were in the wiki they use.

  


I completely agree.

I recommend that we dispense with the FAQ altogether and put what we 
know into the gcc wiki.  The closer we work with the gcc team, the more 
likely it is that they will continue to support us.



b.g.

--
Bill Gatliff
[EMAIL PROTECTED]



Re: Wrong link?

2006-06-22 Thread Bill Gatliff

Gerald:

Gerald Pfeifer wrote:

On Wed, 24 May 2006, Bill Gatliff wrote:
  

Indeed, "bitrotted" is in fact a better description of what is happening.



I have tweaked the ChangeLog entry to say "gone", which is even more
neutral, and will do the same on the 4.1 branch shortly.

Gerald

  


Thanks!


b.g.

--
Bill Gatliff
[EMAIL PROTECTED]