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.

Sign up for GitHub

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

Jump to bottom

Remove hackmd links #1440

Merged
merged 1 commit into from
Feb 26, 2024
Merged

Remove hackmd links #1440

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions activities/communication/community-call-invite-template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,9 @@ If participants can benefit of preparing, mention it as well.]

If you have something else you would like to discuss please let us know, we are happy to make modifications to the agenda.

[Read the full agenda](https://hackmd.io/-OegeqvoThCbAsw3c3gIjw?view).
```
[Read the full agenda](INSERT LINK).
```

We look forward to seeing you on the call!

Expand All @@ -34,6 +36,4 @@ Our next Foundation for Public Code community call will take place at hh.mm on W

If you have something specific you would like to discuss please let us know, we are happy to add items to the agenda.

[Read the full agenda](https://hackmd.io/-OegeqvoThCbAsw3c3gIjw?view).

We look forward to seeing you on the call!
6 changes: 2 additions & 4 deletions activities/communication/running-community-call.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,10 +17,10 @@ The roles on the community call are:

The chair and the notetaker:

* create a notes HackMD.io document for this call
* create a notes document for this call
* add "updates since the last community call" to the notes - keep this to three items or fewer (we want the community call to be a dialogue, not a broadcast). If possible, focus on community related updates
* put these in the call notes doc
* update the [agenda](https://hackmd.io/-OegeqvoThCbAsw3c3gIjw?edit)
* update the agenda and link it
* send out invitations ([template](community-call-invite-template.md))

Ask the [communications coordinator](../../organization/staff.md#communications) if you need help with Foundation updates.
Expand All @@ -40,8 +40,6 @@ Have each person join the call on a separate connection aligned with our [confer

Call-in link: <https://meet.publiccode.net/FoundationCommunityCall>

Agenda link: <https://hackmd.io/9THmWbpQTLi8L9UIzczSyw>

### No show

If nobody joins at the call starting time, wait at least 15 minutes before closing the call.
Expand Down
1 change: 0 additions & 1 deletion activities/trainings/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,6 @@ Here is a list of trainings developed or used by the Foundation for Public Code:
* Rewriting Git History - Amend, Reword, Delete, Reorder, Squash and Split ([video](https://www.youtube.com/watch?v=ElRzTuYln0M), [article](https://www.themoderncoder.com/rewriting-git-history/)) - for making the git history as clear and understandable as possible
* [Git Cheat Sheet](https://education.github.com/git-cheat-sheet-education.pdf) - for a list of the most common used git commands
* [Reviewing contributions](https://sage.thesharps.us/2014/09/01/the-gentle-art-of-patch-review/)
* [HackMD.io](https://hackmd.io/) - for collaborating on draft documents in Markdown with people outside the organization (especially helpful for content we plan to publish)
* [Markdown Here](https://markdown-here.com/) - for formatting emails written using Markdown
* [Jekyll tutorial](https://jekyllrb.com/docs/step-by-step/01-setup/) - for understanding the templates which underpin our website

Expand Down