Skip to content
This repository has been archived by the owner on Sep 15, 2021. It is now read-only.

Rewrite of Skydoc #102

Closed
laurentlb opened this issue Jul 19, 2018 · 7 comments
Closed

Rewrite of Skydoc #102

laurentlb opened this issue Jul 19, 2018 · 7 comments
Assignees

Comments

@laurentlb
Copy link
Contributor

We plan to rewrite Skydoc using a real Skylark interpreter (instead of Python).

@nataliejameson
Copy link

Is there a timeline or anything for this? I have a few features I'd like to add, but it'd kind of suck if they were immediately obsoleted :)

@laurentlb
Copy link
Contributor Author

@c-parsons has a prototype (see recent pull requests).
I would discourage you from doing any meaningful development on the Python code.

@nataliejameson
Copy link

So looking through here: 1946693 does that mean that all development is going to instead be done in the bazel repo?

@c-parsons
Copy link
Contributor

In the short/medium term, yes. Long term we want to move the source code / packages to the skydoc repository (or alternatively the Starlark repository)
..but there's still a lot of work to do to separate the source out from bazel packages.

@c-parsons
Copy link
Contributor

We've announced launch of Stardoc on bazel-dev@googlegroups.com and updated the documentation in https://skydoc.bazel.build
We'll follow up to make a release announcement alongside a Bazel release, and then remove skydoc and its documentation.

@dgoldstein0
Copy link

so... this shipped? should this issue be closed?

@c-parsons
Copy link
Contributor

Yeah -- sure. I was keeping it open for a release annoucement and subsequent removal of old-Skydoc, but I can track that elsewhere.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants