4 ms·
Yeah, paying for accounts for half of your employees seems quite strange. I like that it allows otherwise paying users to create orgs but it creates weird polit
by kevincox 4y ago
Yeah, paying for accounts for half of your employees seems quite strange. I like that it allows otherwise paying users to create orgs but it creates weird politics like stated.
What about just allowing paying users to create many (some high number) orgs for up to 5 people? Maybe scaling a bit if multiple paying users are inside. Then bigger orgs need to be paid.
- twic 4y agoThe expectation is that companies will pay for accounts for all their developers, not half. The post explains pretty clearly: > Users who are members of an organization and have a paid account, regardless if by their own means or by way of sponsorship from the org, have access to both the org's resources and private ownership of resources on SourceHut, e.g. can submit builds.sr.ht jobs on their own account. Org members with unpaid accounts can access the org resources, but cannot hold private resources on SourceHut. > The goal of this approach is to allow users to form grassroots orgs without too much hassle over payment; to allow companies and formal organizations to manage billing centrally for their members; and to balance things such that adding Joe Support Tech to the bug trackers does not mean you have to pay for a full SourceHut account for them, while still incentivizing people to pay for more than 50% if their members would benefit from access to private resources (e.g. the dev team might all have paid accounts regardless of if it exceeds the 50% minimum, just because it's worth the money to them).