Re: DevFaq wiki update

2018-01-12 Thread Bertrand Delacretaz
On Fri, Jan 12, 2018 at 2:05 PM, Neil C Smith wrote: > On Fri, 12 Jan 2018 at 12:50 Bertrand Delacretaz >> MoinMoin is a standard offering indeed, https://wiki.apache.org > ...Or a standard no-longer offering according to that page! So, that rules

Re: DevFaq wiki update

2018-01-12 Thread Neil C Smith
On Fri, 12 Jan 2018 at 12:50 Bertrand Delacretaz wrote: > MoinMoin is a standard offering indeed, https://wiki.apache.org > Or a standard no-longer offering according to that page! So, that rules that out anyway then. Thanks, Neil -- Neil C Smith Artist &

Re: DevFaq wiki update

2018-01-12 Thread Bertrand Delacretaz
On Fri, Jan 12, 2018 at 12:01 PM, Neil C Smith wrote: > ...Emi mentioned the possibility of Apache infra providing MoinMoin for us > earlier, but perhaps we could open a discussion about the merits of a > git-backed wiki system via Apache?... MoinMoin is a standard

Re: DevFaq wiki update

2018-01-12 Thread Neil C Smith
Hi, On Fri, 12 Jan 2018 at 09:19 Bertrand Delacretaz wrote: > Ok, if you're going that route the mirroring should be checked with > ASF infra, ask on infrastructure@ > OK, I'll follow up on that. > Sure, but that content is "precious", I assume the project cannot >

Re: DevFaq wiki update

2018-01-12 Thread Bertrand Delacretaz
Hi Neil, On Thu, Jan 11, 2018 at 5:40 PM, Neil C Smith wrote: > ...Quite a few projects under > Apache have the wiki enabled (not sure on the mirroring situation)... Ok, if you're going that route the mirroring should be checked with ASF infra, ask on infrastructure@ >

Re: DevFaq wiki update

2018-01-11 Thread Neil C Smith
Hi Bertrand, On Thu, 11 Jan 2018 at 14:13 Bertrand Delacretaz wrote: > https://gitbox.apache.org/ implements appropriate mirroring for GitHub > repositories, so using those is fine - but I don't think GitHub wikis > are mirrored, and if they're not using them for core

Re: DevFaq wiki update

2018-01-11 Thread Bertrand Delacretaz
On Wed, Jan 10, 2018 at 7:40 PM, Matthias Bläsing wrote: > ...before someone says "github will stay forever", sourceforge used > its market value for bad marketing (bundle free software with an > malware installing installer) and if enough money is offered, github > and

Re: DevFaq wiki update

2018-01-10 Thread Emilian Bold
vs GitHub would lead to more contributions or not... --emi > Original Message >Subject: Re: DevFaq wiki update >Local Time: 10 January 2018 9:15 PM >UTC Time: 10 January 2018 19:15 >From: neilcsm...@apache.org >To: dev@netbeans.incubator.apache.org > >On W

Re: DevFaq wiki update

2018-01-10 Thread Delfi Ramirez
articles. --emi Original Message Subject: Re: DevFaq wiki update Local Time: 10 January 2018 8:58 PM UTC Time: 10 January 2018 18:58 From: neilcsm...@apache.org To: dev@netbeans.incubator.apache.org On Wed, 10 Jan 2018 at 18:41 Matthias Bläsing mblaes...@doppel-helix.eu wrote

Re: DevFaq wiki update

2018-01-10 Thread Neil C Smith
On Wed, 10 Jan 2018 at 19:03 Emilian Bold wrote: > > I think a static site and a wiki are somewhat orthogonal things. > > I believe even the old wiki needed a login for edit. > Yes, and so would this - the two options are for committers to have direct edit and other

Re: DevFaq wiki update

2018-01-10 Thread Emilian Bold
I also vote on avoiding Confluence. > I think a static site and a wiki are somewhat orthogonal things. I believe even the old wiki needed a login for edit. Using a GitHub PR /might/ be good enough for the technical articles. --emi > Original Message >Subject: Re: De

Re: DevFaq wiki update

2018-01-10 Thread Neil C Smith
On Wed, 10 Jan 2018 at 18:41 Matthias Bläsing wrote: > And before someone says "github will stay forever", sourceforge used > its market value for bad marketing (bundle free software with an > malware installing installer) and if enough money is offered, github > and

Re: DevFaq wiki update

2018-01-10 Thread Matthias Bläsing
Hi all, Am Mittwoch, den 10.01.2018, 11:46 +0100 schrieb Bertrand Delacretaz: > On Wed, Jan 10, 2018 at 9:41 AM, Antonio wrote: > > ...I think we should make a final decision on whether to host the > > wiki at > > Confluence or at the website, taking into account an

Re: DevFaq wiki update

2018-01-10 Thread Neil C Smith
Hi, On Wed, 10 Jan 2018 at 15:55 Antonio Vieiro wrote: > 1. Which “NetBeans Github Repo” are we talking about? The website or the > source code? Maybe the website is more appropriate, right? > I was thinking source code, because that might be more visible? Arguments for

Re: DevFaq wiki update

2018-01-10 Thread Antonio Vieiro
Hi Neil, I think these are all sensible ideas. Just two comments: 1. Which “NetBeans Github Repo” are we talking about? The website or the source code? Maybe the website is more appropriate, right? 2. I just did this experiments with the DevFaq as I thought that would be more useful, maybe we

Re: DevFaq wiki update

2018-01-10 Thread Neil C Smith
Hi, On Wed, 10 Jan 2018 at 08:41 Antonio wrote: > I think we should make a final decision on whether to host the wiki at > Confluence or at the website, taking into account an approximate date > for the website to be available. > My inclination would be to do something

Re: DevFaq wiki update

2018-01-10 Thread Antonio Vieiro
If nobody argues against this I´ll suspend the infra request within a few hours. Thanks, Antonio. > El 10 ene 2018, a las 11:46, Bertrand Delacretaz > escribió: > >> On Wed, Jan 10, 2018 at 9:41 AM, Antonio wrote: >> ...I think we should make a

Re: DevFaq wiki update

2018-01-10 Thread Bertrand Delacretaz
On Wed, Jan 10, 2018 at 9:41 AM, Antonio wrote: > ...I think we should make a final decision on whether to host the wiki at > Confluence or at the website, taking into account an approximate date for > the website to be available +1 and if that decision cannot be made

DevFaq wiki update

2018-01-10 Thread Antonio
Hi all, There's a new 'wiki-convert' tool [1] that converts the files in the old wiki's DevFaq from WikiText to AsciiDoc. The tool (a Maven project that uses eclipse's mylyn wikitext) can also be used to generate markdown or xhtml. The generated AsciiDoc files [2] contain jbake-ready