[For review purpose]

.readthedocs.yml

@@ -26,7 +26,7 @@ build:
     - cp -r demos docs/source/demos
     - cp README.md docs/source/README.md
     - cp ARCHITECTURE.md docs/source/ARCHITECTURE.md
-    - cp CONTRIBUTE.md docs/source/CONTRIBUTE.md
+    - cp CONTRIBUTING.md docs/source/CONTRIBUTING.md
     - cp DEVELOP.md docs/source/DEVELOP.md
 
     # build html

ARCHITECTURE.md

@@ -1,6 +1,6 @@
 # Architecture
 
-This document should help get started with modifying code. See also [develop.md](DEVELOP.md) for developer commands and [CONTRIBUTE.md](CONTRIBUTE.md) for community guidelines.
+This document should help get started with modifying code. See also [develop.md](DEVELOP.md) for developer commands and [CONTRIBUTING.md](CONTRIBUTING.md) for community guidelines.
 
 ## Client/Server Wrangling Tool
 

CHANGELOG.md

@@ -7,9 +7,57 @@ This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
 
 ## [Development]
 
+## [0.35.3 - 2024-12-24]
+
+### Docs
+
+* Rename CONTRIBUTE.md to CONTRIBUTING.md to match OSS standards (snyk)
+* setup.py: add project_urls
+* Add FUNDING.md
+* Add CODE_OF_CONDUCT.md
+
+### Feat
+
+* GFQL serialization: Edge AST node deserializes as more precise `ASTEdge` subclasses
+
+### Fixes
+
+* GFQL Hop: Detect #614 of node id column name colliding with edge src/dst id column name and raise `NotImplementedError`
+* MyPy: Remove explicit type annotation from Engine
+
+## [0.35.2 - 2024-12-13]
+
+### Docs
+
+* Python remote mode notebook: Fixed engine results
+* Python remote mode: Add JSON example
+
+## [0.35.1 - 2024-12-11]
+
+### Fixes
+
+* Fix broken imports in new GFQL remote mode
+
+## [0.35.0 - 2024-12-10]
+
 ### Docs
 
 * New tutorial on GPU memory management and capacity planning in the GPU section
+* New tutorial on remote-mode GFQL
+* New tutorial on remote-mode Python
+
+### Feat
+
+* `plot(render=)` supports literal-typed mode values: `"auto"`, `"g"`, `"url"`, `"ipython"`, `"databricks"`, where `"g"` is a new Plottable
+* Remote metadata: Expose and track uploaded `._dataset_id`, `._url`, `._nodes_file_id`, and `._edges_file_id`
+* Remote upload: Factor out explicit upload method `g2 = g1.upload(); assert all([g2._dataset_id, g2._nodes_file_id, g2._edges_file_id])` from plot interface
+* Remote dataset: Remote dataset binding via `g1 = graphistry.bind(dataset_id='abc123')`
+* Remote GFQL: Remote GFQL calls via `g2 = g1.chain_remote([...])` and `meta_df = g1.chain_remote_shape([...])`
+* Remote GPU Python: Remote Python calls via `g2 = g1.python_remote_g(...)`, `python_remote_table()`, and `python_remote_json()` for different return types
+
+### Changed
+
+* `plot(render=)` now `Union[bool, RenderMode]`, not just `bool` 
 
 ## [0.34.17 - 2024-10-20]
 

CODE_OF_CONDUCT.md

