Hi Uli,

you need to be at least JazzProjectAdmin to create projects.

However, to play around with sourcecode you don't need your own project. Team members can create their own streams and components in a project area, provided they have the permissions in the project area.

I think creating a project is something that a normal user would most likely never want to do. If the project is created and this user is admin in the project it is possible to grant the permissions within the project to roles, manage roles, users etc. As Administrator there he can grant himself permissions, should they are not available.

Currently the Clients supported with SCM are Web, Eclipse and Visual Studio. You need one of these clients to version files. There is a work item for a simple client (such as Turtoise), but we don't have it yet.

It is possible to work with Eclipse for loading the workspaces and edit the files outside of Eclipse. In this case you need to refresh in Eclipse so that it detects the files have been changed outside.

Another way to do what you want would be to load the file from the web UI, edit it and upload the changed file again later.

Thanks,

Ralph

Hi!

Note up front: I'm very new to RTC 3.0 but otherwise an experienced SVN user. I'm currently struggling a bit with how to do things in RTC that I did earlier.
One of the things is that I just want to create a small test program in order to test version control (push/pull changes, branching, merging, conflict resolution etc). Looking at "Getting Started with Jazz Source Control", it seems that I need JazzAdmin authorization in order to create a project as base, which seems ridiculous concerning that people now and then create test projects mostly for their own use but still want version control.

Another thing is that RTC seems very Java/Eclipse-centered. It took me lots of trying and searching before I found how to convince the UI that the files I changed in my favourite editor are changed and that I might want to check them in. It was equally frustrating to just add a file that I copied into the workspace. Can it be that people not using an Eclipse project are more or less out of luck?


Am I missing something here? How do you deal with things like that?

Thanks!

Uli

Hi Uli,

I should have said once a user is member of a project, to version private sourcecode, a user don't need a private project.

Essentially any user with the right permissions can share code in a repository workspace and potentially a stream for versioning.

Ralph

However, to play around with sourcecode you don't need your own project. Team members can create their own streams and components in a project area, provided they have the permissions in the project area.