ISPConfig Roadmap

[till]

I'am currently trying to make a roadmap for the next ISPConfig relaeses and like to hear your suggestions, comments and where you are currently working on. I will split the roadmap in 2 parts, one for the ISPConfig 2.2.x stable releases and one for the ISPConfig 2.3.x dev releases (trunk in SVN).

I think its time to get the current dev release to a point where we can make a new stable branch out of it.

Here are my ideas:

ISPConfig 2.2.x

Just bugfixing and support for new versions of the current supported linux distributions without adding new features

ISPConfig 2.3.x (Dev)

There are many nice new features in the dev branch already, but there was no new dev release for some time because the new script for writing the postfix and sendmail configuration is not finished yet. I'am currently working on it.

Here is a list of new features that I would like to see in the next 2.3.x releases or that are already implemented but not released in 2.3.1:

- Enable / Disable FTP for every user individualy (till, finished).
- Support for AWStats (jnsc, in progress).
- Support for mailman mailing lists (jnsc, in progress).
- Being able to select for which of the domains of a website a email address is created (till, Interface is finished, backend librarys are finished 60%). This is currently the main thing that has to be fixed to make a new dev release.

And many many improvements and bugfixes and translations from other developers, please look at the SVN log for a full list.

When you are currently working on new features, plesae post them.

My Ideas for new features and improvements:

- Selector for the type of apache rewrite rule ISPConfig uses for co-domains to create "real" subdomains where the URL does not change in the browser.
- Support for FreeBSD
- Improve the manuals and include the latest features. A "How to get started with ISPConfig" would be nice too.
- Record sorting and paging for all "inline lists" like co-domains, users and DNS-A, MX and cname records. If this is implemeted once, it will apply to all of these lists automatically.
- User prefix for usernames.
- Creating maildirs with maildirmake when a user is created instead of letting postfix do it. Then a list of additional mail folders might be defined.
- user cron-jobs
- webdav
- mod_mono and mod_python support
- Add a check routine to the installer that makes sure that the libxml2 librarys are installed.
- Translate all german comments in the code to english. In the early ISPConfig development, all developers where native german speakers and so there are many german comments in the code. This is a big problem now and I'am trying to translate them step by step to english, when I edit a file. It will be nice if german speaking developers might help me in translating comments to english when they are working on the files.

This are just my ideas. Please comment and post your priorities and ideas. If you are alreday working on some functions or like to implement a new feature, please let me know so we can coordinate our efforts.

I will try to make a official roadmap as result of this thread where we define our priorities for the next releases and get an overview who is implementing which feature. This will make it easier for new developers to get started with ISPConfig development.

[jnsc]

Thank's for this roadmap, it's full of good ideas for the next Major release. For my part, the AWStats installer has been merged into SVN, but I still have to test a full install from a SVN checkout.

For the Mailman feature, it is usable, but it still needs a lot of attention. Actually it's a patch against 2.2.9, it only works with postfix, and I only tested it on Debian. As I am just a human, it's also surely contains a lot of Bugs. I order to make it a stable feature it needs alot of testing.

For me the most interesting feautures of your list are (but this is just my point of view):

Originally Posted by till

- Creating maildirs with maildirmake when a user is created instead of letting postfix do it. Then a list of additional mail folders might be defined.
- user cron-jobs
- webdav

For the translation of comments as I speak german, I will try to help you whith this point.

Regard's
Jonas

[martinfst]

It this the awstats with static pages? Cause I really want the dropdown box to be able to select previous months / years.

That why I went with the "other" solution, though I know there no pkg of it.

[jnsc]

Yes the static version. But with a little hack I am sure you can add a frame with a drop down list for the static version :-)

[danf.1979]

I think ISPConfig interface is too dated. For example, several php scripts make intensive use of <font> tag or fixed width tables and cells, making css support of little use. I think tables should begin to desappear also from html templates, in favor of <div> tags. I think I can begun to work on the client part (is what matter most), but right now I have to finish a CMS project I'm developing from quite some time. I'll start, but it will be slow...

main.htm template should look something like this:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>{TITLE}</title>
<meta http-equiv="Content-Type" content="text/html; charset={CHARSET}">
<link href="{SERVERURL}/design/default/style.css" rel="stylesheet" type="text/css">
</head>

<body>
<div id="content">
<h1>{WINDOWTITLE}</h1>
{MAIN}
</div>
{WYSIWYG_LIB}
</body>
</html>

And its far more mantainable to do things this way....

Cheers.

[jnsc]

Of course, but that's really a lot of work. And as V3 of ISPConfig is already being developped, I don't know if it worth this effort. But as ussually this is only my point of view :-)

[TobiasTM]

I can write a "How to get started..." and improve the manual.

For the first time in german and later I will translate it into english. Other languages I don´t know ;-)

Just one question I have: Should the "How to get started..." comprehend a section with a HowTo Install or not ? (I think not - but if there someone have another opinion please let me know...)

[till]

I vote for "How to get started..." guide without included installation instructions

We should consider putting the new guide and the current manuals in SVN under version control. What do you think?

[martinfst]

What about a wiki setup for both the manuals?

[falko]

Wikis have a problem: they get spammed very fast because everyone can change content there. We once had a wiki on HowtoForge and had to close it because of spammers.