On 2023-08-16 11:47, sebb wrote:
On Wed, 16 Aug 2023 at 10:19, Daniel Gruno <humbed...@apache.org> wrote:
On 2023-08-16 10:46, Roy Lenferink wrote:
Op wo 16 aug 2023 om 07:19 schreef Daniel Gruno <humbed...@apache.org>:
On 2023-08-15 22:37, sebb wrote:
On Tue, 15 Aug 2023 at 18:55, Brian Proffitt <b...@apache.org> wrote:
All:
ASF’s flagship event, Community Over Code, is happening October 7-10
in Halifax, Nova Scotia (formerly called ApacheCon).
I would like to ask all projects to add the logo and event URL to your
project website to help the ASF promote the event - and thank you to
projects who have already done this! Or, if you'd like, promote the
event with the logos on your project's social media channels.
Logos:
https://apache.org/foundation/press/kit/#eventlogo
Event URL:
https://communityovercode.org/
Thank you!
BKP
There is already a standard way to do this, as is done by:
https://jmeter.apache.org/
https://commons.apache.org/
https://hc.apache.org/
and probably others that use Maven to build their sites.
They include a link to the event page:
https://www.apache.org/events/current-event.html
with an image such as
https://www.apache.org/events/current-event-125x125.png
There is even a newer way, https://www.apachecon.com/event-images/ which
most project sites use by now, and which already features the community
over code logo as the current event.
Whimsy has a check for ^https?://.*apache.org/events/current-event which
checks
against the 'current-event' image/link:
https://whimsy.apache.org/site/check/events
(also part of the site-scan overview: https://whimsy.apache.org/site/ )
It seems that 104 projects link to the 'current-event' image/link.
I remember that the current-event image previously was also used for the
Apache Roadshows, so not only ApacheCon.
I think this is more of a naming issue than anything, and I believe the
conferences team is aware that they need to work towards a
wider-encompassing name here.
Having a look at the project list (I used the Whimsy list): of the first 10
projects
6 use the current-event image/link, 1 also has the Community over code
image (Accumulo)
and 1 contains a direct link to apachecon.com without an image (AGE).
Checking the community.a.o website, even there the current-event image/link
is used.
So to me it seems that not a lot of websites use apachecon.com/event-images/
and it
would be simpler to update the current-event images.
In the short term, I would agree. In the longer term, I would hope that
the recommendations from the conferences team (which is to use the
event-images snippet) would be followed. The current-event image is
quite limited in that it's a single image of a fixed size, so it may not
work for a specific web site theme, and it will only ever be usable for
a single event at a time. The event-images snippet was made to address
these issues by supporting both dark and light themes as well as
multiple events occurring at the same time.
Sites which use the admittedly limited images provided by the
old-style 'current-event' solution will have allowed for this.
Though of course, more sizes could be provided. Also the HTML could
include links to multiple events.
So I don't see those as critical issues.
No one is saying these issues are critical, but they _are_ issues
nonetheless.
Projects should not be forced to change unnecessarily.
No one is saying projects should be forced, but I am _hoping_ that
projects opt for the more configurable option.
Of course if they wish to use the replacement solution they can do so.
And can be encouraged to do so as part of any site redesign.
Note that the new solution uses Javascript.
There is no fallback for browsers that don't support Javascript.
This may be a problem for some assistive readers.
I don't believe there is any issue at all for assistive readers here.
The produced link and image is static once added to the DOM, and has
both alt and title elements to help out. If the content were to change
based on user events, sure, but for static additions like this, the
readers should not have any problem (assuming they were built/updated
within the last decade or so).
Sebb
The idea behind this was to avoid having to change loads of websites
before and after every event.
Instead, the event organisers can change the page content (or add a
redirect) and the various sized images accordingly.
By the way, the SVG and PNG versions of the logo look very different -
is that intentional?
Brian Proffitt
VP, Marketing & Publicity
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
