Commit 7dccd6d1 authored by Jean-Loup Haberbusch's avatar Jean-Loup Haberbusch
Browse files

UPDATED CEP

parent 47714abf
Pipeline #16658 passed with stages
in 25 seconds
......@@ -127,9 +127,8 @@ If your CEP is still in the incubator, you don’t need to think too hard
about its Copyright and the license under which it will
distributed.
| | |
| :---------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| rowspan = “2”| [32px|left](/File:Note.png "wikilink") | When possible, we encourage you to do nothing, i.e., to leave the COPYRIGHT file untouched. Which means that your CEP will be available under the LGPL-v3 license. You don’t need to decide at the beginning if your CEP can/should be distributed as an Open-Source CEP, but it won’t hurt to start thinking about it. |
!!! note
When possible, we encourage you to do nothing, i.e., to leave the COPYRIGHT file untouched. Which means that your CEP will be available under the LGPL-v3 license. You don’t need to decide at the beginning if your CEP can/should be distributed as an Open-Source CEP, but it won’t hurt to start thinking about it. |
If for any reason you think you can not keep the LGPL-v3, please **do
not forget** to edit COPYRIGHT
......@@ -137,9 +136,8 @@ accordingly.
#### Note on CEPS tree structures
| | |
| :---------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| rowspan = “2”| [32px|left](/File:Note.png "wikilink") | For CEP Set, the build and install should be at the top level of the CEP Set, i.e. one level higher than the CEP directories. Consequently there is no src subdirectories. |
!!! note
For CEP Set, the build and install should be at the top level of the CEP Set, i.e. one level higher than the CEP directories. Consequently there is no src subdirectories. |
## CEP maturing
......@@ -147,18 +145,17 @@ When you are first working on a CEP, this one might not be ready to be
publicly visible, this is why it might to be developed a bit more. This
step of maturation is called CEP “incubation”.
[center](/Image:CEPIncubator.png "wikilink")
![center](./assets/CEPIncubator.png)
### Incubators location
Incubators are svn location where you may host your source code to
Incubators are svn and Git location where you may host your source code to
mature it. At the moment, 2 incubators are proposed:
\* One public, where you may host your CEP containing extensions that
are
open-source.
are open-source.
``` bash
svn checkout svn+ssh://login@scm.forge.imag.fr/var/lib/gforge/chroot/scmrepos/svn/camitk/trunk/incubator
```bash
git clone git@gricad-gitlab.univ-grenoble-alpes.fr:CamiTK/CamiTK-Incubator/albert.git
```
......@@ -167,7 +164,7 @@ the TIMC laboratory. Use this incubator if your CEP keeps copyrighted
source
code
``` bash
```bash
svn checkout svn+ssh://login@svn-timc.imag.fr/svn/gmcao/camitk/trunk/camitktimc/incubator-local
```
......@@ -175,14 +172,9 @@ svn checkout svn+ssh://login@svn-timc.imag.fr/svn/gmcao/camitk/trunk/camitktimc/
Do not forget to replace **login** with your actual login and to have
logged into your session your private RSA key (required on the svn-timc
server and optional but convenient on the forge server).
{| style=“color: black; background-color: \#FFFB99;” class=“wikitable” |
rowspan = “2”| [32px|left](/File:Tip.png "wikilink") | colspan=“2” |
If you create a CEP from scratch, use the CEP **skel** located at the
root of any of the incubator. You will find information on how to adapt
it to your own CEP in the **README** file.
|}
!!! tip
If you create a CEP from scratch, use the CEP **skel** located at the root of any of the incubator. You will find information on how to adapt it to your own CEP in the **README** file.
### Maturation stage reached
......@@ -254,7 +246,7 @@ purposes).
[\<File:CepInstallationMaturing.png\>](/File:CepInstallationMaturing.png "wikilink")
![Cep Installation Maturing](./assets/CepInstallationMaturing.png)
## CEP source package
......@@ -302,5 +294,3 @@ the same directory structure as any CamiTK install directory.
camitk-wizard provides a way to automatically build a source code
skeleton for a new CEP. You can also create a new CEP from
scratch.
[Category:Develop\_with\_CamiTK](/Category:Develop_with_CamiTK "wikilink")
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment