On Wed, Aug 12, 2020 at 12:07 PM Gregory Nutt wrote:
>
> How/who would prioritize and
> schedule implementation of roadmap items? How could accomplish any of
> this with only a volunteer organization and no project management with
> any authority?
Open source tends to be driven by people
Thanks for catching that Abdelatif.
I moved the NuttX project board here:
https://github.com/apache/incubator-nuttx/projects/2
We can delete it if we don't like it.
-adam
On Wed, Aug 12, 2020 at 11:43 AM Adam Feuer wrote:
> On Wed, Aug 12, 2020 at 11:40 AM Abdelatif Guettouche <
>
We probably should also include all Github Issues that are listed as
enhancements.
If we use a Github Project Board like Brennan suggested this would be
pretty easy to link them there.
Jira will link to github issues as well, as I recall. We went through
all of this in the early days of
On Wed, Aug 12, 2020 at 11:40 AM Abdelatif Guettouche <
abdelatif.guettou...@gmail.com> wrote:
> Was it intentional to create it in Apache's and not here:
> https://github.com/apache/incubator-nuttx/projects?
Oops. No. :) I'll move it or recreate it there.
-adam
> Well I just made a board for us:
Was it intentional to create it in Apache's and not here:
https://github.com/apache/incubator-nuttx/projects?
On Wed, Aug 12, 2020 at 7:39 PM Gregory Nutt wrote:
>
> Jira is another option available to us.
>
>
Jira is another option available to us.
Well I just made a board for us:
https://github.com/orgs/apache/projects/13
If we don't like it we can delete it. I added the items from the wiki list
as cards in Future, we should really convert them to issues and add more
description to them. We can add the issues that we're working on to the
> Seems doable. Does anyone have any objections to me creating a board like
this for NuttX?
Not from me, I think with Github's projects (or milestones) and
consistent labeling of issues and PRs people would have a better
overview.
Anyone can then follow the development of the feature of interest.
On Wed, Aug 12, 2020 at 11:04 AM Gregory Nutt wrote:
> We probably should also include all Github Issues that are listed as
> enhancements.
>
If we use a Github Project Board like Brennan suggested this would be
pretty easy to link them there.
-adam
--
Adam Feuer
These are projects which gives you a different view from issues. But there's
also a "milestone":
https://docs.github.com/en/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests
I made a wiki page with the raw list of things that people are asking for
in this thread:
https://cwiki.apache.org/confluence/display/NUTTX/Roadmap
Check it out, add anything I missed, and correct errors I made.
Maybe the next step would be to try to complete this list, then maybe
Brennan,
Re: needing an Apache CWiki account, ok, I get it. So something like this?
Github's public roadmap:
https://github.com/github/roadmap/projects/1
Seems doable. Does anyone have any objections to me creating a board like
this for NuttX?
-adam
On Wed, Aug 12, 2020 at 10:54 AM Brennan
+1 (I know it is not a vote, I am just agreeing)
-Original Message-
From: Brennan Ashton [mailto:bash...@brennanashton.com]
Sent: Wednesday, August 12, 2020 10:54 AM
To: dev@nuttx.apache.org
Subject: Re: Roadmap?
On Wed, Aug 12, 2020, 10:40 AM Adam Feuer wrote:
> Folks,
>
&g
On Wed, Aug 12, 2020, 10:40 AM Adam Feuer wrote:
> Folks,
>
> I made a wiki page with the raw list of things that people are asking for
> in this thread:
>
> https://cwiki.apache.org/confluence/display/NUTTX/Roadmap
I am thinking this might be easier to manage as GH tickets with a label,
and
of
> >> dropping an app there.
> >>
> >> Furthermore, I personally like to use submodules but even if you simply
> >> clone or download a git repo containing just the app, you wouldn't need
> a
> >> central database of apps, just a git repo for ea
tion could be
>> used to collect contributed apps.
>>
>> I have a similar mechanism for OS level code, which is compiled as if it
>> were a subdirectory of nuttx/.
>>
>> Best,
>> Matias
>>
>> > Am Mi., 5. Aug. 2020 um 17:20 Uhr schrieb Xian
If we create issues as a first step, we can identify who will be responsible
for driving that effort forward. The issue can then be assigned to that person
and the issue updated to reflect progress.
The issue can be assigned a GitHub milestone (a way to group issues together,
with an optional
m: Gregory Nutt [mailto:spudan...@gmail.com]
> Sent: Wednesday, August 12, 2020 9:07 AM
> To: dev@nuttx.apache.org
> Subject: Re: Roadmap?
>
>
> > I am interested in industrial devices communicating by fieldbuses. I use
> > the NuttX port of FreeModbus stack and I would like
Github project boards or confluence?
-Original Message-
From: Gregory Nutt [mailto:spudan...@gmail.com]
Sent: Wednesday, August 12, 2020 9:07 AM
To: dev@nuttx.apache.org
Subject: Re: Roadmap?
> I am interested in industrial devices communicating by fieldbuses. I use
> the Nutt
;central repository" is desired, a special github organization could be
> > used to collect contributed apps.
> >
> > I have a similar mechanism for OS level code, which is compiled as if it
> > were a subdirectory of nuttx/.
> >
> > Best,
> > Matias
>
I am interested in industrial devices communicating by fieldbuses. I use
the NuttX port of FreeModbus stack and I would like to see more port of
communication stacks like this. I prefer CANopen and Profinet, There are
several open source communication stack for these protocols.
Where would
0 um 17:20 Uhr schrieb Xiang Xiao <
> > xiaoxiang781...@gmail.com>:
> >
> > > I would see the automation test on the roadmap, thanks.
> > >
> > > > -Original Message-
> > > > From: Matias N.
> > > > Sent: Wednesday
of nuttx/.
Best,
Matias
> Am Mi., 5. Aug. 2020 um 17:20 Uhr schrieb Xiang Xiao <
> xiaoxiang781...@gmail.com>:
>
> > I would see the automation test on the roadmap, thanks.
> >
> > > -Original Message-
> > > From: Matias N.
> > > Sent: Wednesda
I would see the automation test on the roadmap, thanks.
> -Original Message-
> From: Matias N.
> Sent: Wednesday, August 5, 2020 4:59 AM
> To: dev@nuttx.apache.org
> Subject: Re: Roadmap?
>
> Having a (public) roadmap is very good idea, it guides and organizes
Having a (public) roadmap is very good idea, it guides and organizes efforts
over time
and also gives indication to existing or potential users about which features
which are
not currently but might as well be there soon.
I personally would like to see support for Bluetooth/WiFi on widely used
25 matches
Mail list logo
