Open qzminski opened 12 years ago
It would also be nice if we could fetch the README file from Github and use it as the description.
I assume you know about this: https://contao.org/en/news/github-import-in-the-extension-repository.html
So basically, your request is only about using the README file's content as description?
There are two issues regarding the current implementation:
The repostory layout must match a sub-structure of TL_ROOT/system/modules/...
But this does not work since a repo may contain another structure, to allow other sources unrelated to content that is subject to ER publishing like test cases and documentation etc.
E.g. my standard Contao extension repo layout is:
publish
Contains publishing materialsdev
Contains development filesext
Contains submodules and other external ressourcestest
Contains test casesTL_ROOT
build.xml
Ant build fileSo what I need is not only to provide the target directory in the ER release, but although a source directory within the specified tag.
Second, insteadof using the README for description text, we could use a file where you can supply all needed settings for publishing a whole release.
E.g. contao-er.xml
<extension name="myext" type="free|commerical|private" ...><!-- creates ext "myext" if not exists -->
<release version="1.1.0 stable" date="now"><!-- creates relase "1.1.0 stable" if not exists -->
<language code="de" translator="Myself"><!-- creates language "de" if not exists -->
<tags>...</tags>
<description>...</description>
<teaser>...</teaser>
</language>
</release>
</extension>
It would be very nice if extension authors could link their modules with repositories. At the moment we all have to export the current repository, pack it to zip and upload. This might become quite wearisome for 5+ extensions.
The idea of connecting repo with extension might be technically a little difficult since many repos are built differently. However, it would be possible if those repos are built on the proposed schema. Otherwise they would just not qualify to be connected.
Once the repo is connect, we could have a little form for publishing a new release: [ s 1.1 ] <- A release version (stable 1.1), text input [ --- Select branch --- [v]] <- 1.0, 1.1, 1.2 [ Import from repository ] <- submit button
What do you think about this idea?