Documentation Portal Meeting Minutes - 2018-04-18

[Sriram Ramkrishna <sri ramkrishna me>]

Link to the minutes on Gitlab - https://gitlab.gnome.org/Community/DeveloperPortal/wikis/Meetings/2018-04-18

Meeting Minutes as follows:

Attendees: 

    * Ken

    * Sri

    * Michael

    

    

    Agenda:

        

 * developer portal server status - https://bugzilla.gnome.org/show_bug.cgi?id=794984

        Not complete, put a note for an update - 

        * Outcome of the  conversation on DDL - https://mail.gnome.org/archives/desktop-devel-list/2018-April/msg00008.html

           Good to know all the other efforts that were out there, especially the mockups by Allan Day which addresses - : https://gitlab.gnome.org/Community/DeveloperPortal/issues/9

           

* default language -  

        There are two issues here, the long term issue of getting language communities to incorporate gobject as part the language paradigm.  This is difficult as we will need someone who understands GObject to go into the various language communitues and argue for incorporating GObject as part of the language as part of an overall  "GUI support'.  Some languages for instances, implicitly support a basic GUI, we could make that GObject/GTK+.  This comes from the DDL thread and specifically by ebassi.

        

        The other issue is that we need something for the short term, and that means we need to create a guide that has a preferred language for a new developer, but doesn't try to exclude other languges.  This is so that we have a basis for people to start from.  What language we pick is ased on the following criteria:

            

            * reasonable toolchain (integration with GNOME Builder)

            * good API docs (we should be able to create documentation on the portal and it gets shown in Builder)  Would be nice to have identical content in Builder and documentation portal

            * Documentation that is manageable, searchable, complete, and up to date

            

        We need an on-going dicsussion on what that language should be.  (Michael will lead that with Phllip, Sri will talk with Christian)

        

    Actions:

        * Michael to build Django templates from Allan's mockup site: TODO

        * Sri to follow up on hosting on GNOME infrastructure: TODO

        * Ken to work on database backups of the dev site: TODO

        * Michael to talk to Philip Chimento about JS API docs & toolchain: TODO

        * Sri to talk to Christian about Builder support & integration: TODO

        * Sri to get representation from GNOME docs team, and perhaps decide a new meeting time if it makes sense: TODO