I understand you concerns. I have them too. Things do not look good
now. The brand has been damaged. And things will probably get worse
before they get better. How optimistic am I in that? Not very. But
there are some very talented people who volunteered to work on this
project and I hope they/we can all learn to work together better.
If not, NuttX will enter into its dark ages, lose its following, and
become irrelevant like so many RTOSs before it.
We can only wait and see. Buy some popcorn and try to get a seat in the
front row. It will be interesting.
Greg
On 12/21/2019 8:14 PM, Disruptive Solutions wrote:
Thats what I stated from day 1. Maybe its an idea to come up with a plan /
roadmap so people can see whats going on and what has to be done and which
issues are there... lead people ..... now its grey and shady over A) expertise
B) progress.... their in the dark now? These mails are giving back uncertainty?
I thought Apache would bring in their workflow and automated tooling and
experience with these projects? But now it seems that the Nuttx/Bitbucket
workflow was not that bad..... it worked from 2007... so how bad was it really?
Oké only Greg as master committer was a SPOF... but could be fixed also right?
Maybe Apache can chip in to come with suggestions?
I personally think that there are people who still believe in the greatness of
Nuttx but are waiting for a good progress and more solid and stable choices?
And maybe people want to help out but are not in a position to do so? And the
license switch could bring uncertainty also for some?
I can only say that change is always good, but it gives insight and insight
gives change!! So I hope you all find a solution to maybe a minor problem....
Nuttx was already a succes, just needs some automation and it has the same
problems in CI/CD like every large project in C in teams at other big firms..??
Thats where Apache could cone to the rescue? As a big software deployer?
Maybe this articles gives one some ideas:
https://proandroiddev.com/how-to-set-up-an-efficient-development-workflow-with-git-and-ci-cd-5e8916f6bece
Heads up and keep believing!
Maybe I should not share my thought, but like most of us I do not care what
other people think :-) I am just concerned..
A spectator....
Ben
Verstuurd vanaf mijn iPhone
Op 22 dec. 2019 om 02:34 heeft Gregory Nutt <spudan...@gmail.com> het volgende
geschreven:
Can we do that for the PR that David created? (I mean applying it on
bitbucket and I bring it to github)
It would takes some agreement to do that. But I don't want to do that either
anymore. The more I think about not having to apply patches everyday, the
better I feel about it. I feel liberated. So I don't really want to do that at
all anymore. It is the PPMC's responsibility to manage the workflow, not mine.
It is better that way.
Related thoughts:
I did tell the IPMC before the project was voted in there would be a knife-edge
transition: The day that the Apache repositories are created would be the day
that I stop updating Bitbucket and turn over full responsibility of the changes
to the PPMC.
Despite some confusion, I have met that commitment. There have been no
further changes to Bitbucket and the PPMC now has full responsibility for the
disposition of changes.
There is essential no change activity in the project. Normally there are might
be 50 changes per week, but I think that there were only 6 last week. That is
good and bad. It is good because I don't see any reason for the PPMC to fear
it is going to overwhelmed by changes in the near future.
It is bad because I interpret this to mean that people have lost confidence in
the project and are just no longer submitting changes. There could be other
reasons, but if it is due to lack of confidence that would be an indication
that the project is being damaged by the lack of coordination.
