Sounds good, we do sometimes use reviewboard if you want us to have a quick
look. (Tho I'm cool w/ just publishing the changes and fixing anything new
when/if there is something new to fix.)


On Tue, Feb 25, 2014 at 9:53 AM, Mark Thomas <ma...@apache.org> wrote:

> On 25/02/2014 17:36, Brian LeRoux wrote:
> > Hey cool if you want to tackle this Mark. Everything you need to know
> > *should* be in the repo README.md [1] but if not just ping this thread
> and
> > we can help.
> >
> > [1] https://svn.apache.org/repos/asf/cordova/site/README.md
>
> Great. The README was all I needed and I have the fix ready to commit.
>
> I'm fairly sure that, due to my infra work, I have commit access to the
> Cordova website but I didn't want to step in and start committing stuff
> to the website without being invited.
>
> I've got a couple of other tasks I'm in the middle of but I should get
> to this later today.
>
> The change is a small one with lots of side-effects so I plan to commit
> the changes to a single file to test it and if that works I'll make the
> larger commit. If I do find I don't actually have the necessary commit
> karma I'll check back here.
>
> Mark
>
>
> >
> >
> > On Tue, Feb 25, 2014 at 1:06 AM, Mark Thomas <ma...@apache.org> wrote:
> >
> >> On 25/02/2014 01:20, Shazron wrote:
> >>> https://issues.apache.org/jira/browse/CB-4561
> >>> https://issues.apache.org/jira/browse/CB-5851
> >>
> >> I thought I'd take a look at this.
> >>
> >> In case it is helpful to others, the necessary dependencies to build the
> >> site on people.a.o should now be installed.
> >>
> >> I know what needs to be done to fix these issues - I just need to figure
> >> out how to do it.
> >>
> >> Mark
> >>
> >>
> >>>
> >>>
> >>> On Mon, Feb 24, 2014 at 5:00 PM, Brian LeRoux <b...@brian.io> wrote:
> >>>
> >>>> looks like a bad deploy OR we need to use /// instead of hardcoding
> >>>> protocol (not in a position to check this atm)
> >>>>
> >>>> http://cordova.apache.org === all good
> >>>> https://cordova.apache.org === yikes
> >>>>
> >>>
> >>
> >>
> >
>
>

Reply via email to