Re: Which repositories are we using and going to document? Let's retire the ones we don't

2020-08-25 Thread Rene Cordier
On 20/08/2020 11:23, Rene Cordier wrote: Based on Eugen comments in the INFRA ticket, I did this: https://github.com/apache/james-project/pull/244 for redirecting notifications to the new ML for this. However I don't think as a commiter I can create the ML, so if a PMC could manage that :)

Re: Which repositories are we using and going to document? Let's retire the ones we don't

2020-08-19 Thread Rene Cordier
On 19/08/2020 17:49, Eugen Stan wrote: I've created an issue to make the ML changes: https://issues.apache.org/jira/browse/INFRA-20735 -- Please add: - notificati...@james.apache.org Please remove: - site-...@james.apache.org - mailet-...@james.apache.org Based on Eugen comments in the INFR

Re: Which repositories are we using and going to document? Let's retire the ones we don't

2020-08-19 Thread Eugen Stan
La 19.08.2020 09:59, Rene Cordier a scris: >> I think we should have separate channels for: >> - development: how we implement features and what features we work on >> - users: how to use James:deploy it, create back-ups, etc. > > Those 2 mailing lists exist already I believe. We have `server-dev`

Re: Which repositories are we using and going to document? Let's retire the ones we don't

2020-08-18 Thread Rene Cordier
I think we should have separate channels for: - development: how we implement features and what features we work on - users: how to use James:deploy it, create back-ups, etc. Those 2 mailing lists exist already I believe. We have `server-dev` for development related things and `server-user` for

Re: Which repositories are we using and going to document? Let's retire the ones we don't

2020-08-17 Thread Eugen Stan
La 17.08.2020 07:45, David Leangen a scris: I do think we might want to leverage this opportunity to close low-traffic unused mailing lists. This includes: My 2 cents: From the user perspective, I think it would be desirable to trim down the number of mailing lists. 😀 Thank you for ta

Re: Which repositories are we using and going to document? Let's retire the ones we don't

2020-08-16 Thread David Leangen
> I do think we might want to leverage this opportunity to close > low-traffic unused mailing lists. This includes: My 2 cents: From the user perspective, I think it would be desirable to trim down the number of mailing lists. 😀

Re: Which repositories are we using and going to document? Let's retire the ones we don't

2020-08-16 Thread Tellier Benoit
Hi René I did a quick review. As such, given the limited content, I mostly agree with it. I do think we might want to leverage this opportunity to close low-traffic unused mailing lists. This includes:  -site-...@james.apache.org : site discussions happens on server-dev and not there, it is low

Re: Which repositories are we using and going to document? Let's retire the ones we don't

2020-08-16 Thread Rene Cordier
Hello, There are things that need to me documented that are not technical: - what / where are the project resources (website, CI, git repos, mailing list) - how to contribute, engage with the community - etc. Just to say I started migrating and writing this part of the documentation here: h

Re: Which repositories are we using and going to document? Let's retire the ones we don't

2020-07-31 Thread David Leangen
> Migrating is not sexy work but is easier than writing new documentation. Conditional on the structure and content being in a desirable state, I would agree with this generalization. In this case, though, I don’t feel the condition is me, so I think we’ll have to agree to disagree. > I've add

Re: Which repositories are we using and going to document? Let's retire the ones we don't

2020-07-31 Thread Eugen Stan
La 31.07.2020 03:13, David Leangen a scris: I've decided to add docs stubs to all repositories. I'm going to start migrating the documentation for the popular libraries and then decide what to do with the others (start the retiring process most likely). Awesome! Nice initiative. Thanks!! An

Re: Which repositories are we using and going to document? Let's retire the ones we don't

2020-07-30 Thread David Leangen
> I've decided to add docs stubs to all repositories. > I'm going to start migrating the documentation for the popular libraries and > then decide what to do with the others (start the retiring process most > likely). Awesome! Nice initiative. Thanks!! > Anyone up for a documentation migration

Re: Which repositories are we using and going to document? Let's retire the ones we don't

2020-07-30 Thread Eugen Stan
La 21.07.2020 01:23, David Leangen a scris: While working on the documentation website I have been distracted by other work the past 2 weeks. I hope to get back to this project within this week. Thanks for helping to push it forward! ---

Re: Which repositories are we using and going to document? Let's retire the ones we don't

2020-07-20 Thread David Leangen
>> While working on the documentation website I have been distracted by other work the past 2 weeks. I hope to get back to this project within this week. Thanks for helping to push it forward! - To unsubscribe, e-mail: serve

Re: Which repositories are we using and going to document? Let's retire the ones we don't

2020-07-20 Thread Tellier Benoit
Le 20/07/2020 à 18:00, Eugen Stan a écrit : > Hello, > > While working on the documentation website I ran into the question of: > What parts to document? > > 1. What are the repositories we still use in James - some like jdkim > have merged in james-project - others ? No. The JDKIM library still

Which repositories are we using and going to document? Let's retire the ones we don't

2020-07-20 Thread Eugen Stan
Hello, While working on the documentation website I ran into the question of: What parts to document? 1. What are the repositories we still use in James - some like jdkim have merged in james-project - others ? 2. Which ones we don't use? 3. Which projects we wish to retire - if any? My su