[xwiki-devs] [GSoC] More extension repositories
GSoC Coding Part Finally starts tomorrow, so the highest time to get down to work. I created modest design page where I put summary of general idea of my project: http://design.xwiki.org/xwiki/bin/view/Proposal/Moreextensionrepositories To start coding I need: 1. A confirmed naming pattern for the extensions that I will develop. My suggestion is "..... Integration" e.g. "Pypi Integration" "Bintray Integration" Imho, the names of possible repositories are popular and verbose enough to impy that the integration is about extension repository. What do you think? 2. Repositories on https://github.com/xwiki-contrib One per each extension (i.e. external) repository: Bintray, Pypi, NPM. Is it enough if I ask for it here or should I create some official request? 3. Some space somewhere in XWiki ecosystem where I would be able to document progress and decisions made - things much more detailed and low-level that are normally presented on design pages or http://extensions.xwiki.org/xwiki/bin/view/Extension/ pages. Best, Krzysztof Płachno
On Mon, May 29, 2017 at 5:00 PM, Krzysiek Płachno <[email protected]> wrote:
GSoC Coding Part Finally starts tomorrow, so the highest time to get down to work.
I created modest design page where I put summary of general idea of my project: http://design.xwiki.org/xwiki/bin/view/Proposal/Moreextensionrepositories
You should probably add some link to http://design.xwiki.org/xwiki/bin/view/Design/ExtensionManagerRepositories which have more of less the same goal than your page.
To start coding I need:
1. A confirmed naming pattern for the extensions that I will develop. My suggestion is "..... Integration" e.g. "Pypi Integration" "Bintray Integration" Imho, the names of possible repositories are popular and verbose enough to impy that the integration is about extension repository. What do you think?
I'm not a big fan of the very vague "Integration" term in this context. Does not say much about what the extension does, even when you know what Pypi is (which might not be so obvious for Java folks). I think I would prefer something like "Pypi Extensions Support" but not sure either. Maybe others have some ideas ? Anyway you have time for the extension display name which will be important when you do your first release mostly.
2. Repositories on https://github.com/xwiki-contrib One per each extension (i.e. external) repository: Bintray, Pypi, NPM. Is it enough if I ask for it here or should I create some official request?
I will create 3 repositories. For the repositories names I was thinking about: * repository-pypi * repository-bintray * repository-pypinpm which is in line with the current "<type>-<name>" based naming on http://contrib.xwiki.org/xwiki/bin/view/Main/WebHome#HChoosingthename. WDYT ?
3. Some space somewhere in XWiki ecosystem where I would be able to document progress and decisions made - things much more detailed and low-level that are normally presented on design pages or http://extensions.xwiki.org/xwiki/bin/view/Extension/ pages.
http://design.xwiki.org/xwiki/bin/view/Proposal/Moreextensionrepositories is fine for this IMO. It can be as low level as you want. Once you made your first release then documentation will go to your new extension documentation page on extensions.xwiki.org. Each extension gets a dedicated space on http://extensions.xwiki.org/xwiki/bin/view/Extension/ so you have plenty of room to put as many details as you want and keep something hight level with links to the details in the extension home page.
Best, Krzysztof Płachno
-- Thomas Mortagne
2017-05-29 17:26 GMT+02:00 Thomas Mortagne <[email protected]>:
On Mon, May 29, 2017 at 5:00 PM, Krzysiek Płachno <[email protected]> wrote:
GSoC Coding Part Finally starts tomorrow, so the highest time to get down to work.
I created modest design page where I put summary of general idea of my project: http://design.xwiki.org/xwiki/bin/view/Proposal/ Moreextensionrepositories
You should probably add some link to http://design.xwiki.org/xwiki/bin/view/Design/ExtensionManagerRepositories which have more of less the same goal than your page.
To start coding I need:
1. A confirmed naming pattern for the extensions that I will develop. My suggestion is "..... Integration" e.g. "Pypi Integration" "Bintray Integration" Imho, the names of possible repositories are popular and verbose enough to impy that the integration is about extension
repository.
What do you think?
I'm not a big fan of the very vague "Integration" term in this context. Does not say much about what the extension does, even when you know what Pypi is (which might not be so obvious for Java folks).
I think I would prefer something like "Pypi Extensions Support" but not sure either. Maybe others have some ideas ? Anyway you have time for the extension display name which will be important when you do your first release mostly.
Ok - makes sense ;) "xxxxx Extensions Support" sounds ok as well.
2. Repositories on https://github.com/xwiki-contrib One per each
extension
(i.e. external) repository: Bintray, Pypi, NPM. Is it enough if I ask for it here or should I create some official request?
I will create 3 repositories.
For the repositories names I was thinking about:
* repository-pypi * repository-bintray * repository-pypinpm
which is in line with the current "<type>-<name>" based naming on http://contrib.xwiki.org/xwiki/bin/view/Main/WebHome#HChoosingthename.
WDYT ?
It's ok. Will I have rights to those repos?
3. Some space somewhere in XWiki ecosystem where I would be able to document progress and decisions made - things much more detailed and low-level that are normally presented on design pages or http://extensions.xwiki.org/xwiki/bin/view/Extension/ pages.
http://design.xwiki.org/xwiki/bin/view/Proposal/Moreextensionrepositories is fine for this IMO. It can be as low level as you want. Once you made your first release then documentation will go to your new extension documentation page on extensions.xwiki.org.
Each extension gets a dedicated space on http://extensions.xwiki.org/xwiki/bin/view/Extension/ so you have plenty of room to put as many details as you want and keep something hight level with links to the details in the extension home page.
Ok, then I will put documentation on desing page.
Best, Krzysztof Płachno
-- Thomas Mortagne
On Tue, May 30, 2017 at 11:06 AM, Krzysiek Płachno <[email protected]> wrote:
2017-05-29 17:26 GMT+02:00 Thomas Mortagne <[email protected]>:
On Mon, May 29, 2017 at 5:00 PM, Krzysiek Płachno <[email protected]> wrote:
GSoC Coding Part Finally starts tomorrow, so the highest time to get down to work.
I created modest design page where I put summary of general idea of my project: http://design.xwiki.org/xwiki/bin/view/Proposal/ Moreextensionrepositories
You should probably add some link to http://design.xwiki.org/xwiki/bin/view/Design/ExtensionManagerRepositories which have more of less the same goal than your page.
To start coding I need:
1. A confirmed naming pattern for the extensions that I will develop. My suggestion is "..... Integration" e.g. "Pypi Integration" "Bintray Integration" Imho, the names of possible repositories are popular and verbose enough to impy that the integration is about extension
repository.
What do you think?
I'm not a big fan of the very vague "Integration" term in this context. Does not say much about what the extension does, even when you know what Pypi is (which might not be so obvious for Java folks).
I think I would prefer something like "Pypi Extensions Support" but not sure either. Maybe others have some ideas ? Anyway you have time for the extension display name which will be important when you do your first release mostly.
Ok - makes sense ;) "xxxxx Extensions Support" sounds ok as well.
This question will probably deserve a dedicated mail after thinking a bit about it later.
2. Repositories on https://github.com/xwiki-contrib One per each
extension
(i.e. external) repository: Bintray, Pypi, NPM. Is it enough if I ask for it here or should I create some official request?
I will create 3 repositories.
For the repositories names I was thinking about:
* repository-pypi * repository-bintray * repository-pypinpm
which is in line with the current "<type>-<name>" based naming on http://contrib.xwiki.org/xwiki/bin/view/Main/WebHome#HChoosingthename.
WDYT ?
It's ok. Will I have rights to those repos?
Created them, you have full write on them.
3. Some space somewhere in XWiki ecosystem where I would be able to document progress and decisions made - things much more detailed and low-level that are normally presented on design pages or http://extensions.xwiki.org/xwiki/bin/view/Extension/ pages.
http://design.xwiki.org/xwiki/bin/view/Proposal/Moreextensionrepositories is fine for this IMO. It can be as low level as you want. Once you made your first release then documentation will go to your new extension documentation page on extensions.xwiki.org.
Each extension gets a dedicated space on http://extensions.xwiki.org/xwiki/bin/view/Extension/ so you have plenty of room to put as many details as you want and keep something hight level with links to the details in the extension home page.
Ok, then I will put documentation on desing page.
Best, Krzysztof Płachno
-- Thomas Mortagne
-- Thomas Mortagne
Thanks! KP 2017-05-30 22:42 GMT+02:00 Thomas Mortagne <[email protected]>:
On Tue, May 30, 2017 at 11:06 AM, Krzysiek Płachno <[email protected]> wrote:
2017-05-29 17:26 GMT+02:00 Thomas Mortagne <[email protected]>:
On Mon, May 29, 2017 at 5:00 PM, Krzysiek Płachno <[email protected]> wrote:
GSoC Coding Part Finally starts tomorrow, so the highest time to get down to work.
I created modest design page where I put summary of general idea of my project: http://design.xwiki.org/xwiki/bin/view/Proposal/ Moreextensionrepositories
You should probably add some link to http://design.xwiki.org/xwiki/bin/view/Design/ ExtensionManagerRepositories which have more of less the same goal than your page.
To start coding I need:
1. A confirmed naming pattern for the extensions that I will develop.
My
suggestion is "..... Integration" e.g. "Pypi Integration" "Bintray Integration" Imho, the names of possible repositories are popular and verbose enough to impy that the integration is about extension repository. What do you think?
I'm not a big fan of the very vague "Integration" term in this context. Does not say much about what the extension does, even when you know what Pypi is (which might not be so obvious for Java folks).
I think I would prefer something like "Pypi Extensions Support" but not sure either. Maybe others have some ideas ? Anyway you have time for the extension display name which will be important when you do your first release mostly.
Ok - makes sense ;) "xxxxx Extensions Support" sounds ok as well.
This question will probably deserve a dedicated mail after thinking a bit about it later.
2. Repositories on https://github.com/xwiki-contrib One per each
extension
(i.e. external) repository: Bintray, Pypi, NPM. Is it enough if I ask
for
it here or should I create some official request?
I will create 3 repositories.
For the repositories names I was thinking about:
* repository-pypi * repository-bintray * repository-pypinpm
which is in line with the current "<type>-<name>" based naming on http://contrib.xwiki.org/xwiki/bin/view/Main/WebHome#HChoosingthename.
WDYT ?
It's ok. Will I have rights to those repos?
Created them, you have full write on them.
3. Some space somewhere in XWiki ecosystem where I would be able to document progress and decisions made - things much more detailed and low-level that are normally presented on design pages or http://extensions.xwiki.org/xwiki/bin/view/Extension/ pages.
Moreextensionrepositories
is fine for this IMO. It can be as low level as you want. Once you made your first release then documentation will go to your new extension documentation page on extensions.xwiki.org.
Each extension gets a dedicated space on http://extensions.xwiki.org/xwiki/bin/view/Extension/ so you have plenty of room to put as many details as you want and keep something hight level with links to the details in the extension home page.
Ok, then I will put documentation on desing page.
Best, Krzysztof Płachno
-- Thomas Mortagne
-- Thomas Mortagne
As regards name of extensions: I've just found that integration with external repositories is called as "Connector": - Extension Repository Connector - XWiki - http://extensions.xwiki.org/xwiki/bin/view/Extension/Extension%20Module/Repo... - Extension Repository Connector - Maven - http://extensions.xwiki.org/xwiki/bin/view/Extension/Extension%20Module/Repo... So according to this convention, names for my new extension would be: - Extension Repository Connector - Bintray - Extension Repository Connector - Pypi - Extension Repository Connector - NPM This "Extension Repository" part - however implies that this extension might be related with Extensions Repository Application ( http://extensions.xwiki.org/xwiki/bin/view/Extension/Repository%20Applicatio...), but well maybe it's not that misleading :P WDYT? KP 2017-05-31 9:23 GMT+02:00 Krzysiek Płachno <[email protected]>:
Thanks!
KP
2017-05-30 22:42 GMT+02:00 Thomas Mortagne <[email protected]>:
On Tue, May 30, 2017 at 11:06 AM, Krzysiek Płachno <[email protected]> wrote:
2017-05-29 17:26 GMT+02:00 Thomas Mortagne <[email protected]>:
On Mon, May 29, 2017 at 5:00 PM, Krzysiek Płachno <[email protected]> wrote:
GSoC Coding Part Finally starts tomorrow, so the highest time to get down to work.
I created modest design page where I put summary of general idea of my project: http://design.xwiki.org/xwiki/bin/view/Proposal/ Moreextensionrepositories
You should probably add some link to http://design.xwiki.org/xwiki/bin/view/Design/ExtensionManag erRepositories which have more of less the same goal than your page.
To start coding I need:
1. A confirmed naming pattern for the extensions that I will
develop. My
suggestion is "..... Integration" e.g. "Pypi Integration" "Bintray Integration" Imho, the names of possible repositories are popular and verbose enough to impy that the integration is about extension repository. What do you think?
I'm not a big fan of the very vague "Integration" term in this context. Does not say much about what the extension does, even when you know what Pypi is (which might not be so obvious for Java folks).
I think I would prefer something like "Pypi Extensions Support" but not sure either. Maybe others have some ideas ? Anyway you have time for the extension display name which will be important when you do your first release mostly.
Ok - makes sense ;) "xxxxx Extensions Support" sounds ok as well.
This question will probably deserve a dedicated mail after thinking a bit about it later.
2. Repositories on https://github.com/xwiki-contrib One per each
extension
(i.e. external) repository: Bintray, Pypi, NPM. Is it enough if I
ask for
it here or should I create some official request?
I will create 3 repositories.
For the repositories names I was thinking about:
* repository-pypi * repository-bintray * repository-pypinpm
which is in line with the current "<type>-<name>" based naming on http://contrib.xwiki.org/xwiki/bin/view/Main/WebHome#HChoosingthename.
WDYT ?
It's ok. Will I have rights to those repos?
Created them, you have full write on them.
3. Some space somewhere in XWiki ecosystem where I would be able to document progress and decisions made - things much more detailed and low-level that are normally presented on design pages or http://extensions.xwiki.org/xwiki/bin/view/Extension/ pages.
http://design.xwiki.org/xwiki/bin/view/Proposal/Moreextensio
nrepositories
is fine for this IMO. It can be as low level as you want. Once you made your first release then documentation will go to your new extension documentation page on extensions.xwiki.org.
Each extension gets a dedicated space on http://extensions.xwiki.org/xwiki/bin/view/Extension/ so you have plenty of room to put as many details as you want and keep something hight level with links to the details in the extension home page.
Ok, then I will put documentation on desing page.
Best, Krzysztof Płachno
-- Thomas Mortagne
-- Thomas Mortagne
participants (2)
-
Krzysiek Płachno -
Thomas Mortagne