Hi Lwazi,
Thank you very much taking time to test it and confirming that it is
not working.
BTW, by working I mean "ble scanning" was working. I think we need
some better application example on NuttX to test BLE. AFAIK our stack
is too limited currently.
BR,
Alan
On 3/10/23, Lwazi Dube wrote:
Hi Alan,
If it is working on other platforms, no problem, I will fix my devices
later if I get a chance. I will put some details here in case someone
with my setup runs into the same issue.
After posting my message I downloaded 9.0.0 and 10.0.0 and tested the
releases (9 works and 10 is broken). He
Hi Lwazi,
I don't know about CC2564, but BLE Stack was working recently to
ESP32, ESP32C3, nRF52, etc
Is it related to this issue: https://github.com/apache/nuttx/issues/8767
BR,
Alan
On 3/9/23, Lwazi Dube wrote:
> On Wed, 8 Mar 2023 at 13:16, Alan C. Assis wrote:
>>
>>
>> Welcome back go Nu
On Wed, 8 Mar 2023 at 13:16, Alan C. Assis wrote:
>
>
> Welcome back go NuttX Lwazi (I'm not been sarcastic, I'm happy to hear
> from you again! You have a great knowledge of BLE can we need! I was
> expecting you to share that working example of BLE application using
> our BLE stack).
>
Thanks, I
First of all, people never respect pull request formats if this is not
enforced. So enforcement is required as well.
No member of the PMC has authority over any other. An Apache project is
ultra democratic bordering on anarchistic. Each member is basically a
"sovereign citizen."
So we c
side and they will be notified
that
someone asks them to step up
Best regards
Alin
-Original Message-
From: Xiang Xiao
Sent: den 9 mars 2023 10:12
To: dev@nuttx.apache.org
Subject: Re: DISCUSSION - Usage of mailing lists for apache projects
If some PR waits for a long time without an
side and they will be notified
that
someone asks them to step up
Best regards
Alin
-Original Message-
From: Xiang Xiao
Sent: den 9 mars 2023 10:12
To: dev@nuttx.apache.org
Subject: Re: DISCUSSION - Usage of mailing lists for apache projects
If some PR waits for a long time without an
l be notified
> that
> >> someone asks them to step up
> >>
> >> Best regards
> >> Alin
> >>
> >>
> >> -Original Message-
> >> From: Xiang Xiao
> >> Sent: den 9 mars 2023 10:12
> >> To: dev@nuttx.apa
Simply add some reviewers on the right side and they will be notified that
someone asks them to step up
Best regards
Alin
-Original Message-
From: Xiang Xiao
Sent: den 9 mars 2023 10:12
To: dev@nuttx.apache.org
Subject: Re: DISCUSSION - Usage of mailing lists for apache projects
If som
> Sent: den 9 mars 2023 10:12
> To: dev@nuttx.apache.org
> Subject: Re: DISCUSSION - Usage of mailing lists for apache projects
>
> If some PR waits for a long time without any review, how to make progress?
> For example, this PR sent two weaks ago:
> https://github.com/apache/nuttx/pull/86
es a patch submitted by another employee from
the
same company, for a board provided by the same company)
Thanks
Alin
-Original Message-
From: Alan C. Assis
Sent: den 8 mars 2023 19:15
To: dev@nuttx.apache.org
Cc: Sebastien Lorquet
Subject: Re: DISCUSSION - Usage of mailing lists for apache
a patch is merged except board changes (ex an employee
> >> from the same company merges a patch submitted by another employee from
> the
> >> same company, for a board provided by the same company)
> >>
> >> Thanks
> >> Alin
> >>
> &g
Alan C. Assis
Sent: den 8 mars 2023 19:15
To: dev@nuttx.apache.org
Cc: Sebastien Lorquet
Subject: Re: DISCUSSION - Usage of mailing lists for apache projects
Hi Lwazi,
It is not sarcarm, I'm talking about facts.
Also I didn't say Sebastien points aren't valid, but is diverting from
...@sony.com
Sent: Thursday, March 9, 2023 4:13 AM
To: dev@nuttx.apache.org
Cc: Sebastien Lorquet
Subject: RE: DISCUSSION - Usage of mailing lists for apache projects
Hi all,
I agree with David but in my opinion this information should go in the
commit message and no commit without message should be
: Sebastien Lorquet
Subject: RE: DISCUSSION - Usage of mailing lists for apache projects
Hi all,
I agree with David but in my opinion this information should go in the
commit message and no commit without message should be merged.
Not all people will check the PR message but you will always see the
Hi Xiang,
Simply add some reviewers on the right side and they will be notified that
someone asks them to step up
Best regards
Alin
-Original Message-
From: Xiang Xiao
Sent: den 9 mars 2023 10:12
To: dev@nuttx.apache.org
Subject: Re: DISCUSSION - Usage of mailing lists for apache
hat do you think ?
Thanks
Alin
-Original Message-
From: David Sidrane
Sent: den 9 mars 2023 10:00
To: dev@nuttx.apache.org
Cc: Sebastien Lorquet
Subject: RE: DISCUSSION - Usage of mailing lists for apache projects
I would add that all pull request must have a statement explaining the
ployee
> from the same company merges a patch submitted by another employee from the
> same company, for a board provided by the same company)
>
> Thanks
> Alin
>
> -Original Message-
> From: Alan C. Assis
> Sent: den 8 mars 2023 19:15
> To: dev@nuttx.apache.o
rsday, March 9, 2023 3:39 AM
To: dev@nuttx.apache.org
Cc: Sebastien Lorquet
Subject: RE: DISCUSSION - Usage of mailing lists for apache projects
Hi all,
I feel that this thread is getting too long without a real outcome
Some observations from my daily interactions with the project:
- I like doi
company merges a patch submitted by another employee from the same company, for
a board provided by the same company)
Thanks
Alin
-Original Message-
From: Alan C. Assis
Sent: den 8 mars 2023 19:15
To: dev@nuttx.apache.org
Cc: Sebastien Lorquet
Subject: Re: DISCUSSION - Usage of mailing
by another employee from the same company, for
a board provided by the same company)
Thanks
Alin
-Original Message-
From: Alan C. Assis
Sent: den 8 mars 2023 19:15
To: dev@nuttx.apache.org
Cc: Sebastien Lorquet
Subject: Re: DISCUSSION - Usage of mailing lists for apache projects
Hi
On Wed, Mar 8, 2023 at 7:16 PM Alan C. Assis wrote:
> Problem is that we don't have enough reviewers.
I was recently invited to the PMC, thank you, this is a great honour,
and obligation, I will try to act as best I can to support you folks..
but this is really lots of everyday work from what I ca
Hi Lwazi,
It is not sarcarm, I'm talking about facts.
Also I didn't say Sebastien points aren't valid, but is diverting from
the real issue.
The issue is not if the discussion is happening here or there, the
Problem is that we don't have enough reviewers.
So, first step is that NuttX needs to i
On Wed, Mar 8, 2023 at 6:08 PM Tomek CEDRO wrote:
> Master branch can have some things that will not work. No one is able
> to predict everything. It is still possible to revert changes or
> redirect them in a good "backward compatible" way with a new feature.
Just a note: There are two approaches
On Wed, Mar 8, 2023 at 10:05 PM Sebastien Lorquet
wrote:
> I dont think your point of view is very realistic. You seem to be
> turning the situation into something that pleases you but is not really
> compatible with what can be observed from outside.
>
> In the archive for 2023 there are 2035 to
On Wed, Mar 8, 2023 at 5:37 PM Lwazi Dube wrote:
> On Wed, 8 Mar 2023 at 09:55, Alan C. Assis wrote:
> >
> > Sebastien,
> >
> > If all the discussions that happens on github start to happen here,
> > this mailing list will be just like the nuttx-commits mailing list.
>
> I'll take this as sarcasm
Hi,
I am really certain "people" have the best intention, but it would be
even better if they shared these with the rest of the community.
And I am not talking about code review.
You cant review code if you dont know there IS serious code to review.
And we dont need to review every typo.
I
On Wed, 8 Mar 2023 at 09:55, Alan C. Assis wrote:
>
> Sebastien,
>
> If all the discussions that happens on github start to happen here,
> this mailing list will be just like the nuttx-commits mailing list.
I'll take this as sarcasm. Sebastien is making a lot of valid points,
in good faith, and b
This whole thread really bums me out. We really should be assuming people
are acting with best intentions, rather than accusing of ulterior motives.
If there are changes that you have concerns about people tend to be very
reasonable about explaining and if we need to revert something or change
some
I think that there are two different kinds of discussion that we need to
have and these are probably best done in different forums.
/*Black Box*/
By black box I mean the externally observed behavior and characteristics
of the OS: Interfaces, performance, driver facilities, build changes
etc.
but, Github PRs and discussion there is not public?
And also the commits, messages and discussions are not being archived?
So, what exactly is the problem?
to me it seems more like you are trying to justify your failure to
follow the project and discuss it in the community.
Obs: I feel like I'
I tend to disagree.
You have extreme views that all commits need to be discussed. That is false.
What need to be discussed is much subtle.
We need to have discussion whenever ANYONE has a doubt about something
that is happening on github BEFORE this is committed.
Xiaomi (and other companies
On 3/8/2023 9:17 AM, Gregory Nutt wrote:
``There's a saying here that "if it didn't happen on list, it didn't
happen." '' (yes, probably from someone that develops or sales a
mailing list software) Hehehe
No. That is official ASF policy summarized as a motto:
https://community.apache.org/ne
``There's a saying here that "if it didn't happen on list, it didn't
happen." '' (yes, probably from someone that develops or sales a
mailing list software) Hehehe
No. That is official ASF policy summarized as a motto:
https://community.apache.org/newbiefaq.html#NewbieFAQ-IsthereaCodeofCond
Hi Nathan,
``There's a saying here that "if it didn't happen on list, it didn't
happen." '' (yes, probably from someone that develops or sales a
mailing list software) Hehehe
I think we need to have a middle ground, if every single commit needs
to "happen on list, to be considered as happen", it
Sebastien,
If all the discussions that happens on github start to happen here,
this mailing list will be just like the nuttx-commits mailing list.
So, your point is a catch 22! (dilemma)... You are against using
github and against have a mailing list with huge email messages.
Also you cannot com
I do think that as a project community, this is an important discussion to have.
There are significant changes taking place regularly. I am in favor of
improving the code, improving our POSIX-like / Linux-like / Unix-like
compliance as much as is feasible while supporting deeply embedded and
small
I dont think your point of view is very realistic. You seem to be
turning the situation into something that pleases you but is not really
compatible with what can be observed from outside.
In the archive for 2023 there are 2035 topics, I just overlooked more
than 600 of them and ALL of them ar
s/he/here/
On 3/8/23, Alan C. Assis wrote:
> Hi Sebastien,
>
> Yes, that commit list is mostly for people who don't want to use
> github but still wanting to see what is going on.
>
> Sometimes when a very important PR raises some concern on GitHub PR,
> people post their concern he, it already h
Hi Sebastien,
Yes, that commit list is mostly for people who don't want to use
github but still wanting to see what is going on.
Sometimes when a very important PR raises some concern on GitHub PR,
people post their concern he, it already happened many times.
But again: the best way to guarantee
Hi,
I had a look and this mailing list is not made for human consumption.
No one has ever sent a message on it manually, right?
In practice, important changes are still NOT discussed on the DEV
mailing list.
You said yourself that "all development has moved to github".
As soon as automated
HI Sebastien,
It is already done, you just need to subscribe to
https://lists.apache.org/list.html?comm...@nuttx.apache.org to receive
all commits messages and discussions.
Everything is archived on apache side!
BR,
Alan
On 3/8/23, Sebastien Lorquet wrote:
> Apache projects are required to us
Apache projects are required to use mailing lists for long term archival
purposes.
It seems to me that this project is avoiding that rule and moved all
development to github
This is in contradiction with the Apache project rules.
I request clarification on this situation and requirement (in
43 matches
Mail list logo
