Hall of Fame
Part of our policy is to give credit to our contributors. Here is our hall of fame, in roughly chronological order. Get in touch if you want to be here, too!
Harald Störrle
Program manager, project leader, chief architect
Anders Friis
Basic features in the first prototype
Jakob Kragelund
Advanced features in the first prototype, initial software architecture
Maciej Kucharek
Re-Engineering, new software architecture, new build process
Johan Flod
First prototype of scenario enactment
Sanam Ali
Extensive fragment stitching case study
Henry Lie
Second (and final) version of the fragment stitching, lead developer 2014-
Ahmed Fikry
Multi-file projects -
Johan P. Nielsen
Effort Estimation by use case points, folder views, batch input facilities 
Jeppe K. Bloch
Visual modeling
Peter B. Bastian
First shot at project merging
Kacper Kawecki
Case Study
Luai Michlawi
Lead developer in 2015-
Danny Fhalpotia
Feature modeling, release planning -
Rustam Hussaini
Bug fixing 
Jesper B. Kjær
Architectural modeling-
Kasper R. Søgaard
First shot at RedCloud 
Ioannis Oikonomidis
Second prototype of RedCloud
Ahmadreza Ranjbartari
Admin and monitoring of RedCloud
Andreas Toftegaard
First prototype of the online version of RED
Tom Grosman
Documentation
S. Tamoor Rahil
Improvement of report generation-
Maybe You?
Tons of interesting tasks! -
Maybe You?
Tons of interesting tasks!
Policies
- RED people are friendly people. We don’t “dis” others. Be nice to other people. Everybody deserves your respect.
- We are reasonable and considerate. Listen before you talk.
- Don’t break anything: clean up after yourself, test your own code and run regression tests.
- Credit where credit is due: people with significant contributions will appear on the "Hall of Fame", if they wish.
Feedback
You're welcome to give feedback in the form of bug reports or feature requests. Before you do that, we ask you to double check your issue is genuine by following these steps.
- Check you bug is really a bug, not a feature, by reading the Manual and in particular the FAQ.
- Since we are testing RED quite heavily, maybe we already know about your concern, so do consult the Known Issues.
- Regarding feature requests, have a look at our plans for the next releases, and the planned features, and check out the latest release notes.
If none of the above filtered away yor issue, send it through our feedback form.
Stay tuned
RED aspires to become an open source project with a vibrant community - help us achieve that and stay in touch! There are currently three ways of staying in touch with the RED project.
- Subscribe to the e-mail newsletter. We intend to send updates on new releases, major bugs, upcoming projects and so on. Until summer 2016, there will be frequent news. After that, we expect between 2 and 4 mails per year. Feel free to consult the newsletter archive for back issues, or look at the newsletter status info at MailChimp.
- Follow us on Twitter@ReqEditor. This will cover the same topics as the newsletter, but will come in smaller chunks and at a higher frequency.
- Join the RED User Group (RUG) on facebook.
- Join the team! There are many things to do and we have limited resources, so any friendly and enthusiastic person who wants to contribute to RED is more than welcome! However, please understand that we reserve the right to prioritize tasks and shape the future of RED the way we do.
