Bug 265253 - Add FreshPorts component to Services product
Summary: Add FreshPorts component to Services product
Status: Closed Not Accepted
Alias: None
Product: Services
Classification: Unclassified
Component: Bug Tracker (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Some People
Assignee: Kubilay Kocak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-16 19:28 UTC by Yuri Victorovich
Modified: 2022-10-26 01:37 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yuri Victorovich freebsd_committer freebsd_triage 2022-07-16 19:28:19 UTC
freshports.org is one of the services.
Comment 1 Yuri Victorovich freebsd_committer freebsd_triage 2022-07-16 19:31:18 UTC
mike at langille.org is probably a contact person.
Comment 2 Yuri Victorovich freebsd_committer freebsd_triage 2022-07-16 19:38:15 UTC
(In reply to Yuri Victorovich from comment #1)

No, e-mails to mike@langille.org get rejected.
I don't know who is the contact person.
Comment 3 Graham Perrin freebsd_committer freebsd_triage 2022-07-17 07:57:18 UTC
<https://www.freshports.org/> has its prominent sidebar link, 

    This site ▶ Issues

– which I use, I was never asked to report issues elsewhere. 


(In reply to Yuri Victorovich from comment #2)

> … I don't know who is the contact person.

Sidebar: 

    This site ▶ Contact
    <https://www.freshports.org/contact.php>

> … If you see a problem with the website (incorrect information, 
> errors, etc), please let us know. The best place for that is via a 
> GitHub Issue. 

– plus an e-mail address for Dan Langille, not Mike.
Comment 4 Graham Perrin freebsd_committer freebsd_triage 2022-07-17 08:25:46 UTC
(In reply to Yuri Victorovich from comment #0)

> freshports.org is one of the services.

I do love (and promote) FreshPorts, however it's not within the freebsd.org domain; not listed at <https://www.freebsd.org/administration/>; and so on.

For what it's worth: I think of FreshPorts as distinct from FreeBSD Project sites and services, in the same way as The FreeBSD Foundation website is distinct. Separate, but no less valuable for being separate. 

Related: bug 265264.
Comment 5 Dan Langille freebsd_committer freebsd_triage 2022-07-17 21:32:31 UTC
(In reply to Yuri Victorovich from comment #1)

No, mike is not. :)
Comment 6 Dan Langille freebsd_committer freebsd_triage 2022-07-17 21:34:44 UTC
Eventually, I hope freshports is taken over by the FreeBSD project. I've run it for 22+ years and I can't see that continuing for 22 more years.
Comment 7 Yuri Victorovich freebsd_committer freebsd_triage 2022-07-17 22:01:39 UTC
(In reply to Dan Langille from comment #6)

I think you should approach the FreeBSD Foundation with this suggestion.
Comment 8 Kubilay Kocak freebsd_committer freebsd_triage 2022-10-11 23:17:56 UTC
(In reply to Dan Langille from comment #6)

@Dan We're happy to add a Services :: FreshPorts if that would be useful for you and the community. We'd only require that we could set a contact for default Assignee and optionally Default CC such that newly created issues notified the appropriate people and taken to resolution
Comment 9 Dan Langille freebsd_committer freebsd_triage 2022-10-12 00:18:51 UTC
(In reply to Kubilay Kocak from comment #8)
I'm not opposed and I'm not driving it. If it's helpful, go for it.

We could create freshports.org email address just for this. It could be an alias and go to multiple people.

I've been running FreshPorts for 20 years. I won't be at it for 20 more. Others will eventually take over.
Comment 10 Kubilay Kocak freebsd_committer freebsd_triage 2022-10-12 00:27:23 UTC
(In reply to Dan Langille from comment #9)

Understood. The only considerations for us are:

- We can set a default Assignee (and/or CC if needed)
- Issues created for the component are handled well

Other consideration might be:


- If there is an existing method mentioned publicly for reporting issues, we may not want to create a(nother) method here.

- As ubiquitous and integrated as freshports is within the freebsd ecosystem, if and until freshports ends up more a 'freebsd service', creating an issue reporting capability here may confuse users as to its level of support, and/or who is (currently) responsible for it.

We don't currently have any in-project (not you), capability to resolve freshports issues.

Ultimately, I think you are the best current person to decide which way to go, as presumably existing freshports.org people (you only?) would end up 'on the hook' for resolution.
Comment 11 Dan Langille freebsd_committer freebsd_triage 2022-10-12 00:45:56 UTC
(In reply to Kubilay Kocak from comment #10)

At present, everything goes through https://github.com/FreshPorts/freshports/issues
Comment 12 Kubilay Kocak freebsd_committer freebsd_triage 2022-10-26 01:35:32 UTC
Closing (per proposal in this issue), upstream has an existing workflow and issue tracking system/method.

Note: This is one instance of quite a few where external upstream repos/processes exist (including freebsd @ github eg: pkg etc), but we may (we do) still have users reporting issues here. Prime examples of this are bug/feature reports for:

ports-mgmt/pkg: *
ports-pgmt/poudriere: *

The broader issue of this overlapping/separate workflow & processes is not in scope for this issue, but I note the 'higher-level problem' here for future reference.
Comment 13 Kubilay Kocak freebsd_committer freebsd_triage 2022-10-26 01:37:06 UTC
P.S: Per comment 8, we're happy to add the requested Service here, as long as issues created are 'handled well' and in a timely manner.