From: Jan-Wijbrand K. <jw...@n-...> - 2008-09-03 07:47:10
|
On Wed, 3 Sep 2008 09:31:07 +0200, XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX wrote: > On 9/3/08, Marcin Tustin <mm...@ze...> wrote: >> What does it need in the way of maintenance? > > Well, when I look at the bug/feature request lists, people have taken > the time to write patches for functionality they were missing (a C# > mode, for example). > > Next to that: software does not only need maintenance, but when > maintenance is done, it also needs releases. Some people think you do > not, but version numbers are a great way of doing your marketing. > (Yes, even OSS projects need to work on their marketing: do you have > any idea how many OSS editors there are - and hence need to compete > with?) > > So, this is about making sure users sending mails actually get their > messages answered; making sure fixes get released in publicly visible > releases; taking time to reward people who write fixes by applying > those fixes; etc. Exactly! > I've accepted maintenance, but am only interested in the Common Lisp > part. This means that anybody who wants to chip in to maintain J is > greatly welcome. Possibly, we can even split up the project since that > would do justice (in terms of visibility) to both components. Ofcourse > J depends on ABCL, but if we do the split correctly, it could still be > done in a non-intrusive way. I think splitting the code bases would indeed do justice to both projects *and* would make the scope of development and maintenance much more clear to the outside world. Being somehwat interested in *helping* maintaining J, I would not dare claim I can maintain J. My Java skills in developement and making releases is very very outdated. But I'd like to learn and help. Let's start out by sharing experiences on the mailinglist again! kind regards, jw |