blob: 87cc9f7e2c5d641dbf4367264017b6490ed13739 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
=== FreshPorts - help wanted
Links: +
link:https://freshports.org/[FreshPorts] URL: link:https://freshports.org/[https://freshports.org/] +
link:https://news.freshports.org/[FreshPorts blog] URL: link:https://news.freshports.org/[https://news.freshports.org/]
Contact: Dan Langille <dvl@FreeBSD.org>
FreshPorts and FreshSource have reported upon FreeBSD commits for 20 years.
They cover all commits, not just ports.
FreshPorts tracks the commits and extracts data from the port Makefiles to create a database of information useful to both port maintainers and port users.
For example, link:https://www.freshports.org/security/acme.sh/[https://www.freshports.org/security/acme.sh/] shows the history of the _acme.sh_ port, back to its creation in May 2017.
==== Converting the backend repository
This topic deals with the FreshPorts code repository.
The front end (website) was converted from Subversion to Git several years ago.
The back end, which processes FreeBSD commits and updates the database, is still on Subversion.
I have wanted to convert these repositories to Git for some time.
I would like help with this please.
I'll give you a copy of the repositories and you give me back several Git repos (one for each).
They will be uploaded to link:https://github.com/FreshPorts[https://github.com/FreshPorts] (our project on GitHub).
These are the existing Subversion repos:
* ingress (code for the back end)
* database schema
* backend - monitoring code
* packaging - scripts for cutting new tarballs - deprecated via Git
* daemontools - now misnamed, because the scripts use man:daemon[8]
* periodics - scripts started by man:periodic[8]
* ports - for the FreeBSD packages which install the above.
==== I won't be running FreshPorts forever
It's been over 22 years and I know others must take over eventually.
I'd like to start that process now.
There are several aspects to FreshPorts:
* FreeBSD admin (updating the OS and packages)
* front end code (website - mostly PHP)
* back end code (commit processing - Perl, Python, shell)
* database design (PostgreSQL).
The database does not change very often and requires little maintenance compared to the applications and OS.
The website pretty much runs itself.
From time to time, a change to the FreeBSD ports infrastructure breaks something or requires a modification, but there is rarely any urgency to fix that.
This is not a huge time commitment.
There is a lot of learning.
While not a complex application, FreshPorts is also not trivial.
|
