Seems as if the whole Apache Confluence server is down now. Is there a
place to see the status of Apache infrastructure resources?
--Brennan
On Wed, Dec 18, 2019 at 10:29 PM Brennan Ashton
wrote:
> Justin,
> Do you know why the viewpdf plugin does not seem to work?
> For now I am embedding them
Justin,
Do you know why the viewpdf plugin does not seem to work?
For now I am embedding them as regular files (they are already attached to
the space), but it seems like I should be able to use this macro
https://confluence.atlassian.com/conf71/pdf-macro-979423446.html
Instead I am getting
Unknow
Hi,
Just in case you were wondering what this is, podlings need to report to the
incubator monthly for 3 months and then quarterly after that. Top level
projects do the same but report to the board. The mentors if happy with the
report sign it off and it gets added to the incubator board repor
Dear podling,
This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.
The board meeting is scheduled for Wed, 15 January 2020, 10:30 am PDT.
The report for your podling will form
Hi,
> However, in order to workaround one jenkins job cannot receive two github
> repos webhook trigger( or I haven't found it yet : ( ), assign two jenkins
> job instead.
There are a number of way around this e.g. off top of my head multiple step
pipeline, jenkins run a shell script to check ou
David, sorry that my expression was not clearly. What I meant is keep only
two repositories apps/ and nuttx/ instead of sub-modules.
However, in order to workaround one jenkins job cannot receive two github
repos webhook trigger( or I haven't found it yet : ( ), assign two jenkins
job instead.
One
On Wed, Dec 18, 2019, 5:06 PM Justin Mclean
wrote:
> Nhi,
>
> > This conversation got me thinking: would we want a repository to write a
> > community-written-and-maintained NuttX book?
> >
> > I think this would have a couple of advantages:
> >
> > (1) Keeps the "official" documentation within t
Nhi,
> This conversation got me thinking: would we want a repository to write a
> community-written-and-maintained NuttX book?
>
> I think this would have a couple of advantages:
>
> (1) Keeps the "official" documentation within the umbrella of the project.
>
> (2) Provides an additional way fo
Hi,
> Will the release artifacts go into SVN at dist.apache.org? Or are git-based
> projects released differently?
They need to be placed their, putting them there means they get distributed to
Apache mirrors sites [1] allowing easy access from allover the world. It
usually take about 24 hours
As we fill in the details, this discussion will naturally blend in specifics of
implementation and tools — I expect “git” might come up in the discussions ;)
But only when we discussing details of implementation... AFTER we have
established functional requirements. Git discussions are basica
We’ve digressed a bit on this thread. Let’s see if we can reboot DavidS’
Workflow thread and keep the thread on topic.
Let me start by stating a few [obvious] objectives:
Keep things simple for those NuttX users who prefer to work with a zip’d
release.
provide best-practice tools and workflow t
For HBaseCon, usually the discussion will first be made in the private
mailing list, to get enough PMC members support, and then you can post it
in the public mailing list to get the PC members for reviewing and
accepting the submissions, and also a PMC member must send an email to the
trademarks m
On Wed, Dec 18, 2019 at 3:51 PM David Sidrane wrote:
> Hi Nathan,
>
> Great list!
>
> I can +1 on most of them, but isn't correct that the PPMC will need to all
> agree on these?
Hi David,
Thank you.
As I said, I was:
> Just throwing some thoughts out here as a starting point for that
> top-do
This conversation got me thinking: would we want a repository to write a
community-written-and-maintained NuttX book?
Like https://nuttx_projects.gitlab.io/nuttx_book/
And whose project is that?
It is very old. phreakuencies is v01d and, I think that is the old
handle for Matias N. (Nitzch
On Wed, Dec 18, 2019 at 6:45 PM Gregory Nutt wrote:
>
> >>> Ben ve Veen has started a Getting Started Book and, as I recall, even
> >> has a publisher in mind. He posted his status in the original thread
> the I
> >> renamed. Perhaps you could discuss ways to collaborate?
> >>
> >> I saw that.
On Wed, Dec 18, 2019 at 4:21 PM Justin Mclean
wrote:
> Hi,
>
> Forgive me for top posting.
>
> Some things that may help:
> - Unusually release are only signed by the RM (but you can have others
> sign it as well)
> - It’s best to use your apache email address (but it’s not required)
> - A key
Ben ve Veen has started a Getting Started Book and, as I recall, even
has a publisher in mind. He posted his status in the original thread the I
renamed. Perhaps you could discuss ways to collaborate?
I saw that. I have published a book (on Android), writing it was a large
amount of work an
On Wed, Dec 18, 2019 at 5:20 PM Justin Mclean
wrote:
> > Ben ve Veen has started a Getting Started Book and, as I recall, even
> has a publisher in mind. He posted his status in the original thread the I
> renamed. Perhaps you could discuss ways to collaborate?
>
> I saw that. I have published
Those of you that are used to the fast-response, shoot-from-the-hip
style of the old BSD NuttX will in for a rude awakening. There will be
some bureaucracy, some overhead, and lots of processes. The processes
are, I believe, good for NuttX. It is now too large and too critical to
depend on ho
A little. :-) I've worked on a few commercial projects in recent
years and way back I did SCADA and real time systems and been
involved as a hobbyist for 15 or so years. I’m spoken at the Open
Hardware Summit and given a number of IoT and MyNewt talks at various
conferences, and run basic
Hi,
To answer a couple of your questions.
> over 2 weeks nuttx.apache.org has content?
Would be good to start what to do about this in another thread. Having a
website even if minimal to start with is sort of important.
> Jira is up?
From what I can see it not decided if JIRA is needed or not
A little. :-) I've worked on a few commercial projects in recent years and way
back I did SCADA and real time systems and been involved as a hobbyist for 15
or so years. I’m spoken at the Open Hardware Summit and given a number of IoT
and MyNewt talks at various conferences, and run basic A
Do we really have to do some sharing in what we did in the past to get each
others trust or something? I really do not care about egos and stuff like that.
Focus and get things done please... politics are another matter right?
Apache: please tell us which milestones are set?
over 2 weeks nuttx.a
With Nathan's workflow on another thread, DavidS's workflow early in
this thread, Nathan's workflow on this thread, Nathan's workflow with my
appended workflow, and Justin's comments ... Do we have enough to define
an initial workflow? I think so. Some of it is a little inconsistent
(but not
Hi,
> That is great that you could commit. I notice that you are the Chair of the
> Mynewt project, so you must have some familiarity.
A little. :-) I've worked on a few commercial projects in recent years and way
back I did SCADA and real time systems and been involved as a hobbyist for 15
We need to get this discussion onto a separate thread. I just created a
getting started thread, but I think we just crossed paths
On 12/18/2019 4:00 PM, Disruptive Solutions wrote:
Maybe one can make a roadmap and milestones when we can expect things getting
back to “normal”. What is who doin
Maybe one can make a roadmap and milestones when we can expect things getting
back to “normal”. What is who doing and what has to be done?
Maybe its better to write a getting started guide how to contribute? Making
patches, code conventions, etc etc
Ben
Verstuurd vanaf mijn iPhone
> Op 18 de
We never had a Getting Started guide. We need one. And because it's so
hard for someone "in the know" not to assume knowledge, we may need
the help of some total n00bs to get this guide written -- to see where
they get stuck and waste time looking for answers, and write those
things in the guid
Hi,
> I can +1 on most of them, but isn't correct that the PPMC will need to all
> agree on these?
There need to reach consensus, that doesn’t mean all need to 100% agree but all
are OK with the proposed workflow.
>> When they wish to contribute, they can do so:
>> * Via a pull request
>> * Via
HI,
> 3.
> PMC should triage and assign the change to a committer. PMC may
> also review for conformance with the Inviolables If this review
> fails, the change is declined.
Most of the Apache projects I’m on let committers select what they what to
review and work on rather than being as
Hi,
> We never had a Getting Started guide. We need one. And because it's so
> hard for someone "in the know" not to assume knowledge, we may need
> the help of some total n00bs to get this guide written -- to see where
> they get stuck and waste time looking for answers, and write those
> things
Hi,
It’s best if the PMC are involved in some way, ideally they would have a hand
in selecting the speakers, and the event would have the ASF as a community
sponsor. For more details see [1]. Given this is an event already in the
planning process and you're an incubating project there’s going t
Hi,
Forgive me for top posting.
Some things that may help:
- Unusually release are only signed by the RM (but you can have others sign it
as well)
- It’s best to use your apache email address (but it’s not required)
- A key signing party is a good idea
- Emails don’t have to be signed (althoug
Where do you see any reference to github (In a url as an example?)
This is all pure git.
Are we going to continue using git?
I will not discuss git or github in this thread. I suggest you start a
new thread on that subject.
Hi Greg,
It is ok to discuss separately the organization of events, they don't need to
happen on the project mailing lists. If the event is open to the community with
an open call for abstracts, then you might want to announce it on the user/dev
lists. Some communities do not like it, though. I
Agreed!
Gosh I am hoping I am not talking down to people. I just remember my
learning curve with git. If we are continuing to use git and I assume we
are: My comments are meant to help people that do not understand how to use
git for the process and evaluate what they will have to do if we choose
Hi Nathan,
Great list!
I can +1 on most of them, but isn't correct that the PPMC will need to all
agree on these?
> When they wish to contribute, they can do so:
> * Via a pull request
> * Via a patch transmitted to us by some method
Is this an ASF edict?
> Regardless of the method, we would c
Greg,
Where do you see any reference to github (In a url as an example?)
This is all pure git.
Are we going to continue using git?
David
-Original Message-
From: Gregory Nutt [mailto:spudan...@gmail.com]
Sent: Wednesday, December 18, 2019 8:07 AM
To: dev@nuttx.apache.org
Subject: Re: [
GOOD and BAD does not say why. It just says how one feel about something.
I get that the system architecture has a clear separate from OS to apps. No
question there. I also see the value in NOT having them in 1 repo.
But please bear with me, and let me tease out some "Why" answers on this
thread.
What about the people who are just learning Nuttx? Simple is relative.
We never had a Getting Started guide. We need one.
The top-level README.txt file has been the only authoritative, supported
getting started guide. It has the most complete discussion without
focusing on any particular ar
My current state is that the outline is formed and that the filling per
"chapter" is on its way and that the purpose of the book is set. Its public is
also for people who come across Nuttx for the first time and do not have seen
movies or other tutorials from Nuttx and did not have the privilege
The 2 and 3 is to contrast HARD against EASY. This is so ALL of us can
realize we are not suggesting doing what is expedient*, What is being
suggested is doing what is right. I am having a really hard time to get you
to see this is not about EASY. It is subtle.
>I don't know if my understanding of
>what advantage does in fact the submodule method bring?
See below
>Even with a hat repository that contains two submodules (apps and nuttx),
>you
>will have to send separate pull requests for each submodule, right?
Yes. But they com nit in 1 Atomic operation.
Submodules 101
This example is wi
>(unless there is a GIT sub-module trick I don't know)
I believe this to be == TRUE. See the steps - try them then you will
understand.
-Original Message-
From: Gregory Nutt [mailto:spudan...@gmail.com]
Sent: Wednesday, December 18, 2019 5:40 AM
To: dev@nuttx.apache.org
Subject: Re: [DIS
Ben vd Veen has been working on a NuttX getting started book for a few
months. I don't know the current state. There was a channel on the old
NuttX Slack devoted to the book, but it has not been updated in a very
long time. Perhaps Ben could fill us in on the current state, progress,
and whe
This is a question for Justin or any other mentor.
There are a couple of associated web sites that are dedicated for NuttX
event planning: nuttx2019.org and https://nuttx.events/. nuttx2019.org
now just re-directs to nuttx.events. They event planners used to use a
private channel in the Nutt
> I'd prefer that the Getting Started guide should be reachable by one
> click from the front page of the NuttX website (which doesn't exist
> yet), so that a TOTAL newbie who hasn't even gotten the code yet can
> read and get a feel for what's involved.
Agree.
I wanted to point out that much of t
On Wed, Dec 18, 2019 at 12:01 PM Gregory Nutt wrote:
> There is this: http://www.nuttx.org/doku.php?id=wiki:getting-started
> where the "external tutorials" is quite extensive:
> http://www.nuttx.org/doku.php?id=wiki:getting-started:external-tutorials
That's great but I think we need our own basi
Boards readme files contain all the information needed to get started
with a particular board.
Many do. They all should. They vary in quality. Some board README
files have no useful information at all; some have old information.
Some consist of only a few lines, some are thousands of li
Boards readme files contain all the information needed to get started
with a particular board.
On Wed, Dec 18, 2019 at 5:01 PM Gregory Nutt wrote:
>
> On 12/18/2019 10:47 AM, Nathan Hartman wrote:
> > On Wed, Dec 18, 2019 at 11:04 AM David Sidrane wrote:
> >> What about the people who are just l
Requirements specification is a top-down activity. It is only driven by
end users needs and project objects. NOT by implementation. That is
the nature of System Engineering: top-down
Just throwing some thoughts out here as a starting point for that
top-down discussion:
Users of NuttX can:
*
On 12/18/2019 10:47 AM, Nathan Hartman wrote:
On Wed, Dec 18, 2019 at 11:04 AM David Sidrane wrote:
What about the people who are just learning Nuttx? Simple is relative.
We never had a Getting Started guide. We need one. And because it's so
hard for someone "in the know" not to assume knowled
On Wed, Dec 18, 2019 at 11:25 AM Gregory Nutt wrote:
>
>
> > I don't think there's a need to sign emails.
> >
> > We just sign the release tarballs and those signatures go into a .sig
> > file that people can download and use to verify the tarballs.
>
> Thanks... I obviously don't know what I am g
On Wed, Dec 18, 2019 at 11:18 AM Gregory Nutt wrote:
> Requirements specification is a top-down activity. It is only driven by
> end users needs and project objects. NOT by implementation. That is
> the nature of System Engineering: top-down
Just throwing some thoughts out here as a starting p
On Wed, Dec 18, 2019 at 11:04 AM David Sidrane wrote:
> What about the people who are just learning Nuttx? Simple is relative.
We never had a Getting Started guide. We need one. And because it's so
hard for someone "in the know" not to assume knowledge, we may need
the help of some total n00bs to
I don't think there's a need to sign emails.
We just sign the release tarballs and those signatures go into a .sig
file that people can download and use to verify the tarballs.
Thanks... I obviously don't know what I am going. Just following
through Apache checklists as I run across them.
On Wed, Dec 18, 2019 at 10:35 AM Gregory Nutt wrote:
> These are Windows computers. My key was created by gpg from the Cygwin
> command line. Do I need to copy this into Windows application data for
> use by a mailer? I use Thunderbird and I am not sure where that would go.
I don't think there
What about the people who are just learning Nuttx? Simple is
relative. I can see how a check out of one folder would make it hard
in your setup and simple for the New folks is'nt that way we are here
to grow the project?
users should not need to learn details of the workflow
BTW: your argume
What about the people who are just learning Nuttx? Simple is relative. I can
see how a check out of one folder would make it hard in your setup and simple
for the New folks is'nt that way we are here to grow the project?
users should not need to learn details of the workflow
BTW: your argum
What about the people who are just learning Nuttx? Simple is relative. I can
see how a check out of one folder would make it hard in your setup and simple
for the New folks is'nt that way we are here to grow the project?
BTW: your argument is solve by sub modules. You would just check out from n
There are three different concepts being discussed here that I think we
should separate. I know that I get confused about which is which.
1. Two repositories apps/ and nuttx/ -- GOOD
2. One respository with apps/ and nuttx/ as folders -- VERY, VERY BAD
3. Three repositories, apps/, nutt
Anotherdumb question...
I have multiple computers and do (work other than just testing) on two:
A desktop and a laptop. I presume that these should have the same key
and that I can just copy .gnupg to that they have the same signing key.
These are Windows computers. My key was created by
On Wed, Dec 18, 2019 at 9:05 AM Gregory Nutt wrote:
> There are three different concepts being discussed here that I think we
> should separate. I know that I get confused about which is which.
>
> 1. Two repositories apps/ and nuttx/ -- GOOD
> 2. One respository with apps/ and nuttx/ as folde
On Wed, Dec 18, 2019 at 9:39 AM Abdelatif Guettouche <
abdelatif.guettou...@gmail.com> wrote:
> Yes they recommend the key to be with an @apache.org email.
> But we can add an email to an existing key.
>
> gpg --edit-key
>
> We then can add an new email through the gpg cli and upload it when we'r
Yes they recommend the key to be with an @apache.org email.
But we can add an email to an existing key.
gpg --edit-key
We then can add an new email through the gpg cli and upload it when we're done.
On Wed, Dec 18, 2019 at 2:12 PM Gregory Nutt wrote:
>
>
> >> I saw the option to send the SSH k
I saw the option to send the SSH keys, so I suppose we will need to fill it
later (for those who didn't it yet).
Also if you do not have your PGP keys yet, you should do that soon. These
are needed for cryptographically signing releases. Several people need to
sign each release in order to rele
git clone --bare
cd
git push --porcelain --mirror
I've done some migrations recently with the commands above.
Justin Mclean 于2019年12月18日周三 下午2:05写道：
> HI,
>
> I think this can be done as simple as using these two commands, but I’ve
> not tried it before.
> git clone —mirror oldrepo
> git p
So I hope that we do not go to far down the github rabbit hole. At this
level. Everytime we have tried to address and agree to the functional
work flow, we get derailed by github technical implementation details.
I think this discussion is relevant still, but we are on edge losing
focus ont
Wait,
what advantage does in fact the submodule method bring?
Even with a hat repository that contains two submodules (apps and nuttx), you
will have to send separate pull requests for each submodule, right?
Sebastien
Le 18/12/2019 à 14:40, Gregory Nutt a écrit :
> On 12/18/2019 4:23 AM, David
5 issue one pull request from your fork nuttx/apps to apache nuttx/apps
master branch
Are you suggesting we have one repo NuttX with 2 folders apps and nuttx?
That will simplify everything! - but I suspect we will receive STRONG
arguments against it.
Isn't this just another case where taki
why completely change what has worked for years?
2 repos as always. Submodules are an absolute pain to manage when you have
branches.
people have always been cloning two repos.
I agree. Let's not change that.
On 12/18/2019 4:23 AM, David Sidrane wrote:
That is precisely what submodules do:submodules aggregate on a single SHAL N
repositories.
The problem is: How to have atomic checkout of the correct configuration with
out a temporal shift?
Please describe how you would do this. Give detailed steps
Option d) Make minimal coding standard changes that can be 100% supported by
option a.*
*) Greg suggested this in the bar at NuttX2019 - caveat it was in the BAR!
No one should be held accountable for what the say in a bar 8-)
A lot depends on the nature of the coding standard change. If
On 12/18/19, Nathan Hartman wrote:
> On Wed, Dec 18, 2019 at 5:46 AM David Sidrane wrote:
>
>> > 5 issue one pull request from your fork nuttx/apps to apache nuttx/apps
>> master branch
>>
>> Are you suggesting we have one repo NuttX with 2 folders apps and nuttx?
>>
>> That will simplify everyth
i would oppose combining those two repos into one because i agree with the
concept that we should not make the user's life harder for our convenience.
I am also (very) opposed to combining repositories. Smearing
functionality is just bad system architecture. Separateness and
modularity is a
Hi Nathan,
On 12/18/19, Nathan Hartman wrote:
> On Wed, Dec 18, 2019 at 5:24 AM Alan Carvalho de Assis
> wrote:
>
> Thank you Greg!
>>
>> I saw the option to send the SSH keys, so I suppose we will need to fill
>> it
>> later (for those who didn't it yet).
>
>
> Also if you do not have your PGP
On Wed, Dec 18, 2019 at 5:46 AM David Sidrane wrote:
> > 5 issue one pull request from your fork nuttx/apps to apache nuttx/apps
> master branch
>
> Are you suggesting we have one repo NuttX with 2 folders apps and nuttx?
>
> That will simplify everything! - but I suspect we will receive STRONG
>
On Wed, Dec 18, 2019 at 5:24 AM Alan Carvalho de Assis
wrote:
Thank you Greg!
>
> I saw the option to send the SSH keys, so I suppose we will need to fill it
> later (for those who didn't it yet).
Also if you do not have your PGP keys yet, you should do that soon. These
are needed for cryptogra
Hi Sebastien,
I agree submodules are a PAIN! But I do not agree this is hard it is just
more steps.
This why: Because on a busy project it will break the build and/or cause
code to not get run.
It will waist time debugging ghosts and creating problem posts to list of
issues that are not reproduc
+1
-Original Message-
From: Gregory Nutt [mailto:spudan...@gmail.com]
Sent: Tuesday, December 17, 2019 8:07 PM
To: dev@nuttx.apache.org
Subject: Re: patch for ntpclient: merge xmit and recv buffer into one to
save the stack
> Should we enable the attachment before the new workflow settle?
why completely change what has worked for years?
2 repos as always. Submodules are an absolute pain to manage when you have
branches.
people have always been cloning two repos.
devs were sending patches for one of them.
Now they send pull request instead. Better tracking, ability to fix while
> 5 issue one pull request from your fork nuttx/apps to apache nuttx/apps
> master branch
Are you suggesting we have one repo NuttX with 2 folders apps and nuttx?
That will simplify everything! - but I suspect we will receive STRONG arguments
against it.
So you say "one pull request"
Where
>I haven’t found proper github plugin to get PRs from multiple repos(especially
>PRs dependency
1) How would you create a way to do this.
Hows about we add a file to the repo with the 2 shals in it and hand edit it
before every push?
["NuttX/nuttx"]
path = NuttX/nuttx
url = h
Thank you Greg!
I saw the option to send the SSH keys, so I suppose we will need to fill it
later (for those who didn't it yet).
BR,
Alan
On Tuesday, December 17, 2019, Gregory Nutt wrote:
> PPMC members have Apache email addresses. Mine is gn...@apache.org for
example. I stumbled across thi
That is precisely what submodules do:submodules aggregate on a single SHAL N
repositories.
The problem is: How to have atomic checkout of the correct configuration with
out a temporal shift?
Please describe how you would do this. Give detailed steps.
On 2019/12/18 10:09:26, Alan Carvalho de As
Hi,
Sharing my thoughts here for discussion.
=== Source code checking
Prior to submission, the submission shall be checked by a source code
beatify-er.
REQ1: The submission shall not be possible without a local check passing.
REQ2: A tool shall be used to check the NuttX coding standard
Hi Liu,
On Wednesday, December 18, 2019, Haitao Liu wrote:
> How about just keep two separate git repositories (apps and nuttx
> projects) instead
> of add a parent knot repo with apps and nuttx as sub-modules?
> As to jenkins CI, I haven’t found proper github plugin to get PRs from
> multiple re
How about just keep two separate git repositories (apps and nuttx
projects) instead
of add a parent knot repo with apps and nuttx as sub-modules?
As to jenkins CI, I haven’t found proper github plugin to get PRs from
multiple repos(especially PRs dependency in apps & nuttx ) in one Jenkins
job. Be
88 matches
Mail list logo
