[Idea]: Proposal for how to use channels to be described in ways of working

[vicenteherrera]

Contact Details

vicente.herrera@control-plane.io

What is the idea

Updating ways of working so it includes the different channels we have at our disposal, that are most accessible behind corporate firewalls.

Executive summary:

• Use email lists for informal discussion, info exchange, and announcements
• Use GitHub issues for meeting agenda, and formal discussion of decisions to be made
• Use GitHub board for tracking task and who would do them when it's know what should be done
• Google Drive: To be deprecated and move reference information also to GitHub.
• Repos:
  • Private: main work on Simple Governance Framework, and refereneces. To be moved to public before OSFF NYC.
  • Public: group description, main place to raise issues, and create board tasks
    • All info about ways of working should be available now on public repo, as people keep asking

Details:

• Finos Calendar: Shows when meetings will happen
• Email lists:
  • Group announcements.
  • Sending and receiving informal information, links, documentation, ideas.
  • Public list open to anyone also providing feedback and informal information.
• Google Drive:
  • Several organizations have it very difficult for people to access this medium. We should transition to share general knowledge about existing frameworks and regulations to GitHub, and encourage people to send references via email or directly with PRs.
  • We could start with PRs to the private repo so it takes shape until it's well organized.
• Repositories
  • Public one: right now, just description of the group.
    • Issues, and board tasks for generic group organization should be open here, as this will be the main repo, and general public will be able to comment here immediately.
  • Private one: holds current work on the Simple Governance Framework. Its content will be moved to the public one the day before OSFF NYC (30 Sept). Issues and board tasks created here should be only for specifics on the framework to be done before that date, as this repo will no longer be used afterwards (important things will be moved).
• GitHub Issues
  • Public repo
  • Agenda for meetings
  • Formal discussion for potential ideas or choices to be carried over in a task
  • Private repo
    * Discussion on framework related topics before OSFF NYC (30 Sept).
    * Not encouraging right now using issues in the private repo a lot, as it will be gone in the future.
• GitHub board
  • Public repo
  • Track tasks that already have a well defined way of completion, who will work on them. Further comment and discussion on task comment is possible.
  • Private repo: There is no board now, not worth starting a separate one.
• Pull Requests:
  • Public repo:
    • Fundamental changes to group description and communication
    • The ways of working should already live there, as people keep asking, PR to be created with this information
  • Private repo:
    • Contributing content for Governance framework
    • Contributing reference material (preferable links) to existing frameworks, regulation, technical info, etc.

Why is it a good idea

We already have some description on ways of working, but we lack a more formal definition of channels usage and people get confused how to proceed.

How does it work?

Included in the main description

primer

artificial intelligence

Any other key information

After some short time open for comment, I will raise a PR to update ways of working in the private repo, and also include the information in the public one.

Code of Conduct

• I agree to follow the FINOS Code of Conduct

[Josephrp]

not using google drive is smart, using a central place for all shares and discussion is too , github is good for this - just one suggestion : code and governance materials should not live inside emails and slack at all (just my personal opinion) , but discussions , why not.

additionally it would be nice to "just use github" for a lot of these PRs and stuff like that , especially discussions and project pages , which i think can also be made quite private, which is nice.