We’re trying something new! Every week, we’ll be posting an interview with one of our many beloved contributors here on Meta. First up:
I’m Felix, and I live in south-western Germany, right about here:
Despite hanging out way too much on Meta, I also have a regular job: I’m working on the verification of cyber-physical systems ( + ) as a PhD student at Saarland University. And in the rare cases when I’m not at work and have no unread posts on Meta, I mount my bike and hunt Geocaches
As far as I remember, I basically stumbled over Discourse kind of randomly on the internet and I immediately liked it a lot. Shortly thereafter, I volunteered for a mathematics preparatory course for freshmen at our university where I was responsible for managing the course’s server. I quickly advocated for using Discourse for this course (instead of the phpBB board integrated into our course management system) and was able to convince the team. After our CMS developer had developed Discourse SSO support for our CMS and I had set up an instance, we were ready to go and had a blast
In addition to being on Meta and occasionally reading the Let’s Encrypt board, I’m running two separate Discourse installs: The one for the mathematics course I mentioned earlier (which I’m now administering together with @GregoryS) and a multisite install for our chair. The multisite install hosts a few instances for projects related to our chair, but we’re mostly using it for lectures: For almost two years now, we’ve been setting up Discourse instances for all large lectures offered by our chair. (Smaller lectures with few participants still use the phpBB board integrated in our CMS.)
Back when I set up my first Discourse instance (even before we had officially decided to use Discourse not just internally, but also for our students), I wanted to use a sub-folder setup, failed, and asked here on Meta. Quickly thereafter, I reported my first bug (in a topic which still is still in pristine condition, with no replies or likes at all ), helped the first customer, and fell in love with the community.
It didn’t take long until I set my notification settings to…
…and since then, I’ve read every new post on Meta
I find that being here feels incredibly rewarding. Overall, the community is extremely helpful and friendly. When you’ve got a problem yourself (and I’ve got plenty of those ), it’s easy to quickly find help; and when you help others, this is always appreciated. It’s a positive atmosphere, and I enjoy being here
While I’m not fundamentalist about that, I think that the open source movement is amazing and brings a lot of value to the world! I’ve released most of my own software projects as open source, and I’m pretty sure I wouldn’t be so active on Meta if Discourse weren’t open source: That would feel like working for a company for free, not like supporting a community I’m a part of.
There haven’t been that many challenges, really. The biggest one I can think of is the hurdle of setting up a development environment. Ignoring two trivial PRs, I’ve never contributed any code to Discourse. That’s mostly because I don’t know my way around Ruby, but for some minor things, I would have made a PR if I had a development environment set up. The guides for settings these up aren’t bad, but they are still quite lengthy, and being on Windows doesn’t make this easier (but even if I ran Ubuntu on my laptop, I probably wouldn’t want to install all dependencies on my machine).
Maybe, setting up a development install on a standard Ubuntu instance could be automated to the point that installation becomes as easy as installing Docker?
wget -qO- https://get.discourse.org/dev | sh
Then, we could have a small guide that helps first-time contributors set up the environment (on Digital Ocean, so anyone could follow, but it should also work for local development, at least on Linux), and fully guide them through doing a change, testing it and creating a PR. (I’ve seen some cases here on Meta where people shied away from the last step.)
I’m not sure this will be worth the effort, but it’s an idea
We encourage respondents to speak candidly on this topic. Even if no sensitive information was discussed, answers will always be presented in a short list.
- Let’s be (even more) patient. Especially with non-native English speakers.
- Strive for “brief and polite” rather than “brief and blunt”.
- Using closed also as a way to mark certain posts as “done” can be problematic.
Meta already is a nice, warm and welcoming place. You asked for ways to become even better, so there’s that
Get going and come join us