On Oct 9, 2013, at 7:17 PM, Jeremie BOUSQUET <[email protected]> wrote:

> Hi Vincent,
> 
> I'm willing to help, as much as my bandwith allows :)

Great!

See below

> Le 9 oct. 2013 16:29, "Vincent Massol" <[email protected]> a écrit :
>> 
>> Hi developers/contributors,
>> 
>> We have quite a lot of applications on http://extensions.xwiki.org
>> 
>> However several haven't been updated for a very long time even though
> XWiki has made progress.
>> 
>> I can think of 3 areas where help would be appreciated:
>> 
>> * Some apps have wiki pages in XWiki Syntax 1.0 version. Those need to be
> upgraded to XWiki Syntax 2.1.
>> * Some apps don't register themselves in the Applications Panel. To
> change that just need to create a new page with the proper XObject. You can
> copy the Blog.ApplicationsPanelEntry page to this app's space and edit it.
>> * Some apps don't automatically register translations and force the user
> to manually add documentation resource bundle in the Administration.
> There's now a better way which is to add an object of type
> XWiki.TranslationDocumentClass
>> 
>> Example of app that would need an update:
>> http://extensions.xwiki.org/xwiki/bin/view/Extension/Polls+Application
>> 
>> So who's willing to help? :)
>> 
>> Note that the best strategy is to ensure that the application has a git
> repo on https://github.com/organizations/xwiki-contrib (there should be a
> Source button on the app page on extensions.xwiki.org too). If not, then
> let me know by answering this email and I'll create it for you and give you
> access so that you can make changes there. FYI the full process is
> documented at http://contrib.xwiki.org and I can help you with that.
> 
> To be clear, does that mean that you take care of creating the repo AND
> populating it with original sources, or that we should do it ?
> Shouldn't this be done by or with authorization from the original extension
> author ?

I can create the repo and if you can populate it then all the better :)

You can ask the original author (always better) but if you don't change the 
license and the license allows it you don't really need to ask.

> I would add that ideally extensions should be published to a maven repo (so
> others can depend on them), but maybe that's too much for the cleaning
> activity you propose... (and could be considered in a second step for a set
> of extensions)

Sure

Thanks
-Vincent

_______________________________________________
users mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/users

Reply via email to