You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Dmitry Blotsky <db...@microsoft.com> on 2015/07/21 11:02:52 UTC
[DISCUSS] Website Repo
Hey folks,
In lieu of the changes coming to the docs and the website design proposed at the hangout, I’d like to consolidate our docs, blog, and website under one Git repo. Right now we have some code in several Git repos (docs, blog posts), and some in the SVN repo (website itself). I’d like to move for one Git repo to contain them all, and to use the SVN only for deployment. For this, I’d like to move to create either github.com/cordova/cordova-website<http://github.com/cordova/cordova-website> or github.com/apache/cordova-website<http://github.com/apache/cordova-website>.
What are your kind thoughts on this matter?
Kindly,
Dmitry
Re: [DISCUSS] Website Repo
Posted by Dmitry Blotsky <db...@microsoft.com>.
I will add an “edit-on-github” feature for the docs.
> On Jul 22, 2015, at 3:45 PM, Carlos Santana <cs...@gmail.com> wrote:
>
> encourage contributions, I don't care what org
>
> I know git submodules are a pain, but might worth looking into them to make
> website a consolidation, and keeping the other repos clean for easy
> contributions
>
> On Tue, Jul 21, 2015 at 3:12 PM Brian LeRoux <b...@brian.io> wrote:
>
>> thumbs up! (idk what happened)
>>
>> On Tue, Jul 21, 2015 at 11:55 AM, Jesse <pu...@gmail.com> wrote:
>>
>>> Brian? was that a thumbs-up or a poo-poo?
>>> Not seeing your emoji ...
>>>
>>> I agree with Nikhil that we should optimize for contribution, and
>> probably
>>> stay within the apache org at github.
>>>
>>>
>>> My team is hiring!
>>> @purplecabbage
>>> risingj.com
>>>
>>> On Tue, Jul 21, 2015 at 10:53 AM, Nikhil Khandelwal <
>>> nikhilkh@microsoft.com>
>>> wrote:
>>>
>>>> 'Cordova' github org is good for committers, but it's unclear we have
>> the
>>>> right basis (CLAs etc.) for accepting contributions there.
>>>>
>>>> Even though Apache org does not provide us with some features like
>> labels
>>>> (and that might change soon), keeping it under that org might be a good
>>>> path forward.
>>>>
>>>> We should really optimize the structure to encourage contribution,
>>>> especially to our docs (as they often go stale and its easiest to have
>>> devs
>>>> contribute to). Cordova-docs repo is currently the place to do that.
>> I'm
>>>> concerned changing that will be a disruptive to contributions in the
>>> short
>>>> term. If we can do a transfer (github redirect) that might be good - I
>>> know
>>>> github supports that. Another alternative is to use the cordova-docs
>> repo
>>>> itself and add website content there.
>>>>
>>>> Thanks,
>>>> Nikhil
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Brian LeRoux [mailto:b@brian.io]
>>>> Sent: Tuesday, July 21, 2015 9:28 AM
>>>> To: <de...@cordova.apache.org>
>>>> Subject: Re: [DISCUSS] Website Repo
>>>>
>>>> On Tue, Jul 21, 2015 at 2:09 AM Dmitry Blotsky <dblotsky@microsoft.com
>>>
>>>> wrote:
>>>>
>>>>> Hey folks,
>>>>>
>>>>> In lieu of the changes coming to the docs and the website design
>>>>> proposed at the hangout, I’d like to consolidate our docs, blog, and
>>>>> website under one Git repo. Right now we have some code in several
>> Git
>>>>> repos (docs, blog posts), and some in the SVN repo (website itself).
>>>>> I’d like to move for one Git repo to contain them all, and to use the
>>>>> SVN only for deployment. For this, I’d like to move to create either
>>>>> github.com/cordova/cordova-website
>>>>> <http://github.com/cordova/cordova-website> or
>>>>> github.com/apache/cordova-website<
>> http://github.com/apache/cordova-web
>>>>> site
>>>>>> .
>>>>>
>>>>> What are your kind thoughts on this matter?
>>>>>
>>>>> Kindly,
>>>>> Dmitry
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>>>> For additional commands, e-mail: dev-help@cordova.apache.org
>>>>
>>>
>>
Re: [DISCUSS] Website Repo
Posted by Carlos Santana <cs...@gmail.com>.
encourage contributions, I don't care what org
I know git submodules are a pain, but might worth looking into them to make
website a consolidation, and keeping the other repos clean for easy
contributions
On Tue, Jul 21, 2015 at 3:12 PM Brian LeRoux <b...@brian.io> wrote:
> thumbs up! (idk what happened)
>
> On Tue, Jul 21, 2015 at 11:55 AM, Jesse <pu...@gmail.com> wrote:
>
> > Brian? was that a thumbs-up or a poo-poo?
> > Not seeing your emoji ...
> >
> > I agree with Nikhil that we should optimize for contribution, and
> probably
> > stay within the apache org at github.
> >
> >
> > My team is hiring!
> > @purplecabbage
> > risingj.com
> >
> > On Tue, Jul 21, 2015 at 10:53 AM, Nikhil Khandelwal <
> > nikhilkh@microsoft.com>
> > wrote:
> >
> > > 'Cordova' github org is good for committers, but it's unclear we have
> the
> > > right basis (CLAs etc.) for accepting contributions there.
> > >
> > > Even though Apache org does not provide us with some features like
> labels
> > > (and that might change soon), keeping it under that org might be a good
> > > path forward.
> > >
> > > We should really optimize the structure to encourage contribution,
> > > especially to our docs (as they often go stale and its easiest to have
> > devs
> > > contribute to). Cordova-docs repo is currently the place to do that.
> I'm
> > > concerned changing that will be a disruptive to contributions in the
> > short
> > > term. If we can do a transfer (github redirect) that might be good - I
> > know
> > > github supports that. Another alternative is to use the cordova-docs
> repo
> > > itself and add website content there.
> > >
> > > Thanks,
> > > Nikhil
> > >
> > >
> > > -----Original Message-----
> > > From: Brian LeRoux [mailto:b@brian.io]
> > > Sent: Tuesday, July 21, 2015 9:28 AM
> > > To: <de...@cordova.apache.org>
> > > Subject: Re: [DISCUSS] Website Repo
> > >
> > > On Tue, Jul 21, 2015 at 2:09 AM Dmitry Blotsky <dblotsky@microsoft.com
> >
> > > wrote:
> > >
> > > > Hey folks,
> > > >
> > > > In lieu of the changes coming to the docs and the website design
> > > > proposed at the hangout, I’d like to consolidate our docs, blog, and
> > > > website under one Git repo. Right now we have some code in several
> Git
> > > > repos (docs, blog posts), and some in the SVN repo (website itself).
> > > > I’d like to move for one Git repo to contain them all, and to use the
> > > > SVN only for deployment. For this, I’d like to move to create either
> > > > github.com/cordova/cordova-website
> > > > <http://github.com/cordova/cordova-website> or
> > > > github.com/apache/cordova-website<
> http://github.com/apache/cordova-web
> > > > site
> > > > >.
> > > >
> > > > What are your kind thoughts on this matter?
> > > >
> > > > Kindly,
> > > > Dmitry
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > For additional commands, e-mail: dev-help@cordova.apache.org
> > >
> >
>
Re: [DISCUSS] Website Repo
Posted by Brian LeRoux <b...@brian.io>.
thumbs up! (idk what happened)
On Tue, Jul 21, 2015 at 11:55 AM, Jesse <pu...@gmail.com> wrote:
> Brian? was that a thumbs-up or a poo-poo?
> Not seeing your emoji ...
>
> I agree with Nikhil that we should optimize for contribution, and probably
> stay within the apache org at github.
>
>
> My team is hiring!
> @purplecabbage
> risingj.com
>
> On Tue, Jul 21, 2015 at 10:53 AM, Nikhil Khandelwal <
> nikhilkh@microsoft.com>
> wrote:
>
> > 'Cordova' github org is good for committers, but it's unclear we have the
> > right basis (CLAs etc.) for accepting contributions there.
> >
> > Even though Apache org does not provide us with some features like labels
> > (and that might change soon), keeping it under that org might be a good
> > path forward.
> >
> > We should really optimize the structure to encourage contribution,
> > especially to our docs (as they often go stale and its easiest to have
> devs
> > contribute to). Cordova-docs repo is currently the place to do that. I'm
> > concerned changing that will be a disruptive to contributions in the
> short
> > term. If we can do a transfer (github redirect) that might be good - I
> know
> > github supports that. Another alternative is to use the cordova-docs repo
> > itself and add website content there.
> >
> > Thanks,
> > Nikhil
> >
> >
> > -----Original Message-----
> > From: Brian LeRoux [mailto:b@brian.io]
> > Sent: Tuesday, July 21, 2015 9:28 AM
> > To: <de...@cordova.apache.org>
> > Subject: Re: [DISCUSS] Website Repo
> >
> > On Tue, Jul 21, 2015 at 2:09 AM Dmitry Blotsky <db...@microsoft.com>
> > wrote:
> >
> > > Hey folks,
> > >
> > > In lieu of the changes coming to the docs and the website design
> > > proposed at the hangout, I’d like to consolidate our docs, blog, and
> > > website under one Git repo. Right now we have some code in several Git
> > > repos (docs, blog posts), and some in the SVN repo (website itself).
> > > I’d like to move for one Git repo to contain them all, and to use the
> > > SVN only for deployment. For this, I’d like to move to create either
> > > github.com/cordova/cordova-website
> > > <http://github.com/cordova/cordova-website> or
> > > github.com/apache/cordova-website<http://github.com/apache/cordova-web
> > > site
> > > >.
> > >
> > > What are your kind thoughts on this matter?
> > >
> > > Kindly,
> > > Dmitry
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
>
Re: [DISCUSS] Website Repo
Posted by Jesse <pu...@gmail.com>.
Brian? was that a thumbs-up or a poo-poo?
Not seeing your emoji ...
I agree with Nikhil that we should optimize for contribution, and probably
stay within the apache org at github.
My team is hiring!
@purplecabbage
risingj.com
On Tue, Jul 21, 2015 at 10:53 AM, Nikhil Khandelwal <ni...@microsoft.com>
wrote:
> 'Cordova' github org is good for committers, but it's unclear we have the
> right basis (CLAs etc.) for accepting contributions there.
>
> Even though Apache org does not provide us with some features like labels
> (and that might change soon), keeping it under that org might be a good
> path forward.
>
> We should really optimize the structure to encourage contribution,
> especially to our docs (as they often go stale and its easiest to have devs
> contribute to). Cordova-docs repo is currently the place to do that. I'm
> concerned changing that will be a disruptive to contributions in the short
> term. If we can do a transfer (github redirect) that might be good - I know
> github supports that. Another alternative is to use the cordova-docs repo
> itself and add website content there.
>
> Thanks,
> Nikhil
>
>
> -----Original Message-----
> From: Brian LeRoux [mailto:b@brian.io]
> Sent: Tuesday, July 21, 2015 9:28 AM
> To: <de...@cordova.apache.org>
> Subject: Re: [DISCUSS] Website Repo
>
> On Tue, Jul 21, 2015 at 2:09 AM Dmitry Blotsky <db...@microsoft.com>
> wrote:
>
> > Hey folks,
> >
> > In lieu of the changes coming to the docs and the website design
> > proposed at the hangout, I’d like to consolidate our docs, blog, and
> > website under one Git repo. Right now we have some code in several Git
> > repos (docs, blog posts), and some in the SVN repo (website itself).
> > I’d like to move for one Git repo to contain them all, and to use the
> > SVN only for deployment. For this, I’d like to move to create either
> > github.com/cordova/cordova-website
> > <http://github.com/cordova/cordova-website> or
> > github.com/apache/cordova-website<http://github.com/apache/cordova-web
> > site
> > >.
> >
> > What are your kind thoughts on this matter?
> >
> > Kindly,
> > Dmitry
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
RE: [DISCUSS] Website Repo
Posted by Nikhil Khandelwal <ni...@microsoft.com>.
'Cordova' github org is good for committers, but it's unclear we have the right basis (CLAs etc.) for accepting contributions there.
Even though Apache org does not provide us with some features like labels (and that might change soon), keeping it under that org might be a good path forward.
We should really optimize the structure to encourage contribution, especially to our docs (as they often go stale and its easiest to have devs contribute to). Cordova-docs repo is currently the place to do that. I'm concerned changing that will be a disruptive to contributions in the short term. If we can do a transfer (github redirect) that might be good - I know github supports that. Another alternative is to use the cordova-docs repo itself and add website content there.
Thanks,
Nikhil
-----Original Message-----
From: Brian LeRoux [mailto:b@brian.io]
Sent: Tuesday, July 21, 2015 9:28 AM
To: <de...@cordova.apache.org>
Subject: Re: [DISCUSS] Website Repo
On Tue, Jul 21, 2015 at 2:09 AM Dmitry Blotsky <db...@microsoft.com>
wrote:
> Hey folks,
>
> In lieu of the changes coming to the docs and the website design
> proposed at the hangout, I’d like to consolidate our docs, blog, and
> website under one Git repo. Right now we have some code in several Git
> repos (docs, blog posts), and some in the SVN repo (website itself).
> I’d like to move for one Git repo to contain them all, and to use the
> SVN only for deployment. For this, I’d like to move to create either
> github.com/cordova/cordova-website
> <http://github.com/cordova/cordova-website> or
> github.com/apache/cordova-website<http://github.com/apache/cordova-web
> site
> >.
>
> What are your kind thoughts on this matter?
>
> Kindly,
> Dmitry
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [DISCUSS] Website Repo
Posted by Brian LeRoux <b...@brian.io>.
On Tue, Jul 21, 2015 at 2:09 AM Dmitry Blotsky <db...@microsoft.com>
wrote:
> Hey folks,
>
> In lieu of the changes coming to the docs and the website design proposed
> at the hangout, I’d like to consolidate our docs, blog, and website under
> one Git repo. Right now we have some code in several Git repos (docs, blog
> posts), and some in the SVN repo (website itself). I’d like to move for one
> Git repo to contain them all, and to use the SVN only for deployment. For
> this, I’d like to move to create either github.com/cordova/cordova-website
> <http://github.com/cordova/cordova-website> or
> github.com/apache/cordova-website<http://github.com/apache/cordova-website
> >.
>
> What are your kind thoughts on this matter?
>
> Kindly,
> Dmitry
>