Thomas Mortagne wrote:
> On Wed, Oct 7, 2009 at 10:02, Vincent Massol <[email protected]> wrote:
>> On Oct 7, 2009, at 9:47 AM, Thomas Mortagne wrote:
>>
>>> On Tue, Oct 6, 2009 at 20:37, Jerome Velociter <[email protected]>
>>> wrote:
>>>> Vincent Massol wrote:
>>>>> Note: It's important to write somewhere clearly that Xlet projects
>>>>> are
>>>>> not done by the xwiki dev team and not supported by the xwiki dev
>>>>> team
>>>>> (and thus that the quality depends on the contributor(s)).
>>>>>
>>>>> It could also be mentioned that at some point an Xlet project
>>>>> could be
>>>>> elected to become a platform project if the interest is generic, if
>>>>> it's voted and if the quality is good enough.
>>>> I agree. I think the best place for that would be a page on
>>>> code.xwiki.org.
>>>>
>>>> I don't think we need a new wiki for the forge (except technically
>>>> - for
>>>> SVN), I would be to aggregate all info that concern contrib in
>>>> code.xwiki.org since they are closely related.
>>>>
>>>> BTW I forgot to mention in the original email, I think we should
>>>> propose
>>>> a generic maven groupId for individuals or projects that don't want
>>>> to
>>>> come up with their own. Something like "org.xwiki.contrib".
>>> all projects are supposed to have at least a name and generally can
>>> use org.xwiki.myproject I think
>> The current rule is org.xwiki.<top level project> so if contrib is a
>> top level project it seems logical to have org.xwiki.contrib.
>
> contrib is a repository of top level projects not a project itself IMO

The problem with "org.xwiki.myproject" is that we lose the "not 
developed by the XWiki team" aspect that contrib brings.

Jerome.
>
>> -Vincent
>>
>>>> wdyt ?
>>>>
>>>> Jerome.
>>>>
>>>>> Thanks
>>>>> -Vincent
>> _______________________________________________
>> devs mailing list
>> [email protected]
>> http://lists.xwiki.org/mailman/listinfo/devs
>>
>
>
>

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

Reply via email to