On Fri, 2018-04-06 at 15:51 +0200, Alexandre Franke wrote:
> On Thu, Apr 5, 2018 at 10:50 PM, Sriram Ramkrishna > wrote:
> > On Thu, Apr 5, 2018 at 2:18 PM Jeremy Bicha wrote:
> > > Let me confirm and restate: GNOME has a Docs team. It would be cool if
> >
On Fri, Apr 6, 2018 at 7:51 AM Alexandre Franke wrote:
> On Thu, Apr 5, 2018 at 10:50 PM, Sriram Ramkrishna
> wrote:
> > On Thu, Apr 5, 2018 at 2:18 PM Jeremy Bicha wrote:
> >> Let me confirm and restate: GNOME has a Docs team. It would
On Thu, Apr 5, 2018 at 10:50 PM, Sriram Ramkrishna wrote:
> On Thu, Apr 5, 2018 at 2:18 PM Jeremy Bicha wrote:
>> Let me confirm and restate: GNOME has a Docs team. It would be cool if
>> you would work with the existing Docs Team when doing big Docs stuff.
Michael Hall wrote:
...
> Is the design for the site used on
> https://people.collabora.com/~meh/gdd/index.html#getstarted still valid?
As valid as it ever was... It was primarily meant as a proof of
concept, particularly in terms of whether we could produce a decent
site
On Thu, Apr 5, 2018 at 2:18 PM Jeremy Bicha wrote:
> On Thu, Apr 5, 2018 at 10:18 AM, Allan Day wrote:
> > Michael Hall wrote:
> > ...
> >> We have a project
> >> on GNOME's Gitlab, a Telegram channel, and have been trying to hold
>
Thanks Allan,
Is the design for the site used on
https://people.collabora.com/~meh/gdd/index.html#getstarted still valid?
I really like the look of it, and I could easily turn it into a template
for Django CMS pages.
On 04/05/2018 01:07 PM, Allan Day wrote:
Michael Hall
On Thu, Apr 5, 2018 at 10:18 AM, Allan Day wrote:
> Michael Hall wrote:
> ...
>> We have a project
>> on GNOME's Gitlab, a Telegram channel, and have been trying to hold regular
>> meetings on it.
>
> This is all news to me... it would have been good to have
On Wed, Apr 4, 2018 at 3:35 PM Emmanuele Bassi wrote:
>
> Mostly because "promoting JavaScript" from a documentation point of view
> isn't related to toolchain improvements.
>
Right. That's why I wanted to ask where we were with tooling when it came
to javascript. Christian
Hi Allan!
On Thu, Apr 5, 2018 at 8:19 AM Allan Day wrote:
> Michael Hall wrote:
> ...
> > We have a project
> > on GNOME's Gitlab, a Telegram channel, and have been trying to hold
> regular
> > meetings on it.
>
> This is all news to me... it would have been
Michael Hall wrote:
...
>> I've been involved in quite a few discussions
>> about GNOME's developer documentation over the years, and have done a
>> fair amount of work on developer documentation design in the past [1]
>> (this came out of a meeting we had at GUADEC in 2016),
On 04/05/2018 10:18 AM, Allan Day wrote:
I've been involved in quite a few discussions
about GNOME's developer documentation over the years, and have done a
fair amount of work on developer documentation design in the past [1]
(this came out of a meeting we had at GUADEC in 2016), including
Michael Hall wrote:
...
> We have a project
> on GNOME's Gitlab, a Telegram channel, and have been trying to hold regular
> meetings on it.
This is all news to me... it would have been good to have heard about
the initiative sooner - I've been involved in quite a few
On 04/05/2018 09:48 AM, Allan Day wrote:
Michael Hall wrote:
...
Some of these are within reach, although as Bastian pointed out,
having the necessary infrastructure has been a stumbling block in the
past.
We've settled on
Who is "we"? Where is the planning and
I want to add my 2 cents:
For the last couple of years I had two experiences on JS vs. Python
platform support/DX in the context of GNOME.
On one hand, I coached someone to write a GNOME based app to write
something similar to Postman[0] to debug/design REST APIs.
>From the API reference
On 5 April 2018 at 14:36, Michael Hall wrote:
> On 04/04/2018 05:35 PM, Emmanuele Bassi wrote:
>
>> You can have the best documentation in the world — but if you don't have
>> people working on the tooling and the actual integration between the
>> language and the platform,
Michael Hall wrote:
...
>> Some of these are within reach, although as Bastian pointed out,
>> having the necessary infrastructure has been a stumbling block in the
>> past.
>
> We've settled on
Who is "we"? Where is the planning and discussion happening for this?
> using
On 04/05/2018 05:42 AM, Allan Day wrote:
Some of these are within reach, although as Bastian pointed out,
having the necessary infrastructure has been a stumbling block in the
past.
We've settled on using Django CMS and are working on getting an instance
up and running. I used this when we
On 04/04/2018 05:35 PM, Emmanuele Bassi wrote:
You can have the best documentation in the world — but if you don't
have people working on the tooling and the actual integration between
the language and the platform, then you don't have anything that other
people can use.
Indeed, and the
On 04/04/2018 05:21 PM, Giovanni Campagna wrote:
More overrides means more need for a language specific documentation,
rather than mentally translating the C API.
Whichever language we choose to promote to new app developers, we will
want to provide API docs specific to that language.
Emmanuele Bassi wrote:>:
...
> This was the conclusion of the 2013 DX hackfest:
>
> https://treitter.livejournal.com/14871.html
...
> - the announcement was made without resourcing, in the *hope* somebody
> would turn up
I don't think that's entirely true - my recollection
Sriram Ramkrishna wrote:
> Some of you may be aware that we have started a documentation effort in
> order to give application developers a proper set of documentation for them
> to write applications.
I'm not aware of this. Can you provide some more information? (Who's
I'm part of newcomers initiative and collaborate primarily on debugger
feature on Builder. Nowadays I'm working to add debug expressions (or
watches) to Builder but if I finish that I want to add a pdb plugin (add
python debugger capabilities for Builder) I can't promise anything but I'm
trying to
On 4 April 2018 at 19:39, Sriram Ramkrishna wrote:
> Some of you may be aware that we have started a documentation effort in
> order to give application developers a proper set of documentation for them
> to write applications.
>
> We need to optimize for one language rather
On Thu, Apr 5, 2018 at 12:21 AM, Giovanni Campagna
wrote:
>
>
> Python has autocompletion through Jedi (although it chokes on GI types,
> for understandable reasons). GJS's autocompletion relies on "word in the
> documents", which I found to be pretty OK anyway.
>
> One
On Wed, Apr 4, 2018 at 11:39 AM, Sriram Ramkrishna
wrote:
> Some of you may be aware that we have started a documentation effort in
> order to give application developers a proper set of documentation for them
> to write applications.
>
> We need to optimize for one language
On Wed, Apr 4, 2018 at 1:37 PM Bastian Ilso
wrote:
> From newcomer guide POV, the major blocker for us to start in writing
> javascript/python/etc documentation is having a modern central online
> place/platform to write, edit and store the documentation in. GNOME
>
From newcomer guide POV, the major blocker for us to start in writing
javascript/python/etc documentation is having a modern central online
place/platform to write, edit and store the documentation in. GNOME
Developer Center really needs a helping hand. To assess requirements
for such a
27 matches
Mail list logo