Repository: Mailu/Mailu

Issue:
Discussion of 1.9 roadmap
As proposed in the last project meeting (#1582 (comment)), we are experimenting with a discussion driven model for determining the roadmap of the next release. This follows the existing practice of the succesful community run project Gitea (e.g go-gitea/gitea#14477).

During last meeting someone made the remark that with everything in the pipeline we already have sufficient work for a 1.9 release. I agree. We have this special situation due to the 1.8rc where we had a release candidate for over 7 months. This caused many PRs to be merged, but not included in 1.8. These are now waiting to be made available via a 1.9 release. This also caused a lot of already submitted PRs not be reviewed yet. We wanted to focus on getting 1.8 out of the door.

There are new PRs waiting for review for
- Updating the interface to AdminLTE3 #1800. This is not only a security update, but also adds a lot of functionality such as
  - a language selector
  - more modern look&feel of interface elements
  - filtering and column ordering for tables.
- Multiple PRs for increasing the overall security of mailu #1922, #1916, #1902. 
  - For these PRs we (I?) will also introduce a brand new security documentation page where you can find all documentation on what security measures are in place, how it works and how it can be tweaked. 
- updated polish translations #1751 and completely new Hebrew translation #1873.

We have already merged PRs on master for
- Completely new CLI configuration import/export which really exports/imports the complete mailu configuration database. With this it is possible to migrate the mailu config to another mailu instance. You can also use it to easily add new configuration (e.g. import users with specific settings) https://mailu.io/master/cli.html#config-export
- single sign on for webmail. Webmail uses the admin web interface for authenticating users
- various security related enhancements
- All other already merged PRs which were not included in 1.8. See all newsfragments for the details https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

IMHO All those features together are sufficient to release a new version.


I suggest we review all open PRs and then check what issues really need to be included as well for 1.9 and include these on the roadmap. Examples are:
- I think a good example is the new SSO #1929. When you are redirected to the login page, it does not show that the login is for the webmail. You have the feeling that you are redirected to the wrong page. See the demo site for an example (https://test.mailu.io/webmail/). Of course this is not production worthy. 
- Incorrect documentation
  - E.g.the documentation on translations #1869. We have no weblate instance anymore for web-based translations. The documentation must be updated as it is incorrect now. You can only do translations manually with a tool such as poedit and send a PR for getting your new translation files merged .
  - documentation on development environment for the admin interface #1577. The faulty documentation should be removed or directly updated with the correct steps.

For small non-critical issues/features I suggest we do not put it on the roadmap, but simply offer anyone the chance to pick these up and submit a PR if they want it included. 

What are your thoughts? Please share your feedback.
Regardless the above wall of text, feel free to mention any feature/issue you would like included in 1.9.





Discussion:
To keep track of things, I'd like to try using a github project for 1.9. I created a 1.9 project (https://github.com/Mailu/Mailu/projects/8). By simply using it we can determine if it is preferred over using a milestone. We could still use both at the same time. 
A milestone quickly shows what has not been finished yet. 
However I like that a project also shows if an issue has already been picked up by someone (moved from column to-do, to column in-progress)
Do we want to have the rate-limit changes part of 1.9 or are we okay with having another release where we have no effective rate-limiting?
I guess that depends on your availability since you generously offered to provide this functionality. It would be really neat. 
I think if we are honest, it will probably take 2-3 months before we release 1.9?
Since we are with only a couple of people everything goes slowly. I think 2-3 months is realistic. 
If you currently do not feel like it, I'd say let's do it after 1.9. 


Resolving patch:
diff --git a/core/admin/mailu/configuration.py b/core/admin/mailu/configuration.py
--- a/core/admin/mailu/configuration.py
+++ b/core/admin/mailu/configuration.py
@@ -27,7 +27,7 @@
     'SQLALCHEMY_TRACK_MODIFICATIONS': False,
     # Statistics management
     'INSTANCE_ID_PATH': '/data/instance',
-    'STATS_ENDPOINT': '18.{}.stats.mailu.io',
+    'STATS_ENDPOINT': '19.{}.stats.mailu.io',
     # Common configuration variables
     'SECRET_KEY': 'changeMe',
     'DOMAIN': 'mailu.io',
diff --git a/docs/conf.py b/docs/conf.py
--- a/docs/conf.py
+++ b/docs/conf.py
@@ -36,12 +36,10 @@
     'github_user': 'mailu',
     'github_repo': 'mailu',
     'github_version': version,
-    'stable_version': '1.8',
+    'stable_version': '1.9',
     'versions': [
-        ('1.5', '/1.5/'),
-        ('1.6', '/1.6/'),
-        ('1.7', '/1.7/'),
         ('1.8', '/1.8/'),
+        ('1.9', '/1.9/'),
         ('master', '/master/')
     ],
     'conf_py_path': '/docs/'


Test patch: