At 01:10 AM 9/29/00, Mills CP wrote:
>Why not release mj2 as it is now, sure, it may have an extensive wishlist,
>but why not have that ready for v2.5 of something.
I've already asked for a feature set freeze and release, haven't heard
an answer. I'm behind on writing the docs for the stuff that got done
last week, but the number of configuration options *IS* getting to the
point where you can do anything you want if only you can FIND the command.
>As I have said above, I have recently been looking for an open source
>product that I can help develop. I have quite a bit of experience (c. 5
>years) developing perl and cgi based web applications
>and some experience in a lot of other languages (c, c++, java, etc). Is Mj2
>still being written in Perl? If so, is there a list of things which need
>working on? Would you developers like some help?
Yes, yes, and yes. For example, there's no way to search the archives.
That's a bounded problem that no one is working on and which is arguably
something that needs to be in place before a full release. For another
example, I want a way to dump the ENTIRE database in the form of commands
to create it from scratch. This already exists for subscriptions and
personal option settings, but you can't dump the core database that
contains user passwords and full name with comment fields (the registry),
nor can you dump the aliases (for people posting from multiple addresses).
>I sure am willing to offer it. I do not have a lot of time to spare, but I
>would like to get involved if thats possible?
Need more? Review the archives from mj2-dev and you'll see all sorts
of stuff I've requested. Most of the big stuff has been done, but
as you've already read there are really only two code contributors
and their time is limited.
Hey, if anyone is worried that they can't work on object oriented Perl
(and that includes ME), I can always use help on the help docs. I've written
a Perl hack that automates some of the help file maintenance, but we
really need an index/table of contents to help people find the feature
they need. Having a newbie review the docs might pick up a bunch of
wording assumptions and/or gibberish that needs to be rewritten.
SRE
mailto:eckert@climber.org | http://www.climber.org/eckert/
Info on peak climbing email lists mailto:info@climber.org
Amateurs built the ark. Professionals built the Titanic.
Follow-Ups:
References:
|
|
