You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mynewt.apache.org by James Pace <pa...@runtime.io> on 2015/11/25 01:06:34 UTC

contributing to documentation?

Hello, Mynewties. I am walking through a lot of the documentation related to Mynewt and would like to make a few edits/changes per the instructions on the site. I think that I need to be explicitly added as a committer in order to “git push” these changes. What’s the process for becoming a committer so that I might help? 

appreciatively,

James Pace

Re: contributing to documentation?

Posted by James Pace <pa...@runtime.io>.

Thanks, Greg and Aditi. I’ll continue to plug away on my forked branch and walk through the link that Aditi has sent. I think that this should work out fine.

best,

James

On Nov 25, 2015, at 15:40, aditi hilbert <ad...@runtime.io> wrote:

> I see there is a proposed workflow for non-committers. 
> https://git-wip-us.apache.org/docs/workflow.html <https://git-wip-us.apache.org/docs/workflow.html>
> 
> I am adding references to that in the Mynewt documentation/site as well.
> 
> thanks,
> aditi
> 
>> On Nov 24, 2015, at 9:11 PM, Greg Stein <gs...@gmail.com> wrote:
>> 
>> That's great, James!
>> 
>> You're our first request for committer status, so we kinda need some time
>> to figure out how we'd like to onboard volunteers like yourself. Sort of a
>> meta- discussion. ... and with the Thanksgiving holiday in the US, it's
>> gonna derail that needed discussion. As an incubating project, we need to
>> figure some of this stuff out.
>> 
>> If you have a GitHub account, then I'd suggest that you go ahead and make
>> any/all changes that you like there, via a fork of
>> https://github.com/apache/incubator-mynewt-documentation. We can always get
>> those integrated. I'd also suggest not worrying about pull requests right
>> now. Just create a fork and have fun. We can take all your work, or cherry
>> pick, but right now... no need to for more overhead.
>> 
>> If you don't have a GH account, then I'd suggest just building up changes
>> in your local git clone, and we'll figure it out from there.
>> 
>> Thanks!
>> -g
>> 
>> 
>> On Tue, Nov 24, 2015 at 6:06 PM, James Pace <pa...@runtime.io> wrote:
>> 
>>> Hello, Mynewties. I am walking through a lot of the documentation related
>>> to Mynewt and would like to make a few edits/changes per the instructions
>>> on the site. I think that I need to be explicitly added as a committer in
>>> order to “git push” these changes. What’s the process for becoming a
>>> committer so that I might help?
>>> 
>>> appreciatively,
>>> 
>>> James Pace
>

Re: contributing to documentation?

Posted by aditi hilbert <ad...@runtime.io>.

I see there is a proposed workflow for non-committers. 
https://git-wip-us.apache.org/docs/workflow.html <https://git-wip-us.apache.org/docs/workflow.html>

I am adding references to that in the Mynewt documentation/site as well.

thanks,
aditi

> On Nov 24, 2015, at 9:11 PM, Greg Stein <gs...@gmail.com> wrote:
> 
> That's great, James!
> 
> You're our first request for committer status, so we kinda need some time
> to figure out how we'd like to onboard volunteers like yourself. Sort of a
> meta- discussion. ... and with the Thanksgiving holiday in the US, it's
> gonna derail that needed discussion. As an incubating project, we need to
> figure some of this stuff out.
> 
> If you have a GitHub account, then I'd suggest that you go ahead and make
> any/all changes that you like there, via a fork of
> https://github.com/apache/incubator-mynewt-documentation. We can always get
> those integrated. I'd also suggest not worrying about pull requests right
> now. Just create a fork and have fun. We can take all your work, or cherry
> pick, but right now... no need to for more overhead.
> 
> If you don't have a GH account, then I'd suggest just building up changes
> in your local git clone, and we'll figure it out from there.
> 
> Thanks!
> -g
> 
> 
> On Tue, Nov 24, 2015 at 6:06 PM, James Pace <pa...@runtime.io> wrote:
> 
>> Hello, Mynewties. I am walking through a lot of the documentation related
>> to Mynewt and would like to make a few edits/changes per the instructions
>> on the site. I think that I need to be explicitly added as a committer in
>> order to “git push” these changes. What’s the process for becoming a
>> committer so that I might help?
>> 
>> appreciatively,
>> 
>> James Pace

Re: contributing to documentation?

Posted by Greg Stein <gs...@gmail.com>.

That's great, James!

You're our first request for committer status, so we kinda need some time
to figure out how we'd like to onboard volunteers like yourself. Sort of a
meta- discussion. ... and with the Thanksgiving holiday in the US, it's
gonna derail that needed discussion. As an incubating project, we need to
figure some of this stuff out.

If you have a GitHub account, then I'd suggest that you go ahead and make
any/all changes that you like there, via a fork of
https://github.com/apache/incubator-mynewt-documentation. We can always get
those integrated. I'd also suggest not worrying about pull requests right
now. Just create a fork and have fun. We can take all your work, or cherry
pick, but right now... no need to for more overhead.

If you don't have a GH account, then I'd suggest just building up changes
in your local git clone, and we'll figure it out from there.

Thanks!
-g

On Tue, Nov 24, 2015 at 6:06 PM, James Pace <pa...@runtime.io> wrote:

> Hello, Mynewties. I am walking through a lot of the documentation related
> to Mynewt and would like to make a few edits/changes per the instructions
> on the site. I think that I need to be explicitly added as a committer in
> order to “git push” these changes. What’s the process for becoming a
> committer so that I might help?
>
> appreciatively,
>
> James Pace