chrisranderson / chrisranderson/beholder
Discuss Beholder potentially becoming an officially supported TensorBoard plugin
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 462
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
To: @jart @dandelionmane @wchargin
I think @jart and @dandelionmane both mentioned potentially merging this repo into TensorBoard. Here are some of my questions.
- Would you actually like to merge the repo? What if it was left separate, and I just waited for the plugin system to be changed so that installation was easier? A summary of your view of pros and cons for both parties would be nice.
- What changes in the code would have to happen before a transfer?
- What would the timeline be?
- How will my influence be limited? How would I contribute afterwards? It's been fun to build, and it's a bit sad to me to consider not being able to work on it as much.
- What will happen to this repo?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or implementation entry point is identified. Start by reviewing the Beholder repository and TensorBoard's plugin-system expectations, then document a decision on merging or remaining separate, required code changes, timeline, contribution arrangements, and the future of this repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, tensorflow
- Domain
- data-visualization, machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100