Mailing-List: contact dev-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
Subject: Re: Where's the code?
From: Rich Bowen <rbowen@rcbowen.com>
To: dev <dev@community.apache.org>
References: <084abe18-ea3e-233a-39fb-83a2442830e5@rcbowen.com>
Message-ID: <b7f58747-aca9-cd52-e4d0-d50e664e6649@rcbowen.com>
Date: Wed, 21 Jun 2017 16:43:51 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.1.0
MIME-Version: 1.0
In-Reply-To: <084abe18-ea3e-233a-39fb-83a2442830e5@rcbowen.com>
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary="TshuXTAc4Dfk6oCnAH7cOWqtUU62W2esI"
archived-at: Wed, 21 Jun 2017 14:44:06 -0000

--TshuXTAc4Dfk6oCnAH7cOWqtUU62W2esI
Content-Type: multipart/mixed; boundary="d8aphunOvQeaRj31I43tGNbUX5dwQaNoh";
 protected-headers="v1"
From: Rich Bowen <rbowen@rcbowen.com>
To: dev <dev@community.apache.org>
Message-ID: <b7f58747-aca9-cd52-e4d0-d50e664e6649@rcbowen.com>
Subject: Re: Where's the code?
References: <084abe18-ea3e-233a-39fb-83a2442830e5@rcbowen.com>
In-Reply-To: <084abe18-ea3e-233a-39fb-83a2442830e5@rcbowen.com>

--d8aphunOvQeaRj31I43tGNbUX5dwQaNoh
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

FYI:
https://docs.google.com/spreadsheets/d/1BxQzPVnzyAUD8NpCNB1MIwvlglU1G5lTX=
AvYGzkSlP0/edit#gid=3D0
if you want to play along.

On 06/21/2017 10:57 AM, Rich Bowen wrote:
> One of the "low hanging fruit" that I believe would increase
> contributions to our projects is telling people where the code is. It's=

> astonishingly hard to find out, for most of our projects.
>=20
> For the example of how to do it, see https://commons.apache.org/
>=20
> Note that in the navigation, it says SOURCE REPOSITORIES. The first lin=
k
> there - "General Information" - tells you exactly how to get the code,
> as well as providing links to browse the code.
>=20
> This should be part of the site nav for every project.
>=20
> This isn't mandated by our site policy, nor should it be, IMHO. I have
> no desire to create policy here. What I do want to do, however, is
> organize an effort to go through every one of our projects, find the
> relevant code locations, and submit patches to these projects to provid=
e
> this information on their websites.
>=20
> Obviously, I should start with my own project. Finding the code for
> httpd is possible, but not obvious. I'll go fix that. After that, I'm
> going to start tracking this information in a doc somewhere as I work
> through the other projects.
>=20
> Anyone interested in working on a cross-project effort like this with m=
e?
>=20


--=20
Rich Bowen - rbowen@rcbowen.com - @rbowen
http://apachecon.com/ - @apachecon


--d8aphunOvQeaRj31I43tGNbUX5dwQaNoh--

--TshuXTAc4Dfk6oCnAH7cOWqtUU62W2esI
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJZSoYnAAoJEHhwUUeLEqujnjMQAMTbFRgvUJNVQFmVfv3VLqRc
mAVQm04wMCGpdE3aew0Cte+tFU0Vy4dMEvM0mxdVRF07aTzRZTHGwiq2PUEnffHW
5BFJDBc9PoxFf83YHaYdeiStfo+NvDnlBFIIIIy/sF6hz6nrUP7zqGC6NOz2z5GS
mQd6/i70pl49iQo5K0bbS1W3c3OgumeLnp/j5y5yYG6TxVeLnHzxk6TZjS+VJAcm
Orfdcu/eVyPFikEqj2pWBPhqhkaCpfmekerUGwTfDpdPxvv7ESnylj8EuUwcw9Ap
TuItTIpuQ1+KTHESuvZyt3vWRWql6fMHqTMtWxrorTtdGoB9RKKhoYFrFENpCSgG
XwqVnMdnVSHF7O499KU5zIo5ycH19kMX4k51VMYE13baMXdNYodN3B1W+CJg/pLg
ZuIKvn90O0KMXWrzGxWODWWzXcKVLw064xUu1B6cTaXuoKeNBInrcWbDikDkaLj/
s/X89TiwlMzGdltVbhUbKUCqU1dD9S6ks8bPNKzgfcArgxqrdfhb3Wr9hZ6E5HMA
/Vh5j+2q9G6E40AH/nr3J9LVNhZKI3vaImWt+vWBNGZseC/uv6iXJ8EsNAId3ucO
r6rth1A1n7mHRrTm9GhaI7olZ6Z5Sq0agS43TVwoBaCMm9OWl0aOW2DUzHsV1iDK
TON+pUICuw90RRiDouxL
=uzEi
-----END PGP SIGNATURE-----

--TshuXTAc4Dfk6oCnAH7cOWqtUU62W2esI--