head 1.4; access; symbols; locks; strict; comment @# @; 1.4 date 2005.08.30.14.19.39; author rse; state Exp; branches; next 1.3; 1.3 date 2004.10.20.09.13.21; author thl; state Exp; branches; next 1.2; 1.2 date 2004.10.03.07.29.56; author rse; state Exp; branches; next 1.1; 1.1 date 2004.02.27.20.03.29; author rse; state Exp; branches; next ; desc @@ 1.4 log @flush pending changes and add 2.[34] and 2.5 ;-) for feedback form @ text @ #use "page.inc" page=feedback Community Feedback

Community Feedback

Feedback from our community is very important to us. So if you want to support the OpenPKG project, please fill out the feedback form. It allows us to better understand our community and also develop the OpenPKG project according to your wishes.

The feedback form content is directly sent to the OpenPKG team for individual consideration and is treated confidentially. As an exception, if you explicitly include a personal Public Advocacy Statement (see last point in form), your information might be publically quoted by the OpenPKG project.

@ 1.3 log @freshen feedback form with new releases, generic OS and new time/date fields @ text @d81 1 a81 1 d86 1 a86 1
(optional, e.g., "john.doe@@example.com") d255 3 @ 1.2 log @flush pending changes @ text @d151 1 d189 4 a192 3  FreeBSD    GNU/Linux    Sun Solaris d247 4 a250 2  1.0-RELEASE    1.1-RELEASE   d252 3 a254 2  1.2-RELEASE    1.3-RELEASE   a255 1  2.0-RELEASE   d296 2 a297 2 (if provided, includes the approval for quotation by the OpenPKG project, possibly on our forthcoming Community Advocacy page). @ 1.1 log @add feedback page to CVS @ text @d16 1 a16 1 if you explicitly include a personal Public Advocacy Statement @