Re: [g-a-devel] Could we release new Accerciser version ? Last one was on 2016-09-20

2019-01-14 Thread Samuel Thibault
Javier Hernandez, le lun. 14 janv. 2019 15:19:54 +0100, a ecrit:
> That sounds great to me. Samuel, count on me for the application process.

Good :)

FTR, I had requested the account as ticket #15942 on rt.gnome.org

Samuel
___
gnome-accessibility-list mailing list
gnome-accessibility-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list


Re: [g-a-devel] Could we release new Accerciser version ? Last one was on 2016-09-20

2019-01-14 Thread Javier Hernandez via gnome-accessibility-list
On Mon, Jan 14, 2019 at 3:12 PM apinheiro  wrote:

>
> On 14/1/19 14:46, Javier Hernandez wrote:
>
> Hey all,
>
> first, thanks API for rolling that Accerciser release. It's great to see
> it moving again.
>
>
> I dropped the API nickname, too confusing :P Jokes apart, thanks for
> replying.
>

I never got the API deprecation warning!! xD


>
> And yeah, sorry for my silence, but I rarely check the GNOME channels on
> my email, Juanjo pinged me on Telegram about this thread.
>
> As I already told to Alex and Samuel off-list a few months ago, I'd be
> really happy to get them involved so they can take over the maintenance of
> Accerciser. Nowadays, it's pretty hard for me to find the time to work on
> it, my spare time is very limited :/
> As I remember from those exchanges, the problem was that they didn't have
> a gnome git account and that I couldn't just give them control over it. I
> told them that the best way to go was to produce a few contributions first
> that we could use during an application process for a gnome account. In any
> case, I'm not sure if the process to get git access has changed in the past
> 3/4 years or if Samuel already got a gnome account (or not an account, but
> contributed patches to other GNOME projects). So from my side, nothing
> against having Samuel maintaining Accerciser as long as we can vouch for
> him for a gnome account.
>
> Reading here:
>
> https://wiki.gnome.org/AccountsTeam/NewAccounts
>
>
> the number of contributions needed are "reasonable amount of patches". I
> think that adding Samuel ATK and Accerciser patches, he fulfills that
> requisite. So I think that it would be good if Samuel request an account.
>
>
>
That sounds great to me. Samuel, count on me for the application process.

Cheers,
Javi


>
> Cheers,
> Javi
>
> On Mon, Jan 14, 2019 at 11:29 AM apinheiro  wrote:
>
>>
>> On 14/1/19 9:59, Alex ARNAUD wrote:
>> > Le 12/01/2019 à 11:01, apinheiro a écrit :
>> >> Hi,
>> >>
>> >> I have just rolled a new Accerciser release. It is basically all
>> >> included on master since the last release. You can see the details on
>> >> the announcement I have just send.
>> >
>> > Thank you very much Alejandro for this.
>>
>>
>> You are welcome.
>>
>>
>> >
>> >> Ideally we would need the agreement of current maintainer. But as far
>> as
>> >> I understand your previous email, you didn't get any answer from
>> Javier.
>> >> Could you confirm that? If we don't get any answer from Javier, the
>> >> alternative is asking permission at desktop-devel-l...@gnome.org (or
>> >> perhaps at the foundation list).
>> >
>> > I've contacted Javier to make the Samuel patches about the iPython5
>> > support available, he has made the review.
>> >
>> > I really respect the Javier work on Accerciser and his involvement on
>> > accessibility.
>> > I've contacted him privately the 2018-10-17 about Accerciser release
>> > without any answer from him.
>
> > I personally consider we shouldn't wait more because I shouldn't have
>> > to request a new release to a maintainer after years. I assume he no
>> > longer has the time to work on Accerciser.
>>
>>
>> Ok, then let's reduce my proposed two-weeks to one week. For two
>> reasons. First, I always tend to be conservative on this things, and
>> after all this time, and with a fresh release, waiting just one more
>> week shouldn't be a big deal. Second, because I bet that on
>> desktop-devel they will ask how much we waited from our last ping.
>>
>>
>> >
>> > @Alejandro: Does Samuel need to have a sponsor to become a maintainer ?
>>
>>
>> Well, not sure. This kind of maintainer reassignement without the
>> previous maintainer available are not usual, so I don't think that there
>> are a fixed list of requirements. I would personally propose Samuel as
>> maintainer, and list all the reasons of why that is a good idea. I hope
>> that's to be enough.
>>
>>
>> >
>> > Thanks in advance.
>> >
>> > Best regards,
>> > Alex.
>> >
>>
>
___
gnome-accessibility-list mailing list
gnome-accessibility-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list


