Thread: Update the git landing page

Update the git landing page

From
Greg Sabino Mullane
Date:
For reasons, I was scanning for something here today:


...and wow!, some of that stuff is very old and clearly will never be used again. Maybe we can move anything not updated in three years to a separate page, or at least put it at the bottom of the list? And while we are at it, can we put the actual postgres project at the top? It doesn't look good that the first three projects have had no updates in a decade on average, and you have to dig a bit to find postgres.

--
Cheers,
Greg

--
Enterprise Postgres Software Products & Tech Support

Re: Update the git landing page

From
Magnus Hagander
Date:
On Thu, Feb 20, 2025 at 9:29 PM Greg Sabino Mullane <htamfids@gmail.com> wrote:
For reasons, I was scanning for something here today:


...and wow!, some of that stuff is very old and clearly will never be used again. Maybe we can move anything not updated in three years to a separate page, or at least put it at the bottom of the list? And while we are at it, can we put the actual postgres project at the top? It doesn't look good that the first three projects have had no updates in a decade on average, and you have to dig a bit to find postgres.


This is the output from gitweb. I don't believe gitweb supports any such pagination.

There is a link to the postgres project in the header text :)

//Magnus

Re: Update the git landing page

From
Daniel Gustafsson
Date:
On 20 Feb 2025, at 21:31, Magnus Hagander <magnus@hagander.net> wrote:

On Thu, Feb 20, 2025 at 9:29 PM Greg Sabino Mullane <htamfids@gmail.com> wrote:
For reasons, I was scanning for something here today:


...and wow!, some of that stuff is very old and clearly will never be used again. Maybe we can move anything not updated in three years to a separate page, or at least put it at the bottom of the list? And while we are at it, can we put the actual postgres project at the top? It doesn't look good that the first three projects have had no updates in a decade on average, and you have to dig a bit to find postgres.


This is the output from gitweb. I don't believe gitweb supports any such pagination.

You can instead use cgit and sort by idle, that will order the list with the
oldest entries below the fold:

https://git.postgresql.org/cgit/?s=idle

--
Daniel Gustafsson

Re: Update the git landing page

From
"Euler Taveira"
Date:
On Thu, Feb 20, 2025, at 5:34 PM, Daniel Gustafsson wrote:
On 20 Feb 2025, at 21:31, Magnus Hagander <magnus@hagander.net> wrote:

On Thu, Feb 20, 2025 at 9:29 PM Greg Sabino Mullane <htamfids@gmail.com> wrote:
For reasons, I was scanning for something here today:


...and wow!, some of that stuff is very old and clearly will never be used again. Maybe we can move anything not updated in three years to a separate page, or at least put it at the bottom of the list? And while we are at it, can we put the actual postgres project at the top? It doesn't look good that the first three projects have had no updates in a decade on average, and you have to dig a bit to find postgres.


This is the output from gitweb. I don't believe gitweb supports any such pagination.

You can instead use cgit and sort by idle, that will order the list with the
oldest entries below the fold:

https://git.postgresql.org/cgit/?s=idle

... or click on Last Change link.


This order can also be set in the gitweb.conf [1].

our $default_projects_order = "age";

Regarding to the old projects, we can use the category feature that allows us
to group by category and the active projects can be listed on top. The
$projects_list_group_categories enables this feature [2].




--
Euler Taveira

Re: Update the git landing page

From
Álvaro Herrera
Date:
On 2025-Feb-21, Euler Taveira wrote:

> Regarding to the old projects, we can use the category feature that allows us
> to group by category and the active projects can be listed on top. The
> $projects_list_group_categories enables this feature [2].

> [2] https://git-scm.com/docs/gitweb.conf#Documentation/gitweb.conf.txt-projectslistgroupcategories

Sounds like we could create a category "obsolete" and add such a category
marker to all projects that haven't had a commit in the last, say, 5 years.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"La grandeza es una experiencia transitoria.  Nunca es consistente.
Depende en gran parte de la imaginación humana creadora de mitos"
(Irulan)



Re: Update the git landing page

From
Magnus Hagander
Date:
On Fri, Feb 21, 2025 at 4:54 PM Álvaro Herrera <alvherre@alvh.no-ip.org> wrote:
On 2025-Feb-21, Euler Taveira wrote:

> Regarding to the old projects, we can use the category feature that allows us
> to group by category and the active projects can be listed on top. The
> $projects_list_group_categories enables this feature [2].

> [2] https://git-scm.com/docs/gitweb.conf#Documentation/gitweb.conf.txt-projectslistgroupcategories

Sounds like we could create a category "obsolete" and add such a category
marker to all projects that haven't had a commit in the last, say, 5 years.

That sounds pretty reasonable. Maybe name it "inactive" or something instead, as it's not by definition obsolete just because it doesn't receive new commits, but basically that. 

--

Re: Update the git landing page

From
Álvaro Herrera
Date:
On 2025-Feb-21, Euler Taveira wrote:

> Regarding to the old projects, we can use the category feature that allows us
> to group by category and the active projects can be listed on top. The
> $projects_list_group_categories enables this feature [2].

This has been done.  It doesn't look particularly pretty though, and
the cgit interface doesn't show the categorization.


Some more of these repos can also be marked as inactive (the bottom few
when sorted by date):

fosdem2021-static.git
pgopen2019-test.git
pgdu2018.git
pgdu2018-test.git
pgphonehome.git


These projects here have no commits at all -- should they also be
inactive?

cfbot.git
pgjdbc.git
record_inspect.git

Or maybe we should just delete them?

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/



Re: Update the git landing page

From
Greg Sabino Mullane
Date:
The page is already looking much better, thanks! I think the final piece is:

our $default_projects_order = "age";

For the inactive projects, I would nominate everything "slony" and older, when sorting by age.

These projects here have no commits at all -- should they also be inactive?

Probably yes, although zero commits means no way to tell how old they are (that I could find) 

Cheers,
Greg

--
Enterprise Postgres Software Products & Tech Support