| | 1 | = MacPorts PortMgr |
| | 2 | |
| | 3 | There's a talk from 2016, see [wiki:Meetings/MacPortsMeeting2016/Programme#MacPortsPortMgr]. Compared to two years ago, `portmgr@` no longer deals with managing the infrastructure, since we now have the infrastructure team to do that and rely on GitHub. |
| | 4 | |
| | 5 | == Should there be a voting process to confirm `portmgr@` and/or get new members elected? |
| | 6 | * Is this really necessary? Since there is very little conflict within MacPorts anyway, elections might be more trouble then it's worth. |
| | 7 | * Getting voting right is complicated. |
| | 8 | |
| | 9 | == `portmgr@` response times |
| | 10 | * `portmgr@` is sometimes slow to respond to inquiries |
| | 11 | * Should there be a "portmgr@ timeout" (one or two weeks) for somebody to object and a default to accept a proposal if the timeout occurs? |
| | 12 | * This was a problem when discussing funding requests for travel to the meeting. |
| | 13 | |
| | 14 | == Legal organizations & fund handling |
| | 15 | * Handling money is an issue for us, since we cannot easily accept donations |
| | 16 | * There are options, such as founding an association (which may require a certain number of people in a certain jurisdiction) or joining an existing organization such as Software Freedom Conservancy |