Re: [g-a-devel] Could we release new Accerciser version ? Last one was on 2016-09-20

2019-01-14 Thread apinheiro

On 14/1/19 14:46, Javier Hernandez wrote:
> Hey all,
>
> first, thanks API for rolling that Accerciser release. It's great to
> see it moving again.


I dropped the API nickname, too confusing :P Jokes apart, thanks for
replying.


> And yeah, sorry for my silence, but I rarely check the GNOME channels
> on my email, Juanjo pinged me on Telegram about this thread.
>
> As I already told to Alex and Samuel off-list a few months ago, I'd be
> really happy to get them involved so they can take over the
> maintenance of Accerciser. Nowadays, it's pretty hard for me to find
> the time to work on it, my spare time is very limited :/
> As I remember from those exchanges, the problem was that they didn't
> have a gnome git account and that I couldn't just give them control
> over it. I told them that the best way to go was to produce a few
> contributions first that we could use during an application process
> for a gnome account. In any case, I'm not sure if the process to get
> git access has changed in the past 3/4 years or if Samuel already got
> a gnome account (or not an account, but contributed patches to other
> GNOME projects). So from my side, nothing against having Samuel
> maintaining Accerciser as long as we can vouch for him for a gnome
> account.

Reading here:

https://wiki.gnome.org/AccountsTeam/NewAccounts


the number of contributions needed are "reasonable amount of patches". I
think that adding Samuel ATK and Accerciser patches, he fulfills that
requisite. So I think that it would be good if Samuel request an account.


>
> Cheers,
> Javi
>
> On Mon, Jan 14, 2019 at 11:29 AM apinheiro  > wrote:
>
>
> On 14/1/19 9:59, Alex ARNAUD wrote:
> > Le 12/01/2019 à 11:01, apinheiro a écrit :
> >> Hi,
> >>
> >> I have just rolled a new Accerciser release. It is basically all
> >> included on master since the last release. You can see the
> details on
> >> the announcement I have just send.
> >
> > Thank you very much Alejandro for this.
>
>
> You are welcome.
>
>
> >
> >> Ideally we would need the agreement of current maintainer. But
> as far as
> >> I understand your previous email, you didn't get any answer
> from Javier.
> >> Could you confirm that? If we don't get any answer from Javier, the
> >> alternative is asking permission at
> desktop-devel-l...@gnome.org  (or
> >> perhaps at the foundation list).
> >
> > I've contacted Javier to make the Samuel patches about the iPython5
> > support available, he has made the review.
> >
> > I really respect the Javier work on Accerciser and his
> involvement on
> > accessibility.
> > I've contacted him privately the 2018-10-17 about Accerciser release
> > without any answer from him. 
>
> > I personally consider we shouldn't wait more because I shouldn't
> have
> > to request a new release to a maintainer after years. I assume he no
> > longer has the time to work on Accerciser.
>
>
> Ok, then let's reduce my proposed two-weeks to one week. For two
> reasons. First, I always tend to be conservative on this things, and
> after all this time, and with a fresh release, waiting just one more
> week shouldn't be a big deal. Second, because I bet that on
> desktop-devel they will ask how much we waited from our last ping.
>
>
> >
> > @Alejandro: Does Samuel need to have a sponsor to become a
> maintainer ?
>
>
> Well, not sure. This kind of maintainer reassignement without the
> previous maintainer available are not usual, so I don't think that
> there
> are a fixed list of requirements. I would personally propose Samuel as
> maintainer, and list all the reasons of why that is a good idea. I
> hope
> that's to be enough.
>
>
> >
> > Thanks in advance.
> >
> > Best regards,
> > Alex.
> >
>


pEpkey.asc
Description: application/pgp-keys
___
gnome-accessibility-list mailing list
gnome-accessibility-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list


Re: [g-a-devel] Could we release new Accerciser version ? Last one was on 2016-09-20

2019-01-14 Thread Javier Hernandez via gnome-accessibility-list
Hey all,

first, thanks API for rolling that Accerciser release. It's great to see it
moving again.
And yeah, sorry for my silence, but I rarely check the GNOME channels on my
email, Juanjo pinged me on Telegram about this thread.