@@ -0,0 +1,29 @@
+# PyGraphistry Code of Conduct
+
+PyGraphistry is an open-source project built on collaboration and respect. This Code of Conduct lays out how we expect everyone to interact so we can maintain a positive and productive environment.
+
+## How We Work Together
+
+- Treat others decently—listen, respond constructively, and keep it professional.
+- Stay focused on ideas and solutions, not personal disagreements.
+- Be helpful, especially to newcomers or those asking for clarification.
+
+## What’s Not Okay
+
+Harassment, personal attacks, or sharing private information without permission are not okay. Be respectful and avoid language or behavior that alienates or disrupts others.
+
+## Where This Applies
+
+This Code of Conduct applies to all spaces related to the PyGraphistry project, like GitHub repositories, pull request discussions, and private communications. If you’re representing PyGraphistry in public (e.g., social media or events), we expect the same standards of behavior.
+
+## If There’s a Problem
+
+If you see or experience behavior that doesn’t align with this Code of Conduct, let us know at **[[email protected]](mailto:[email protected])**. We’ll handle it privately and work together to figure out the next steps.
+
+## What Happens Next
+
+Breaking the rules? We’ll handle it case by case. You might get a warning, a temporary ban, or permanent removal from the project.
+
+---
+
+Thanks for being part of PyGraphistry!

DEVELOP.md

@@ -1,6 +1,6 @@
 # Development Setup
 
-See also [CONTRIBUTE.md](CONTRIBUTE.md) and [ARCHITECTURE.md](ARCHITECTURE.md)
+See also [CONTRIBUTING.md](CONTRIBUTING.md) and [ARCHITECTURE.md](ARCHITECTURE.md)
 
 Development is setup for local native and containerized Python coding & testing, and with automatic GitHub Actions for CI + CD. The server tests are like the local ones, except against a wider test matrix of environments.
 

FUNDING.md

@@ -0,0 +1,32 @@
+# Supporting PyGraphistry
+
+PyGraphistry is an open-source Python project proudly sponsored by [Graphistry](https://www.graphistry.com), a leader in GPU-accelerated visual graph analytics and AI. Your support helps us maintain and expand PyGraphistry as a free and open tool for the data science and graph analytics community.
+
+## How to Support
+
+If your organization uses PyGraphistry or benefits from GPU-accelerated analytics, please consider supporting this project indirectly by becoming a customer or directly such as through code contributions and sponsored development. Reach out to the Graphistry team to discuss sponsorship opportunities:
+
+- Email: [[email protected]](mailto:[email protected])
+- Website: [Graphistry Sponsorship](https://www.graphistry.com)
+- Social: Say hello and stay connected via the [community Slack](https://join.slack.com/t/graphistry-community/shared_invite/zt-53ik36w2-fpP0Ibjbk7IJuVFIRSnr6g), [Twitter](https://twitter.com/graphistry) account, & [LinkedIn](https://www.linkedin.com/company/graphistry)
+
+## Why Support PyGraphistry?
+
+Your contributions help us:
+- Keep PyGraphistry maintained, up-to-date, and secure
+- Be responsive to user feedback, bug reports, and feature requests
+- Advance PyGraphistry's capabilities, performance, and usability
+- Ensure the project remains free and open-source
+- Support the community through documentation, tutorials, and responsive issue tracking
+
+## Corporate Sponsorship Opportunities
+
+We welcome sponsorships from companies that depend on PyGraphistry for analytics, visualization, and AI. Sponsorships may include:
+- Recognition in PyGraphistry's release notes and documentation
+- Early access to new features and roadmap acceleration
+- Collaboration opportunities with the Graphistry team
+
+## Thank You
+
+A huge thanks to the Graphistry team and community for supporting PyGraphistry, and to all our users for their continued support!
+

README.md

@@ -207,5 +207,5 @@ Explore [10 Minutes to PyGraphistry](https://pygraphistry.readthedocs.io/en/late
 
 ## Contribute
 
-See [CONTRIBUTE](https://pygraphistry.readthedocs.io/en/latest/CONTRIBUTE.html) and [DEVELOP](https://pygraphistry.readthedocs.io/en/latest/DEVELOP.html) for participating in PyGraphistry development, or reach out to our team
+See [CONTRIBUTING](https://pygraphistry.readthedocs.io/en/latest/CONTRIBUTING.html) and [DEVELOP](https://pygraphistry.readthedocs.io/en/latest/DEVELOP.html) for participating in PyGraphistry development, or reach out to our team