Обсуждение: Patch to clean up and add missing GSoC pages
Hi there,
Attached you'll find a patch containing changes on the GSoC pages.
Following changes have been done:
Page summerofcode.html changed:
Added all information currently available for GSoC 2023.
In addation I have added a section in FAQ pointing to the PostgreSQL Wiki pages about communication channels and how to apply.
The section with recent projects has been changed with the projects from the previous two years, namely 2021 and 2022.
I kept the names of the people who had worked on that project, as I believe it is only fair to mention them here.
Pages summerfocode2022.html, summerfocode2021.html, summerfocode2020.html, summerfocode2019.html, summerfocode2018.html, summerfocode2017.html added:
The layout is based on 2018.
Added all information currently available for GSoC about each year.
The section with recent projects has been changed with the projects from the previous two years, except 2018 with last year (2017) and 2017 which is kept as it was.
I kept the names of the people who had worked on that project, as I believe it is only fair to mention them here.
In addition I changed the text and link about the timeline to always go to the current timeline on the google pages. The old timeline is not available and in my humble opinion it might be useful, to go to the current information.
Best regards,
Stefanie
-- ProOpenSource OÜ Director Stefanie Janine Stölting Sepapaja 6 Tallinn 15551 Estonia Registry Code: 16258841 Web: https://ProOpenSource.eu
Вложения
Hi Stefanie, On 4/21/23 5:27 AM, Stefanie Janine Stölting wrote: > Hi there, > > Attached you'll find a patch containing changes on the GSoC pages. Thanks for submitting this! I'm not sure where these pages are linkable from currently. The only link I see is to the wiki from the developers page[1], but we don't have any more links back to the .org page. IIRC, this was done in part due to what you've raised with this patchset, i.e. the content goes stale and requires someone to actively maintain it. I agree that the timeline is useful. Maybe we put that on the developers page, since it seems all of the other content is available on the wiki? That way, we can retire the .org page. Thoughts? Thanks, Jonathan [1] https://www.postgresql.org/developer/
Вложения
> On 22 Apr 2023, at 20:59, Jonathan S. Katz <jkatz@postgresql.org> wrote: > > Hi Stefanie, > > On 4/21/23 5:27 AM, Stefanie Janine Stölting wrote: >> Hi there, >> Attached you'll find a patch containing changes on the GSoC pages. > > Thanks for submitting this! Seconded! > I'm not sure where these pages are linkable from currently. The only link I see is to the wiki from the developers page[1],but we don't have any more links back to the .org page. IIRC, this was done in part due to what you've raised withthis patchset, i.e. the content goes stale and requires someone to actively maintain it. It's currently not linked at all, but searching for GSoC on the site leads to /summerofcode/ which is in a sad state now. > I agree that the timeline is useful. Maybe we put that on the developers page, since it seems all of the other contentis available on the wiki? That way, we can retire the .org page. I would prefer to actively maintain the .org page as the entry point for GSoC and leave the Wiki for the projects and other things which changes more frequently. The current maintainence overhead is to change the list of admins and mentors as well as add the past year, and that seems quite manageable. I do however think we should keep the timeline on /summerofcode/ and not on each individual yearly archive page (the fact that newly added pages in the patch has the timeline to 2008 while the main page goes to 2006 highlights this). We can work on where to link to this as a separate step, but to clean up the current state I think we should go ahead with this patch. Reading through it can't spot any markup errors. -- Daniel Gustafsson
Hi there, I have been thinking about how to have better links, too. An easy solution might be to just link to the Wiki for year, the GSoC page is about. Every GSoC page itself might link to a certain amount of recent years, for example two. That way you can go to previous years in nice way. I can add the two points fast. The goal for this patch has not been, to have everything replaced at once, it was about filling up the information that is available on Googles GSoC pages and to fill the gap. And in addition to have links to Google GSoC sites, that do work instead of ending on an empty page (if you are lucky). In a next step I would also like to go back on GSoC pages as far as possible, meaning, what I can get on information of Google as they changed the links. Some pages might be available on archive pages, which I will check, too. I believe it would also be useful, to have more information about the projects on our pages. Namely the project descriptions on Google GSoC pages. Cheers, Stefanie -- ProOpenSource OÜ Director Stefanie Janine Stölting Sepapaja 6 Tallinn 15551 Estonia Registry Code: 16258841 VAT: EE102386758 Web: https://ProOpenSource.eu On 24.04.23 10:33, Daniel Gustafsson wrote: >> On 22 Apr 2023, at 20:59, Jonathan S. Katz <jkatz@postgresql.org> wrote: >> >> Hi Stefanie, >> >> On 4/21/23 5:27 AM, Stefanie Janine Stölting wrote: >>> Hi there, >>> Attached you'll find a patch containing changes on the GSoC pages. >> Thanks for submitting this! > Seconded! > >> I'm not sure where these pages are linkable from currently. The only link I see is to the wiki from the developers page[1],but we don't have any more links back to the .org page. IIRC, this was done in part due to what you've raised withthis patchset, i.e. the content goes stale and requires someone to actively maintain it. > It's currently not linked at all, but searching for GSoC on the site leads to > /summerofcode/ which is in a sad state now. > >> I agree that the timeline is useful. Maybe we put that on the developers page, since it seems all of the other contentis available on the wiki? That way, we can retire the .org page. > I would prefer to actively maintain the .org page as the entry point for GSoC > and leave the Wiki for the projects and other things which changes more > frequently. The current maintainence overhead is to change the list of admins > and mentors as well as add the past year, and that seems quite manageable. > > I do however think we should keep the timeline on /summerofcode/ and not on > each individual yearly archive page (the fact that newly added pages in the > patch has the timeline to 2008 while the main page goes to 2006 highlights > this). > > We can work on where to link to this as a separate step, but to clean up the > current state I think we should go ahead with this patch. Reading through it > can't spot any markup errors. > > -- > Daniel Gustafsson >
On 22.04.23 20:59, Jonathan S. Katz wrote: > Hi Stefanie, > > On 4/21/23 5:27 AM, Stefanie Janine Stölting wrote: >> Hi there, >> >> Attached you'll find a patch containing changes on the GSoC pages. > > Thanks for submitting this! > > I'm not sure where these pages are linkable from currently. The only > link I see is to the wiki from the developers page[1], but we don't > have any more links back to the .org page. IIRC, this was done in part > due to what you've raised with this patchset, i.e. the content goes > stale and requires someone to actively maintain it. I changed the links to have only one link to the Wiki: The one, that the page is about. Beneath I added links to the two previous years of GSoC, except 2017, as there is only 2016 and no 2015. > I agree that the timeline is useful. Maybe we put that on the > developers page, since it seems all of the other content is available > on the wiki? That way, we can retire the .org page. > > Thoughts? > > Thanks, > > Jonathan > > [1] https://www.postgresql.org/developer/ As mentioned, the goal was to have the GSoC information for the current year and the most recent years available. More changes will probably come later for the years 2016 and older GSoC. The problem here is, that this information is mostly not available on Googles GSoC pages. Cheers, Stefanie
Вложения
On 25/04/2023 09:53, Stefanie Janine Stölting wrote: > > On 22.04.23 20:59, Jonathan S. Katz wrote: >> Hi Stefanie, >> >> On 4/21/23 5:27 AM, Stefanie Janine Stölting wrote: >>> Hi there, >>> >>> Attached you'll find a patch containing changes on the GSoC pages. >> >> Thanks for submitting this! >> >> I'm not sure where these pages are linkable from currently. The only >> link I see is to the wiki from the developers page[1], but we don't >> have any more links back to the .org page. IIRC, this was done in >> part due to what you've raised with this patchset, i.e. the content >> goes stale and requires someone to actively maintain it. > > I changed the links to have only one link to the Wiki: The one, that > the page is about. > > Beneath I added links to the two previous years of GSoC, except 2017, > as there is only 2016 and no 2015. > > >> I agree that the timeline is useful. Maybe we put that on the >> developers page, since it seems all of the other content is available >> on the wiki? That way, we can retire the .org page. >> >> Thoughts? >> >> Thanks, >> >> Jonathan >> >> [1] https://www.postgresql.org/developer/ > > As mentioned, the goal was to have the GSoC information for the > current year and the most recent years available. > > More changes will probably come later for the years 2016 and older > GSoC. The problem here is, that this information is mostly not > available on Googles GSoC pages. As the 2023 GSoC is closed as well, is this patch something which can go up on the website? Would be nice to have the information for all previous years where the project participated in GSoC. Regards, -- Andreas 'ads' Scherbaum German PostgreSQL User Group European PostgreSQL User Group - Board of Directors Volunteer Regional Contact, Germany - PostgreSQL Project
> On 11 Oct 2023, at 22:54, Andreas 'ads' Scherbaum <ads@pgug.de> wrote: > As the 2023 GSoC is closed as well, is this patch something which can go up on the website? > Would be nice to have the information for all previous years where the project participated in GSoC. It's on my TODO to properly review this patch, it just got sidetracked by a bazillion other entries on it but I'll get to it. -- Daniel Gustafsson