Re: [g-a-devel] Could we release new Accerciser version ? Last one was on 2016-09-20
apinheiro <[email protected]> Mon, 14 Jan 2019 15:12:06 +0100
| Newsgroups | gmane.comp.gnome.accessibility.general,gmane.comp.gnome.accessibility.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --------------F87F5C6780E92D8E2CFFA027 Content-Type: multipart/alternative; boundary="------------AFFCA5AE59E498999F8DA1D0" --------------AFFCA5AE59E498999F8DA1D0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 <[email protected] > <mailto:[email protected]>> wrote: > > > On 14/1/19 9:59, Alex ARNAUD wrote: > > Le 12/01/2019 =C3=A0 11:01, apinheiro a =C3=A9crit=C2=A0: > >> 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 > [email protected] <mailto:[email protected]> = (or > >> perhaps at the foundation list). > > > > I've contacted Javier to make the Samuel patches about the iPytho= n5 > > 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 rele= ase > > without any answer from him.=C2=A0 > > > 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, an= d > after all this time, and with a fresh release, waiting just one mor= e > 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. > > > --------------AFFCA5AE59E498999F8DA1D0 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF= -8"> </head> <body text=3D"#000000" bgcolor=3D"#FFFFFF"> <p><br> </p> <div class=3D"moz-cite-prefix">On 14/1/19 14:46, Javier Hernandez wrote:<br> </div> <blockquote type=3D"cite" cite=3D"mid:[email protected]= l.com"> <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DU= TF-8"> <div dir=3D"ltr"> <div dir=3D"ltr">Hey all, <div><br> </div> <div>first, thanks API for rolling that Accerciser release. It's great to see it moving again.</div> </div> </div> </blockquote> <p><br> </p> <p>I dropped the API nickname, too confusing :P Jokes apart, thanks for replying.<br> </p> <p><br> </p> <blockquote type=3D"cite" cite=3D"mid:[email protected]= l.com"> <div dir=3D"ltr"> <div dir=3D"ltr"> <div>And yeah, sorry for my silence, but I rarely check the GNOME channels on my email, Juanjo pinged me on Telegram about this thread.</div> <div><br> </div> <div>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 :/</div> <div>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.</div> </div> </div> </blockquote> <p>Reading here:</p> <p><a class=3D"moz-txt-link-freetext" href=3D"https://wiki.gnome.org/= AccountsTeam/NewAccounts">https://wiki.gnome.org/AccountsTeam/NewAccounts= </a></p> <p><br> </p> <p>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.<br> </p> <p><br> </p> <blockquote type=3D"cite" cite=3D"mid:[email protected]= l.com"> <div dir=3D"ltr"> <div dir=3D"ltr"> <div><br> </div> <div>Cheers,</div> <div>Javi</div> </div> <br> <div class=3D"gmail_quote"> <div dir=3D"ltr">On Mon, Jan 14, 2019 at 11:29 AM apinheiro <= ;<a href=3D"mailto:[email protected]" target=3D"_blank" moz-do-not-send=3D"true">[email protected]</a>> wrote= :<br> </div> <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br> On 14/1/19 9:59, Alex ARNAUD wrote:<br> > Le 12/01/2019 =C3=A0 11:01, apinheiro a =C3=A9crit=C2=A0= :<br> >> Hi,<br> >><br> >> I have just rolled a new Accerciser release. It is basically all<br> >> included on master since the last release. You can see the details on<br> >> the announcement I have just send.<br> ><br> > Thank you very much Alejandro for this.<br> <br> <br> You are welcome.<br> <br> <br> ><br> >> Ideally we would need the agreement of current maintainer. But as far as<br> >> I understand your previous email, you didn't get any answer from Javier.<br> >> Could you confirm that? If we don't get any answer from Javier, the<br> >> alternative is asking permission at <a href=3D"mailto:[email protected]" target=3D"_bla= nk" moz-do-not-send=3D"true">[email protected]</a> (or<br> >> perhaps at the foundation list).<br> ><br> > I've contacted Javier to make the Samuel patches about the iPython5<br> > support available, he has made the review.<br> ><br> > I really respect the Javier work on Accerciser and his involvement on<br> > accessibility.<br> > I've contacted him privately the 2018-10-17 about Accerciser release<br> > without any answer from him.=C2=A0</blockquote> <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> > I personally consider we shouldn't wait more because I shouldn't have<br> > to request a new release to a maintainer after years. I assume he no<br> > longer has the time to work on Accerciser.<br> <br> <br> Ok, then let's reduce my proposed two-weeks to one week. For two<br> reasons. First, I always tend to be conservative on this things, and<br> after all this time, and with a fresh release, waiting just one more<br> week shouldn't be a big deal. Second, because I bet that on<b= r> desktop-devel they will ask how much we waited from our last ping.<br> <br> <br> ><br> > @Alejandro: Does Samuel need to have a sponsor to become a maintainer ?<br> <br> <br> Well, not sure. This kind of maintainer reassignement without the<br> previous maintainer available are not usual, so I don't think that there<br> are a fixed list of requirements. I would personally propose Samuel as<br> maintainer, and list all the reasons of why that is a good idea. I hope<br> that's to be enough.<br> <br> <br> ><br> > Thanks in advance.<br> ><br> > Best regards,<br> > Alex.<br> ><br> </blockquote> </div> </div> </blockquote> </body> </html> --------------AFFCA5AE59E498999F8DA1D0-- --------------F87F5C6780E92D8E2CFFA027 Content-Type: application/pgp-keys; name="pEpkey.asc" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="pEpkey.asc" -----BEGIN PGP PUBLIC KEY BLOCK----- mQGiBEPOgCARBAD/C3F8TTDu/T0oxmDRxF1gXDdceloiFU3lJqVYikzJD012sTlq 4UcqB+PBy519bsGpAuIObhN/C8v7iidoZW+xjyiozeM7/nESPDrBHtIzSYbcZOb3 QEP0eNeCNv0Cp6bXLgFtO6yqGol3u9HpE/DlLnmxWtcYYIqNqtXk3J0h4wCg4FrR JjIwuMDnyaWSB1nZW0e/s28D+QFFms7plZCKlHN2gKRPX1R1syyyvyp1nMWePQDq 6RdEPTNJZHi/B2+NMTUVA8fn/fPpbOZtpujD330Vp6z68zOSeqMbQzIwr1SzzLJs w1xNyUAawCZ3VCpaCEB4z1/YQ4mCV5uGOhY7oHJrdcThv82Q8fDBL/2W3wmJkdDU IyysBAC5ZTVhj2bDHCuZOcIlsQHnlCGZxNw5ZQr+SrAJTFTkghkI99fHFqUZnnOY 38/XVoX9Y0x9+ZAPwNzfSFsPHof3gXaBC41tv7sEZbpiO5crqmU3YXmWhOMTew9r RkntvoRMF02romOfyuiWZH1FqPrxgrsMdEA2K2Ql+FOO2lY2EbQvQWxlamFuZHJv IFBpbmhlaXJvIChBUEkpIDxhcGluaGVpcm9AaWdhbGlhLmNvbT6IXgQTEQIAHgUC Q86AIAIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRDzmXD8yifwiOSyAJ4jFBJs pmFi5zt8rG7ZrkUT87/cKQCgoMXlFhXHhX2tffRwdiT+m2x3PbGIXgQTEQIAHgUC Q86AIAIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRDzmXD8yifwiOSyAKCfb8T5 c4z1ATHJvw5Fkp5U/+7XjgCfbVUFlgn/2NBZOz6XV/DuNm3rvJWIRgQQEQIABgUC Rlwz2QAKCRBh1JgHiQsVsiShAJ9Z/zfVHcYMAUz//42BAGV0P5HcAQCfchb10pUB rf3VqpxAqomH0xEMo5u5AQ0EQ86AIhAEALf54fp4Y8bJxvGZ0pbMFBO36csQUxpI BGHv2qxK7Oov0kLk8gL7e2MSMwYv6Ekam4D27s8FIkXJYdibucah98b5CDtdT+mk EgiT0TU0L92/O4PKMiaU+oOAQ9HCUUcgwFHirDnK6gGicm3rtUUyFTUTQ1i4IX0v LlXKfrRA0oUbAAMFBACYd3UCEAErcCtWAhIMmyhebzdY6iWxzSAkiR15xBPROXEh T+eMkXP/9irGbbu4lt0P+PEMMHTUOQv6t7bNTSQDMr0ADMAOFsEGNnJpcA8eUUTo svHH76ewdpnABhU3x+TyIda3rWO8oQtsWI9JEJwPfTUZNbQSOFQaX9wj7m7TZYhJ BBgRAgAJBQJDzoAiAhsMAAoJEPOZcPzKJ/CIxDoAoIdmz9dsWO/hpmfnEViMxzB6 A+GuAJ9m3QyC3Ewu9272nvegzvXimRHuWA=3D=3D =3DGVI/ -----END PGP PUBLIC KEY BLOCK----- --------------F87F5C6780E92D8E2CFFA027 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ gnome-accessibility-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list --------------F87F5C6780E92D8E2CFFA027--