Loading...
 
[edu.t.o] Development

[edu.t.o] Development

Forum List Topic List

Forums » [edu.t.o] Development » Uniting efforts in AulaWiki (message for Pingus)
 
Thread actions
Print this page
  • Print all pages

    • Uniting efforts in AulaWiki (message for Pingus)

    Posted by MangaPowerX posts: 4 ☆
    Pingus, we have integrated AulaWiki 1.6.5b in the experimental branch of WorkSpaces.
    So, from now on all modifications in AulaWiki MUST be done in this branch, because it's troublesome to handle the modifications that you do by yourself and the ones we do in the branch. Keep it in mind.

    These are the commands you must execute (it's also the same commands, if you work on windows, please install support for svn):
    1 - svn co https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/experimental/workspaces/ workspaces
    (With this you grab the code)

    2.- Then modificate the code that you want. Before you commit you must update, so execute:
    svn up

    3. - If you add a new archive or directory you must to include it in the svn, so you ought to type svn add (directory or file). The same if you want to remove something, svn remove (file or directory)

    4.- When you finished with your work, please type svn commit -m "Type of contribuition The general message"
    Ex: svn commit -m "FIX Fixed one bug in blablabla.tpl"

    For this operations, you don't need a great or megasuper or whatever broadband internet connection. Because you only need to checkout the code one time. After this, if you keep this directory, you only need to do updates with the command svn up (this only will update the files that need to).

    Keep in mind this (it's very easy) and with this, we can collaborate together in the same direction.
    Reads: 26894
    Link
    Posted by pingus posts: 52 ☆ ☆ ☆
    > Pingus, we have integrated AulaWiki 1.6.5b in the experimental branch of WorkSpaces.

    Is it a tikiwiki-3.x tree?

    > So, from now on all modifications in AulaWiki MUST be done in this branch, because it's troublesome to handle the modifications

    Yes, I used cvs on my personal box for large projects. A hell.
    Anyway I installed svn, checked out everything (more than 2 hours, with all the Zend stuff, but interesting) now when I try to commit with the username an passwd I have at tiki.org it obviously says wrong!
    Someone has to put me somewhere so that I can do that.

    In the svn tree, found aulawiki in th mods subdir, and only my 1.6.5b files.
    Meanwhile I've uploaded a 1.6.5d-COMPLETE at the trackers, it's fairly testable, maybe you can commit it before me.


    > For this operations, you don't need a great or megasuper or whatever broadband internet connection. Because you only need to
    Link

    Posted by Roberto López posts: 32 ☆ ☆ ☆
    Pingus,
    It's better you commit to the mods branch. Have a look here wink

    Please, follow this link to get commit access.

    I would say that all these modifications (1.6.5) should be submitted to the mods branch, nor the experimental branch for workspaces. It's better to have a very stable/secure version of aulawiki on the mods branch, that it's going to be very useful for tiki2.x, tiki 3.x users.

    Tiki admins will update the mods.tikiwiki.org repository with the very last version you put on the mods branch.

    For the development of the new workspaces it's better to grab the code we need from the mods repository, step by step.

    So, checkout the mods trunk, and commit your aulawiki 1.6.5 files there one by one.

    Just my opinion biggrin
    Link

    Switch Language