Re: Extensions review



Drago,

What I'm trying to avoid is basically: https://extensions.gnome.org/review/3806
I don't think we want a lot of Main.Util.trySpawnCommandLine and more if you want to do is try to spawn gtk applications or so.

What do you think?


2014-05-25 21:57 GMT+02:00 drago01 <drago01 gmail com>:
On Sun, May 25, 2014 at 9:52 PM, Carlos Soriano Sánchez
<carlos soriano89 gmail com> wrote:
> Hi,
>
> With the mission of make review of extension simpler, I wrote some
> guidelines to accept or not an extension.
> My intention is also to allow less on extensions, going forward to more
> security and privacy, making the review work simpler and the extension
> ecosystem less messed.
> If we can agree on something like that, we will do this work more simple, so
> more community people can get in.
> Please give me feedback on that. It's just a draft to do the first step
> forward on that. So we can add, remove or modify those.
> https://wiki.gnome.org/CarlosSoriano/ExtensionsGuidelines
>
> Thanks!

1) GTK: You can't really use GTK inside an extension other then for
extension preferences (which is a valid case)
2) Duplicates: Yeah forgot to tell you about that in the last mail
while doing a review check for dupes and if there is one don't approve
it either get both authors to work together or if one gets abounded
let the new user become the owner (i.e send mail wait two weeks if he
does not respond transfer ownership).
3) Should probably add that sync I/O should be avoided because it
blocks the whole compositor process.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]