Comments (5)
As someone interested in this project, I think you can manage code flow however you want! As a GSOC mentor, my only concern would be that piling up requests for code reviews on your own repo not slow you down if the reviews are slower than your coding.
Keep in mind that official GSOC coding doesn't begin until May 30th, so official code reviews shouldn't start until then at the earliest.
Also remember that members of the Processing team may not have availability to participate in PRs until that time -- this is the "Community Bonding" period. You can still generate PRs even just for yourself when I'm not available, but I would also suggest that you first invite core Processing members -- like @benfry, @REAS, and @shiffman, and whoever expresses interest -- and ask them whether they suggest using PRs for this repository during GSOC, and if so how, and who participates in them.
from processing.r.
Sounds like more work for yourself to work via PRs—I'd echo @jeremydouglass to say work in whatever way makes you most efficient. Then if/when you need input, it's easy to @ tag us on commits/notes/whatever when you need input on something.
from processing.r.
OK, I know. To improve the code quality of Processing.R, I have imported codacy as an automated code review tool. My goal is to keep the code readable. If I need some suggestions I will use @ in the corresponding PR :)
Thanks for your explanation :)
from processing.r.
My goal is to keep the code readable.
Yes, feel free to use @ in PRs if you have readability concerns and prefer to get feedback in that way.
You can also bring up general discussions of code style and best practices for Processing in general on the forum, or ask for feedback on code style policies on a wiki page in this repo. Most code will be Java, but example code will be R, so there are two related issues here: following project Java style, and adopting a readable R style as discussed in #52
For Java style, also keep in mind that spending time browsing the Processing repo is a great way to get a sense of how the Processing Foundation uses Java. Processing.R should be consistent with itself first, but after that it can try to be consistent with the code style of the larger project.
from processing.r.
Just as a note -- for the Java side of style, Processing also has its own style guide, recently updated:
https://github.com/processing/processing/wiki/Style-Guidelines
The most important thing is that the Processing.R mode be self-consistent. After that, the Processing Style Guidelines are a good reference for the in-house Java style of the Processing Foundation.
from processing.r.
Related Issues (20)
- println() not working HOT 1
- Docs: Tutorials do not list author
- Docs: resolve laDefense.jpg HOT 5
- Support PVector
- Support Table in R HOT 1
- Add GitMate Support
- R Style API HOT 1
- [maintenance] Transfer the project to processing-r and invite Jeremy to be the first official maintainer HOT 2
- Processing.R mode not detected in contributions manager HOT 5
- Build instructions HOT 13
- Update readme.md badge stack HOT 3
- Update windows build versions (processing, ant)
- Transfer codacy integration to codacy org
- Remove RLangMode.zip from repo HOT 1
- Add ribbon nav connecting other Processing sites
- get(), set() -- cast double to int
- Getting this running with Processing 4.0 HOT 5
- example SineWave fails with SketchException
- example He_Mesh/demo incorrectly packaged, fails to run
- processing.R not compatible with R version 3.6.3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from processing.r.