Hi Arun, happy news! We migrated to git, please send your PR to https://github.com/apache/couchdb-www
:) On Sun, Mar 15, 2015 at 11:40 AM, Arun Agarwal <[email protected]> wrote: > Thanks much Robert. > This should help. I will get into [email protected]. as well. > > regards.Arun. > > > > On Sunday, March 15, 2015 3:57 AM, Robert Kowalski <[email protected]> > wrote: > > > Hi Arun, > > thanks so much for your efforts! > > I would really like to point you in the right direction to fix it > right now, but we are currently migrating our website from svn to git > (it is the reason why you have not found a way to fix it) :( > > Give us 2-3 weeks and I will ping you again on this mailing-list, with > hopefully awesome news how you can contribute these fixes to CouchDB > :) > > P.S.: feel free to join our website group at [email protected] > which got just created :) > > Best, > Robert > > > > On Fri, Mar 13, 2015 at 7:46 PM, Arun Agarwal > <[email protected]> wrote: >> Hi Dev team. >> I wanted to start contributing to CouchDB with few of the small, easy to >> address issues. While searching for pointers, I came across few >> documentation typos which I thought worth sharing with you so that they can >> be fixed when we get time. >> A. on http://couchdb.apache.org/developer-preview/2.0/ >> we have two .... detailed instrucitons on how to get the prerequisits >> set up. B. on http://couchdb.apache.org/ 1. we should remove the join the >> erlang mailing list hyperlink to the same page: >> http://couchdb.apache.org/#erlang-mailing-list >> the list is discontinued in favor of dev list and so the reference >> won't make sense. 2. on my machine send a tweet link is shown as : >> http://couchdb.apache.org/twitter.com/CouchDB >> which won't work for end-users, I think this is happening because >> of missing http:// in the hyperlink, which causes it to think its relative >> to the same serving domain. >> I didn't find the above stuff checked-in to >> https://github.com/apache/couchdb-documentation repo, else I would have sent >> a review request. Let me know how can I help fixing these small problems in >> documentation and will be happy to help. >> Let me know if there is another way of notifying such issues and will take >> that path. >> Thanks much. >> regards.Arun Agarwal. >> > > >
