[
https://issues.apache.org/jira/browse/WICKET-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14247413#comment-14247413
]
Martijn Dashorst commented on WICKET-3341:
------------------------------------------
Regarding the github banner: the discussion on board@ has subsided and there
are varying opinions, some stated they wouldn't mind, others would mind. Which
doesn't mean it is a free for all.
Re-reading the relevant section from our marks policy/guidelines
(http://www.apache.org/foundation/marks/linking#projectthanks) tells me that we
should not link to github directly from all our pages (including the front
page). The guidelines specifically state:
> Project Thanks Pages / Listings:
> [...]
> * Should not be on the project's home page.
And
> PMCs may choose to provide relevant listings of other useful
> websites within their larger ecosystem, as a service to the
> project's users. Such listings may include factual links to outside
> organizations offering support, training, hosting, or other similar
> services related to that Apache project.
>
> [...]
> * Should not be on the project homepage, only on a secondary
> page on the project website. Placing prominent links to third party
> services or products on the homepage of a project is often seen
> by new users as an advertisement, and an implicit endorsement
> of that service or product by Apache, which is probably not what
> we intend.
So this is the policy.
In my personal opinion, major linkage to github on our homepage is telling
folks "Hey we are not here at Apache, but we are over there! Don't join us
at Apache, but do a drive-by at github. YOLO".
If we were to have a banner (note the **if**) it should link to our contribute
page where we lay down the list of ways someone can contribute:
- patch through jira/mailinglist
- PR at github
- ... etc
The banner could say "Contribute to Wicket", "Join Wicket", or something
else catchy. That said, I think such a banner would not be beneficial to our
website nor our community.
> New design for wicket site
> --------------------------
>
> Key: WICKET-3341
> URL: https://issues.apache.org/jira/browse/WICKET-3341
> Project: Wicket
> Issue Type: Improvement
> Components: site
> Reporter: Martijn Dashorst
> Attachments: ASF.LICENSE.NOT.GRANTED--Alternative design.jpg,
> Keynote001.png, KeynoteScreenSnapz001.png, KeynoteScreenSnapz002.png,
> KeynoteScreenSnapz003.png, KeynoteScreenSnapz004.png,
> KeynoteScreenSnapz005.png, logo.wicket.ai, logo.wicket.jpg,
> wicket-flat-new-top.002.png, wicket-flat-new-top.003.png,
> wicket-flat-new-top.004.png, wicket-flat-new-top.005.png,
> wicket-flat.001.png, wicket-logo-big.png, wicket-logo.svg
>
>
> Our current site design has been with us for quite a while. It looked fresh
> in the 1980s, but now it has gone stale.
> This is a proposal for a new, fresh design of the home page and sub pages.
> The home page will feature a prominent download link, a list of feature
> descriptions, screenshots of sites powered by Wicket, official blog items and
> Buzz by our users.
> The screenshots of wicket powered websites will link to short descriptions of
> the sites under /meet/poweredby. Links to the websites will of course have
> nofollow
> Other pages will feature a menu on the right side of the page providing
> direct links to content.
> Attached are a couple of screen shots of how the site might look like.
> Screen 005 is an alternative of the home page without the list of features,
> but including the introduction to wicket article.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
