Hi Mauro have you asked on the irc channel or pleas send a mail to the
list and explain what is not going write for you and some body will try
and help. One thing to remember is that the devs are fue and don't have
much time. Sorry you are getting frustrated.
Hi Carlos you make some good points.
>>Thanks for your input. It's good to let new people to embedded
devices know just how people got started and how you conquered the
learning curve.
On 03/03/2017 18:36, Carlos Ferreira wrote:
Embedded development requires patience and strong will. Yes it is a
frustrating process and although that scares a lot of new junior
developers, it is not the only reason.
Software development for embedded devices is a very different niche
when compared to android/ios development or what is currently called
"cloud development". I have seen CS students running away from a
simple application development, when discovering that it would be
implemented in C language. There's an addiction in CS degrees for
teaching "high-level languages" like Java and so on. It is not the
same thing nor it works the same way. That is also why there are
specific degrees for this, which usually mix Electronics and System
Development.
Although an expert buddy is an interesting idea, it requires time and
dedication from the experts. Most of the time, such is not possible
without personal sacrifice and most of the experts are already
sacrificing much of their personal time. MS has something that
LEDE/OpenWRT do not have. Money, lots of it.
I myself, have learned a lot by example. By following the work of
others and a good amount of dedication in reading the literature. By
reading theory books, blogs and mailing lists. It's a continuous
process. Not everyone is capable of accepting this. That is why there
are so few embedded devs when compared to web development.
--
Carlos Ferreira
On 3 March 2017 at 16:55, Mauro Mozzarelli <ma...@ezplanet.org> wrote:
I have been trying to make a very simple contribution to LEDE, but it has
been a frustrating process because my contribution got stuck due to form
rather than substance.
Unfortunately this might turn away contributors who do not have the patience
to persevere.
I would like to suggest, that when a new potential contributor is putting
forward his proposed change, an expert buddy is assigned to guide the new
contributor through to getting his changes reviewed and pushed into the
mainstream code. A successful contribution would mean a lot and inspire more
work.
Mauro
On 01/03/17 19:42, tapper wrote:
Hi Is LEDE ready to try and get more people from the wider community
involved?
A thought I had is to do a code optimization week.
I know that LEDE is optimized to fit on small flash chips, but It mite be
a good way of getting other coders to look in the code to see if they can
save a bite here and there, or try and make something run a little faster.
Or if that is know good what about a bug bash week? MS has bug bashes and
they seem to get a lot of people talking about windows 10. I am not a coder
and don't understand all the ins and outs of what I am talking about, but I
like LEDE. If just one new dev or doc righter was to be added to the team it
is a net win for all.
If something like this was to be tryed you could post about it on the
forLinux forums and on Slashdot, Hacker News and /r/linux r/openwrt.
_______________________________________________
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
_______________________________________________
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
_______________________________________________
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
_______________________________________________
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
