[DG: User Experience] 3akai UX code now available on Github

[Oszkar Nagy]

As the subject suggests, the latest UX code is now available on Github.
We have taken the opportunity to do some cleanup work and updating,
along with the migration, which will settle in by the end of the week.
All the commit history of SVN has been taken over, and we successfully
tested a basic fork -> develop -> check -> merge work-flow with
Christian and Simon. I haven't copied the abandoned branches/tags or
trunk, only the SVN branch we have been using so far.


-------------

The code can be downloaded by clicking on the Download button on:
http://github.com/oszkarnagy/3akai-ux

or by using Git and the following clone URL:
git://github.com/oszkarnagy/3akai-ux.git

--------------


Suggested work-flow:

In general code management should be simple, so I would like to propose
a similar work-flow which Ian is using for kernel development:
I will maintain a master branch available on the addresses above where I
will merge all patches, after reviewing them.
All UX developers should fork my master, do development, commit often
locally then push. When a developer pushed to his/her fork at Github,
should send me a pull request. I will go over the code, and merge it to
my master branch if it does good things and doesn't break other people's
code.

Anybody who would like to help out on front-end development here are
some steps which might help, not specific commands as everybody has
his/her own taste/tools. This served me well so far with the added
security of a clean master branch, but I am still learning:

Initial setup:
  1. Make sure you have Git installed on your machine
  2. Get a Github account (not necessary, but makes your/my life easier)
  3. Fork my master branch on Github, this will be the place where you
put your patch.
  4. Clone your forked 3akai-ux repository to your local machine

Doing development:
  1. Make sure your local 3akai-ux master branch is up to date
  2. Make a new "dev" branch for your new dev work, and switch to it
  3. Do development
  4. Commit
  5. Do some more development
  6. Commit
  7. Switch back to your master branch
  8. Merge in your "dev" branch to your master
  9. push your master to your 3akai-ux fork on Github
10. Send me a pull request



Tags - Demo/Dev/Sandbox servers:
I will create at least one tag per week, every time the UX code reaches
a stable point. This tagged version can go on the sandbox server, where
people can try out the latest stable. If there is a particularly
stable/good tag on the sandbox, it can go to the qa/demo servers which
will hold the most stable kernel+UX code. As for kernel-UX code
integration IMHO the best thing to do is to tag K2 more often, and only
tagged version pairs would go on the servers, treating a tag
conceptually as a mini release. Obviously this is a question for the
back-end guys as well, but I've heard that Ian is planning to tag more
frequently. I'll match up good K2-UX tags as I'll need to test
frequently anyway. I can imagine this working next week, providing we
have the servers ready. Let me know Clay if you need any help on this.

My aim is to establish working practices + finish cleanup work + send
out coding guidelines this week, then concentrate on new designs and
progression from next week.

Comments, ideas more than welcome as always,
Oszkar





_______________________________________________
sakai-ux mailing list
sakai-ux@...
http://collab.sakaiproject.org/mailman/listinfo/sakai-ux

TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"