Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On Tue, Feb 6, 2018 at 7:17 AM, Oleg Kalnichevski wrote: > On Mon, 2018-02-05 at 23:39 -0700, Bindul Bhowmik wrote: > > ... > >> >> If I may ask as a user of the library, would the new site still have >> parts of the site that are generated from releases? For example, >>

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On Tue, 2018-02-06 at 19:46 +0100, Michael Osipov wrote: > Am 2018-02-06 um 19:39 schrieb Oleg Kalnichevski: > > On Tue, 2018-02-06 at 16:45 +, sebb wrote: > > > On 6 February 2018 at 14:31, Oleg Kalnichevski > > > > ... > > > > > > > > > ... > > > > > > > > > I *am*

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

Am 2018-02-06 um 19:39 schrieb Oleg Kalnichevski: On Tue, 2018-02-06 at 16:45 +, sebb wrote: On 6 February 2018 at 14:31, Oleg Kalnichevski ... ... I *am* saying we need to preserve links. Moving from Maven may make this harder, so that needs to be factored in to

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On Tue, 2018-02-06 at 16:45 +, sebb wrote: > On 6 February 2018 at 14:31, Oleg Kalnichevski ... > > > ... > > > > > I *am* saying we need to preserve links. > > > Moving from Maven may make this harder, so that needs to be > > > factored > > > in to the decision. > > >

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On Tue, 2018-02-06 at 16:28 +, sebb wrote: > On 6 February 2018 at 14:17, Oleg Kalnichevski > wrote: > > On Mon, 2018-02-05 at 23:39 -0700, Bindul Bhowmik wrote: > > > > ... > > Absolutely. Being able to take a full advantage of better tooling > > is a > > primary

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On 6 February 2018 at 14:31, Oleg Kalnichevski wrote: > On Tue, 2018-02-06 at 09:55 +, sebb wrote: >> On 4 February 2018 at 11:49, Oleg Kalnichevski >> wrote: >> > On Sat, 2018-02-03 at 23:02 +, sebb wrote: >> > > On 3 February 2018 at 10:32, Oleg

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On 6 February 2018 at 14:17, Oleg Kalnichevski wrote: > On Mon, 2018-02-05 at 23:39 -0700, Bindul Bhowmik wrote: > > ... > >> >> If I may ask as a user of the library, would the new site still have >> parts of the site that are generated from releases? For example, >> Javadocs?

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On Tue, 2018-02-06 at 09:55 +, sebb wrote: > On 4 February 2018 at 11:49, Oleg Kalnichevski > wrote: > > On Sat, 2018-02-03 at 23:02 +, sebb wrote: > > > On 3 February 2018 at 10:32, Oleg Kalnichevski > > > > ... > > > > > > > > > Like, better tools

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On Mon, 2018-02-05 at 23:39 -0700, Bindul Bhowmik wrote: ... > > If I may ask as a user of the library, would the new site still have > parts of the site that are generated from releases? For example, > Javadocs? > Hi Bindul Yes, most certainly javadocs would still be there (given that

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On 4 February 2018 at 11:49, Oleg Kalnichevski wrote: > On Sat, 2018-02-03 at 23:02 +, sebb wrote: >> On 3 February 2018 at 10:32, Oleg Kalnichevski > > ... > >> >> > Like, better tools tend to use markdown. >> >> But Maven is not a content generation

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On Sun, Feb 4, 2018 at 4:49 AM, Oleg Kalnichevski wrote: > On Sat, 2018-02-03 at 23:02 +, sebb wrote: >> On 3 February 2018 at 10:32, Oleg Kalnichevski > > ... > >> >> > Like, better tools tend to use markdown. >> >> But Maven is not a content generation

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On Sat, 2018-02-03 at 23:02 +, sebb wrote: > On 3 February 2018 at 10:32, Oleg Kalnichevski ... > > > Like, better tools tend to use markdown. > > But Maven is not a content generation tool; Why are we using it as a content generation tool I am wondering? >

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On 3 February 2018 at 10:32, Oleg Kalnichevski wrote: > On Sat, 2018-02-03 at 10:21 +, sebb wrote: >> On 2 February 2018 at 17:41, Oleg Kalnichevski >> wrote: >> > On Fri, 2018-02-02 at 17:05 +, sebb wrote: >> > > On 2 February 2018 at 13:33, Oleg

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

Am 2018-02-03 um 10:31 schrieb Oleg Kalnichevski: On Fri, 2018-02-02 at 23:01 +0100, Michael Osipov wrote: Am 2018-01-31 um 14:06 schrieb Oleg Kalnichevski: Folks We have a dubious honor of having absolutely the most hideous project web site in existence. It makes my eyes bleed every time I

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On Sat, 2018-02-03 at 10:21 +, sebb wrote: > On 2 February 2018 at 17:41, Oleg Kalnichevski > wrote: > > On Fri, 2018-02-02 at 17:05 +, sebb wrote: > > > On 2 February 2018 at 13:33, Oleg Kalnichevski > > > wrote: > > > > On Wed, 2018-01-31 at 20:18

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On Sat, 2018-02-03 at 10:18 +, sebb wrote: > On 3 February 2018 at 09:31, Oleg Kalnichevski > wrote: > > On Fri, 2018-02-02 at 23:01 +0100, Michael Osipov wrote: > > > Am 2018-01-31 um 14:06 schrieb Oleg Kalnichevski: > > > > Folks > > > > > > > > We have a dubious honor of

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On 2 February 2018 at 17:41, Oleg Kalnichevski wrote: > On Fri, 2018-02-02 at 17:05 +, sebb wrote: >> On 2 February 2018 at 13:33, Oleg Kalnichevski >> wrote: >> > On Wed, 2018-01-31 at 20:18 +, sebb wrote: >> > > It may not be pretty, but I find it

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On 3 February 2018 at 09:31, Oleg Kalnichevski wrote: > On Fri, 2018-02-02 at 23:01 +0100, Michael Osipov wrote: >> Am 2018-01-31 um 14:06 schrieb Oleg Kalnichevski: >> > Folks >> > >> > We have a dubious honor of having absolutely the most hideous >> > project >> > web site in

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On Fri, 2018-02-02 at 23:01 +0100, Michael Osipov wrote: > Am 2018-01-31 um 14:06 schrieb Oleg Kalnichevski: > > Folks > > > > We have a dubious honor of having absolutely the most hideous > > project > > web site in existence. It makes my eyes bleed every time I have to > > update it. It is

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

Am 2018-01-31 um 14:06 schrieb Oleg Kalnichevski: Folks We have a dubious honor of having absolutely the most hideous project web site in existence. It makes my eyes bleed every time I have to update it. It is simply horrible. I would like to migrate project website sources from Maven apt and

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On Fri, 2018-02-02 at 17:05 +, sebb wrote: > On 2 February 2018 at 13:33, Oleg Kalnichevski > wrote: > > On Wed, 2018-01-31 at 20:18 +, sebb wrote: > > > It may not be pretty, but I find it legible and generally easy to > > > navigate so I hope those attributes won't be

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On 2 February 2018 at 13:33, Oleg Kalnichevski wrote: > On Wed, 2018-01-31 at 20:18 +, sebb wrote: >> It may not be pretty, but I find it legible and generally easy to >> navigate so I hope those attributes won't be lost. >> >> Also, it's important not to break any links. >>

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On Wed, 2018-01-31 at 20:18 +, sebb wrote: > It may not be pretty, but I find it legible and generally easy to > navigate so I hope those attributes won't be lost. > > Also, it's important not to break any links. > It is also important to eat healthy, be polite and stay away from those

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

It may not be pretty, but I find it legible and generally easy to navigate so I hope those attributes won't be lost. Also, it's important not to break any links. If the site is no longer built using Maven, then it may be difficult to preserve all the links (e.g. project info page links). It

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On Wed, Jan 31, 2018 at 7:57 AM, Oleg Kalnichevski wrote: > On Wed, 2018-01-31 at 07:43 -0700, Gary Gregory wrote: > > > > > ... > > > > On Wed, Jan 31, 2018 at 6:06 AM, Oleg Kalnichevski > > wrote: > > > > Granted the site is not the most attractive, the

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On 1/31/2018 6:36 PM, Oleg Kalnichevski wrote: Folks We have a dubious honor of having absolutely the most hideous project web site in existence. It makes my eyes bleed every time I have to update it. It is simply horrible. I would like to migrate project website sources from Maven apt and

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On Wed, 2018-01-31 at 07:43 -0700, Gary Gregory wrote: > > ... > On Wed, Jan 31, 2018 at 6:06 AM, Oleg Kalnichevski > wrote: > > Granted the site is not the most attractive, the only time I want to > dedicate to this topic is to discuss it here. I do not care about > which

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On Wed, Jan 31, 2018 at 6:06 AM, Oleg Kalnichevski wrote: > Folks > > We have a dubious honor of having absolutely the most hideous project > web site in existence. It makes my eyes bleed every time I have to > update it. It is simply horrible. > > I would like to migrate

[DISCUSS] Migrating project website content to markdown (2nd attempt)

Folks We have a dubious honor of having absolutely the most hideous project web site in existence. It makes my eyes bleed every time I have to update it. It is simply horrible. I would like to migrate project website sources from Maven apt and xdoc to markdown format and switch to using either