On Mon, 13 May 2019 at 15:59, Rich Bowen wrote:
>
>
>
> On 5/13/19 10:03 AM, sebb wrote:
> > On Mon, 13 May 2019 at 14:48, Rich Bowen wrote:
> >>
> >>
> >>
> >> On 5/13/19 8:34 AM, Suresh Kumar Anaparti wrote:
> >>> Hi ApacheCo
Maybe there should be a blank or holding image that can be used when
the current event is over and the new image is not yet ready?
I think that would look better than a stale image.
On Tue, 27 Nov 2018 at 21:46, Rich Bowen wrote:
>
>
>
> On 11/26/18 3:04 PM, Tanya Schlusser wrote:
> > Hello,
> >
<rbo...@rcbowen.com> wrote:
> Yes please.
>
> On 07/31/2017 09:58 AM, sebb wrote:
>> Should there be an issue tracker for ApacheCon?
>>
>> This could be used to track website issues etc.
>>
>> Much easier than using a mailing list, especiall
Should there be an issue tracker for ApacheCon?
This could be used to track website issues etc.
Much easier than using a mailing list, especially for patches.
On 9 May 2017 at 23:30, Nick Burch <n...@apache.org> wrote:
> On Mon, 8 May 2017, sebb wrote:
>>>
>>> https://svn.apache.org/repos/infra/apachecon/archive.apachecon.com/ .
>>> It's
>>
>>
>> According to the site itself, the source is
On 8 May 2017 at 22:00, Nick Burch <n...@apache.org> wrote:
> On Mon, 8 May 2017, sebb wrote:
>>
>> The apachecon pages aren't fully set up for use over https:
>> Several images use hard-coded http: URLs.
>>
>> There are also some links to http://apache
The apachecon pages aren't fully set up for use over https:
Several images use hard-coded http: URLs.
There are also some links to http://apachecon.com/ URLs which ought to
be host-relative URLs.
I tried to fix these, but I don't have karma.
Is there a recommended way to provide patches?