Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 35A1F108AC for ; Tue, 11 Feb 2014 19:40:22 +0000 (UTC) Received: (qmail 90652 invoked by uid 500); 11 Feb 2014 19:40:20 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 90601 invoked by uid 500); 11 Feb 2014 19:40:20 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 90578 invoked by uid 99); 11 Feb 2014 19:40:19 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Feb 2014 19:40:19 +0000 Date: Tue, 11 Feb 2014 19:40:19 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: dev@couchdb.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (COUCHDB-2057) Fix broken internal links to mailing lists in webstite frontpage MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/COUCHDB-2057?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13= 898205#comment-13898205 ]=20 ASF subversion and git services commented on COUCHDB-2057: ---------------------------------------------------------- Commit 1567332 from [~andywenk] [ https://svn.apache.org/r1567332 ] COUCHDB-2057 Fix broken internal links to mailing lists in webstite frontpa= ge > Fix broken internal links to mailing lists in webstite frontpage > ---------------------------------------------------------------- > > Key: COUCHDB-2057 > URL: https://issues.apache.org/jira/browse/COUCHDB-2057 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues)=20 > Components: Website > Reporter: Vincent F=C3=A9rotin > Assignee: Andy Wenk > Priority: Minor > Attachments: fix-mailing-lists-refs.patch > > > Hi, CouchDB team. > The CouchDB website front page has some broken internal links to various = mailing-lists. For example, in footer quicklinks, link to above mailing-lis= ts section misses some ending "s". There are other links which are similar= y broken. > Here some patch to be applied on revision "1567146" to the Subversion rep= ository: https://svn.apache.org/repos/asf/couchdb/site/ using "svn diff" > {code} > Index: index.html > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- index.html=09(r=C3=A9vision 1567147) > +++ index.html=09(copie de travail) > @@ -113,11 +113,11 @@ > =20 >

CouchDB is an open source project. And that means everything, fro= m this website to the core of the database itself, has been contributed by = passionate, helpful individuals (such as yourself) who liked what they saw = and wanted to make something better of it. So if you like what you= see, and want to make something better of it, we’d like to = see your contributions. It doesn’t matter how familiar you are with C= ouchDB, or whether you know how to program Erlang. There are plenty of ways= to be helpful! Just ask! > =20 > -

Our community is our most valuable asset, and it could always do = with a bit more love and attention. One of the first things you should do i= s actually use CouchDB, and get to know it, read about it, evangelise it, a= nd engage with the wider community. Arrange a meetup, give a talk, publicize your use and let p= eople know how you use CouchDB in the wild. You could also get stuck in on the user mailing list or IRC channel, helping new users with their problems. Or c= ome join us on the developer mailing list and= lets us know how else you think you can help. There’s bound to be so= meone to point you in the right direction. > +

Our community is our most valuable asset, and it could always do = with a bit more love and attention. One of the first things you should do i= s actually use CouchDB, and get to know it, read about it, evangelise it, a= nd engage with the wider community. Arrange a meetup, give a talk, publicize your use and let p= eople know how you use CouchDB in the wild. You could also get stuck in on the user mailing list or IRC channel, helping new users with their problems.= Or come join us on the developer maili= ng list and lets us know how else you think you can help. There’s= bound to be someone to point you in the right direction. > =20 > -

Why don’t you check out JIRA and help us triage some of those issues? Or maybe you’d li= ke to help us keep the wiki= up-to-date? If you’re looking for something a little more technical,= you could help us with our documentation, QA, packaging, mobile, or releas= e efforts, perhaps? Just drop by on the developer= mailing list and let us know what you want to do. There's enough room = for any sort of contribution!

> +

Why don’t you check out JIRA and help us triage some of those issues? Or maybe you’d li= ke to help us keep the wiki= up-to-date? If you’re looking for something a little more technical,= you could help us with our documentation, QA, packaging, mobile, or releas= e efforts, perhaps? Just drop by on the developer mailing list and let us know what you want to do. There's en= ough room for any sort of contribution!

> =20 > -

Do you want to contribute code? Great! There's lots of stuff to w= ork on. Don't know Erlang? Join the Erlang list, and learn you some Erlang in a friendly environment! You can use JIRA t= o find easy, medium, and hard issues to work on. O= r, if you’d prefer, just open a new issue, and attach your patch. Don= 't want to use JIRA? Fork us = on GitHub and send a pull request. Why don't you check out the contributor workflo= w guide? > +

Do you want to contribute code? Great! There's lots of stuff to w= ork on. Don't know Erlang? Join the Erlang= list, and learn you some Erlang in a friendly environment! You can use= JIRA to find easy= , medium, and hard issues to work = on. Or, if you’d prefer, just open a new issue, and attach your patch= . Don't want to use JIRA? For= k us on GitHub and send a pull request. Why don't you check out the contributor wor= kflow guide? > =20 > > =20 > @@ -371,7 +371,7 @@ >

> {code} > Hope this help :-) > Best, > Vincent -- This message was sent by Atlassian JIRA (v6.1.5#6160)