As I already told to Alex and Samuel off-list a few months ago, I'd be
really happy to get them involved so they can take over the maintenance of
Accerciser. Nowadays, it's pretty hard for me to find the time to work on
it, my spare time is very limited :/
As I remember from those exchanges, the problem was that they didn't have a
gnome git account and that I couldn't just give them control over it. I
told them that the best way to go was to produce a few contributions first
that we could use during an application process for a gnome account. In any
case, I'm not sure if the process to get git access has changed in the past
3/4 years or if Samuel already got a gnome account (or not an account, but
contributed patches to other GNOME projects). So from my side, nothing
against having Samuel maintaining Accerciser as long as we can vouch for
him for a gnome account.

Cheers,
Javi

On Mon, Jan 14, 2019 at 11:29 AM apinheiro  wrote:

>
> On 14/1/19 9:59, Alex ARNAUD wrote:
> > Le 12/01/2019 à 11:01, apinheiro a écrit :
> >> Hi,
> >>
> >> I have just rolled a new Accerciser release. It is basically all
> >> included on master since the last release. You can see the details on
> >> the announcement I have just send.
> >
> > Thank you very much Alejandro for this.
>
>
> You are welcome.
>
>
> >
> >> Ideally we would need the agreement of current maintainer. But as far as
> >> I understand your previous email, you didn't get any answer from Javier.
> >> Could you confirm that? If we don't get any answer from Javier, the
> >> alternative is asking permission at desktop-devel-l...@gnome.org (or
> >> perhaps at the foundation list).
> >
> > I've contacted Javier to make the Samuel patches about the iPython5
> > support available, he has made the review.
> >
> > I really respect the Javier work on Accerciser and his involvement on
> > accessibility.
> > I've contacted him privately the 2018-10-17 about Accerciser release
> > without any answer from him.

> I personally consider we shouldn't wait more because I shouldn't have
> > to request a new release to a maintainer after years. I assume he no
> > longer has the time to work on Accerciser.
>
>
> Ok, then let's reduce my proposed two-weeks to one week. For two
> reasons. First, I always tend to be conservative on this things, and
> after all this time, and with a fresh release, waiting just one more
> week shouldn't be a big deal. Second, because I bet that on
> desktop-devel they will ask how much we waited from our last ping.
>
>
> >
> > @Alejandro: Does Samuel need to have a sponsor to become a maintainer ?
>
>
> Well, not sure. This kind of maintainer reassignement without the
> previous maintainer available are not usual, so I don't think that there
> are a fixed list of requirements. I would personally propose Samuel as
> maintainer, and list all the reasons of why that is a good idea. I hope
> that's to be enough.
>
>
> >
> > Thanks in advance.
> >
> > Best regards,
> > Alex.
> >
>
___
gnome-accessibility-list mailing list
gnome-accessibility-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list


Re: [g-a-devel] Could we release new Accerciser version ? Last one was on 2016-09-20

2019-01-14 Thread apinheiro

On 14/1/19 9:59, Alex ARNAUD wrote:
> Le 12/01/2019 à 11:01, apinheiro a écrit :
>> Hi,
>>
>> I have just rolled a new Accerciser release. It is basically all
>> included on master since the last release. You can see the details on
>> the announcement I have just send.
>
> Thank you very much Alejandro for this.


You are welcome.


>
>> Ideally we would need the agreement of current maintainer. But as far as
>> I understand your previous email, you didn't get any answer from Javier.
>> Could you confirm that? If we don't get any answer from Javier, the
>> alternative is asking permission at desktop-devel-l...@gnome.org (or
>> perhaps at the foundation list).
>
> I've contacted Javier to make the Samuel patches about the iPython5
> support available, he has made the review.
>
> I really respect the Javier work on Accerciser and his involvement on
> accessibility.
> I've contacted him privately the 2018-10-17 about Accerciser release
> without any answer from him.
> I personally consider we shouldn't wait more because I shouldn't have
> to request a new release to a maintainer after years. I assume he no
> longer has the time to work on Accerciser.


Ok, then let's reduce my proposed two-weeks to one week. For two
reasons. First, I always tend to be conservative on this things, and
after all this time, and with a fresh release, waiting just one more
week shouldn't be a big deal. Second, because I bet that on
desktop-devel they will ask how much we waited from our last ping.


>
> @Alejandro: Does Samuel need to have a sponsor to become a maintainer ?


Well, not sure. This kind of maintainer reassignement without the
previous maintainer available are not usual, so I don't think that there
are a fixed list of requirements. I would personally propose Samuel as
maintainer, and list all the reasons of why that is a good idea. I hope
that's to be enough.


>
> Thanks in advance.
>
> Best regards,
> Alex.
>


pEpkey.asc
Description: application/pgp-keys
___
gnome-accessibility-list mailing list
gnome-accessibility-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list


