Hi,
> Things are a bit different in ASF as we can use jenkins instead of travis ci.
Other CIs are available, but jenkins is probably he most widely used one.
Thanks,
Justin
Hi,
> I am just wondering if we are excluding any users by forcing everyone to use
> PRs.
In my experience there are people why will refuse to use GitHub (because of
reasons), they may however still use git.
Thanks,
Justin
JFYI
> Begin forwarded message:
>
> From: jincheng sun
> Subject: Add some instructions or make the link available on Nuttx home page
> Date: 16 December 2019 at 6:07:28 pm AEDT
> To: gene...@incubator.apache.org
> Reply-To: gene...@incubator.apache.org
>
> I found there is a link of NuttX is
Ok,
That was a bigger hassle than I expected. The converter tool was getting
tripped up with odd escaping and generating bad XML files for confluence,
but I think it is good now.
I also went through and manually cleaned the naming, obvious issues, and
inserted a bunch of confluence macros on the
Things are a bit different in ASF as we can use jenkins instead of travis
ci.
If the code is ready on github, I could help setting up the jenkins job to
pull PR as I've done this for other ASF projects in the past.
Thanks.
Xiang Xiao 于2019年12月16日周一 上午11:35写道：
> Yes, GitHub has the standard
Yes, GitHub has the standard workflow, we just need insert our special
requirement(style, build and test) into it:
https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/github-flow
Here is one example mynewt:
https://github.com/apache/mynewt-core/pull/2126
Thanks
Xiang
On
Case in point: My $company uses a really awesome SCM: Apache Subversion :-)
All very large corporations I have worked for use commercial SCM
suites. GIT is a great thing for open source projects and small
businesses, but for those companies with essentially unlimited resources
you will often
On Sun, Dec 15, 2019 at 9:12 PM Gregory Nutt wrote:
> Sorry to keep running on...
>
> Another thing is that we do not want dictate to uses of release what
> configuration management tools they must use. In our open source
> culture, GIT is pervasive, but remember that many corporations prefer
>
But I think that someone from committer need convert patch to the
github pull request, and then pass all automatic check before
submitting the change.
To ensure the commit quality, nobody can bypass the workflow we will setup.
You are absolutely right. There is not difference between
Sorry to keep running on...
Another thing is that we do not want dictate to uses of release what
configuration management tools they must use. In our open source
culture, GIT is pervasive, but remember that many corporations prefer
commercial SCM systems. I don't think anything about the
But I think that someone from committer need convert patch to the
github pull request, and then pass all automatic check before
submitting the change.
To ensure the commit quality, nobody can bypass the workflow we will setup.
On Mon, Dec 16, 2019 at 9:48 AM Gregory Nutt wrote:
>
> Just a guess,
Just a guess, but I think right now we receive 50 or so patches for each
PR. That is very deeply ingrained in NuttX userland.
On 12/15/2019 7:45 PM, Gregory Nutt wrote:
I am just wondering if we are excluding any users by forcing everyone
to use PRs. I personally don't have problems with
I am just wondering if we are excluding any users by forcing everyone
to use PRs. I personally don't have problems with mixed PRs and
patches, provided that the patches apply clean. I think we should
take the side of the lowest common denominator user and NOT the point
of view that makes
I am just wondering if we are excluding any users by forcing everyone to
use PRs. I personally don't have problems with mixed PRs and patches,
provided that the patches apply clean. I think we should take the side
of the lowest common denominator user and NOT the point of view that
makes our
Hi,
.
> That's basically true of IRC, conference call, or any real time
> communication.
>
Email has many advantages:
- it allows anyone not matter their day job or time zone to take part
- it tends to have a higher ratio of informational content
- its easily searchable and archived
- it has
On Sun, Dec 15, 2019 at 5:29 PM Gregory Nutt wrote:
>
> >> I created a #nuttx Slack channel in the ASF Slack. My understanding is
> >> that anyone can join a single channel even if you are not a project
> member.
> > If I may... I'm not sure that's such a great idea.
> >
> > I'm open to
First stab at the import went surprisingly well. All but a few pages
converted, unfortunately the hierarchy did not convert correctly so I will
have to mess with it more (these tools are mostly abandoned for 8+ years so
at least they run).
That is good news.
Greg I dont think I will need
First stab at the import went surprisingly well. All but a few pages
converted, unfortunately the hierarchy did not convert correctly so I will
have to mess with it more (these tools are mostly abandoned for 8+ years so
at least they run).
Greg I dont think I will need the other non wiki files
On 12/15/19, Gregory Nutt wrote:
>
>>> A little off topic: What are going to do with all of those fragmentary,
>>> unsupported versions of the Wiki in other languages. People got enthused
>>> to have a copy of the Wiki in there own language, converted a couple of
>>> pages, then wandered off to
Hi Greg,
On 12/15/19, Gregory Nutt wrote:
>
>> Did you get access? When I try to login, it tell me I don't have
>> permission.
>>
>> So, let see if you get the UWC working converting DocuWiki to Confluence.
>>
>> I can help organizing the content to create better categories to let
>> users find
Did you get access? When I try to login, it tell me I don't have permission.
So, let see if you get the UWC working converting DocuWiki to Confluence.
I can help organizing the content to create better categories to let
users find it easily.
A little off topic: What are going to do with
Hi Brennan,
Did you get access? When I try to login, it tell me I don't have permission.
So, let see if you get the UWC working converting DocuWiki to Confluence.
I can help organizing the content to create better categories to let
users find it easily.
BR,
Alan
On 12/15/19, Gregory Nutt
On Sun, Dec 15, 2019 at 5:12 PM Gregory Nutt wrote:
> > Apache supports a Slack. But it is only available for posting by
> > project members.
> > https://cwiki.apache.org/confluence/display/INFRA/Slack+Guest+Invites
> > No members can join into a single channel, but I am not sure exactly
> > how
On 12/15/2019 3:19 PM, Brennan Ashton wrote:
Ftp or just a zip is fine. The media can be mixed with the pages or not.
However it's setup now should be fine. This is what I need from the docs of
the first converter stage.
I can tar up the data directories, put them in a google drive, and share
Apache supports a Slack. But it is only available for posting by
project members.
https://cwiki.apache.org/confluence/display/INFRA/Slack+Guest+Invites
No members can join into a single channel, but I am not sure exactly
how that works. The sign-up is here http://s.apache.org/slack-invite
I would rather use an IRC channel than slack :p
Where is this channel? Freenode? #nuttx ?
Sebastien
On 12/15/19 11:05 PM, Gregory Nutt wrote:
Communication stuff
I still see the slack channels, but they will go away? The IRC
channel will get back up in IRC apache? Linked in yes no? What
Communication stuff
I still see the slack channels, but they will go away? The IRC channel will get
back up in IRC apache? Linked in yes no? What the communication plan??!
Slack is shutting down. I tried to login earlier to deactivate myself
and it turns out that I was already deactivated.
On Sun, Dec 15, 2019 at 3:34 AM Disruptive Solutions
wrote:
>
> Its a bit messy on the mail right now... (And maybe its only my feeling then
> please do nothing with my question/signal).
Yes. We need to get accustomed to the new way of doing things...
I think the key is to keep one thread per
I would never permit anything that was not BSD or MIT into the repositories on
into the build (and now Apache). It is our policy that there will be no
licensing surprises to the end-user. There should be no concerns there.
When I did a quick review of the last release I did find one GPL
hello,
I am not favorable personally with submodules. They are a pain to keep
in sync across multiple remotes and branches.
This was used in the past in NuttX, and it was aborted.
Sebastien
On 12/13/19 3:28 AM, Anthony Merlino wrote:
I think submodules are a good way to go. That would
Ftp or just a zip is fine. The media can be mixed with the pages or not.
However it's setup now should be fine. This is what I need from the docs of
the first converter stage.
--Brennan
On Sun, Dec 15, 2019, 1:15 PM Gregory Nutt wrote:
>
> >> I would be happy to push this
So, could we just remove the original BSD header
from Samsung modified files and just keep their Apache license into
those file?
I don’t recommend we do that as they may of made changes or the files may of
changed since they copied them. They probably also used teh 3rd party header
not the
Hi,
> Also, there are no unmodified 3rd party files. Third party files were used
> as starting points for the development of NuttX-specific applications. All
> were highly modified and converted to the NuttX coding standard.
See here for how to treat 3rd party works [1]. In general the
I would be happy to push this forward. If there is a test space I can give
it a go this evening.
I’ve created a test space for you, if you need another just ask.
https://cwiki.apache.org/confluence/display/NUTTXTEST
There are only a few things that need to be brought in. From DocuWiki,
Justin,
Username is btashton
Greg could you send me a zip with the raw wiki folder? That would simplify
things for me.
Thanks,
Brennan
On Sun, Dec 15, 2019, 1:07 PM Justin Mclean
wrote:
> Hi,
>
> I’ve given the PPMC basic permissions, if you need more ask.
>
> Thanks,
> Justin
Hi,
> When Samsung got the NuttX files they put an Apache license header
> over the BSD header, now the original BSD Header will disappear from
> NuttX project files.
Correct we’ll replace, where needed, the original BSD header with an ASF one.
Note that the ASF has a different header for it’s
In the nuttx/ repository, there are a total 10,626 .c and .h files with copyrights in
the header (which should be all of them). Build-related files may also have
copyrights but are excluded here. I hold the copyright on 8,328 of them (78%). Sony
holds the copyright 401 files on (<4%) and
Hi,
I’ve given the PPMC basic permissions, if you need more ask.
Thanks,
Justin
Hi,
> I would be happy to push this forward. If there is a test space I can give
> it a go this evening.
I’ve created a test space for you, if you need another just ask.
https://cwiki.apache.org/confluence/display/NUTTXTEST
I’ll need your account name to give you permissions
Thanks,
Justin
Hi,
> You mean like Samsung did (and Motorola and project Ara an on and on..).
Not really in the spirit of OS there, sorry that happened.
> Samsung took the code from me first. I would not be taking any of their code
> at all. Just their license.
They may of made changes and we would need
Moving to the dev list.
Infra have go back to use and are willing to try it, but need someone to help.
Can someone here help?
I am the only person that knows that Wiki well. I don't believe that
there any anyone else that can help.
And I would be glad to help.
Greg
Well it possible to use the code and both licenses are compatible. You would
generally want have people be involved and donate code rather than just taking
it.
You mean like Samsung did (and Motorola and project Ara an on and
on..). Samsung took the code from me first. I would not be
Justin,
I would be happy to push this forward. If there is a test space I can give
it a go this evening.
--Brennan
On Sun, Dec 15, 2019, 12:49 PM Justin Mclean
wrote:
> Hi,
>
> Moving to the dev list.
>
> Infra have go back to use and are willing to try it, but need someone to
> help. Can
Hi,
> And committed a new nuttx.xml file under trunk/content/projects, but then I
> was checking the svn log, and I saw a commit from you adding a nuttx.yml file
> under trunk/content/podlings. Is the documentation stale and we are supposed
> to track the status in the file you added? Could
Hi,
> But I suppose, since it is done under Samsungs legal responsibility, we could
> bring any code back from Samsung? (as if I had a clue what I am talking
> about).
Well it possible to use the code and both licenses are compatible. You would
generally want have people be involved and
Hi,
We would need to refine that list to explode 3rd party code, what matters is
which files we going to change the headers on to Apache.
Thanks,
Justin
Perhaps it would be more efficient if you could forward my reply now.
I can add more if I am granted access.
Nevermind, I see that I don't have to join the list to post. Everything
should be there (although I do not see my long response yet).
1.
https://lists.apache.org/thread.html/d58f8edd36eff155f061e84229dc035a71ea5cd7f0fa622bdd1a5dd0%40%3Clegal-discuss.apache.org%3E
Some general comments on that thread:
"It would be more accurate to say that Gregory Nutt *claims* copyright
over the whole code. However, the facts you give —
Hi,
Some chaos was expected. The project is still on the road of moving.
The main communication channel is the dev list now.
The google group is still operational but that won't be for too long. It
will either get archived or posters will be redirected to the dev mailing
list..
The Slack channel
49 matches
Mail list logo
