community.html

---
layout: default
title: GECODE community
headline: Community
---

  <h3>Questions and Answers</h3>

  <p>You can contact the Gecode developers and users via
  a Google group. But, please make sure to not waste your 
  time and the time of others:</p>
  
  <ul>
  <li>Please check <a href="documentation.html">Gecode's 
      documentation</a> first.</li>
  <li>Please check previous discussions in the <a
  href="https://groups.google.com/d/forum/gecode">
  Gecode Google Group</a>.</li>
  <li>You can also have a look at the <a href="users-archive/">archive of the old Gecode users' mailing list</a>. It is a little messy but useful!</li>
  <li>Please focus on questions specific to Gecode. For general
      questions about constraint programming more suitable forums
      exist.</li>
  <li>Please provide sufficient detail: describe your platform
      (operating system, compiler, Gecode version) and your problem
      (what does not work, what do you want to do, what is the
      problem you observe) as accurately as you can.</li>
  <li>Please do not contact individual developers: it
  is much better to build a comprehensive archive of questions and
  answers related to Gecode that can be useful for everyone.
  If you have any questions not suitable for the public group,
  please do not hesitate to contact one of the authors directly.</li>
  <li>Never ask for solutions to homework. The only more
  offensive thing you could do is to provide a solution on the
  group if someone has violated the no homework policy!</li>
  </ul>

  <h3>Technical Discussion Group</h3>

  <p>
  For technical discussions about Gecode, please
  <a href="https://groups.google.com/d/forum/gecode">
  use the Gecode Google Group</a>.  You can also send to email to the group using the address <a href="mailto:users@gecode.org"><tt>users@gecode.org</tt></a>.
  </p>

  <h3>Bugs</h3>

  <p>
  We are grateful for any suggestions how to improve Gecode.
  Please report any bug you should find as well as feature requests using
  <a href="https://github.com/Gecode/gecode/issues">the Gecode issue page on GitHub</a>.
  </p>

  <p>
  Please do not report bugs in external projects to Gecode, in
  particular not for those distributed with Gecode in the
  <tt>contribs</tt> directory.
  </p>

  <h3>People</h3>

  <p>
  Gecode was founded by <a href="https//chschulte.github.io">Christian
  Schulte</a> (<a href="http://www.kth.se">KTH</a>, Sweden), who led
  the development until his
  passing <a href="https://www.a4cp.org/christian-in-memoriam">(ACP In
  Memoriam)</a>.
  </p>

  <p>
    Gecode is currently developed by
  </p>

  <ul>
  <li><a href="http://www.csse.monash.edu/~guidot/">Guido Tack</a>
      (<a href="mailto:tack@gecode.org">email</a>)
      (<a href="http://www.monash.edu/">Monash University</a>,
      Australia)
  </li>
  <li><a href="https://zayenz.se">Mikael Zayenz Lagerkvist</a>
      (<a href="mailto:lagerkvist@gecode.org">email</a>)
  </li>
  </ul>
  
  <p>
  For a complete list of authors, contributors, and bugfixers, please
  refer to the <a href="doc-latest/reference/PageLic.html">license and 
  authors information</a> in the <a href="doc-latest/reference/index.html"
  >reference documentation</a>.
  </p>

  <p>The Gecode logo has been designed by <a
     href="https://www.linkedin.com/in/lindig/">Christian Lindig</a>.
     You can <a href="logo.html">download the logo</a> in different
     formats and sizes.
  </p>