Re: [g-a-devel] Could we release new Accerciser version ? Last one was on 2016-09-20

2019-01-14 Thread Alex ARNAUD

Le 12/01/2019 à 11:01, apinheiro a écrit :

Hi,

I have just rolled a new Accerciser release. It is basically all
included on master since the last release. You can see the details on
the announcement I have just send.


Thank you very much Alejandro for this.


Ideally we would need the agreement of current maintainer. But as far as
I understand your previous email, you didn't get any answer from Javier.
Could you confirm that? If we don't get any answer from Javier, the
alternative is asking permission at desktop-devel-l...@gnome.org (or
perhaps at the foundation list).


I've contacted Javier to make the Samuel patches about the iPython5 
support available, he has made the review.


I really respect the Javier work on Accerciser and his involvement on 
accessibility.
I've contacted him privately the 2018-10-17 about Accerciser release 
without any answer from him.
I personally consider we shouldn't wait more because I shouldn't have to 
request a new release to a maintainer after years. I assume he no longer 
has the time to work on Accerciser.


@Alejandro: Does Samuel need to have a sponsor to become a maintainer ?

Thanks in advance.

Best regards,
Alex.
___
gnome-accessibility-list mailing list
gnome-accessibility-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list


Re: [g-a-devel] Could we release new Accerciser version ? Last one was on 2016-09-20

2019-01-14 Thread apinheiro

On 12/1/19 18:04, Samuel Thibault wrote:
> Hello,


Hi,


>
> apinheiro, le sam. 12 janv. 2019 11:01:42 +0100, a ecrit:
>> Having said so, WARNING, it is a blind release. I took what it was
>> available on master, and checked that compiled with make distcheck, but
>> I didn't test it. I would really really appreciate some testing,
> It seems to be working fine for my needs at least :)


Ok, thanks for the testing.


>
>> So Alex, is any of you volunteering to co-maintaine accerciser?
>> Samuel perhaps?
> I can happily co-maintain, yes :)
> I use it very often anyway, so I'm already making sure it does work,
> anyway :)


Awesome! Thanks. I have re-added Javier on this email thread (I didn't
include it on the previous email by mistake). So Javier, if you are reading:

What do you think about adding Samuel Thibault as Accerciser co-maintainer?


Having said so, as we didn't have too much activity from Javier lately,
as I mentioned, the fallback plan would be ask on desktop-devel. I think
that wait ~two weeks for Javier is reasonable.


PS: I tried to find an alternative Javier email, but I was not lucky. If
any of you know an alternative way to contact Javier, go ahead please.


BR


>
> Samuel
>


pEpkey.asc
Description: application/pgp-keys
___
gnome-accessibility-list mailing list
gnome-accessibility-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list


Re: [g-a-devel] Could we release new Accerciser version ? Last one was on 2016-09-20

2019-01-12 Thread Samuel Thibault
Hello,

apinheiro, le sam. 12 janv. 2019 11:01:42 +0100, a ecrit:
> Having said so, WARNING, it is a blind release. I took what it was
> available on master, and checked that compiled with make distcheck, but
> I didn't test it. I would really really appreciate some testing,

It seems to be working fine for my needs at least :)

> So Alex, is any of you volunteering to co-maintaine accerciser?
> Samuel perhaps?

I can happily co-maintain, yes :)
I use it very often anyway, so I'm already making sure it does work,
anyway :)

Samuel
___
gnome-accessibility-list mailing list
gnome-accessibility-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list


Re: [g-a-devel] Could we release new Accerciser version ? Last one was on 2016-09-20

2019-01-12 Thread apinheiro
Hi,

I have just rolled a new Accerciser release. It is basically all
included on master since the last release. You can see the details on
the announcement I have just send.

Having said so, WARNING, it is a blind release. I took what it was
available on master, and checked that compiled with make distcheck, but
I didn't test it. I would really really appreciate some testing, hoping
to fix anything missing before 3.31.90 (look here [1] for this cycle
dates). And hopefully, by 3.31.90 we would have improved the maintainer
status. So Alex, is any of you volunteering to co-maintaine accerciser?
Samuel perhaps?

Ideally we would need the agreement of current maintainer. But as far as
I understand your previous email, you didn't get any answer from Javier.
Could you confirm that? If we don't get any answer from Javier, the
alternative is asking permission at desktop-devel-l...@gnome.org (or
perhaps at the foundation list).

So, with everything this in mind, how something about this?:

* We check if there is any volunteer to step as accerciser maintainer.

