Page MenuHome

Plane Track Deform node
ClosedPublic

Authored by Shubham Gupta (shubham0209) on Apr 22 2016, 8:49 AM.

Details

Summary

Added the plane track deform node

Diff Detail

Repository
rBM Blender Manual

Event Timeline

Shubham Gupta (shubham0209) retitled this revision from to Plane Track Deform node.
Shubham Gupta (shubham0209) updated this object.

To use this node, plane track documentation is needed, which is currently not updated. Is anyone working on that? if not, shall I update it? I believe I have to notify people that I am updating it. Any ideas how to do that?

@Shubham Gupta (shubham0209) I was going to work on it but I found that I don't have enough knowledge of the area. So I would love some help on this. There is also a task for it, see T42937

Shubham Gupta (shubham0209) edited edge metadata.

Made it more consistent

Aaron Carlisle (Blendify) edited edge metadata.

Looks go to me.

This revision is now accepted and ready to land.Apr 22 2016, 9:10 PM

I got a few questions. What is repository, and is there a list of repositories available somewhere? How to commit a diff? Who all can commit a diff?

Shubham Gupta (shubham0209) set the repository for this revision to rBM Blender Manual.
  1. Setting the repository is not needed. (Definition is a location for storage, often for safety or preservation. This is where all the .rst files for the manual are stored on a server to be compiled whenever an update is made)
  1. Here is a list of Blender's repositories: https://developer.blender.org/diffusion/
  1. How to commit, you must first have commit rights (see #4) then you can use svn to commit with svn commit -m "Commit message" (See http://openoffice.apache.org/svn-basics.html#committing-a-file) However, most of the time I just use a GUI client such as Smart SVN for windows to manage this.
  1. Anyone who belongs to the Documentation project has commit rights to rBM and rBMT
This revision was automatically updated to reflect the committed changes.

So, do I have to claim a project to commit?

Currently, I have tried both the CLI and GUI method and it is not committing.

Like I said in #4 you must belong to Documentation to be able to commit. Only an administrator has access to add people to the task. (Something I am not)

How would you know if you belong or not?