Re: Extensions review

[Sriram Ramkrishna <sri ramkrishna me>]

On Sat, May 24, 2014 at 10:14 AM, Carlos Soriano Sánchez
<carlos soriano89 gmail com> wrote:
> Drago,
> Ok. No, I don't have rights, my username is csoriano.
> Didn't know there were more extensions reviewers. I will help to the current
> queue so people not aware of the current situation will not be angry, but I
> think it would help to have a warning dialog or something in
> https://extensions.gnome.org/ that current review time is long and that we
> need developers to review extensions to maintain the service in a good way.
> Also I would do some guidelines for the recruitment of the help, maybe
> requiring some upstream patches or extensions?. What do you think?
> Also, don't we have the webpage code somewhere to do patches, do we?
>
> Sriram,
> Still, that's more work for developers, who already seems to be working on
> something else more important upstream. At the end, what we need is someone
> to go trough commits and make a list of important changes before a release.
> Not sure who be willing to do so, although Drago did it last release, I
> don't know how time consuming was to do it.

My request was more directed at Sindhu and not one of the core
developers.  What would happen is that towards the end of the release,
she can speak with shell folks and get an idea what might have changed
that would affect extensions.  Eventually, I am hoping that would not
be required and instead would know directly from git.  So it's a path
to learning how shell works and how extensions work.  At that point,
she would be able to write her own extensions.  The task is open to
anybody else that might be interested as well.  I'm interested in
seeing a smooth transition each release.

Now that I think about it, another way to find out is to use GNOME
continuous and find out which extensions break and map it backwards.
It doesn't do full coverage but can document immediate breakage.  I
would love to see this automated on a web page so that we know what is
broken.  I will start a new thread for that, no need to clutter this
one with that.

sri

> 2014-05-24 17:44 GMT+02:00 Sriram Ramkrishna <sri ramkrishna me>:
>
> > What might be interesting is to have a liaison who can help track changes
> > in shell that needs to be communicated to extension authors so that there is
> > less breakage every release.  Maybe like a release porting guide that we can
> > make as part of the shell release?
> >
> > This could also help you figure out more on the shell internals.  What do
> > you think?
> >
> > On May 24, 2014 3:55 AM, "Sindhu S" <sindhus live in> wrote:
> > > hi, all
> > >
> > > I am interested in tasks related to Shell extensions. I have not been
> > > able to write an extension so far but I've written a blog post about it [1].
> > > How can I help?
> > >
> > > [1] sindhus.bitbucket.org/writing-shell-extensions-in-gnome.html
> > >
> > > _______________________________________________
> > > gnome-shell-list mailing list
> > > gnome-shell-list gnome org
> > > https://mail.gnome.org/mailman/listinfo/gnome-shell-list