open-services / open-services Goto Github PK

Files exists but obviously need to actually contain text and be finalized.

Once V1 is finished, we lock it and start working towards a V2 if needed.

• finance
  • automatic-expensing.md
  • monthly-donations.md
  • public-history.md
  • self-funded.md
  • shutdown.md
• governance
  • governance.md
  • memberships.md
  • migration.md
  • transparency.md
• infrastructure
  • automatic-infrastructure.md
  • public-introspection.md
  • secrets.md
• product
  • compatibility.md
  • export.md
  • offline-first.md
  • phases.md
  • shutdown.md
  • single-product-focus.md
• Template for services/ directory
• Open Services Website
  • Outlines
  • Develop
  • Publish

Currently, the governance has bunch of scenarios that involve voting.

Some votes are open for everyone, others just for contributors and others just for the leadership team.

The is currently no structure around this voting, as the membership is very low.

I've been thinking about how to implement voting, either via a third-party service, or via GitHub.

First thing to sketch up would be how the states of the vote progresses.

Secondly finding something where we can implement it.

One service I found via OpenCollective's GitHub org is https://gh-polls.com/ (repo: https://github.com/apex/gh-polls) which seems simple and allows us to perform votes.

Only thing missing there is opening votes for when certain files changes (like if the docs/governance.md file changes, make sure the PR which proposes the change includes a poll to vote yes/no/veto)

So, Open-Registry was the first project but won't be the last.

In general, the idea is to see what services OSS developers and users are relying on to continue to exist for doing their work properly and efficiently.

Before Open-Registry was created, the idea was to have a website hosting service, run as a Open Service.

Other ideas include (but not excluded to):

• Proxy
• Forum
• Shop
• Storage
• Metrics
• Webhooks
• Monitoring
• Pager
• Deploy
• Comments
• Identification
• Forms

In the end, all of those are just possible ideas.

What else is there out there that people are using, but are currently limited to use for-profit companies for it?

Rather than having the leadership deciding on a roadmap they come up with, we should have a pipeline where ideas from the community can flow into the roadmap and get prioritized if it's a feature/thing a lot of people want.

Haven't thought too much about this, except the fact that we want people to be involved in the roadmap creation as much as possible.

The framework governance document has the following section:

2.2 Currently, the inclusion in this group is manual. You'll receive an invite to the "Contributors" team on GitHub if activity from you is seen.

We should be running a bot connected to GitHub which performs this action automatically.

So the rules would be:

1. Look through all the activity in the selected organization
2. If any activity is seen from a new contributor:

• Make sure they haven't been invited yet
• Invite them to the Contributors team

Should be relatively straightforward.

Right now, services would have to manually perform any expensing for infrastructure. We should provide a supported way of doing this automatically.

• Receive invoices for infrastructure costs
  • Hetzner
  • DNSimple
• Automatically create expense report for OpenCollective
  • OpenCollective to support creation of invoices via API
• Create service for receiving invoices and create expense in OpenCollective