Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: haiku/website
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 3e4babb0666c
Choose a base ref
...
head repository: haiku/website
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 441da64a38db
Choose a head ref
  • 3 commits
  • 1 file changed
  • 1 contributor

Commits on Oct 2, 2021

  1. Write news item announcing code sprint 

    Wrote a news item announcing the code sprint, with details about the coding sprint for both existing and new contributors.
    @jt15s @pulkomandy
    jt15s authored and pulkomandy committed Oct 2, 2021
    Copy the full SHA
    0c129ae View commit details

  2. Moved content to event page 

    Moved the news item content to the event page as suggested by @pulkomandy
    @jt15s @pulkomandy
    jt15s authored and pulkomandy committed Oct 2, 2021
    Copy the full SHA
    9b7e209 View commit details

  3. Update 2021_online_coding_sprint.md 

    Removed unnecessary info as suggested by @pulkomandy
    @jt15s @pulkomandy
    jt15s authored and pulkomandy committed Oct 2, 2021
    Copy the full SHA
    441da64 View commit details
Showing with 19 additions and 10 deletions.
  1. +19 −10 content/conference/2021_online_coding_sprint.md
29 changes: 19 additions & 10 deletions content/conference/2021_online_coding_sprint.md
View file
Original file line number Diff line number Diff line change
@@ -10,19 +10,28 @@ homepage = "https://discuss.haiku-os.org/t/haiku-coding-sprint-2021/11327"
country = "Worldwide"
+++

Since it is not so easy to organize in-person events currently, this year
coding sprint will be online.
This year Haiku will be holding a virtual coding sprint (due to international travel restrictions), between 18th and the 31st of October. These dates were chosen because they matched up with the traditional dates for the in-person coding sprint and the BeGeistert conference.

In order to accomodate everyone, it will last for two weeks, and you are free
to join (or leave) at any time.
This also lines up with [Hacktoberfest](https://hacktoberfest.digitalocean.com/) - do note though that whilst working on Haiku, the operating system for Hacktoberfest won't work (the development work for this happens on our own hosted git repositories and on Gerrit, not on GitHub), helping out at [HaikuArchives](https://github.com/HaikuArchives), [HaikuPorts](https://github.com/haikuports/haikuports) or doing some work on our [website](https://github.com/haiku/website) and [web infrastructure](https://github.com/haiku/infrastructure) will as those are hosted on GitHub.

The event is open to everyone who wants to work on Haiku or any related software
project: write new applications, port existing applications, update already
ported applications, no matter if it's your own or someone else's. And of course
it's also possible to dig deeper into Haiku internals and fix some bugs there.
## How does the coding sprint work?
In past years, coding sprints involved gathering developers in a room (a meeting room, usually) where they would work on Haiku. Obviously, with this virtual coding sprint everything will run online, presumably with an IRC channel or another online platform.

The event overlaps with Hacktoberfest, so you can also take part into that if
you want to.
Anyone can participate, and there is **no obligation on how much time you put in** even though the sprint runs for two weeks. It's a good opportunity for existing contributors to work on something Haiku-related, like fix bugs or embark on that large project that's been sitting on their to-do list for a while, or help resurrect an app (might be their own or an app from the BeOS days sitting around in [HaikuArchives waiting for some TLC](https://github.com/HaikuArchives)), help finalise patches waiting on [Gerrit](https://review.haiku-os.org), submit proposals, etc. etc. And since there'll be more people online during this sprint, you'll have plenty of help from your fellow developers on hand!

## What about new contributors?
This is also a good chance for new contributors to get started too! Just to ensure you're ready for the sprint, it's a good idea to first check out our [page on how you can get started on development](https://www.haiku-os.org/community/getting-involved/developing), with ideas on what you might like to work on. You might also want to:

We can guarantee you'll definitely find something to work on. Still have no idea what to do? Just ask on the [forums](https://discuss.haiku-os.org) or [our chatroom](https://www.haiku-os.org/community/irc/) and we'll work together to find something you can work on.

If you're not much of a developer, it's a good time too to get stuck into some non-coding work for Haiku. If you're stuck on ideas, you might like to:
* [Help with translations](https://www.haiku-os.org/community/getting-involved/translating)
* [Write some documentation](https://www.haiku-os.org/community/getting-involved/documenting/)
* [Test out Haiku](https://www.haiku-os.org/community/getting-involved/testing/)
* [Do some design work](https://www.haiku-os.org/community/getting-involved/designing/)
* [Donate to us](https://www.haiku-inc.org/donate/) (more on that soon - watch this space!)

We hope this coding sprint is enjoyable and productive for all!

---