acassis commented on PR #17352: URL: https://github.com/apache/nuttx/pull/17352#issuecomment-3571141126
> > @xiaoxiang781216 I think we should have a Roadmap from Xiaomi of commits submission, to avoid issues like this. There are my useful things that Xiaomi people did and most still not updated to mainline yet, this causes people to waste their time re-implementing something that you guys already implemented (CMUX support is an example, fortunately the submitted implemented was for userspace and will not conflict with yours and you explained that didn't send it early because it had some issues). > > Having this Roadmap will avoid: > > > > 1. People wasting time reinventing the wheel > > 2. Xiaomi devs will not have to modify their implementation or create internal patches to replace mainline with yours (worst case) > > 3. The situation where someone submit a PR and yours dev submit the same PR to avoid their to enter in mainline that could cause situation 2. > > Who come to first isn't important, we should select the implementation which is better and complete. If both implementation is valuable like cmux and signal, both should be merged. If some work need be done to merge both and the contributor doens't have time to do it, we can take time to do it and keep their credit. > > > I think it also will be useful to bring more awareness of what is coming next and community devs could engage on this process to improve that solution before that it submitted here. > > yes, it will be better to have a place to share the roadmap. I suggest using the Projects here in github to maps the Roadmap features. I should include the supposed date (Weeks of Year 1-52 or Q1-Q3 for distant/complex features). It could contains reference to existing open Issues, to explain what could be implemented in the coming PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
