[prev in list] [next in list] [prev in thread] [next in thread]
List: gtk-devel
Subject: Re: Contribution question
From: Pavlo Solntsev <pavlo.solntsev () gmail ! com>
Date: 2018-01-24 2:24:30
Message-ID: CADsq9iqjzoYR4iywYYFaRx0fRJ3p6Rmrt3+aEwseTTUpgY5iCg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Dear Sri.
Could you please outline the scope of the project you are talking about? It
wasn't clear to me. The biggest problem with GNOME infrastructure in my
opinion is a spreading documentation all the way around and luck of
examples in API. Think about, if I am professional GNOME developer I need
only simple reference API. If I am newcomers, I need more then that. I need
examples, clear explanation not for advanced users. The recent observation
is GList object. Citation from API page "There is no function to create a
GList <glib-Doubly-Linked-Lists.html#GList>. NULL
<glib-Standard-Macros.html#NULL:CAPS> is considered to be a valid, empty
list so you simply set a GList <glib-Doubly-Linked-Lists.html#GList>* to
NULL <glib-Standard-Macros.html#NULL:CAPS> to initialize it." Does it mean
that GList object MUST be initialized to NULL. For me it doesn't. Try to
use g_list_append() for list object non initiated to NULL. I am not talking
how many hours i spent to setup JHBuild, Flatpak (still not sure how to use
it for dev), BuildStream. Every single tool I listed has significant
limitation. And again, I don't know, is it luck of functionality or
documentation. Buildstream was promising but then I realized I can't use my
current project to test, say gnome-builder. They are not visible. Anyway, I
can continue for a long time. Playing around I built a solid understanding
how GNOME tools designed. Basic understanding. I decided to help with Glib
because it is fundamental library for GNOME infrastructure and all GNOME
development. Actually not just GNOME. I remember, when I just start using
GNOME infrastructure, It was hard to collect all documentation in one
place. I didn't know what i need. I can see progress since that time. But
still some work needs to be done. I can compare to QT project. devhelp can
be that good wrap for documentation. The same html can be placed online and
It should not be just an API reference. I am open for discussion. Do you
have a clear goal/picture for your project?
Sorry for this kind of stream of thoughts. Some parts may not be relevant
to this email list. I don't want to create much discussion from this. I am
not trying to blame anyone or criticize just giving you my overall
impression. World is not perfect, but we should try to make it better.
Best.
-Pavlo Solntsev
---------------------------------------------------------------------------------------------
*Please avoid sending me Word or PowerPoint attachments.See
http://www.gnu.org/philosophy/no-word-attachments.html
<http://www.gnu.org/philosophy/no-word-attachments.html>*
On Tue, Jan 23, 2018 at 6:35 PM, Sriram Ramkrishna <sri@ramkrishna.me>
wrote:
>
>
> On Thu, Jan 18, 2018 at 3:30 PM Pavlo Solntsev <pavlo.solntsev@gmail.com>
> wrote:
>
>> Hi,
>>
>> To better understand how some glib modules work, I write mini tests. I
>> was thinking it would be beneficial for a lot of people if more examples
>> will be included into the documentation to better explain how an object can
>> be used. Similar to what QT has. I may contribute my examples. When I see
>> a code on git hub I think about pull request. Do you use this approach? Or
>> I should generate a patch and attach it to the bug report as described here
>> https://github.com/GNOME/glib. I saw https://gitlab.gnome.org/ was
>> created. Is it a common trend for ? Does glib also go there? Sorry for so
>> many questions, just want to understand how dev process works.
>>
>>
>
> Some of us are working on a documentation portal and we would love
> volunteers. The goal is to create code snippets and what not. But the
> current structure at developer.gnome.org has documentation in various
> parts and doesn't have a particular organizing principle (eg someone who
> understands how technical documentation is put together) across all
> languages.
>
> So if you want to help with creating documetnation we could definitely use
> you.
>
> sri
>
> Thanks.
>>
>>
>>
>> -Pavlo Solntsev
>> ------------------------------------------------------------
>> ---------------------------------
>>
>> *Please avoid sending me Word or PowerPoint attachments.See
>> http://www.gnu.org/philosophy/no-word-attachments.html
>> <http://www.gnu.org/philosophy/no-word-attachments.html>*
>> _______________________________________________
>> gtk-devel-list mailing list
>> gtk-devel-list@gnome.org
>> https://mail.gnome.org/mailman/listinfo/gtk-devel-list
>>
>
[Attachment #5 (text/html)]
<div dir="ltr"><div><div><div>Dear Sri.<br><br></div>Could you please outline the \
scope of the project you are talking about? It wasn't clear to me. The biggest \
problem with GNOME infrastructure in my opinion is a spreading documentation all the \
way around and luck of examples in API. Think about, if I am professional GNOME \
developer I need only simple reference API. If I am newcomers, I need more then that. \
I need examples, clear explanation not for advanced users. The recent observation is \
GList object. Citation from API page "<span \
style="color:rgb(0,0,0);font-family:cantarell,sans-serif;font-size:medium;font-style:n \
ormal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:sta \
rt;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline;float:none">There \
is no function to create a<span class="gmail-Apple-converted-space"> \
</span></span><a class="gmail-link" href="glib-Doubly-Linked-Lists.html#GList" \
title="struct GList" \
style="text-decoration:none;color:rgb(52,101,164);font-family:cantarell,sans-serif;fon \
t-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text- \
align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span \
class="gmail-type">GList</span></a><span \
style="color:rgb(0,0,0);font-family:cantarell,sans-serif;font-size:medium;font-style:n \
ormal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:sta \
rt;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline;float:none">.<span \
class="gmail-Apple-converted-space"> </span></span><a class="gmail-link" \
href="glib-Standard-Macros.html#NULL:CAPS" title="NULL" \
style="text-decoration:none;color:rgb(52,101,164);font-family:cantarell,sans-serif;fon \
t-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text- \
align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><code \
class="gmail-literal">NULL</code></a><span \
style="color:rgb(0,0,0);font-family:cantarell,sans-serif;font-size:medium;font-style:n \
ormal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:sta \
rt;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline;float:none"><span \
class="gmail-Apple-converted-space"> </span>is considered to be a valid, empty list \
so you simply set a<span class="gmail-Apple-converted-space"> </span></span><a \
class="gmail-link" href="glib-Doubly-Linked-Lists.html#GList" title="struct GList" \
style="text-decoration:none;color:rgb(52,101,164);font-family:cantarell,sans-serif;fon \
t-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text- \
align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span \
class="gmail-type">GList</span></a><span \
style="color:rgb(0,0,0);font-family:cantarell,sans-serif;font-size:medium;font-style:n \
ormal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:sta \
rt;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline;float:none">* \
to<span class="gmail-Apple-converted-space"> </span></span><a class="gmail-link" \
href="glib-Standard-Macros.html#NULL:CAPS" title="NULL" \
style="text-decoration:none;color:rgb(52,101,164);font-family:cantarell,sans-serif;fon \
t-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text- \
align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><code \
class="gmail-literal">NULL</code></a><span \
style="color:rgb(0,0,0);font-family:cantarell,sans-serif;font-size:medium;font-style:n \
ormal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:sta \
rt;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline;float:none"><span \
class="gmail-Apple-converted-space"> </span>to initialize it.</span>" Does it \
mean that GList object MUST be initialized to NULL. For me it doesn't. Try to use \
g_list_append() for list object non initiated to NULL. I am not talking how many \
hours i spent to setup JHBuild, Flatpak (still not sure how to use it for dev), \
BuildStream. Every single tool I listed has significant limitation. And again, I \
don't know, is it luck of functionality or documentation. Buildstream was \
promising but then I realized I can't use my current project to test, say \
gnome-builder. They are not visible. Anyway, I can continue for a long time. Playing \
around I built a solid understanding how GNOME tools designed. Basic understanding. I \
decided to help with Glib because it is fundamental library for GNOME infrastructure \
and all GNOME development. Actually not just GNOME. I remember, when I just start \
using GNOME infrastructure, It was hard to collect all documentation in one place. I \
didn't know what i need. I can see progress since that time. But still some work \
needs to be done. I can compare to QT project. devhelp can be that good wrap for \
documentation. The same html can be placed online and It should not be just an API \
reference. I am open for discussion. Do you have a clear goal/picture for your \
project? <br></div>Sorry for this kind of stream of thoughts. Some parts may not be \
relevant to this email list. I don't want to create much discussion from this. I \
am not trying to blame anyone or criticize just giving you my overall impression. \
World is not perfect, but we should try to make it better. \
<br><br></div>Best.<br><div><div><br><br><br><br></div></div></div><div \
class="gmail_extra"><br clear="all"><div><div class="gmail_signature" \
data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div \
dir="ltr">-Pavlo Solntsev</div><div \
dir="ltr">---------------------------------------------------------------------------------------------</div></div><div \
dir="ltr"><em style="color:rgb(0,0,0);font-family:"Times New \
Roman";font-size:16px">Please avoid sending me Word or PowerPoint \
attachments.<br>See <a href="http://www.gnu.org/philosophy/no-word-attachments.html" \
target="_blank">http://www.gnu.org/philosophy/no-word-attachments.html</a></em><br></div></div></div></div></div></div>
<br><div class="gmail_quote">On Tue, Jan 23, 2018 at 6:35 PM, Sriram Ramkrishna \
<span dir="ltr"><<a href="mailto:sri@ramkrishna.me" \
target="_blank">sri@ramkrishna.me</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><br><br><div class="gmail_quote"><span \
class=""><div dir="ltr">On Thu, Jan 18, 2018 at 3:30 PM Pavlo Solntsev <<a \
href="mailto:pavlo.solntsev@gmail.com" \
target="_blank">pavlo.solntsev@gmail.com</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><div>Hi,</div><div><br></div><div>To better \
understand how some glib modules work, I write mini tests. I was thinking it would be \
beneficial for a lot of people if more examples will be included into the \
documentation to better explain how an object can be used. Similar to what QT has. I \
may contribute my examples. When I see a code on git hub I think about pull request. \
Do you use this approach? Or I should generate a patch and attach it to the bug \
report as described here <a href="https://github.com/GNOME/glib" \
target="_blank">https://github.com/GNOME/glib</a>. I saw <a \
href="https://gitlab.gnome.org/" target="_blank">https://gitlab.gnome.org/</a> was \
created. Is it a common trend for ? Does glib also go there? Sorry for so many \
questions, just want to understand how dev process works. \
</div><div><br></div></div></blockquote><div><br></div><div><br></div></span><div>Some \
of us are working on a documentation portal and we would love volunteers. The goal \
is to create code snippets and what not. But the current structure at <a \
href="http://developer.gnome.org" target="_blank">developer.gnome.org</a> has \
documentation in various parts and doesn't have a particular organizing principle \
(eg someone who understands how technical documentation is put together) across all \
languages.</div><div><br></div><div>So if you want to help with creating \
documetnation we could definitely use you. \
<br></div><div><br></div><div>sri</div><div><br></div><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span \
class=""><div dir="ltr"><div></div><div>Thanks.</div><div><br></div><div><br></div><br \
clear="all"><div><div \
class="m_-2516630438251350537m_-6978405076964271130gmail_signature"><div \
dir="ltr"><div><div dir="ltr"><div><div dir="ltr">-Pavlo Solntsev</div><div \
dir="ltr">------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>---</div></div><div \
dir="ltr"><i style="color:rgb(0,0,0);font-family:"Times New \
Roman";font-size:16px">Please avoid sending me Word or PowerPoint \
attachments.<br>See <a href="http://www.gnu.org/philosophy/no-word-attachments.html" \
target="_blank">http://www.gnu.org/philosophy/<wbr>no-word-attachments.html</a></i><br></div></div></div></div></div></div>
</div></span>
______________________________<wbr>_________________<br>
gtk-devel-list mailing list<br>
<a href="mailto:gtk-devel-list@gnome.org" \
target="_blank">gtk-devel-list@gnome.org</a><br> <a \
href="https://mail.gnome.org/mailman/listinfo/gtk-devel-list" rel="noreferrer" \
target="_blank">https://mail.gnome.org/<wbr>mailman/listinfo/gtk-devel-<wbr>list</a><br>
</blockquote></div></div>
</blockquote></div><br></div>
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-devel-list
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic