Right, I'm willing to maintain it, and think that the first step towards
a properly maintained module is to accept reality and move it to
unsupported until it can safely be told it earned it's starts (as per
the module matrix page)
Gabriel
Andrea Aime wrote:
> Justin Deoliveira ha scritto:
>> A
Justin Deoliveira ha scritto:
>
>>> The wfs datastore module is going to be moved
>>> to unsupported
>> I thought Gabriel was maintaining this?
>
> Nevermind, just saw the next email :)
Doh, did not see yours in time! ;-)
Cheers
Andrea
---
Justin Deoliveira ha scritto:
> Andrea Aime wrote:
>> Hi all,
>> final mail for the modules that need to be moved.
>>
>> The unsupported/ogc modules family is going to
>> be moved to extensions. Mind, the poms are missing
>> a maintainer declaration.
> I will add maintainer declarations for myself.
>> The wfs datastore module is going to be moved
>> to unsupported
> I thought Gabriel was maintaining this?
Nevermind, just saw the next email :)
>> The wms module is going to be moved to extensions?
>> (would not make much sense in library since
>> nothing else depends on it).
>>
>> The swing
Andrea Aime wrote:
> Hi all,
> final mail for the modules that need to be moved.
>
> The unsupported/ogc modules family is going to
> be moved to extensions. Mind, the poms are missing
> a maintainer declaration.
I will add maintainer declarations for myself.
>
> The wfs datastore module is going
Hi all,
final mail for the modules that need to be moved.
The unsupported/ogc modules family is going to
be moved to extensions. Mind, the poms are missing
a maintainer declaration.
The wfs datastore module is going to be moved
to unsupported
The wms module is going to be moved to extensions?
(w