[
https://issues.apache.org/jira/browse/JAMES-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138745#comment-17138745
]
Ioan Eugen Stan commented on JAMES-2586:
----------------------------------------
Thanks. It's a bit clear for me from where the difference in perspective comes
from.
For managing the project we have a few tools at our disposal: JIRA for issue
tracking, mailing list and gitter for discussion, the documentation files, the
James website.
Each tool has a purpose and sure there is overlap between them.
I don't believe I hold the absolute truth about how tools should be used and
which tool is used for what.
I would like to reach a common understanding so we can all work together to
produce good software and enjoy life.
Please keep this in mind while you read the next pieces of text.
As you correctly pointed out, I do consider JIRA for issue tracking and doing
the project management part.
We also have github and this creates duplication and we should discuss this in
another thread.
I think ideas should be discussed on the mailing list. The mailing list is
indexed and appears in google results.
Mailing list serve this purpose - discuss ideas, offer support:
https://www.apache.org/foundation/mailinglists.html .
If the idea has merit and people are willing to work on it, we can use JIRA to
track and coordinate.
I don't think JIRA is a good place for ideas since it interferes with the
project management part.
For example in kubernetes they have thousands of issues.
They mark them stale and rotten because otherwise they would be overwhelmed.
We don't have thousands of open issues and I don't want to reach that number.
Low number of issues means it's easy for us to focus on those things and get
them done.
It's easy for someone who joins the community to identity the current issues
and work on them.
> Implement a Postgres-specific backend
> -------------------------------------
>
> Key: JAMES-2586
> URL: https://issues.apache.org/jira/browse/JAMES-2586
> Project: James Server
> Issue Type: New Feature
> Reporter: Matthieu Baechler
> Priority: Major
>
> James has a JPA implementation of most interfaces that allows to deploy it on
> top of some popular RDBMS.
> However, while useful for some kind of applications, ORM are usually a bad
> fit for applications requiring high performance like a mail server.
> As an abstraction, it also prevents from using advanced features of a given
> RDBMS.
> For most usages, James would probably run great on top of Postgres, given
> that we use advanced features to implement search, for example.
> A good strategy would be to implement all interfaces implemented by JPA with
> a modern Postgres driver.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
