Hey Josh,
It's great to know that you're interested in helping out on the
documentation update!
Indeed, the old Ruby generator has served us well but it's dated and
becoming a hindrance to our productivity. A straight rewrite in node is not
how I want to approach. Programming languages come and g
> I think a note in the README for docs indicating that the code is being
> rewritten (with a bug link and an ETA) would have prevented me from
> investing time in it.
Probably. But this is Apache and nothing happens at Apache unless it
happens on the mailing list. Friendly note saying, "hey guys
Brian wrote:
> Would be good to mail the list before blindly implementing.
I started on it one night while I was offline, and did some more work this
evening.
It isn't an implementation, it's a raw port from Ruby to Node.js.
> Both Michael and I have WIP to do the very same so we're triply d
Would be good to mail the list before blindly implementing. Both Michael
and I have WIP to do the very same so we're triply duplicating effort. =(
I'll let Mike chime in on direction. My thing was to understand the space.
Yours/his could be good candidates for the next gen.
Also: frustration note
What¹s the status of https://issues.apache.org/jira/browse/CB-876 ?
The current Ruby requirement frustrated me, so I started blindly porting
cordova-docs/lib to Node.js:
https://github.com/jsoref/cordova-docs/tree/docs_as_node_js
It doesn¹t actually work, but I suspect that in another day or so
