Recherche avancée

Médias (91)

Autres articles (69)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Installation en mode standalone

    4 février 2011, par

    L’installation de la distribution MediaSPIP se fait en plusieurs étapes : la récupération des fichiers nécessaires. À ce moment là deux méthodes sont possibles : en installant l’archive ZIP contenant l’ensemble de la distribution ; via SVN en récupérant les sources de chaque modules séparément ; la préconfiguration ; l’installation définitive ;
    [mediaspip_zip]Installation de l’archive ZIP de MediaSPIP
    Ce mode d’installation est la méthode la plus simple afin d’installer l’ensemble de la distribution (...)

  • Le plugin : Gestion de la mutualisation

    2 mars 2010, par

    Le plugin de Gestion de mutualisation permet de gérer les différents canaux de mediaspip depuis un site maître. Il a pour but de fournir une solution pure SPIP afin de remplacer cette ancienne solution.
    Installation basique
    On installe les fichiers de SPIP sur le serveur.
    On ajoute ensuite le plugin "mutualisation" à la racine du site comme décrit ici.
    On customise le fichier mes_options.php central comme on le souhaite. Voilà pour l’exemple celui de la plateforme mediaspip.net :
    < ?php (...)

Sur d’autres sites (6484)

  • We are hiring engineers to build an awesome product and platform used by millions of people

    16 février 2016, par Piwik Core Team — Uncategorized

    Are you ready for a new challenge ? Or maybe you know someone who is looking for a change ? We have some exciting problems to solve and are looking for senior developers to work with us and our community on our open source Piwik Analytics platform. Piwik is used by more than one million websites all over the world. It is deployed on more than 300.000 servers and some users track more than 1 billion actions per month.

    What is it like to work on Piwik ?

    We develop this software using modern PHP, MySQL, Redis, AngularJS and more. We provide several kind of APIs and a plugin architecture to allow developers to extend and change Piwik to their needs. However, we would not be Piwik if we stopped at this point ! We want to turn Piwik into an even more awesome product and platform.
    You can imagine there is a lot to do and many challenges to face !

    While one part is to always make Piwik scale better and to improve UI and UX, we also want to provide simple APIs to make the life of developers as pleasant as possible. We aim to solve things the right way and our thousands of unit, integration, system, JavaScript and screenshot tests help us to innovate and to not be afraid of change. We like clean code and constant improvements.

    The Piwik team lives in New Zealand and Europe (Germany). We do the vast majority of our collaboration online. Our values include being open, transparent and sharing knowledge. For this we use tools like GitHub and Slack to communicate and Quake servers to take our minds off complex challenges. We are a small, flexible team, so when you come aboard, you will play an integral part in engineering and have a big impact on the product loved by so many people. You’ll help to create a welcoming environment for new contributors and set an example with your development practices and communications skills.

    Apply now, or spread the word !

    If you have strong skills in PHP send us an email with your CV and tell us a little about yourself and your experience in engineering complex applications.

    Apply for a job here http://piwik.org/jobs/ and if you’re maybe not the right candidate, contribute to the project by sharing this blog post and by sending it to your friends !

  • Unable to 'make' android ndk project - build fails : [build-openh264-x86] Error 2

    18 décembre 2015, par NoobNinja

    I’ve attempted these two fixes I’ve found while researching the issue :

    android update project  --23 --/Users/ajswann/Downloads/android-sdk-macosx

    make OS=android NDKROOT=/Users/ajswann/Downloads/android-sdk-macosx TARGET=android-19 ARCH=x86 clean

    ...however neither seems to resolve the issue.

    Any input/suggestions are appreciated.

    P.S.

    I’m running OSX - could this be an issue with attempting to run an x86 architecture on a 64 bit machine ?

    Error Message :

    chris-mini-mac:linphone-android ajswann$ sudo make
    ls: /opt/local/etc/openssl/certs: No such file or directory
    /Users/ajswann/Downloads/android-sdk-macosx/tools/android update project --path . --target android-23
    Updated project.properties
    Updated local.properties
    build.xml: Found version-tag: custom. File will not be updated.
    Updated file ./proguard-project.txt
    It seems that there are sub-projects. If you want to update them
    please use the --subprojects parameter.
    /Users/ajswann/Downloads/android-sdk-macosx/tools/android update test-project --path tests -m .
    Resolved location of main project to: /groupchat/linphone-android/tests
    Updated project.properties
    Updated local.properties
    Updated file tests/proguard-project.txt
    Updated ant.properties
    /Users/ajswann/Downloads/android-sdk-macosx/tools/android update project --path liblinphone_tester --target android-23
    Updated project.properties
    Updated local.properties
    Updated file liblinphone_tester/proguard-project.txt
    ant -e -S clean
    Buildfile: /groupchat/linphone-android/build.xml
    No sub-builds to iterate on
    mkdir -p /groupchat/linphone-android/submodules/externals/openh264/include/wels
    rsync -rvLpgoc --exclude ".git"  /groupchat/linphone-android/submodules/externals/openh264/codec/api/svc/* /groupchat/linphone-android/submodules/externals/openh264/include/wels/.
    building file list ... done

    sent 156 bytes  received 20 bytes  352.00 bytes/sec
    total size is 56216  speedup is 319.41
    mkdir -p /groupchat/linphone-android/submodules/externals/build/openh264
    mkdir -p /groupchat/linphone-android/submodules/externals/build/openh264/arm
    cd /groupchat/linphone-android/submodules/externals/build/openh264/arm \
       &amp;&amp; rsync -rvLpgoc --exclude ".git"  /groupchat/linphone-android/submodules/externals/openh264/* .
    building file list ... done

    sent 18841 bytes  received 20 bytes  37722.00 bytes/sec
    total size is 48272799  speedup is 2559.40
    cd /groupchat/linphone-android/submodules/externals/build/openh264/arm &amp;&amp; \
       make libraries -j4 OS=android ARCH=arm NDKROOT=/Users/ajswann/Downloads/android-ndk-r10e TARGET=android-19
    cd ./ &amp;&amp; sh ./codec/common/generate_version.sh
    Keeping existing codec/common/inc/version_gen.h
    mkdir -p /groupchat/linphone-android/submodules/externals/build/openh264
    mkdir -p /groupchat/linphone-android/submodules/externals/build/openh264/x86
    cd /groupchat/linphone-android/submodules/externals/build/openh264/x86 \
       &amp;&amp; rsync -rvLpgoc --exclude ".git"  /groupchat/linphone-android/submodules/externals/openh264/* .
    building file list ... done

    sent 18841 bytes  received 20 bytes  12574.00 bytes/sec
    total size is 48272799  speedup is 2559.40
    cd /groupchat/linphone-android/submodules/externals/build/openh264/x86 &amp;&amp; \
       make libraries -j4 OS=android ARCH=x86 NDKROOT=/Users/ajswann/Downloads/android-ndk-r10e TARGET=android-19
    cd ./ &amp;&amp; sh ./codec/common/generate_version.sh
    nasm -DX86_32 -f elf -I./codec/common/x86/   -o codec/decoder/core/x86/dct.o codec/decoder/core/x86/dct.asm
    codec/decoder/core/x86/dct.asm:1: error: label or instruction expected at start of line
    codec/decoder/core/x86/dct.asm:144: error: label or instruction expected at start of line
    codec/decoder/core/x86/dct.asm:234: error: symbol `IdctResAddPred_mmx' redefined
    codec/decoder/core/x86/dct.asm:262: error: symbol `WelsBlockZero16x16_sse2' redefined
    codec/decoder/core/x86/dct.asm:276: error: symbol `WelsBlockZero8x8_sse2' redefined
    codec/decoder/core/x86/dct.asm:287: error: label or instruction expected at start of line
    make[1]: *** [codec/decoder/core/x86/dct.o] Error 1
    make[1]: *** Waiting for unfinished jobs....
    Keeping existing codec/common/inc/version_gen.h
    make[1]: *** wait: No child processes.  Stop.
    make: *** [build-openh264-x86] Error 2

    Source Repository (I simply clone it, add the platform-tools and tools folder from my android-sdk and run ’make’ and I get this error) :

    https://github.com/TheBaobabTeam/linphone-android

  • We are hiring engineers to build an awesome product and platform used by millions of people

    16 février 2016, par Piwik Core Team — Jobs

    Are you ready for a new challenge ? Or maybe you know someone who is looking for a change ? We have some exciting problems to solve and are looking for senior developers to work with us and our community on our open source Piwik Analytics platform. Piwik is used by more than one million websites all over the world. It is deployed on more than 300.000 servers and some users track more than 1 billion actions per month.

    What is it like to work on Piwik ?

    We develop this software using modern PHP, MySQL, Redis, AngularJS and more. We provide several kind of APIs and a plugin architecture to allow developers to extend and change Piwik to their needs. However, we would not be Piwik if we stopped at this point ! We want to turn Piwik into an even more awesome product and platform.
    You can imagine there is a lot to do and many challenges to face !

    While one part is to always make Piwik scale better and to improve UI and UX, we also want to provide simple APIs to make the life of developers as pleasant as possible. We aim to solve things the right way and our thousands of unit, integration, system, JavaScript and screenshot tests help us to innovate and to not be afraid of change. We like clean code and constant improvements.

    The Piwik team lives in New Zealand, Europe (Poland, Germany) and in the U.S. We do the vast majority of our collaboration online. Our values include being open, transparent and sharing knowledge. For this we use tools like GitHub and Slack to communicate and Quake servers to take our minds off complex challenges. We are a small, flexible team, so when you come aboard, you will play an integral part in engineering and have a big impact on the product loved by so many people. You’ll help to create a welcoming environment for new contributors and set an example with your development practices and communications skills.

    Apply now, or spread the word !

    If you have strong skills in PHP send us an email with your CV and tell us a little about yourself and your experience in engineering complex applications.

    Apply for a job here http://piwik.org/jobs/ and if you’re maybe not the right candidate, contribute to the project by sharing this blog post and by sending it to your friends !