RSGallery2 Support Forums
Welcome, Guest. Please login or register.

Login with username, password and session length
  Home    Forum    Help    Search    Login    Register  
*
News : November 22, 2008, 04:02:33 pm
+  RSGallery2 Support Forums
|-+  Developers corner
| |-+  Nightly Builds for RSGallery2 Legacy, J1.5 or J1.0 - Now Reopened! (Moderators: Daniel Tulp, Chef Groovy)
| | |-+  Where is SVN repository?
Advanced search
  « previous next »
Pages 1
Author
Topic: Where is SVN repository?  (Read 6124 times)
« on: December 08, 2006, 06:36:46 am »
Sorin Sbārnea Offline
Newbie
*
Posts: 4

View Profile Email

I would like to know where is the SVN repository? And maybe in the "near" future how could I obtain write access to it?

Until then I would like to know the location in order to do a checkout. Downloading every day snapshot is for fools only Smiley (no offense).
Logged
 
Reply #1
« on: December 08, 2006, 06:49:00 am »
Ronald Smit Offline
Administrator
Hero Member
*****
Posts: 1214

View Profile WWW Email

First of all we do take offense.

The people that download the latest Nightly Build are a crucial group of people that give feedback on the immediate development progress. Without them the component would not be where it is today. I am sure they don't consider themselves as fools.

The SVN is located in the Joomla Forge and is accessible to the Development Team only.
If you wan't to obtain write access to it, you can start by browsing though the forum and help the people that come here with problems they have by fixing small bugs and providing us with the code. That way we can assess your coding skills and you might be able to apply for a development membership.

So ironically, the way you can show us how your coding skills are and prove you would be an asset to the Development Team is by starting to download the Nightly Builds and test them. If you come accross any sort of bugs, you can start providing fixes for that in the forum.

To help you understand the component you can check out the API on the website, this is updated regularly.

Good luck,





Logged

Ronald Smit
RSGallery2 Developer
FAQ|Known issues
 
Reply #2
« on: December 08, 2006, 07:22:23 am »
Sorin Sbārnea Offline
Newbie
*
Posts: 4

View Profile Email

Here is my point:it take a lot of time to install a nigtly build (especially if you want to manually update the components in joomla). Using SVN to update is almost instantly and it takes only one command.

I've been contributor to many open source projects (like OOo) and all have open access to the repository (read-only). I don't see any reason why the read only access should be limited.

I know that obtaining write access takes time and I agree - it should take enough time in order to prove that the newbie is understanding the project and the development direction.

What I want to remark here is that every "tester" is loosing ~30minutes/day updating the sources - this time can be used in detecting and repairing bugs.

I've just discovered that the SVN is open and I've done a full checkout. COOL

Please write a like on the http://rsgallery2.net/content/view/55/16/ and tell the people that they CAN do a checkout. It's far more productive Smiley

PS. Updating OOo using svn is not quite instantly Smiley
Logged
 
Reply #3
« on: December 08, 2006, 07:38:46 am »
Sorin Sbārnea Offline
Newbie
*
Posts: 4

View Profile Email

I think that the step #3  ("Do not try to install them, instead copy the files over the old ones.") is quite a hard job.
There is no bash/cmb batch for doing this? I supose it's not.
I'll make one myself and send it to your.

Here is how i see the better way:

First time install
1. check out the svn (one line)
2. run the install batch to copy the checkout module to joomla structure (will copy the .svn directories too, very important)

Repetitive update task
3. svn update in the joomla root installation - this will update it. (Yes you can have multiple combined svn projects in the same directory tree)

How about that?
Logged
 
Reply #4
« on: December 08, 2006, 07:53:56 am »
Sorin Sbārnea Offline
Newbie
*
Posts: 4

View Profile Email

Oops it seams that there is a problem with this: in svn you can have same thing like this:
/myproject/                        -> repository_a/
/myproject/subdir1/             -> repository_a/subdir1/
/myproiect/other/                -> repository_b

if you run an update on root will update the files from both repositories (good so update on joomla root will update modules too)... but

The problem is the current module repository is considered to be the "installer structure" not the "installed structure".
In the current structure we have files in the same directory that must go in different folders. This is NOT GOOD because this way we cannot combine it well.

Joomla XML definitions seams to be limited so the only solution I see is to store the component module in the "installed structure" and to have a small script named "make_release.sh" that will build the release structure and zip it.

How about this?
« Last Edit: December 08, 2006, 09:20:51 am by Sorin Sbārnea » Logged
 
Reply #5
« on: December 08, 2006, 10:28:07 am »
Ronald Smit Offline
Administrator
Hero Member
*****
Posts: 1214

View Profile WWW Email

Sorin,

1. True, the read access to the SVN is open for everyone.
2. Not all testers are using SVN, cause the are not all coders . Some only test layout and logic. Also not every Build is installable, so copying is the safest way. But is not straight forward, i agree.
3. As for the installer and installed structure, this is the standard way an SVN is built if you don't specifically create the structure. This is no problem for the most of us, because we do not edit in the checked out files.
My setup contains a local web development environment (My Sandbox to play around in). When I am satisfied with the coding I us a file merge application to merge my coding into the local repository. This sounds like an extra step but it gives me the opportunity to review the coding once more before adding it to the SVN. After that I do a commit from my local repository to the SVN server.
4. I thought we had the instruction for Read Access there, but you are right: it's not there. I will add this tonight.
5. I will talk about the SVN structure with the team and we'll get back to you on that one.

Cheers,



Logged

Ronald Smit
RSGallery2 Developer
FAQ|Known issues
 
Reply #6
« on: December 12, 2006, 12:12:10 pm »
Jonah Offline
Administrator
Hero Member
*****
Posts: 1412

View Profile


The problem is the current module repository is considered to be the "installer structure" not the "installed structure".
In the current structure we have files in the same directory that must go in different folders. This is NOT GOOD because this way we cannot combine it well.

Joomla XML definitions seams to be limited so the only solution I see is to store the component module in the "installed structure" and to have a small script named "make_release.sh" that will build the release structure and zip it.

How about this?

Thanks for your involvement and feedback Sorin, it is always appreciated.

We've debated SVN structure before.  As a cheap solution what I did on one of my dev machines is a script that did a checkout and copy all the files into both directories.

I don't do that anymore however.  What I have now is a script that creates installer files from the SVN.  Then I just uninstall and install.  If the installer breaks, it's the first thing I fix.

I would advise using one of those two methods.

I can't see the SVN structure changing at this point.  It's the standard Joomla way of keeping your SVN for components and modules.  The reason it is like that is because most devs find it the best.
Logged

Due to time constraints, I have taken a step back from RSGallery2.  In the event of an emergency, you will need to PM me.
 
Print  Pages 1
« previous next »
Jump to: