Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone.

Please find below the report on the maintenance and development of QGIS-Django 
and QGIS-Hugo for the last week:

Migration of the QGIS plugins website:

  *   We have successfully migrated the QGIS plugins website to an updated 
server. Many thanks to everyone who helped us achieve this.
  *   The QGIS plugins website now uses up-to-date stacks and packages such as 
Django 4, Postgresql 16, and the latest Metabase.
  *   Please feel free to share your feedback or create issues about them on 
the QGIS-Django repository

New PRs QGIS-Hugo:

  *   Fix in page anchor scroll
  *   Make the download link on top in the installation 
guide
  *   Change all project link occurrences to 
product

This week, I will work on fixing QGIS-Hugo issues, performing maintenance 
tasks, and updating the branding for the QGIS plugin website.

Best regards,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit http://kartoza.com to find out about open source:
* Desktop GIS programming services
* Geospatial web development
* GIS Training
* Consulting Services
Office: +261(0)34 09 524 73




From: Lova Andriarimalala 
Date: Friday, 3 May 2024 at 4:33 PM
To: qgis-developer@lists.osgeo.org 
Subject: QGIS Full Stack Web Developer Report
Hello everyone,

IMPORTANT NOTE FOR THE QGIS PLUGINS WEBSITE: We’ve scheduled the migration to 
the updated servers into production for 06 May 2024. During this time, 
uploading new plugins will be disabled and the ability to install plugins may 
be intermittently unavailable.

I mainly focused on the following tasks this week:

  *   Continue working with the QGIS Plugins Site branding 
updates. It’s based on the 
changes made for the PR #374

  *   Some final checks and fixes on the updated servers:

 *   Fix plugins download feature
 *   Fix all the warning status on the monitoring server

Next week, I will focus on post-migration tasks and maintenance. We will also 
continue with the branding update for the QGIS plugins website.

Have a great weekend.

Best regards,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit http://kartoza.com to find out about open source:
* Desktop GIS programming services
* Geospatial web development
* GIS Training
* Consulting Services
Office: +261(0)34 09 524 73



___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Post-mortem of application to Google Summer of Code

[Emma Hain via QGIS-Developer]

Hi All
How can we, and do we prepare for this next year?

I take it we need:

Mentors to be put forward - I see this information
:
*Mentors are people from the community who volunteer to work with a GSoC
contributor. Mentors provide guidance such as pointers to useful
documentation, code reviews, etc. In addition to providing GSoC
contributors with feedback and pointers, a mentor acts as an ambassador to
help GSoC contributors integrate into their project’s community. Some
organizations choose to assign more than one mentor to each of their GSoC
contributors. Many members of the community provide guidance to their
project’s GSoC contributors without mentoring in an “official” capacity,
much as they would answer anyone’s questions on the project’s mailing list
or chat channel. *

I also see there is a fair amount time required by the mentor and that a
stipend is provided to the project at the end of the GSoC. Would this
stipend be then passed onto the Mentor to assist with the time applied?


Contributors - I see this is for individuals - is this something we can
broadcast on our channels and within our user groups?



On Mon, 6 May 2024 at 18:51, Julien Cabieces via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

>
> Hi Valentin,
>
> I'm really sad to hear that you were not selected.
>
> I was really happy to meet you in person in Grenoble, and thought at
> that time that you really deserved to be choosen. Your proposal was of
> high quality, and you prove to have a great maturity for your arge (and
> this post-mortem mail proves it even more, I share all of your
> conclusions).
>
> I think that we fail something on our side (Oslandia side) regarding the
> lack of mentors, and thought that this matter was addressed.
>
> I encourage you to continue your effort and hope to see QGIS pull
> requests in near future.
>
> Regards,
> Julien
>
>
>
> > Hi devs,
> >
> > Last month, I applied for Google Summer of Code (GSoC), unfortunately
> > I was not accepted into this year's program.
> > I know it's disappointing, since we all would like to see an open
> > source alternative to existing ETL, and I feel like the stars were
> > aligned here.
> >
> > So here my little post-mortem, and few tips and suggestions to help
> > futures applications:
> >
> > What went well
> >
> > - First QGIS community was very enthusiastic and supportive, I am very
> > grateful to the community. I was also incredibly well received at the
> > local contributor meeting in Grenoble.
> > - We had two rounds of feedbacks to taylor the proposal one by mail,
> > and a second in person with local contributor meeting
> >
> > What went wrong
> >
> > - Despite the enthusiasm around the proposal, my proposal was
> > rejected. I am only making a guess here, but I suppose it was because
> > of the lack of mentors.
> >
> > Tips and suggestions for future applications.
> >
> > *For students*
> > - Be proactive to look for mentors
> > Git commands like 'git log' and 'git blame' are your friends to find
> > people with common interest in your proposals.Gitk can also be used to
> > get a more friendly graphical interface
> > with 'gitk -- ./path/to/directory, you can see all the contributor who
> > committed in that specify directory for exemple to search for
> > processing related
> > use 'gitk -- ./src/core/processing/' or 'gitk -- ./src/gui/processing/'
> > - QGIS participates in GSoC under the umbrella of the OSGeo
> > organization. You don't only need to convince QGIS devs but also
> > OSGeo. So don't only submit proposals on the GSoC platform, and also
> > post your proposal on the Soc mailing list[0] dedicated to coordinate
> > at OSGeo level ( s...@lists.osgeo.org )
> > - Remember that mailing lists are plain text only, I had the surprise
> > to discover that all the formatting for quoted text didn't work,
> > because I sent my mails as html( which is the default in gmail) and
> > not as plain text (And I'm yet to find how to properly justify plain
> > text mail). The migration from mailing list to discourse should
> > however fix these issues .
> >
> > *For mentors*
> > - Volunteer as a mentor early on the SOC mailing list. There is
> > usually a call for ideas and mentors[1] around the end of January ~2
> > month before the application deadline for students. However at this
> > point you don't have the full picture, you don't know which proposals
> > students will submit. Some years there are multiple volunteers for
> > QGIS, this year there was no volunteers for the QGIS project
> >
> > *For both mentors and students*
> > - Communicate on SOC mailing list, I can't stress this enough. I think
> > it's the key point why my proposal was not accepted. It's unfortunate
> > because I discussed with multiple mentors/companies that were
> > interested in mentoring me, but we never formalised it on an official
> > channel of communication.
> > - Since OSGeo handles a lot of projects, it means we