The ARP Advisory Committee is comprised of leading Flash, Flex and RIA developers who use ARP. All advisory committee members have commit rights for ARP’s Advisory branch in the ARP labs.
Different committee members may have different focus areas within ARP and more information on each committee member may be found on their individual profile pages, when they are ready.
Following up on the talk we had last week regarding personal spaces in the repository, the repository has been rearranged. Here is it’s new structure (which you can see by doing an update on your local copy):
/trunk - The main (stable) ARP branch | | | |_ /actionscript - ARP packages live here | |_ /docs - (possibly in the future) | |_ /examples - (sample applications; not there yet) /branches - Branches of the main trunk will be kept here | | | |_ /advisory - Currently the only branch. This is the main advisory branch. | | Only commit here after discussing it with the list. | | Changes here will most likely be merged into the trunk. | |_ /actionscript - ARP packages live here | |_ etc. (/docs, /examples, etc. -- all folders as in the trunk) /labs - This is where you can create your own lab and use it to experiment, etc. | | These are *not* branches (although you can set up your own branch in there | | if you want, like Peter has). All code committed must compile. | | | |_ phall - Peter's lab. | |_ abalkan - Aral's lab. | |_ etc. /tags - These are release builds. (none yet.)
In Subversion, there is actually no difference between doing a copy, branching and creating a tag. To copy a folder with TortoiseSVN, choose TortoiseSVN → Branch/Tag... Note that if you carry out the copy/branch/tag on the server, you have to Update to see get the latest changes.
Remember to use the TortoiseSVN→Delete option if you ever want to delete a *folder* (instead of just deleting it Windows Explorer.) You can delete regular *files* using Explorer if you wish.
Lab(s) are your own personal space. You can use them to experiment, share ideas, etc. but *they are not branches*. Once the advisory agrees that a certain experimental feature in someone’s lab should be added to the advisory branch (of which there is only one), it will be added there. Once fully documented, tested, etc. in the advisory branch, changes may be merged into the trunk.
You all have commit rights on the advisory branch and on the labs folder. Please create your own labs using the <first initial><last name> convention to follow the structure of your usernames.
The most important thing to remember is that the repository is *not* an alternative to communication. It is a tool that allows us to work on ARP together but please use the Advisory mailing list to communicate. There are no stupid questions/threads – when in doubt, ask! When not in doubt... still ask! :)