You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by rc...@apache.org on 2020/08/25 10:11:53 UTC
[james-project] branch master updated (9b0d56c -> 38de32e)
This is an automated email from the ASF dual-hosted git repository.
rcordier pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/james-project.git.
from 9b0d56c [Refactoring] Fix issues in DistributedMailboxSetMethodTest
new e135587 JAMES-3187 Community documentation page contribution
new f7ee31a JAMES-3187 ASF compliance community documentation nav section
new b9729a8 JAMES-3187 Support subsection of the community documentation
new 11da66c JAMES-3187 Mailing lists subsection of the community documentation
new 8d4beb5 JAMES-3187 Guidelines subsection of the community documentation
new 0b195a9 JAMES-3187 Contributing subsection of the community new documentation
new ad774f7 JAMES-3187 Update mailing lists
new 38de32e JAMES-3187 Update mailing-lists.adoc
The 8 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../modules/community}/images/linagora.png | Bin
docs/modules/community/nav.adoc | 13 ++
docs/modules/community/pages/contributing.adoc | 185 +++++++++++++++++++++
docs/modules/community/pages/download.adoc | 4 +
docs/modules/community/pages/guidelines.adoc | 140 ++++++++++++++++
docs/modules/community/pages/index.adoc | 39 ++++-
docs/modules/community/pages/mailing-lists.adoc | 162 ++++++++++++++++++
docs/modules/community/pages/support.adoc | 16 ++
8 files changed, 558 insertions(+), 1 deletion(-)
copy {src/site/resources => docs/modules/community}/images/linagora.png (100%)
create mode 100644 docs/modules/community/pages/contributing.adoc
create mode 100644 docs/modules/community/pages/download.adoc
create mode 100644 docs/modules/community/pages/guidelines.adoc
create mode 100644 docs/modules/community/pages/mailing-lists.adoc
create mode 100644 docs/modules/community/pages/support.adoc
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[james-project] 02/08: JAMES-3187 ASF compliance community
documentation nav section
Posted by rc...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
rcordier pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/james-project.git
commit f7ee31af4885d1ed611fb07ceaf82b2d8dda61d1
Author: Rene Cordier <rc...@linagora.com>
AuthorDate: Tue Aug 11 15:48:41 2020 +0700
JAMES-3187 ASF compliance community documentation nav section
---
docs/modules/community/nav.adoc | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/docs/modules/community/nav.adoc b/docs/modules/community/nav.adoc
index 5b3d99d..993ebd7 100644
--- a/docs/modules/community/nav.adoc
+++ b/docs/modules/community/nav.adoc
@@ -3,4 +3,12 @@
** xref:contributing.adoc[]
** xref:guidelines.adoc[]
** xref:download.adoc[]
-** xref:support.adoc[]
\ No newline at end of file
+** xref:support.adoc[]
+** Apache Software Foundation
+*** https://www.apache.org/[ASF]
+*** https://www.apache.org/foundation/getinvolved.html[Get involved]
+*** https://www.apache.org/foundation/faq.html[FAQ]
+*** https://www.apache.org/licenses/[Licenses]
+*** https://www.apache.org/security/[Security]
+*** https://www.apache.org/foundation/sponsorship.html[Sponsorship]
+*** https://www.apache.org/foundation/thanks.html[Thanks]
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[james-project] 05/08: JAMES-3187 Guidelines subsection of the
community documentation
Posted by rc...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
rcordier pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/james-project.git
commit 8d4beb5bb71ced9691b1eb5b564ff5e6785b9445
Author: Rene Cordier <rc...@linagora.com>
AuthorDate: Wed Aug 19 17:08:31 2020 +0700
JAMES-3187 Guidelines subsection of the community documentation
---
docs/modules/community/pages/guidelines.adoc | 137 ++++++++++++++++++++++++++-
1 file changed, 136 insertions(+), 1 deletion(-)
diff --git a/docs/modules/community/pages/guidelines.adoc b/docs/modules/community/pages/guidelines.adoc
index 5590057..e07f1a7 100644
--- a/docs/modules/community/pages/guidelines.adoc
+++ b/docs/modules/community/pages/guidelines.adoc
@@ -1,4 +1,139 @@
= Apache James Project guidelines
:navtitle: Guidelines
-(TODO)
+This document defines the guidelines for the Apache James Project. It includes definitions of how conflict is being
+resolved by voting and who is able to vote.
+
+The objective here is to avoid unnecessary conflicts over changes and continue to produce a quality system in a timely
+manner. Not all conflict can be avoided, but at least we can agree on the procedures for conflicts to be resolved.
+
+== People, Places, and Things
+
+=== Apache James Project Management Committee
+
+The group of volunteers who are responsible for managing the Apache James Project. This includes deciding what is
+distributed as products of the Apache James Project, maintaining the Project's shared resources, speaking on behalf of
+the Project, resolving license disputes regarding Apache James products, nominating new PMC members or committers,
+and establishing these guidelines.
+
+Membership in the Apache James PMC is by invitation only and must be approved by consensus of the active Apache James
+PMC members. A PMC member is considered inactive by their own declaration or by not contributing in any form to the
+project for over six months. An inactive member can become active again by reversing whichever condition made them
+inactive (i.e., by reversing their earlier declaration or by once again contributing toward the project's work).
+Membership can be revoked by a unanimous vote of all the active PMC members other than the member in question.
+
+=== Apache James Committers
+
+The group of volunteers who are responsible for the technical aspects of the Apache James Project. This group has write
+access to the appropriate source repositories and these volunteers may cast non-binding votes on any technical discussion.
+
+Membership as a Committer is by invitation only and must be approved by consensus of the active Apache James PMC members.
+A Committer is considered inactive by their own declaration or by not contributing in any form to the project for over
+six months. An inactive member can become active again by reversing whichever condition made them inactive (i.e., by
+reversing their earlier declaration or by once again contributing toward the project's work). Membership can be revoked
+by a unanimous vote of all the active PMC members (except the member in question if they are a PMC member).
+
+=== Mailing list
+
+The Apache committers' primary mailing list for discussion of issues and changes related to the project
+(xref:mailing-lists.adoc#_server_developer_list[server-dev@james.apache.org]). Subscription to the list is open, but
+only subscribers can post directly to the list.
+
+=== Private list
+
+The Apache James Project's private mailing list for discussion of issues that are inappropriate for public discussion,
+such as legal, personal, or security issues prior to a published fix. Subscription to the list is only opened to Apache
+James PMC members and Apache Software Foundation Members.
+
+=== GIT
+
+All of the Apache James products are maintained in shared information repositories using GIT on git-wip-us.apache.org.
+The Apache committers have write access to these repositories; everyone has read access via anonymous GIT.
+
+== Voting
+
+Any of the Apache James Committers may vote on any issue or action item. However, the only binding votes are those cast
+by active members of the Apache James PMC; if the vote is about a change to source code or documentation, the primary
+author of what is being changed may also cast a binding vote on that issue. All other votes are non-binding. All
+committers are encouraged to participate in decisions, but the decision itself is made by those who have been long-time
+contributors to the project. In other words, the Apache Project is a minimum-threshold meritocracy.
+
+The act of voting carries certain obligations -- voting members are not only stating their opinion, they are agreeing
+to help do the work of the Apache Project. Since we are all volunteers, members often become inactive for periods of
+time in order to take care of their "real jobs" or devote more time to other projects. It is therefore unlikely that the
+entire group membership will vote on every issue. To account for this, all voting decisions are based on a minimum quorum.
+
+Each vote can be made in one of three flavors:
+
+*+1*
+Yes, agree, or the action should be performed. On some issues, this vote is only binding if the voter has tested the
+action on their own system(s).
+
+*+-0*
+Abstain, no opinion, or I am happy to let the other group members decide this issue. An abstention may have detrimental
+effects if too many people abstain.
+
+*-1*
+No. On issues where consensus is required, this vote counts as a veto. All vetos must include an explanation of why the
+veto is appropriate. A veto with no explanation is void. No veto can be overruled. If you disagree with the veto, you
+should lobby the person who casts the veto. Voters intending to veto an action item should make their opinions known to
+the group immediately, so that the problem can be remedied as early as possible.
+
+An action item requiring consensus approval must receive at least 3 binding +1 votes and no vetos. An action item
+requiring majority approval must receive at least 3 binding +1 votes and more +1 votes than -1 votes (i.e., a majority
+with a minimum quorum of three positive votes). All other action items are considered to have lazy approval until
+someone votes -1, after which point they are decided by either consensus or a majority vote, depending upon the type
+of action item.
+
+All votes must be either sent to the mailing list for that action item.
+
+Votes are to remain open for 72 hours after which the developer who put forth the vote should tabulate the result and
+send this to the mailing list. A developer should be sensitive to holidays that could dampen participation in the vote.
+
+== Types of Action Items
+
+=== Long Term Plans
+
+Long term plans are simply announcements that group members are working on particular issues related to the Apache
+software. These are not voted on, but group members who do not agree with a particular plan, or think an alternate plan
+would be better, are obligated to inform the group of their feelings. In general, it is always better to hear about
+alternate plans prior to spending time on less adequate solutions.
+
+=== Short Term Plans
+
+Short term plans are announcements that a developer is working on a particular set of documentation or code files, with
+the implication that other committers should avoid them or try to coordinate their changes. This is a good way to
+proactively avoid conflict and possible duplication of work.
+
+=== Release Plan
+
+A release plan is used to keep all the committers aware of when a release is desired, who will be the release manager,
+when the repository will be frozen in order to create the release, and assorted other trivia to keep us from tripping
+over ourselves during the final moments. Lazy majority decides each issue in the release plan.
+
+=== Release Testing
+
+After a new release is built, colloquially termed a tarball, it must be tested before being released to the public.
+Majority approval is required before the tarball can be publically released.
+
+=== Showstoppers
+
+Showstoppers are issues that require a fix be in place before the next public release.
+
+=== Product Changes
+
+Changes to the Apache James products, including code and documentation, will appear as action items under several
+categories corresponding to the change status:
+
+* *Concept/Plan*
+An idea or plan for a change. These are represented as ADRs (Architectural Decision Records), stored under the `src/adr`
+folder. Votes are being requested early so as to uncover conflicts before too much work is done.
+
+* *Proposed Patch*
+A specific set of changes to the current product in the form of input to the patch command (a diff output).
+
+* *Committed Change*
+A one-line summary of a change that has been committed to the repository since the last public release.
+
+All product changes to the currently active repository are subject to lazy consensus. All product changes to a
+prior-branch (old version) repository require consensus before the change is committed.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[james-project] 08/08: JAMES-3187 Update mailing-lists.adoc
Posted by rc...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
rcordier pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/james-project.git
commit 38de32ed500d355dbc730f30929ca3a40c980d16
Author: Eugen Stan <eu...@ieugen.ro>
AuthorDate: Thu Aug 20 09:30:33 2020 +0300
JAMES-3187 Update mailing-lists.adoc
Added link to web archive
Replaced mail-archive with Apache lists.apache.org service.
---
docs/modules/community/pages/mailing-lists.adoc | 18 +++++++++++++-----
1 file changed, 13 insertions(+), 5 deletions(-)
diff --git a/docs/modules/community/pages/mailing-lists.adoc b/docs/modules/community/pages/mailing-lists.adoc
index 7ebcd89..73aeed7 100644
--- a/docs/modules/community/pages/mailing-lists.adoc
+++ b/docs/modules/community/pages/mailing-lists.adoc
@@ -4,12 +4,20 @@ Please read the <<_guidelines>> below before subscribing to our lists and join o
== James mailing lists
+Most James mailing lists are open and also archived and available online.
+You can read them even if you are not subscribed.
+You can post only if you are subscribed.
+
+=== Mailing list archives and web browsing
+
+You can browse the mailing list archives online using the https://lists.apache.org/list.html?james.apache.org[Pony Mail] instance.
+
=== Server user list
*Low traffic*
mailto:server-user-subscribe@james.apache.org[Subscribe]
mailto:server-user-unsubscribe@james.apache.org[Unsubscribe]
-http://www.mail-archive.com/server-user@james.apache.org[Archive]
+https://lists.apache.org/list.html?server-user@james.apache.org[Archive]
This is the list where users of the Apache James (Server) meet and discuss issues. Developers are also expected to be
subscribed to this list to offer support to users of Apache James (Server).
@@ -19,7 +27,7 @@ subscribed to this list to offer support to users of Apache James (Server).
*Medium traffic*
mailto:server-dev-subscribe@james.apache.org[Subscribe]
mailto:server-dev-unsubscribe@james.apache.org[Unsubscribe]
-http://www.mail-archive.com/server-dev@james.apache.org[Archive]
+https://lists.apache.org/list.html?server-dev@james.apache.org[Archive]
This is the list where participating developers of the Apache James Project meet and discuss issues, code changes/additions,
etc. Do not send mail to this list with usage questions or configuration problems -- that's what server-user@james is for.
@@ -29,7 +37,7 @@ etc. Do not send mail to this list with usage questions or configuration problem
*Medium traffic*
mailto:mime4j-dev-subscribe@james.apache.org[Subscribe]
mailto:mime4j-dev-unsubscribe@james.apache.org[Unsubscribe]
-http://mail-archives.apache.org/mod_mbox/james-mime4j-dev[Archive]
+https://lists.apache.org/list.html?mime4j-dev@james.apache.org[Archive]
Discussions on the http://james.apache.org/mime4j[Mime4j] parser library.
@@ -38,7 +46,7 @@ Discussions on the http://james.apache.org/mime4j[Mime4j] parser library.
*Low traffic*
mailto:general-subscribe@james.apache.org[Subscribe]
mailto:general-unsubscribe@james.apache.org[Unsubscribe]
-http://www.mail-archive.com/general@james.apache.org[Archive]
+https://lists.apache.org/list.html?general@james.apache.org[Archive]
This is the list for general discussions related to the running of the project, it is the public list of the
James project management committee (PMC) and is a public list opened to all. Do not send mail to this list with James
@@ -49,7 +57,7 @@ software problems -- that's what server-user@james is for.
*High traffic*
mailto:notifications-subscribe@james.apache.org[Subscribe]
mailto:notifications-unsubscribe@james.apache.org[Unsubscribe]
-http://www.mail-archive.com/notifications@james.apache.org[Archive]
+https://lists.apache.org/list.html?notifications@james.apache.org[Archive]
Subscribers to this list get notices of each and every code change, build results, testing notices, etc. This list is
not for asking help, raising issues or starting discussions on the james product -- other mailing lists are specifically
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[james-project] 07/08: JAMES-3187 Update mailing lists
Posted by rc...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
rcordier pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/james-project.git
commit ad774f73ef8b3e471c8c0753835a4ac48b23c299
Author: Rene Cordier <rc...@linagora.com>
AuthorDate: Mon Aug 24 11:34:50 2020 +0700
JAMES-3187 Update mailing lists
Add:
* notifications@james.apache.org
Remove:
* site-dev@james.apache.org
* mailet-api@james.apache.org
---
docs/modules/community/pages/mailing-lists.adoc | 32 ++++++++-----------------
1 file changed, 10 insertions(+), 22 deletions(-)
diff --git a/docs/modules/community/pages/mailing-lists.adoc b/docs/modules/community/pages/mailing-lists.adoc
index 68dedf1..7ebcd89 100644
--- a/docs/modules/community/pages/mailing-lists.adoc
+++ b/docs/modules/community/pages/mailing-lists.adoc
@@ -16,14 +16,13 @@ subscribed to this list to offer support to users of Apache James (Server).
=== Server developer list
-*High traffic*
+*Medium traffic*
mailto:server-dev-subscribe@james.apache.org[Subscribe]
mailto:server-dev-unsubscribe@james.apache.org[Unsubscribe]
http://www.mail-archive.com/server-dev@james.apache.org[Archive]
This is the list where participating developers of the Apache James Project meet and discuss issues, code changes/additions,
-etc. Subscribers to this list get notices of each and every code change, build results, testing notices, etc. Do not
-send mail to this list with usage questions or configuration problems -- that's what server-user@james is for.
+etc. Do not send mail to this list with usage questions or configuration problems -- that's what server-user@james is for.
=== Mime4j
@@ -34,17 +33,6 @@ http://mail-archives.apache.org/mod_mbox/james-mime4j-dev[Archive]
Discussions on the http://james.apache.org/mime4j[Mime4j] parser library.
-=== Site developer list
-
-*Low traffic*
-mailto:site-dev-subscribe@james.apache.org[Subscribe]
-mailto:site-dev-unsubscribe@james.apache.org[Unsubscribe]
-http://www.mail-archive.com/site-dev@james.apache.org[Archive]
-
-This is the list where participating developers of the Apache James project discuss changes/additions to the James
-websites etc. Subscribers to this list get notifications of every commit of the website resources. Do not send mail to
-this list with James software problems -- that's what server-user@james is for.
-
=== James general list
*Low traffic*
@@ -56,16 +44,16 @@ This is the list for general discussions related to the running of the project,
James project management committee (PMC) and is a public list opened to all. Do not send mail to this list with James
software problems -- that's what server-user@james is for.
-=== Mailet API list
+=== Notifications mailing list
-*Low traffic*
-mailto:mailet-api-subscribe@james.apache.org[Subscribe]
-mailto:mailet-api-unsubscribe@james.apache.org[Unsubscribe]
-https://mail-archives.apache.org/mod_mbox/james-mailet-api[Archive]
+*High traffic*
+mailto:notifications-subscribe@james.apache.org[Subscribe]
+mailto:notifications-unsubscribe@james.apache.org[Unsubscribe]
+http://www.mail-archive.com/notifications@james.apache.org[Archive]
-This is the public list for the Mailet API subproject, discussing all http://james.apache.org/mailet/index.html[Mailet API]
-design and implementation related topics. Questions about using Mailets and their configuration should be addressed
-to the server-user list.
+Subscribers to this list get notices of each and every code change, build results, testing notices, etc. This list is
+not for asking help, raising issues or starting discussions on the james product -- other mailing lists are specifically
+dedicated to that already.
== How to unsubscribe your old email address
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[james-project] 01/08: JAMES-3187 Community documentation page
contribution
Posted by rc...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
rcordier pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/james-project.git
commit e1355873d38984023a354b88e50ec6c34ee6e916
Author: Rene Cordier <rc...@linagora.com>
AuthorDate: Tue Aug 11 15:02:14 2020 +0700
JAMES-3187 Community documentation page contribution
---
docs/modules/community/nav.adoc | 5 ++++
docs/modules/community/pages/contributing.adoc | 3 ++
docs/modules/community/pages/download.adoc | 4 +++
docs/modules/community/pages/guidelines.adoc | 4 +++
docs/modules/community/pages/index.adoc | 39 ++++++++++++++++++++++++-
docs/modules/community/pages/mailing-lists.adoc | 3 ++
docs/modules/community/pages/support.adoc | 3 ++
7 files changed, 60 insertions(+), 1 deletion(-)
diff --git a/docs/modules/community/nav.adoc b/docs/modules/community/nav.adoc
index 31f850e..5b3d99d 100644
--- a/docs/modules/community/nav.adoc
+++ b/docs/modules/community/nav.adoc
@@ -1 +1,6 @@
* xref:index.adoc[]
+** xref:mailing-lists.adoc[]
+** xref:contributing.adoc[]
+** xref:guidelines.adoc[]
+** xref:download.adoc[]
+** xref:support.adoc[]
\ No newline at end of file
diff --git a/docs/modules/community/pages/contributing.adoc b/docs/modules/community/pages/contributing.adoc
new file mode 100644
index 0000000..463288d
--- /dev/null
+++ b/docs/modules/community/pages/contributing.adoc
@@ -0,0 +1,3 @@
+= Contributing
+
+(TODO)
diff --git a/docs/modules/community/pages/download.adoc b/docs/modules/community/pages/download.adoc
new file mode 100644
index 0000000..61300ac
--- /dev/null
+++ b/docs/modules/community/pages/download.adoc
@@ -0,0 +1,4 @@
+= Download Apache James releases
+:navtitle: Download releases
+
+(TODO)
diff --git a/docs/modules/community/pages/guidelines.adoc b/docs/modules/community/pages/guidelines.adoc
new file mode 100644
index 0000000..5590057
--- /dev/null
+++ b/docs/modules/community/pages/guidelines.adoc
@@ -0,0 +1,4 @@
+= Apache James Project guidelines
+:navtitle: Guidelines
+
+(TODO)
diff --git a/docs/modules/community/pages/index.adoc b/docs/modules/community/pages/index.adoc
index 5cf5498..60dcd30 100644
--- a/docs/modules/community/pages/index.adoc
+++ b/docs/modules/community/pages/index.adoc
@@ -1,5 +1,42 @@
= Apache James Community
:navtitle: Community
-(TODO)
+Apache James Project is an Open Source all-volunteer project obtaining its strength from its Community made of
+developers and users. All are welcome to the Community!
+== Join the community
+
+There are many ways for Users, Developers, Curious and Fans to join and be part of the James Community:
+
+ * https://james.apache.org/[Apache James Website]
+ * xref:mailing-lists.adoc[Mailing lists]: Subscribe to the appropriate Mailing Lists according to your interests and profile.
+ * https://gitter.im/apache/james-project[Gitter chat room]: Chat in live with the community on Gitter.
+ * https://twitter.com/ApacheJames[Twitter]: Express yourself and follow us @ApacheJames.
+ * https://github.com/apache/james-project[Github]: Read and contribute to the source code of the project.
+ * https://issues.apache.org/jira/projects/JAMES[JIRA]: Report issues or make suggestions for the project on our bug tracker.
+ * https://builds.apache.org/job/ApacheJames/[CI]: Check the status of James builds on our Jenkins CI.
+ * xref:download.adoc[Download releases]: Download artifacts and sources your need for the James Server and James libraries.
+ * xref:support.adoc[Professional support]: Find a list of companies which can provide you some support on James.
+
+== Contribute
+
+James is a project that lives from the contributions of its community. *Anyone can contribute!*
+
+That's right, we always want to hear from people with contributions to the code, the documentation, the website,
+and bug reports. We more than welcome non-coding contributions.
+
+You can find more information on how to contribute to the James project on the xref:contributing.adoc[contributing] section.
+
+== The Apache Software Foundation
+
+James is a project belonging to the https://www.apache.org/[Apache Software Foundation [ASF\]]. Thus, the Apache Jame project
+is governed by a number of xref:guidelines.adoc[guidelines] directly depending on the *ASF*.
+
+If you wish to get more involved with the *ASF* community in general, those links might interest you as well:
+
+ * https://www.apache.org/foundation/getinvolved.html[Get involved with the ASF]
+ * https://www.apache.org/foundation/faq.html[Apache FAQ]
+ * https://www.apache.org/licenses/[Apache Licenses]
+ * https://www.apache.org/security/[The Apache security team]
+ * https://www.apache.org/foundation/sponsorship.html[Sponsorship program]
+ * https://www.apache.org/foundation/thanks.html[Sponsors list]
diff --git a/docs/modules/community/pages/mailing-lists.adoc b/docs/modules/community/pages/mailing-lists.adoc
new file mode 100644
index 0000000..dc3bd18
--- /dev/null
+++ b/docs/modules/community/pages/mailing-lists.adoc
@@ -0,0 +1,3 @@
+= Mailing lists
+
+(TODO)
diff --git a/docs/modules/community/pages/support.adoc b/docs/modules/community/pages/support.adoc
new file mode 100644
index 0000000..38bb320
--- /dev/null
+++ b/docs/modules/community/pages/support.adoc
@@ -0,0 +1,3 @@
+= Professional support
+
+(TODO)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[james-project] 03/08: JAMES-3187 Support subsection of the
community documentation
Posted by rc...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
rcordier pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/james-project.git
commit b9729a89531cd2d38255362d289a65e16ae74b4f
Author: Rene Cordier <rc...@linagora.com>
AuthorDate: Tue Aug 11 17:33:39 2020 +0700
JAMES-3187 Support subsection of the community documentation
---
docs/modules/community/images/linagora.png | Bin 0 -> 14370 bytes
docs/modules/community/pages/support.adoc | 15 ++++++++++++++-
2 files changed, 14 insertions(+), 1 deletion(-)
diff --git a/docs/modules/community/images/linagora.png b/docs/modules/community/images/linagora.png
new file mode 100644
index 0000000..de0a185
Binary files /dev/null and b/docs/modules/community/images/linagora.png differ
diff --git a/docs/modules/community/pages/support.adoc b/docs/modules/community/pages/support.adoc
index 38bb320..e44c516 100644
--- a/docs/modules/community/pages/support.adoc
+++ b/docs/modules/community/pages/support.adoc
@@ -1,3 +1,16 @@
= Professional support
-(TODO)
+Here is a list of companies which can provide you some support on James.
+
+== Linagora
+
+image::linagora.png[link=https://linagora.com]
+
+*Linagora* is an Open Source Software Company.
+
+Their mission is to bring digital independency to their customers.
+
+They are focused on large organizations both from private and public sector. They have set themselves the goal of
+helping Governments to achieve their digital sovereignty.
+
+*Linagora* can offer professional services related to James: support, feature development or project integration.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[james-project] 04/08: JAMES-3187 Mailing lists subsection of the
community documentation
Posted by rc...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
rcordier pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/james-project.git
commit 11da66c8cee934de4fec943b2d44731084ee9d77
Author: Rene Cordier <rc...@linagora.com>
AuthorDate: Fri Aug 14 11:48:45 2020 +0700
JAMES-3187 Mailing lists subsection of the community documentation
---
docs/modules/community/pages/mailing-lists.adoc | 165 +++++++++++++++++++++++-
1 file changed, 164 insertions(+), 1 deletion(-)
diff --git a/docs/modules/community/pages/mailing-lists.adoc b/docs/modules/community/pages/mailing-lists.adoc
index dc3bd18..68dedf1 100644
--- a/docs/modules/community/pages/mailing-lists.adoc
+++ b/docs/modules/community/pages/mailing-lists.adoc
@@ -1,3 +1,166 @@
= Mailing lists
-(TODO)
+Please read the <<_guidelines>> below before subscribing to our lists and join our community.
+
+== James mailing lists
+
+=== Server user list
+
+*Low traffic*
+mailto:server-user-subscribe@james.apache.org[Subscribe]
+mailto:server-user-unsubscribe@james.apache.org[Unsubscribe]
+http://www.mail-archive.com/server-user@james.apache.org[Archive]
+
+This is the list where users of the Apache James (Server) meet and discuss issues. Developers are also expected to be
+subscribed to this list to offer support to users of Apache James (Server).
+
+=== Server developer list
+
+*High traffic*
+mailto:server-dev-subscribe@james.apache.org[Subscribe]
+mailto:server-dev-unsubscribe@james.apache.org[Unsubscribe]
+http://www.mail-archive.com/server-dev@james.apache.org[Archive]
+
+This is the list where participating developers of the Apache James Project meet and discuss issues, code changes/additions,
+etc. Subscribers to this list get notices of each and every code change, build results, testing notices, etc. Do not
+send mail to this list with usage questions or configuration problems -- that's what server-user@james is for.
+
+=== Mime4j
+
+*Medium traffic*
+mailto:mime4j-dev-subscribe@james.apache.org[Subscribe]
+mailto:mime4j-dev-unsubscribe@james.apache.org[Unsubscribe]
+http://mail-archives.apache.org/mod_mbox/james-mime4j-dev[Archive]
+
+Discussions on the http://james.apache.org/mime4j[Mime4j] parser library.
+
+=== Site developer list
+
+*Low traffic*
+mailto:site-dev-subscribe@james.apache.org[Subscribe]
+mailto:site-dev-unsubscribe@james.apache.org[Unsubscribe]
+http://www.mail-archive.com/site-dev@james.apache.org[Archive]
+
+This is the list where participating developers of the Apache James project discuss changes/additions to the James
+websites etc. Subscribers to this list get notifications of every commit of the website resources. Do not send mail to
+this list with James software problems -- that's what server-user@james is for.
+
+=== James general list
+
+*Low traffic*
+mailto:general-subscribe@james.apache.org[Subscribe]
+mailto:general-unsubscribe@james.apache.org[Unsubscribe]
+http://www.mail-archive.com/general@james.apache.org[Archive]
+
+This is the list for general discussions related to the running of the project, it is the public list of the
+James project management committee (PMC) and is a public list opened to all. Do not send mail to this list with James
+software problems -- that's what server-user@james is for.
+
+=== Mailet API list
+
+*Low traffic*
+mailto:mailet-api-subscribe@james.apache.org[Subscribe]
+mailto:mailet-api-unsubscribe@james.apache.org[Unsubscribe]
+https://mail-archives.apache.org/mod_mbox/james-mailet-api[Archive]
+
+This is the public list for the Mailet API subproject, discussing all http://james.apache.org/mailet/index.html[Mailet API]
+design and implementation related topics. Questions about using Mailets and their configuration should be addressed
+to the server-user list.
+
+== How to unsubscribe your old email address
+
+First, find out the particular email adress to which ezmlm is sending. The email headers are visible in Microsoft Outlook
+via the messages menu "View | Options".
+
+ Microsoft Mail Internet Headers Version 2.0
+ ...
+ List-Unsubscribe: <ma...@james.apache.org>
+ List-Help: <ma...@james.apache.org>
+ List-Post: <ma...@james.apache.org>
+ List-Id: "James Server Users List" <server-user.james.apache.org>
+ Reply-To: "James Server Users List" <se...@james.apache.org>
+ Delivered-To: mailing list server-user@james.apache.org
+ ...
+ Return-Path: server-user-return-12345-john=host.domain@james.apache.org
+ ...
+
+The _Return-Path_ header contains the email address which is subscribed.
+
+To stop subscription for the address _john@host.domain_, send an email to
+
+`server-dev-unsubscribe-john=\host.domain@james.apache.org`
+
+or to
+
+`server-user-unsubscribe-john=\host.domain@james.apache.org`
+
+== Guidelines
+
+A mailing list is an electronic discussion forum that anyone can subscribe to. When someone sends an email message to
+the mailing list, a copy of that message is broadcasted to everyone who is subscribed to that mailing list.
+Mailing lists provide a simple and effective communication mechanism for discussion and decision making.
+
+The *Apache Software Foundation* has well established reasons for using email and not other types of forum.
+You may use a mail-news gateway, gmail or anything else you like but email is, and will remain, the official medium.
+
+With potentially thousands of subscribers, there is a common etiquette that you should observe. Please keep on reading.
+
+*Respect the mailing list type*
+
+* "User" lists are lists where you can send questions and comments about configuration, setup, usage and other "user"
+types of questions.
+* "Developer" lists are lists where you can send questions, comments and contributions about the project's software
+source code and general "development" types of questions.
+
+Some questions are appropriate for posting on both the "user" and the "developer" lists. In this case, pick one and
+only one. Do not cross post.
+
+Asking a configuration question on the developers list is frowned upon because developers' time is as precious as yours.
+By contacting them directly instead of the users list you are abusing resources. It is unlikely that you will get a
+quicker answer this way, those developers who have time to devote to providing support are also subscribed to the users
+list. If you contact individuals directly, or post your user issues to the developer list you may get no answer at all.
+
+*Join the lists that are appropriate for your discussion*
+
+Please make sure that you are joining the list that is appropriated for the topic that you would like to discuss.
+The general list is for discussions about the management and direction of the James project, not for "general support".
+
+*Ask smart questions*
+
+Every volunteer project obtains its strength from the people involved in it. You are welcome to join any of our mailing
+lists. You can choose to lurk, or actively participate; it's up to you. The level of community responsiveness to
+specific questions is generally directly proportional to the amount of effort you spend formulating your question.
+Eric Raymond and Rick Moen have even written an essay entitled "Asking Smart Questions" precisely on this topic.
+Although somewhat militant, it is definitely worth reading.
+
+*Note*: Please do NOT send your Java problems to the two authors. They welcome feedback on the FAQ's contents, but are
+simply not a Java help resource. Follow the essay's advice and choose your forum carefully.
+
+*Keep your email short and to the point*
+
+If your email is more than about a page of text, chances are that it won't get read by very many people. It is much
+better to try to pack a lot of informative information (see above about asking smart questions) into as small of an
+email as possible. If you are replying to a previous email only quote the parts that you are replying to and to remove
+the unnecessary bits. This makes it easier for people to follow a thread as well as making the email archives easier
+to search and read.
+
+*Do your best to ensure that you are not sending HTML or "Stylelized" email to the list*
+
+If you are using Outlook or Outlook Express or Eudora, chances are that you are sending HTML email by default. There is
+usually a setting that will allow you to send "Plain Text" email. If you are using Microsoft products to send email,
+there are several bugs in the software that prevent you from turning off the sending of HTML email.
+
+*Watch where you are sending email*
+
+The majority of our mailing lists have set the Reply-To to go back to the list. That means that when you Reply to a
+message, it will go to the list and not to the original author directly. The reason is because it helps facilitate
+discussion on the list for everyone to benefit from. Be careful of this as sometimes you may intend to reply to a
+message directly to someone instead of the entire list. The appropriate contents of the Reply-To header is an age-old
+debate that should not be brought up on the mailing lists. You can examine opposing points of view condemning our
+convention and condoning it. Bringing this up for debate on a mailing list will add nothing new and is considered off-topic.
+
+*Do not cross post messages*
+
+In other words, pick one mailing list and send your messages to that mailing list only. Do not send your messages to
+multiple mailing lists. The reason is that people may be subscribed to one list and not to the other. Therefore, some
+people will only see part of the conversation.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[james-project] 06/08: JAMES-3187 Contributing subsection of the
community new documentation
Posted by rc...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
rcordier pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/james-project.git
commit 0b195a92265d1d7f345cc911d9970f32f680d0dc
Author: Rene Cordier <rc...@linagora.com>
AuthorDate: Thu Aug 20 16:11:07 2020 +0700
JAMES-3187 Contributing subsection of the community new documentation
---
docs/modules/community/pages/contributing.adoc | 184 ++++++++++++++++++++++++-
docs/modules/community/pages/guidelines.adoc | 3 +-
2 files changed, 185 insertions(+), 2 deletions(-)
diff --git a/docs/modules/community/pages/contributing.adoc b/docs/modules/community/pages/contributing.adoc
index 463288d..7691e4e 100644
--- a/docs/modules/community/pages/contributing.adoc
+++ b/docs/modules/community/pages/contributing.adoc
@@ -1,3 +1,185 @@
= Contributing
-(TODO)
+This document defines the different ways available for contributing to the Apache James project.
+
+To keep you informed on James issues, subscribe to the relevant xref:mailing-lists.adoc[mailing lists].
+
+== Be involved in the community
+
+An easy start is to be involved in the community.
+
+Share your experiences with James, your needs, your enhancements proposition via the
+xref:mailing-lists.adoc[mailing lists], on https://gitter.im/apache/james-project[Gitter], or on our
+https://issues.apache.org/jira/projects/JAMES/issues[Bug Tracker].
+
+Don't hesitate to write articles and blog posts. Use your preferred media to spread the love!
+
+== Reporting bugs
+
+Many improvements come as a direct result of bug reports.
+
+To report a bug, please use the appropriate Bug Tracker JIRA link according to the project you want to address:
+
+* https://issues.apache.org/jira/browse/JAMES[Server]
+* https://issues.apache.org/jira/browse/MAILET[Mailet]
+* https://issues.apache.org/jira/browse/MAILBOX[Mailbox]
+* https://issues.apache.org/jira/browse/PROTOCOLS[Protocols]
+* https://issues.apache.org/jira/browse/MPT[MPT]
+* https://issues.apache.org/jira/browse/MIME4J[Mime4j]
+* https://issues.apache.org/jira/browse/JSIEVE[jSieve]
+* https://issues.apache.org/jira/browse/JSPF[jSPF]
+* https://issues.apache.org/jira/browse/JDKIM[jDKIM]
+* https://issues.apache.org/jira/browse/HUPA[Hupa]
+
+Once you are logged on the appropriate JIRA page, click on the red Create button, then complete the different fields
+as accurately as possible, so that any user can reproduce the reported bug. Also note that all your information must be
+readable (use markdown).
+
+Then, you have to click on Create to submit your bug.
+
+=== Reporting security vulnerabilities
+
+http://www.apache.org/security/[Security vulnerabilities] should be announced to the Apache Security team.
+PMCs will be notified about them, and will work hard to propose fixes as fast as possible.
+
+Specific details about security in James can be found here.
+
+== Documentation
+
+Documentation is an easy way to get on board! Check out the
+https://issues.apache.org/jira/issues/?jql=project%20%3D%20JAMES%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20%3D%20documentation%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC[~documentation]
+label on JIRA to get some ideas.
+Report on JIRA the typos you spot, the information you miss, and any improvement you can think of.
+The next step is to contribute the documentation changes via https://github.com/apache/james-project/tree/master/docs/modules[Git].
+
+To edit an existing document try to edit the adoc version in `docs/modules` (check it out from Git) and if you can, submit a
+patch as for xref:_code_patches[Code Patches].
+
+If you want to contribute new files please try to use the AsciiDoc format as shown in `docs/modules`.
+
+If all this seems like unnecessary nonsense, send us whatever you like, we'd still be happy to receive good documentation.
+
+Each of the Apache James projects has its own documentation maintained with the automated build. Once a build is done,
+the documentation can be further committed in the https://git-wip-us.apache.org/repos/asf/james-site.git[site module]
+which will be automatically published via gitpubsub to http://james.apache.org[Apache James web site].
+
+== How to contribute some code?
+
+* Clone the source code of the project from its link:git://git.apache.org/james-project.git[apache git repository] or its
+https://github.com/apache/james-project[Github]
+* Create your branch and name it with the JIRA ticket number.
+* Create a Pull Request with your branch name and prefix its different commits with the same name.
+
+Alternatively you can create a patch as xref:_code_patches[outlined below], and attach it to the JIRA ticket.
+
+A valid commit comment might be:
+
+```
+JAMES-2285 My awesome commit title
+
+Here is some more details about what my commit does, and the rationals of the choice I took.
+```
+
+=== Licenses
+
+All contributions to the James project are made under the https://www.apache.org/licenses[Apache license 2.0]
+
+=== Contributions proposals
+
+* We reference some easy tasks to start with:
+https://issues.apache.org/jira/issues/?jql=project%20%3D%20JAMES%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20%3D%20newbie%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC[~newbie]
+* We have a collection of minor fixes awaiting contributions:
+https://issues.apache.org/jira/issues/?jql=project%20%3D%20JAMES%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20%3D%20easyfix%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC[~easyfix]
+* Challenge yourself with some cool features we thought to:
+https://issues.apache.org/jira/issues/?jql=project%20%3D%20JAMES%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20%3D%20feature%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC[~feature]
+
+Additional ideas are more than welcome. Don't hesitate to discuss that with us!
+
+=== Coding standards
+
+While we are glad to accept contributions to documentation from anyone, in almost any format, because its much better
+than none, please consider these guidelines to help us to assimilate your contribution.
+
+Submissions to the James project must follow the coding conventions outlined in this document. James developers are
+asked to follow coding conventions already present in the code. (For example, if the existing code has the bracket on
+the same line as the if statement, then all subsequent code should also follow that convention.) Anything not explicitly
+mentioned in this document should adhere to the official
+https://www.oracle.com/java/technologies/javase/codeconventions-contents.html[Java Coding Conventions].
+
+*Developers who commit code that does not follow the coding conventions outlined in this document will be responsible
+for fixing their own code.*
+
+. Your code should pass our https://github.com/apache/james-project/blob/master/checkstyle.xml[checkstyle] which runs
+upon mvn clean install.
+. Extra spaces between parentheses are not allowed:
+
+```
+ if (foo) > Good
+
+ or
+
+ if ( foo ) > Bad
+```
+
+[start=3]
+. Four spaces. *No tabs.* Period.
+The James mailing list receives commit messages that are almost impossible to read if tabs are used.
+. Use Unix linefeeds for all .java source code files. Only platform-specific files (e.g. .bat files for Windows) should
+contain non-Unix linefeeds.
+. Javadoc *MUST* exist on all API methods. Contributing a missing javadoc for any method, class, variable, etc., will be
+GREATLY appreciated as this will help to improve the James project.
+. The standard Apache license header *MUST* be placed at the top of every file.
+. Your change set *MUST* be covered by tests. We also strongly appreciate integration tests.
+. We also require the following best practice regarding maven and the *pom.xml*:
+
+** Define your dependency versions in james-project pom.xml. This structurally ensures all projects get the same v
+ersion, and that there is no version clashes.
+** Don't use _org.apache.james_ groupId for your dependencies. Use _${james.groupId}_. If not, you break the policies
+for automatic sorting, as well as make it more ambiguous.
+** You should be ordering your dependencies. The sort order is:
+*** If the project is part of org.james.apache groupId? Internal dependencies goes first.
+*** Then we order by groupId
+*** Then we order by artifactId
+*** Then we order by type. test-jar goes last.
+
+You should also split multiple attributes each on a new line.
+
+You should ensure your POM files, as well as sections ordering follow the
+https://maven.apache.org/ref/3.0.3/maven-model/maven.html[Maven Model].
+
+=== Code patches
+
+Patches should be attached to the corresponding JIRA issue.
+
+Always use diff -u to generate patches, so we can apply them using 'patch'.
+
+Make sure the patch only contains what is intended, your checkout could be outdated.
+
+Make sure it conforms to the code standards, otherwise it may be ignored. It is OK to make a single patch covering
+several files, but please only one issue at a time.
+
+Briefly outline the reason for your patch, the solution your patch implements, why a patch is needed and why your code
+will solve the problem. Note any bug numbers your patch addresses.
+
+The reason for these rules is so that committers can easily see what you are trying to achieve, it is their
+responsibility to manage the code and review submissions, if you make it easy for them to see what you are doing your
+patch is more likely to be committed quickly.
+
+== Idea or design proposals
+
+People can submit ideas, features or design changes proposals by discussing it through the
+xref:mailing-lists.adoc[mailing lists] and/or submitting an ADR (Architecture Decision Record). A discussion
+on the mailing list getting a consensus of the community can be the object of the writing of an ADR to confirm the
+change agreed upon.
+
+ADRs *MUST* be submitted under the folder `src/adr` via a pull request. The standards used for writing an ADR are
+described in the https://github.com/apache/james-project/blob/master/src/adr/0001-record-architecture-decisions.md[first ADR]
+written for the Apache James project.
+
+The number of the ADR should be incremental. If an other ADR gets merged concurrently, the committer is responsible for
+updating its number accordingly.
+
+When the ADR reaches a consensus within the community and is accepted, it can be merged and goes into effect.
+
+An ADR can't be removed after being accepted and merged. However, a new ADR can supersede a previous one. This is so
+we are able to keep track on all the decisions being made regarding the project.
diff --git a/docs/modules/community/pages/guidelines.adoc b/docs/modules/community/pages/guidelines.adoc
index e07f1a7..cd31b8c 100644
--- a/docs/modules/community/pages/guidelines.adoc
+++ b/docs/modules/community/pages/guidelines.adoc
@@ -127,7 +127,8 @@ categories corresponding to the change status:
* *Concept/Plan*
An idea or plan for a change. These are represented as ADRs (Architectural Decision Records), stored under the `src/adr`
-folder. Votes are being requested early so as to uncover conflicts before too much work is done.
+folder. Votes are being requested early so as to uncover conflicts before too much work is done. You can find more
+information about this xref:contributing.adoc#_idea_or_design_proposals[here].
* *Proposed Patch*
A specific set of changes to the current product in the form of input to the patch command (a diff output).
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org