* We send another email to Javier, perhaps looking for an alternative
email address.

* We wait a reasonable amount of time (reasonable is subjective, not
sure how much to wait).

* If we don't get an answer from Javier, we ask permission to
co-maintain accerciser to GNOME.

Opinions?

[1] https://wiki.gnome.org/ThreePointThirtyone

On 11/1/19 12:08, Alex ARNAUD wrote:
> Hello all,
>
> The current version of Accerciser was release on 2016 and are not
> longer usable on recent system due to iPython5 migration. On Debian,
> we've specific patches applied to avoid that (patches are available
> upstream).
>
> This situation prevents people on some distributions to use Accerciser
> for increase or test accessibility.
> As we're already too few people working on accessibility, having a
> broken accessibility inspector make people tells me "how I make
> Accerciser to work on OpenSuse?" and could abandoned to take care of
> accessibility.
>
> When looking at the Git repository I'm seeing people making patches
> and updating translations.
>
> At Hypra, we've adding the iPython 5 support on December 2017. As no
> one from Hypra (especially Samuel Thibault) has not the permission to
> make a release we need to rely on someone with the rights to do that.
>
> @Joanie/jbicha and all: Could you help us to release a new version of
> Accerciser ? I've not your experience on the GNOME Project to know how
> we should proceed in such critical situation.
>
> @javier: Do you have the time to continue to be Accerciser maintainer?
> The last commit of you was on 2016-09-20.
>
> Thanks in advance.
>
> Best regards,
> Alex.
> ___
> gnome-accessibility-devel mailing list
> gnome-accessibility-de...@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
>


pEpkey.asc
Description: application/pgp-keys
___
gnome-accessibility-list mailing list
gnome-accessibility-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list


Re: [g-a-devel] Could we release new Accerciser version ? Last one was on 2016-09-20

2019-01-11 Thread Alex ARNAUD

Le 11/01/2019 à 14:36, apinheiro a écrit :

If Debian need those patches, does that means that accerciser from
gitlab master doesn't work either? 


We've submitted those fixes upstream and they are committed on master 
branche: see https://bugzilla.gnome.org/show_bug.cgi?id=776301 and 
https://gitlab.gnome.org/GNOME/accerciser/commit/5a3242b4c7f5a5c844a20821881d68d1cabcae1e


Best regards,
Alex.
___
gnome-accessibility-list mailing list
gnome-accessibility-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list


Re: [g-a-devel] Could we release new Accerciser version ? Last one was on 2016-09-20

2019-01-11 Thread apinheiro
On 11/1/19 12:08, Alex ARNAUD wrote:
> Hello all,
>
> The current version of Accerciser was release on 2016 

Yes, I agree that it would be good to do an Accerciser release.


> and are not longer usable on recent system due to iPython5 migration.
> On Debian, we've specific patches applied to avoid that (patches are
> available upstream).


If Debian need those patches, does that means that accerciser from
gitlab master doesn't work either? Or do you mean patches from master
applied on top of last release?

The thing is that if in order to make it working on Debian, it is enough
to use accerciser master, I could try to roll a release this cycle. If
some extra development work is needed, unfourtunately I would not have
time for that.

Having said so, that would be just a one-time fix, because as you are
mentioning below, I think that it is time to find a new co-maintainer of
Accerciser. I'm personally struggling to get ATK releases rolling, so I
would not be able to consistently do Accercisers releases.

>
> This situation prevents people on some distributions to use Accerciser
> for increase or test accessibility.
> As we're already too few people working on accessibility, having a
> broken accessibility inspector make people tells me "how I make
> Accerciser to work on OpenSuse?" and could abandoned to take care of
> accessibility.
>
> When looking at the Git repository I'm seeing people making patches
> and updating translations.
>
> At Hypra, we've adding the iPython 5 support on December 2017. As no
> one from Hypra (especially Samuel Thibault) has not the permission to
> make a release we need to rely on someone with the rights to do that.
>
> @Joanie/jbicha and all: Could you help us to release a new version of
> Accerciser ? I've not your experience on the GNOME Project to know how
> we should proceed in such critical situation.
>
> @javier: Do you have the time to continue to be Accerciser maintainer?
> The last commit of you was on 2016-09-20.


Did Javier replied this ping?


>
> Thanks in advance.
>
> Best regards,
> Alex.
> ___
> gnome-accessibility-devel mailing list
> gnome-accessibility-de...@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
>


pEpkey.asc
Description: application/pgp-keys
___
gnome-accessibility-list mailing list
gnome-accessibility-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list