On Mon, Mar 10, 2014 at 7:48 AM, Christoph Reiter
reiter.christ...@gmail.com wrote:
On Mon, Mar 10, 2014 at 4:27 AM, Simon Feltman s.felt...@gmail.com wrote:
In terms of overrides having additional side effects beyond the
intended GI API, I really hope we can deprecate those scenarios or
On 7 March 2014 17:45, meg ford meg...@gmail.com wrote:
It would also be awesome if whoever takes the lead on this makes sure that
the functionality we are documenting actually works. If we want devs to be
able to write GNOME apps then having documentation that matches the
functionality they
Stefan Sauer wrote:
On 03/08/2014 06:15 PM, Christoph Reiter wrote:
I've tried the devhelp export and it seemed to work quite well for the all
in one API docs. But I'm not sure how linking between different Sphinx
builds would work with devhelp. (but I have no idea how devhelp does it
On 7 March 2014 17:45, meg ford meg...@gmail.com wrote:
It would also be awesome if whoever takes the lead on this makes sure
that
the functionality we are documenting actually works. If we want devs to
be
able to write GNOME apps then having documentation that matches the
functionality
Frederic Peters fpet...@gnome.org wrote:
...
Developer documentation will be a topic during the Developer
Experience Hackfest, but I believe we will fail again to provide
lasting effects if nobody takes on a coordination role.
...
But I'm a bit lost since the decisions that were agreed at the
On Sun, Mar 9, 2014 at 11:35 PM, Stefan Sauer enso...@hora-obscura.de wrote:
devhelp is basically the index.sgml (ignore the sgml extension, it is
not) + prerendered html. devhelp does not do anything with the link in
the html doc, except trying to follow them when one is clicked.
OK, thanks
On Mon, Mar 10, 2014 at 4:27 AM, Simon Feltman s.felt...@gmail.com wrote:
On Sat, Mar 8, 2014 at 9:15 AM, Christoph Reiter
reiter.christ...@gmail.com wrote:
On Sat, Mar 8, 2014 at 4:04 AM, Simon Feltman s.felt...@gmail.com wrote:
* GI function argument interpretation for Python docs would be
On 03/08/2014 02:31 AM, Alberto Ruiz wrote:
Pull requests are not encouraged, we tell anyone that tries one to go
to Bugzilla/ML and we cancel it.
I see. The pull requests would lower the barrier to fix docs.
Stefan
2014-03-07 22:58 GMT+01:00 Stefan Sauer enso...@hora-obscura.de
On Sun, Mar 9, 2014 at 11:54 AM, Stefan Sauer enso...@hora-obscura.dewrote:
I see. The pull requests would lower the barrier to fix docs.
There was a lengthy discussion of this on the foundation-list last August,
and a follow-up email from Karen in September regarding the Board's
decision
On 03/08/2014 06:15 PM, Christoph Reiter wrote:
On Sat, Mar 8, 2014 at 4:04 AM, Simon Feltman s.felt...@gmail.com wrote:
That would be helpful. I think it would be nice to integrate your work
(or abstracted parts of it) with pygobject itself.
An idea that has been cooking in the back of my
On Sat, Mar 8, 2014 at 9:15 AM, Christoph Reiter
reiter.christ...@gmail.com wrote:
On Sat, Mar 8, 2014 at 4:04 AM, Simon Feltman s.felt...@gmail.com wrote:
* GI function argument interpretation for Python docs would be as
close as possible to pygobject by having the argument translation code
Simon and others,
With respect to PyGObject docs, I hope you are all aware of
http://lazka.github.io/pgi-docs/ and http://learngtk.org/
The first link is especially fantastic.
FWIW I also purchased www.pygobject.org a while ago and am wondering what
to do with it. My current plan is to
On Sat, Mar 8, 2014 at 4:04 AM, Simon Feltman s.felt...@gmail.com wrote:
That would be helpful. I think it would be nice to integrate your work
(or abstracted parts of it) with pygobject itself.
An idea that has been cooking in the back of my mind (and to a very
small degree has been realized
On Sat, Mar 8, 2014 at 1:52 AM, John Stowers
john.stowers.li...@gmail.com wrote:
Simon and others,
With respect to PyGObject docs, I hope you are all aware of
http://lazka.github.io/pgi-docs/ and http://learngtk.org/
The first link is especially fantastic.
Yep, Christoph's (lazka) API docs
On Thu, Mar 6, 2014 at 11:37 AM, Ekaterina Gerasimova
kittykat3...@gmail.com wrote:
On 6 March 2014 10:07, Christoph Reiter reiter.christ...@gmail.com wrote:
Since it wasn't mentioned so far; outside of gnome.org, on the Python
side of things, there exists the GTK+ 3 tutorial [0] maintained by
On 4 March 2014 16:58, Frederic Peters fpet...@gnome.org wrote:
Hey,
It's been proved again in recent hackfests, we have a really great
team writing user documentations, and thanks have to be given to
Shaun, and now Kat, for coordinating the effort.
On the other hand we have absolutely no
It would also be awesome if whoever takes the lead on this makes sure that
the functionality we are documenting actually works. If we want devs to be
able to write GNOME apps then having documentation that matches the
functionality they can access using the the language application developer
docs
On 03/06/2014 05:41 PM, Sébastien Wilmet wrote:
On Tue, Mar 04, 2014 at 07:05:30PM +0100, Frederic Peters wrote:
I was mostly concerned by our technical infrastructure for developer
documentation, but that itself has of course been driven by the
content we produced (or wanted to produce), so I
Pull requests are not encouraged, we tell anyone that tries one to go to
Bugzilla/ML and we cancel it.
2014-03-07 22:58 GMT+01:00 Stefan Sauer enso...@hora-obscura.de:
On 03/06/2014 05:41 PM, Sébastien Wilmet wrote:
On Tue, Mar 04, 2014 at 07:05:30PM +0100, Frederic Peters wrote:
I was
On Fri, Mar 7, 2014 at 3:22 AM, Christoph Reiter
reiter.christ...@gmail.com wrote:
On Thu, Mar 6, 2014 at 11:37 AM, Ekaterina Gerasimova
kittykat3...@gmail.com wrote:
On 6 March 2014 10:07, Christoph Reiter reiter.christ...@gmail.com wrote:
Since it wasn't mentioned so far; outside of
(responding to the wrong mail since I just subscribed and don't bother
modifying mail headers..)
Since it wasn't mentioned so far; outside of gnome.org, on the Python
side of things, there exists the GTK+ 3 tutorial [0] maintained by
Sebastian Pölsterl (accepts pull requests, but isn't actively
On 6 March 2014 10:07, Christoph Reiter reiter.christ...@gmail.com wrote:
(responding to the wrong mail since I just subscribed and don't bother
modifying mail headers..)
Since it wasn't mentioned so far; outside of gnome.org, on the Python
side of things, there exists the GTK+ 3 tutorial [0]
On 03/04/2014 07:05 PM, Frederic Peters wrote:
Hi Allan,
Allan Day wrote:
So, are you interested?
It would help to know a bit more about what you think this
coordination role would involve. Are you concerned with keeping
technical changes in step, for example, or is it more the content in
On Tue, Mar 4, 2014, at 10:54 AM, Jasper St. Pierre wrote:
The issue seems to be that people show up, write a bunch of tutorials,
docs, build a website, and then never finish it. They just leave and
we're left with a half-finished developer docs site.
It's been great seeing this happen at the
On Wed, Mar 5, 2014 at 2:20 PM, Michael Hill mdhil...@fastmail.fm wrote:
On Tue, Mar 4, 2014, at 10:54 AM, Jasper St. Pierre wrote:
The issue seems to be that people show up, write a bunch of tutorials, docs,
build a website, and then never finish it. They just leave and we're left
with a
Hey,
It's been proved again in recent hackfests, we have a really great
team writing user documentations, and thanks have to be given to
Shaun, and now Kat, for coordinating the effort.
On the other hand we have absolutely no coordination for developer
docs, I maintain developer.gnome.org with
Frederic Peters fpet...@gnome.org wrote:
...
It's been proved again in recent hackfests, we have a really great
team writing user documentations, and thanks have to be given to
Shaun, and now Kat, for coordinating the effort.
On the other hand we have absolutely no coordination for developer
Hi Allan,
Allan Day wrote:
So, are you interested?
It would help to know a bit more about what you think this
coordination role would involve. Are you concerned with keeping
technical changes in step, for example, or is it more the content in
our hand written documentation that we need to
The issue seems to be that people show up, write a bunch of tutorials,
docs, build a website, and then never finish it. They just leave and we're
left with a half-finished developer docs site.
Usually, the tutorials that these guys write end up not compiling or
running in newer versions of the
On Tue, Mar 4, 2014 at 10:54 AM, Jasper St. Pierre
jstpie...@mecheye.net wrote:
The issue seems to be that people show up, write a bunch of tutorials, docs,
build a website, and then never finish it. They just leave and we're left
with a half-finished developer docs site.
This is very true
On Tue, 2014-03-04 at 13:47 -0800, Sriram Ramkrishna wrote:
On Tue, Mar 4, 2014 at 10:54 AM, Jasper St. Pierre
jstpie...@mecheye.net wrote:
The issue seems to be that people show up, write a bunch of tutorials, docs,
build a website, and then never finish it. They just leave and we're left
31 matches
Mail list logo
