Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Turn a good text into a blog post #472

Open
bast opened this issue Jan 9, 2025 · 0 comments
Open

Turn a good text into a blog post #472

bast opened this issue Jan 9, 2025 · 0 comments

Comments

@bast
Copy link
Member

bast commented Jan 9, 2025

The text below was saved from a repo which we decided to delete and which was replaced by https://github.com/nordic-rse/nrse2025.

I did not want the text to get lost.

Author: @rantahar


The Issues I Wanted to Fix

  • Hidden conversations

    A lot of the planning for this conference happened in meetings. For a new volunteer or a participant, it's hard to gain ownership in the conference.

    Later we moved to Zulip and to coffee breaks. These are more accessible, but still not as public as I would like.

  • Missed decisions

    We often made decisions in a meeting and forgot. We then had to go through the same conversation again. I want to clarify what counts as a decitions and make sure they are written down.

  • Forgotten tasks

    Some things happened late or did not happen because no-one was assigned to do it.

How this repository works

This is a suggestion, we can change this as we go.

My idea is to follow a single endorsement policy:

  1. Anyone can make a suggestion (formally by a pull request)
  2. Any conference organizer can merge (and should, if they approve)
  3. Organizers should not merge their own requests.
  • Discussions happen publicly in issues.
  • When there is an actual task to do, this should be a new issue and should be assigned. Tasks that are not assigned to a single person tend to not be done.
  • Information in this repository is official and nothing outside this repository is official.
  • There are few things that cannot be public. For example communication with invited speakers, who
    have not yet accepted. This information is added when possible.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant