The primary issue for me is that my work with ESME is not front-burner; there are "other fish to fry" before it moves forward, even though I did a lot of earlier coding to begin the process of adding structured conversations to it. So, waiting for the ESME team to reassemble itself might not help.
Jack On Thu, Apr 18, 2013 at 6:52 AM, Richard Hirsch <[email protected]> wrote: > I wouldn't have a problem with ESME existing under another name on github. > > I just know that after a year of writing Apache board quarterly > reports - each one a copy of the last and reporting no activity, it is > time for a change. > > D. > > On Thu, Apr 18, 2013 at 3:44 PM, Bertrand Delacretaz > <[email protected]> wrote: >> On Thu, Apr 18, 2013 at 3:05 PM, Jack Park <[email protected]> wrote: >>> At some risk of social hari kari, would it make sense to fork the >>> project over to, say, Github and continue its development there >>> without the risk of being sent to the boneyard?... >> >> There's absolutely no problem with that except the name, and as we're >> seeing it's probably an easier way to continue with a smaller team. >> What would be bad is forking an existing community, but this community >> as almost non-existent now. >> >> The name issue is that the ESME trademark belongs to the Apache >> Software Foundation, so the forked project needs to use a different >> name. One such example is http://ibatis.apache.org/ which changed its >> name to MyBatis when it left the foundation. >> >> -Bertrand
