Patrick Ben Koetter
2018-10-09 20:48:20 UTC
Greetings,
first, and I really, really mean first before anything else can be said:
Thank you Mark! Thank you for all the work you put into amavis, for all
the hours of thinking and testing and thanks for fixing all the bugs over
the past years.
Now: I've been in contact offlist with a few people (including Mark),
discussing if and how we would want to maintain amavis in the future. At the
moment I'm ahead of these people, as some still have to check with their
companies or for other reasons if and how deeply they may get involved into
amavis.
As a quick measure we've decided to create infrastructure, open to the
community, to allow for open development and collaborative work.
== Development discussion
Those of you, who want to participate actively in amavis development
discussions, are invited to join the amavis-***@amavis.org mailing list.
Visit <https://lists.amavis.org/cgi-bin/mailman/listinfo/amavis-devel> to
subscribe.
== Coding, Documentation, Contributions
Those of you, who want to work on the code, are invited to get an account at
gitlab.com and join the amavis project at <https://gitlab.com/amavis/amavis>.
I took all amavis releases from Mark's collection and imported them in
historical order as branches (using a Perl script Mark had put together). At
the moment the repos master branch serves amavisd-new-2.11.1.
== Next Steps
So what are the next steps when you pick up the loose ends on a great project
that hasn't seen much attention recently?
These are the next steps that come to my mind:
- Fix known and blocking bugs and release a new version as soon as possible
- Form a group of people interested to contribute in amavis development (bug
fixing, documentation etc.)
- Create a list of issues (bugs, enhancements, suggestions etc.)
- Agree on certain project standards (workflow, coding, documentation etc.)
- Create a roadmap
- Get the work done
What is it you can do?
- File an issue/bug at <https://gitlab.com/amavis/amavis/issues>
- Tell what you would like to see improved in amavis
Looking forward to hear from all of you!
***@rick
first, and I really, really mean first before anything else can be said:
Thank you Mark! Thank you for all the work you put into amavis, for all
the hours of thinking and testing and thanks for fixing all the bugs over
the past years.
Now: I've been in contact offlist with a few people (including Mark),
discussing if and how we would want to maintain amavis in the future. At the
moment I'm ahead of these people, as some still have to check with their
companies or for other reasons if and how deeply they may get involved into
amavis.
As a quick measure we've decided to create infrastructure, open to the
community, to allow for open development and collaborative work.
== Development discussion
Those of you, who want to participate actively in amavis development
discussions, are invited to join the amavis-***@amavis.org mailing list.
Visit <https://lists.amavis.org/cgi-bin/mailman/listinfo/amavis-devel> to
subscribe.
== Coding, Documentation, Contributions
Those of you, who want to work on the code, are invited to get an account at
gitlab.com and join the amavis project at <https://gitlab.com/amavis/amavis>.
I took all amavis releases from Mark's collection and imported them in
historical order as branches (using a Perl script Mark had put together). At
the moment the repos master branch serves amavisd-new-2.11.1.
== Next Steps
So what are the next steps when you pick up the loose ends on a great project
that hasn't seen much attention recently?
These are the next steps that come to my mind:
- Fix known and blocking bugs and release a new version as soon as possible
- Form a group of people interested to contribute in amavis development (bug
fixing, documentation etc.)
- Create a list of issues (bugs, enhancements, suggestions etc.)
- Agree on certain project standards (workflow, coding, documentation etc.)
- Create a roadmap
- Get the work done
What is it you can do?
- File an issue/bug at <https://gitlab.com/amavis/amavis/issues>
- Tell what you would like to see improved in amavis
Looking forward to hear from all of you!
***@rick
--
[*] sys4 AG
https://sys4.de, +49 (89) 30 90 46 64
SchleiÃheimer StraÃe 26/MG,80333 MÃŒnchen
Sitz der Gesellschaft: MÃŒnchen, Amtsgericht MÃŒnchen: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief
Aufsichtsratsvorsitzender: Florian Kirstein
[*] sys4 AG
https://sys4.de, +49 (89) 30 90 46 64
SchleiÃheimer StraÃe 26/MG,80333 MÃŒnchen
Sitz der Gesellschaft: MÃŒnchen, Amtsgericht MÃŒnchen: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief
Aufsichtsratsvorsitzender: Florian Kirstein