No subject


Sat Nov 15 01:15:06 PST 2014


probably be the protocols.  Expanding those, including perhaps adding
smaller recipes, will be important IMO.

An API / tools distinction like Qingpeng spoke of makes a lot of sense.
The protocols/recipes is a natural hub of a more tools focused community.
It is also a real(ish) world testbed and place to find interesting
problems/questions for folks more focused on the CS / software engineering.
The forum coordinating the nitty gritty work on the API level would
constitute another community hub, not entirely separate of course, but
different.

Anyways, it might make sense to make a formal distinction between
khmer-tools (scripts, protocols, ect.) and khmer-lib (API).

Just my relatively uninformed $0.02.

--001a1134f920c01c1b0507ebd07c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">From a rather outside POV, the entrance point to khmer for=
 most folks will probably be the protocols.=C2=A0 Expanding those, includin=
g perhaps adding smaller recipes, will be important IMO.<div><br></div><div=
>An API / tools distinction like Qingpeng spoke of makes a lot of sense.</d=
iv><div>The protocols/recipes is a natural hub of a more tools focused comm=
unity.=C2=A0 It is also a real(ish) world testbed and place to find interes=
ting problems/questions for folks more focused on the CS / software enginee=
ring.</div><div>The forum coordinating the nitty gritty work on the API lev=
el would constitute another community hub, not entirely separate of course,=
 but different.</div><div><br></div><div>Anyways, it might make sense to ma=
ke a formal distinction between khmer-tools (scripts, protocols, ect.) and =
khmer-lib (API).</div><div><br></div><div>Just my relatively uninformed $0.=
02.</div></div>

--001a1134f920c01c1b0507ebd07c--



More information about the khmer mailing list