Re: java-atk-wrapper maintainership

[Alejandro Piñeiro <apinheiro igalia com>]

On 10/17/2014 06:54 PM, Magdalen Berns wrote:
>     On 2014-10-17 16:37, Magdalen Berns <m berns thismagpie com
>     <mailto:m berns thismagpie com>> wrote:
>
>         I would like to support the new java wrapper maintainer,
>         Alejandro with the
>         task of maintaining java-atk-wrapper since the whole module
>         needs updating
>         having been abandoned back in 2011 until recently when I
>         submitted a patch
>         to allow it to be built successfully on the latest version of
>         GNOME[1,2]. I
>         also updated the doap to reflect reality and conform to the
>         latest doap
>         standard used by GNOME[3]
>
>
>     As Alejandro is the maintainer, you should ask him, rather than
>     desktop-devel-list, if you want to become a maintainer.
>
>
> I have asked him, lots of times both before and after he added himself 
> as maintainer for the module.[1]

From this bug [2], what you asked several times was about removing Ke  
Wang as maintainer. From the thread you listed [1], you said " I would 
like to support the new java wrapper maintainer". I understood willing 
to help, not offering you to be co-maintainer, sorry for the 
misunderstanding.

> I haven't had any objections from Alejandro Emailing this list is the 
> correct procedure to request maintainership of a module.
>
>         The first commit since 2011, were just this week and, it's
>         fair to say that
>         the module has generally got a bit old and suboptimal over
>         time.[4]
>
>         I reckon it would really be great to put a bit more brainspace
>         and time
>         into improving things for java(by making use of what the most
>         current java
>         API can offer and ensuring that the module is wrapping the
>         latest interface
>         methods. For example, at the moment the text interface is
>         completely
>         outdated and this is likely to create problems for users if it
>         is not dealt
>         with.[5]
>
>
>     It is promising that you have ideas and want to contribute to the
>     project, but you do not need to be a maintainer to accomplish
>     those goals.
>
> I am failing to see your point. Nobody else is planning to do update 
> the wrapper.

As I said when I somewhat took over java-atk-wrapper [3], if I added  
myself as maintainer was mostly in order to have an updated contact, 
and  more important, even if I didn't plan to work directly on it, at 
least  having someone to review the patches the community were 
providing, and  doing a release if needed (as I did, first release in 4 
years 45]), that  are some of the additional tasks a maintainer is 
supposed to do, in addition to coding. I also said, that ideally it 
should be something temporal as Caribou, until a new maintainer 
appeared, that seems to be the case.

So the question is, if you want to also do the releasing and the other 
tasks that usually involve became maintainer of a module?

> Magdalen
>
> [1] 
> https://mail.gnome.org/archives/gnome-accessibility-devel/2014-May/thread.html
[2] https://bugzilla.gnome.org/show_bug.cgi?id=730121
[3] 
https://mail.gnome.org/archives/gnome-accessibility-devel/2014-May/msg00001.html
[4] 
https://mail.gnome.org/archives/gnome-announce-list/2014-September/msg00045.html