Hi, On Fri, 12 Jan 2018 at 09:19 Bertrand Delacretaz <[email protected]> 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 > afford to lose it. > Well, some might benefit from archiving ;-) I agree that temporary solutions are ok but once NetBeans graduates > such things need to be cleaned up. > Yes, but there were two points to my suggestion. One is a temporary solution to updating and migrating important info into other documentation. The other is finding an ongoing solution to temporary (well, work-in-progress) information. As primarily a platform dev, I've found the wiki invaluable because people have been able to throw up information quite easily, sometimes conflicting things on the same page! ;-) I really don't want us to lose (if anything make easier) a wiki as a slightly anarchic place people can put up solutions quickly without worrying whether it's ready for "primetime". I think in any migration we do from the current wiki we're losing important info already in terms of history? I don't know what migration in/out of Confluence is like? The appealing thing for me of using the GitHub wiki UI in the immediate term is not about hosting it there - it's about having everything backed by a git repository of plain text files - useful and editable in many other ways, even locally, without ever needing to "migrate" anything ever again. 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? Best wishes, Neil -- Neil C Smith Artist & Technologist www.neilcsmith.net Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
