• R/O
  • HTTP
  • SSH
  • HTTPS

website: Commit

HTML source code, style-sheets, scripts, and images for deployment on mingw.osdn.io


Commit MetaInfo

Revision899ad64ce7c6e05311acffd60d559ea65f7a27c0 (tree)
Time2020-11-06 08:00:14
AuthorKeith Marshall <keith@user...>
CommiterKeith Marshall

Log Message

Add contact and mailing-list information pages.

* contact.html mailing.html: New files.
* index.html (font-awesome): Add stylesheet link.

* site.css (hr): Adjust adjacent paragraph top margin spacing.
(li): Set explicit top margin, within both <ul> and <ol> blocks.
(dl, dt, dd): Add general style; suppress left margin indent...
(dl.no-indent dd): ...for so-qualified definition entries.
(navbar.li): Adjust margins; add a bottom margin specification.
(form.search): Set display width, margins, and styles for input
fields and search buttons.

Change Summary

Incremental Difference

--- /dev/null
+++ b/contact.html
@@ -0,0 +1,213 @@
1+<!DOCTYPE HTML><!--
2+ *
3+ * contact.html
4+ *
5+ * Summary of approved methods for contacting the members of the
6+ * MinGW.org user and developer community.
7+ *
8+ *
9+ * $Id$
10+ *
11+ * Written by Keith Marshall <keith@users.osdn.me>
12+ * Copyright (C) 2020, MinGW.org Project
13+ *
14+ *
15+ * Redistribution and use in source and 'compiled' forms (SGML, HTML,
16+ * PDF, PostScript, RTF, etc) with or without modification, are permitted
17+ * provided that the following conditions are met:
18+ *
19+ * 1. Redistributions of source code must retain the above copyright
20+ * notice, this list of conditions and the following disclaimer as
21+ * the first lines of this file, unmodified.
22+ *
23+ * 2. Redistributions in compiled form (transformed to other DTDs,
24+ * converted to PDF, PostScript, RTF and other formats) must
25+ * reproduce the above copyright notice, this list of conditions
26+ * and the following disclaimer in the documentation and/or other
27+ * materials provided with the distribution.
28+ *
29+ * THIS DOCUMENTATION IS PROVIDED BY THE MINGW.ORG PROJECT "AS IS" AND
30+ * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
31+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
32+ * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE MINGW.ORG PROJECT, OR
33+ * ITS CONTRIBUTORS, BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
34+ * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
35+ * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
36+ * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
37+ * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
38+ * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
39+ * OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
40+ * DAMAGE.
41+ *
42+ *
43+ * Note: this page assumes browser support for the following numeric
44+ * HTML entity code:
45+ *
46+ * &#8209; non-breaking hyphen
47+ * &#8220; left (opening) typographic double quote
48+ * &#8221; right (closing) typographic double quote
49+ *
50+-->
51+<dl class="masthead"><!-- hidden for masthead class -->
52+<!-- FIXME: is there a better way to do this? We need to propagate
53+ content to the "as-page-title" and "as-page-subtitle" place-holders,
54+ within the "page-content" div of "index.html"; our javascript page
55+ loader will explicitly look for these hidden elements, and copy
56+ their content into the corresponding visible place-holders.
57+-->
58+ <dt id="page-title">Contacting MinGW.org</dt>
59+ <dt id="page-subtitle">When a Web-Search Fails to Resolve your Issue</dt>
60+</dl><!-- masthead -->
61+<p>If you have exhausted all of the web&#8209;site resources,
62+and you have searched all of the
63+<a href="index.html?page=mailing.html"
64+>available mailing&#8209;list archives</a>,
65+and all of the on&#8209;line
66+<a rel="noopener noreferrer" target="_blank"
67+ href="https://osdn.net/projects/mingw/ticket/"
68+>bug report and feature request tickets</a>,
69+then you may wish to contact MinGW.org for assistance.
70+Please refer to the relevant sections below,
71+for guidance on <a href="#general-enquiry">making general enquiries</a>,
72+on <a href="#bug-report">filing bug reports</a>,
73+or on <a href="#feature-request">requesting new features</a>.
74+</p>
75+<p><em>Please note:
76+the mingw&#8209;w64 and MSYS2 projects are <strong>not</strong>,
77+in any way, affiliated with MinGW.org;
78+MinGW.org <strong>does not</strong> support the products
79+of these projects.</em>
80+</p>
81+<div id="general-enquiry">
82+<h3>General Enquiries</h3>
83+<p>If you encounter a problem using MinGW, or MSYS,
84+and you cannot find a satisfactory answer on our web&#8209;site,
85+in our
86+<a href="index.html?page=mailing.html">mailing&#8209;list archives</a>,
87+or elsewhere on the internet,
88+or if you simply need some advice relating to MinGW, or MSYS,
89+then we advise you to
90+<a rel="noopener noreferrer" target="_blank"
91+ href="https://lists.osdn.me/mailman/listinfo/mingw-users"
92+>subscribe to the MinGW&#8209;Users mailing&#8209;list</a>,
93+and ask.
94+</p>
95+<p><em>Do please note that, to help avoid spam,
96+this mailing&#8209;list is open to subscribers only.
97+Please <strong>do not</strong>
98+attempt to circumvent the subscription process,
99+by sending mail to either the mingw-users-owner,
100+or the mingw-users-admin addresses.
101+Doing so will be of no benefit to you,
102+since subscription is free&#8209;of&#8209;charge in any case,
103+and you will get no reply from the former address,
104+while the latter is reserved for automated self&#8209;help replies,
105+in response to specific subject keywords.</em>
106+</p>
107+<p>Before posting to this mailing&#8209;list,
108+we <em>strongly</em> recommend that you acquaint yourself with
109+<a href="index.html?page=mailing.html#list-etiquette"
110+>the mailing&#8209;list posting etiquette</a>;
111+compliance with this may improve your chances of receiving a response,
112+whereas non&#8209;compliance may result in your post being ignored.
113+</p></div><!-- general-enquiry -->
114+<div id="bug-report">
115+<h3>Reporting Bugs</h3>
116+<p>After discussing an issue on the mailing&#8209;list,
117+as described above, you may be asked to file a formal bug report.
118+(Alternatively,
119+if you are certain that you have identified a bug in a MinGW.org product,
120+you may choose to file such a bug report of your own volition;
121+however, if you choose this course of action,
122+please be aware that many bug reports,
123+which are filed <em>without</em> prior discussion,
124+are ultimately dismissed as user error).
125+</p>
126+<p><em>Before you even consider filing a bug report,
127+please review
128+<a rel="noopener noreferrer" target="_blank"
129+ href="https://osdn.net/projects/mingw/ticket/"
130+>the list of existing tickets</a>,
131+(<strong>including closed tickets</strong>
132+&mdash; ensure that the &#8220;Open&#8221; and &#8220;Closed&#8221;
133+status check&#8209;boxes are <strong>both</strong> selected,
134+and click the &#8220;Search&#8221; button),
135+to ensure that the issue has not already been reported</em>.
136+</p>
137+<p><em>Please <strong>do not</strong> file a bug report,
138+if your issue relates to an unimplemented API feature;
139+it is more appropriate to file
140+a &#8220;<a href="#feature-request">Feature Request</a>&#8221; instead</em>.
141+</p>
142+<p><em>Please do not waste your time, (and ours),
143+reporting issues with your anti&#8209;virus software;
144+the heuristic nature of such software, all too frequently,
145+results in false&#8209;positive reports,
146+and in the absence of deterministic evidence of infection,
147+we will take no action in response.</em>
148+</p>
149+<p>Regardless of your motivation for filing a bug report,
150+you <em>must</em>, (unless you already have one),
151+<em><a rel="noopener noreferrer" target="_blank"
152+ href="https://osdn.net/account/register.php"
153+>create a personal OSDN.net account</a></em>,
154+and you should also
155+<em><a target="_blank" href="index.html?page=buginfo.html"
156+>acquaint yourself with the bug reporting guidelines</a></em>.
157+You may then
158+<em><a rel="noopener noreferrer" target="_blank"
159+ href="https://osdn.net/account/login.php?return_to=/ticket/newticket.php?group_id=3917"
160+>log in to your OSDN.net account</a></em>,
161+and proceed to
162+<em><a rel="noopener noreferrer" target="_blank"
163+ href="https://osdn.net/ticket/newticket.php?group_id=3917"
164+>the bug report submission form</a></em>.
165+Please review the submission instructions,
166+(which appear at the top of the submission form),
167+then complete the form,
168+leaving the ticket type set to &#8220;Issue&#8221;.
169+</p>
170+<p><em>Please <strong>do not</strong> ignore the submission instructions.
171+In particular, note that,
172+unless you are a member of the MinGW.org Project development team,
173+you are <strong>not</strong> authorized to assign a specific responder
174+for the ticket; nor are you authorized to assign an elevated priority
175+or severity attribute for your ticket.
176+If you exceed your authority,
177+your ticket <strong>will</strong> be reassigned to <strong>lowest</strong>
178+priority/severity, and may even be rejected altogether</em>.
179+</p>
180+<p>Before you finally submit your report,
181+please use the &#8220;Preview&#8221; facility to check for,
182+and correct, any markup errors;
183+(these are, alas, all too common,
184+and create a bad impression of the reporter).
185+Finally, when you are satisfied, click the &#8220;Submit&#8221; button
186+to complete the ticket submission process.
187+</p></div><!-- bug-report -->
188+<div id="feature-request">
189+<h3>Feature Requests</h3>
190+<p>When you wish to request the implementation of a new feature,
191+(e.g.&nbsp;to support a currently unsupported MSVC or POSIX API function),
192+you should file a feature request ticket.
193+The procedure is effectively the same as that for
194+<a href="#bug-report">filing a bug report</a>,
195+<em>except</em> that you set the ticket type to &#8220;Feature Request&#8221;,
196+instead of leaving it as &#8220;Issue&#8221;.
197+</p>
198+<p><em>Please be aware that feature request submissions are subject
199+to the same restrictions on your authority,
200+as are applicable to <a href="#bug-report">bug reporting</a></em>.
201+</p>
202+<p>Before you submit a feature request,
203+it is recommended that you discuss the feasibility of implementing
204+the proposed feature, as a <a href="#general-enquiry">general enquiry topic</a>,
205+on the mailing&#8209;list.
206+Additionally, <em>after</em> you have submitted such a request,
207+you should use the mailing&#8209;list to bring it to the
208+attention of the MinGW user community,
209+and invite them to support your request,
210+by <em>voting</em> on your ticket;
211+(please note that MinGW developers will consider votes,
212+when prioritizing feature requests).
213+</p></div><!-- feature-request -->
--- a/index.html
+++ b/index.html
@@ -45,6 +45,7 @@
4545 * DAMAGE.
4646 *
4747 -->
48+ <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css">
4849 <link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Alegreya+Sans+SC:wght@500&family=Roboto&display=swap" />
4950 <link rel="stylesheet" href="site.css" />
5051 <script src="site.js"></script>
--- /dev/null
+++ b/mailing.html
@@ -0,0 +1,363 @@
1+<!DOCTYPE HTML><!--
2+ *
3+ * mailing.html
4+ *
5+ * $Id$
6+ *
7+ * Written by Keith Marshall <keith@users.osdn.me>
8+ * Copyright (C) 2020, MinGW.org Project
9+ *
10+ * Uses a web-search form-field implementation derived from the
11+ * DuckDuckGo search widget implementation by Juri Wornowitski, as
12+ * described at https://www.plainlight.com/ddg
13+ *
14+ *
15+ * Redistribution and use in source and 'compiled' forms (SGML, HTML,
16+ * PDF, PostScript, RTF, etc) with or without modification, are permitted
17+ * provided that the following conditions are met:
18+ *
19+ * 1. Redistributions of source code must retain the above copyright
20+ * notice, this list of conditions and the following disclaimer as
21+ * the first lines of this file, unmodified.
22+ *
23+ * 2. Redistributions in compiled form (transformed to other DTDs,
24+ * converted to PDF, PostScript, RTF and other formats) must
25+ * reproduce the above copyright notice, this list of conditions
26+ * and the following disclaimer in the documentation and/or other
27+ * materials provided with the distribution.
28+ *
29+ * THIS DOCUMENTATION IS PROVIDED BY THE MINGW.ORG PROJECT "AS IS" AND
30+ * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
31+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
32+ * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE MINGW.ORG PROJECT, OR
33+ * ITS CONTRIBUTORS, BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
34+ * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
35+ * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
36+ * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
37+ * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
38+ * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
39+ * OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
40+ * DAMAGE.
41+ *
42+ *
43+ * Note: this page assumes browser support for the following numeric
44+ * HTML entity codes:
45+ *
46+ * &#8209; non-breaking hyphen
47+ * &#8217; typographic apostrophe
48+ * &#8220; left (opening) typographic double quote
49+ * &#8221; right (closing) typographic double quote
50+ *
51+-->
52+<dl class="masthead"><!-- hidden for masthead class -->
53+<!-- FIXME: is there a better way to do this? We need to propagate
54+ content to the "as-page-title" and "as-page-subtitle" place-holders,
55+ within the "page-content" div of "index.html"; our javascript page
56+ loader will explicitly look for these hidden elements, and copy
57+ their content into the corresponding visible place-holders.
58+-->
59+ <dt id="page-title">MinGW.org Mailing-Lists</dt>
60+ <dt id="page-subtitle">Mailing-Lists and Mail Archives Operated by MinGW.org</dt>
61+</dl><!-- masthead -->
62+<p>MinGW.org&#8217;s preferred method for communication,
63+between users and the project team, is by way of mailing&#8209;lists.
64+Historically, there were several topic&#8209;specific lists, originally
65+<a rel="noopener noreferrer" target="_blank"
66+ href="https://sourceforge.net/p/mingw/mailman/"
67+>hosted on SourceForge.net</a>;
68+today, only two remain operational, and both are
69+<a rel="noopener noreferrer" target="_blank"
70+ href="https://osdn.net/projects/mingw/lists/"
71+>hosted on OSDN.net</a>.
72+</p>
73+<h3>Operational Mailing&#8209;Lists</h3>
74+<p>The currently operational
75+MinGW.org mailing&#8209;lists are:&mdash;
76+</p>
77+<dl class="no-indent" id="mingw-users">
78+<dt><a rel="noopener noreferrer" target="_blank"
79+ href="https://lists.osdn.me/mailman/listinfo/mingw-users"
80+>MinGW&#8209;Users Mailing&#8209;List</a>
81+</dt>
82+<dd>This is the primary conduit for dialogue between MinGW users
83+and the MinGW.org project team;
84+(you are advised to use this mailing&#8209;list
85+at any time when you wish to engage in such dialogue).
86+It is a public mailing&#8209;list, but to avoid spam,
87+<a rel="noopener noreferrer" target="_blank"
88+ href="https://lists.osdn.me/mailman/listinfo/mingw-users"
89+>you <em>must</em> subscribe</a>
90+<em>before</em> you will be
91+permitted to post your first message,
92+(and your subscription <em>must</em> remain active,
93+if you wish to post subsequent messages).
94+</dd>
95+<dd>Before
96+posting to this mailing&#8209;list
97+you are advised to acquaint yourself with the
98+<a href="#list-etiquette">posting etiquette</a>;
99+failure to comply with this etiquette may seriously impair
100+your chances of receiving a useful response,
101+and, in cases of flagrant disregard,
102+may even result in your future posts being moderated.
103+</dd>
104+<dd>Previous correspondence,
105+posted to this mailing&#8209;list between February&nbsp;2018
106+and the present day, has been
107+<a rel="noopener noreferrer" target="_blank"
108+ href="https://osdn.net/projects/mingw/lists/archive/users"
109+>archived on OSDN.net</a>;
110+(earlier correspondence, prior to February&nbsp;2018, has also been
111+<a rel="noopener noreferrer" target="_blank"
112+ href="https://sourceforge.net/p/mingw/mailman/mingw-users"
113+>archived, on SourceForge.net</a>).
114+As noted in the <a href="#list-etiquette">etiquette</a>,
115+before you introduce a new topic on this mailing&#8209;list,
116+you are advised to search these archives,
117+to ensure that you are not asking a question
118+which has already been answered.
119+You may use the following pair of search boxes to perform
120+keyword searches within the OSDN.net (upper),
121+and the SourceForge.net (lower box) archives, respectively.
122+(If your question relates to MSYS, you may also wish to refer to the
123+<a href="#mingw-msys">historical MinGW&#8209;MSYS archive, below</a>).
124+<form class="search" method="get" action="https://duckduckgo.com/" target="_blank">
125+ <button class="fa fa-search" type="submit"></button>
126+ <input type="text" name="q" placeholder="Search MinGW-Users on OSDN.net ..." />
127+ <input type="hidden" name="sites" value="https://osdn.net/projects/mingw/lists/archive/users" />
128+ <input type="hidden" name="kn" value="1" />
129+</form>
130+<form class="search" method="get" action="https://sourceforge.net/p/mingw/mailman/search/" target="_blank">
131+ <button class="fa fa-search" type="submit"></button>
132+ <input type="text" name="q" placeholder="Search MinGW-Users on SourceForge.net ..." />
133+ <input type="hidden" name="mailing_list" value="mingw-users" />
134+</form>
135+</dd>
136+</dl><dl class="no-indent" id="mingw-notify">
137+<dt><a rel="noopener noreferrer" target="_blank"
138+ href="https://lists.osdn.me/mailman/listinfo/mingw-notify"
139+>MinGW&#8209;Notify Mailing&#8209;List</a>
140+</dt>
141+<dd>This is a <em>read&#8209;only</em> mailing&#8209;list,
142+which is used to deliver notifications of source code repository updates,
143+issue tracker submissions, and feature request submissions.
144+If you would like to receive such notifications,
145+you are welcome to subscribe to this mailing&#8209;list,
146+but please <em>do not</em> attempt to post messages to it.
147+</dd>
148+<dd>Notifications posted to this mailing&#8209;list,
149+since November&nbsp;2017, have been
150+<a rel="noopener noreferrer" target="_blank"
151+ href="https://osdn.net/projects/mingw/lists/archive/notify"
152+>archived on OSDN.net</a>,
153+while notifications posted prior to September&nbsp;2017 have been
154+<a rel="noopener noreferrer" target="_blank"
155+ href="https://sourceforge.net/p/mingw/mailman/mingw-notify"
156+>archived, on SourceForge.net</a>.
157+Once again, you may use the following pair of search boxes
158+to perform keyword searches on these archives, respectively.
159+<form class="search" method="get" action="https://duckduckgo.com/" target="_blank">
160+ <button class="fa fa-search" type="submit"></button>
161+ <input type="text" name="q" placeholder="Search MinGW-Notify on OSDN.net ..." />
162+ <input type="hidden" name="sites" value="https://osdn.net/projects/mingw/lists/archive/notify" />
163+ <input type="hidden" name="kn" value="1" />
164+</form>
165+<form class="search" method="get" action="https://sourceforge.net/p/mingw/mailman/search/" target="_blank">
166+ <button class="fa fa-search" type="submit"></button>
167+ <input type="text" name="q" placeholder="Search MinGW-Notify on SourceForge.net ..." />
168+ <input type="hidden" name="mailing_list" value="mingw-notify" />
169+</form>
170+</dd>
171+</dl>
172+<h3>Historical Mailing&#8209;List Archives</h3>
173+<p>In earlier days of the project history,
174+the volume of mailing&#8209;list traffic was significantly greater
175+than it is today.
176+This traffic was distributed over five topic&#8209;specific
177+mailing&#8209;lists, of which only the two identified above
178+remain operational today;
179+the other three historical lists, which are identified below,
180+are now closed, and it is no longer possible to subscribe,
181+or to post messages to them.
182+However, archives of historical postings remain
183+<a rel="noopener noreferrer" target="_blank"
184+ href="https://sourceforge.net/p/mingw/mailman/"
185+>available on SourceForge.net</a>,
186+and may be searched using their respective keyword&#8209;search boxes,
187+below.
188+</p>
189+<dl class="no-indent" id="mingw-msys">
190+<dt><a rel="noopener noreferrer" target="_blank"
191+ href="https://sourceforge.net/p/mingw/mailman/mingw-msys"
192+>MinGW&#8209;MSYS Mailing&#8209;List</a>
193+</dt>
194+<dd>This was a public mailing&#8209;list,
195+dedicated to correspondence relating specifically to MSYS,
196+in order to segregate it from more general MinGW&#8209;Users list traffic;
197+today, such correspondence should be directed to
198+<a href="#mingw-users">the MinGW&#8209Users mailing&#8209;list</a>.
199+</dd>
200+<dd>You may use this search box to perform a keyword search
201+on the historical MinGW-MSYS archive.
202+<form class="search" method="get" action="https://sourceforge.net/p/mingw/mailman/search/" target="_blank">
203+ <button class="fa fa-search" type="submit"></button>
204+ <input type="text" name="q" placeholder="Search MinGW-MSYS on SourceForge.net ..." />
205+ <input type="hidden" name="mailing_list" value="mingw-msys" />
206+</form>
207+</dd>
208+<dt><a rel="noopener noreferrer" target="_blank"
209+ href="https://sourceforge.net/p/mingw/mailman/mingw-dvlpr"
210+>MinGW&#8209;Dvlpr Mailing&#8209;List</a>
211+</dt>
212+<dd>This was a private, but publicly archived mailing&#8209;list,
213+which was used by MinGW.org Project contributors, to discuss various
214+aspects of project development; this mailing&#8209;list has now been
215+superseded by alternative web technologies, for such discussion.
216+</dd>
217+<dd>You may use this search box to perform a keyword search
218+on the historical MinGW-Dvlpr public archive.
219+<form class="search" method="get" action="https://sourceforge.net/p/mingw/mailman/search/" target="_blank">
220+ <button class="fa fa-search" type="submit"></button>
221+ <input type="text" name="q" placeholder="Search MinGW-Dvlpr on SourceForge.net ..." />
222+ <input type="hidden" name="mailing_list" value="mingw-dvlpr" />
223+</form>
224+</dd>
225+<dt><a rel="noopener noreferrer" target="_blank"
226+ href="https://sourceforge.net/p/mingw/mailman/mingw-cvs"
227+>MinGW&#8209;CVS Mailing&#8209;List</a>
228+</dt>
229+<dd>This obsolete <em>read&#8209;only</em> mailing&#8209;list was
230+formerly used for posting of notifications of updates to the
231+MinGW.org CVS, (and more recently <em>git</em>),
232+source code repositories;
233+since migration of these repositories to
234+<a rel="noopener noreferrer" target="_blank"
235+ href="https://osdn.net/projects/mingw/scm/"
236+>OSDN.net</a>, such notifications have been directed to
237+<a href="#mingw-notify">the MinGW&#8209;Notify mailing&#8209;list</a>.
238+</dd>
239+<dd>You may use this search box to perform a keyword search
240+on the historical MinGW-CVS archive.
241+<form class="search" method="get" action="https://sourceforge.net/p/mingw/mailman/search/" target="_blank">
242+ <button class="fa fa-search" type="submit"></button>
243+ <input type="text" name="q" placeholder="Search MinGW-CVS on SourceForge.net ..." />
244+ <input type="hidden" name="mailing_list" value="mingw-cvs" />
245+</form>
246+</dd>
247+</dl>
248+<div id="list-etiquette">
249+<h3>Mailing&#8209;List Posting Etiquette</h3>
250+<p>MinGW is an open source project.
251+As such, it is heavily dependent on people who dedicate
252+their spare time to the goals and continuing development of the project,
253+so please keep this in mind when posting to the mailing&#8209;list.
254+</p>
255+<p>Before you post, you are advised to
256+acquaint yourself with the following commonly accepted guidelines,
257+with which you are strongly encouraged to comply,
258+when composing your posts.
259+Failure to comply with these guidelines may result
260+in your posts being ignored by a number of knowledgeable people,
261+and repeated offenses may even lead to your posts being vetted,
262+and potentially rejected, by the list moderator.
263+</p>
264+<ul style="padding-right: 1em">
265+<li>The language of the lists is <em><strong>English</strong></em>&hairsp;;
266+if you post in any other language, you are unlikely to elicit a response.
267+</li>
268+<li><em><strong>Do search</strong></em> the mailing list archives,
269+(both the current archives, and those of the historical topic&#8209;specific
270+lists), before posting, (see the links associated with each of the lists above);
271+many questions have already been asked and answered.
272+</li>
273+<li><em><strong>Do use</strong></em>
274+a <em><strong>meaningful</strong></em> subject line.
275+A subject line should include a pertinent few words summarizing
276+the subject of the email;
277+(when one replies to emails,
278+one should always make certain the subject line of the email is still
279+relevant to the reply).
280+In particular, if you receive list mail in digest format,
281+<em><strong>do always</strong></em>
282+set the subject back to the original text,
283+from the message to which you are replying.
284+<em><strong>Do not</strong></em> reply with a subject of
285+<em>&#8220;Re: MinGW-??? Digest no. ???&#8221;</em>;
286+such replies are prime candidates for deletion, without being read.
287+</li>
288+<li><em><strong>Do post</strong></em> in a MIME format with
289+<em>&#8220;Content-Type: text</em>/<em>plain&#8221;</em>.
290+<em><strong>Do not</strong></em> post as HTML, or in any other MIME format,
291+(and in particular, <em><strong>do not</strong></em> use multi-part MIME,
292+with plain text duplicated as HTML);
293+some list subscribers are unable to, or choose not to read such mail,
294+and will be unable or unwilling to answer you.
295+</li>
296+<li><em><strong>Do not</strong></em>
297+post messages with very long lines of text;
298+except when pasting screenshots, where line wrapping might lead to confusion,
299+ensure that lines of running text are wrapped with hard line breaks,
300+at a length of between 65 and 72 characters.
301+</li>
302+<li><em><strong>Do quote</strong></em> sections of the original text,
303+and <em><strong>interleave</strong></em> your replies to individual points,
304+<em><strong>below</strong></em> the relevant context.
305+<em><strong>Do not</strong></em>
306+<a rel="noopener noreferrer" target="_blank"
307+ href="http://en.wikipedia.org/wiki/Top_post"
308+>top-post</a>;
309+(this
310+<a rel="noopener noreferrer" target="_blank"
311+ href="http://redballoon.net/~snorwood/quote-rant.shtml"
312+>treatise</a>
313+explains why top-posting is considered unacceptable).
314+</li>
315+<li><em><strong>Do trim out</strong></em> sections of the original mail,
316+which are not required to establish the context of your reply.
317+(Once more,
318+this is particularly important when replying to mail received in digest form;
319+<em><strong>do reply</strong></em>
320+to <em><strong>one subject at a time</strong></em>,
321+and <em><strong>do remove</strong></em> all content related to other subjects).
322+<em><strong>Do not</strong></em> persistently recycle irrelevant junk,
323+quoted from earlier messages in the thread.
324+</li>
325+<li><em><strong>Do not</strong></em>
326+include <em>&#8220;legal mumble&#8221;</em> signatures.
327+You are posting to a list that will be read by thousands of users,
328+and anything you say will be archived in the public domain;
329+in this context, such drivel in your signature is neither enforceable,
330+nor meaningful.
331+</li>
332+<li><em><strong>Do not hijack</strong></em> an existing topic thread,
333+when you wish to introduce an unrelated subject;
334+(i.e. <em><strong>do not</strong></em> reply to an existing message,
335+when your reply is unrelated to the original subject).
336+When you want to introduce a new topic, plainly start a new thread,
337+(i.e. a completely new message).
338+Replying in an existing thread confuses mail readers
339+and humans who are trying to participate in the original discussion;
340+it is a sure way to irritate other subscribers,
341+and will likely get you ignored,
342+if not even black-listed.
343+</li>
344+</ul>
345+<p>Historical information on <em>netiquette</em> may be found in
346+<a rel="noopener noreferrer" target="_blank"
347+ href="http://www.faqs.org/rfcs/rfc1855.html"
348+>RFC-1855</a>.
349+</p>
350+<p>This
351+<a rel="noopener noreferrer" target="_blank"
352+ href="http://linuxmafia.com/faq/Essays/smart-questions.html"
353+>article</a>,
354+(also available
355+<a rel="noopener noreferrer" target="_blank"
356+ href="http://www.catb.org/~esr/faqs/smart-questions.html"
357+>here</a>),
358+offers valuable advice on how to ask questions,
359+in a manner most likely to elicit useful replies.
360+</p>
361+</div><!-- list-etiquette -->
362+
363+<!-- $RCSfile$: end of file -->
--- a/site.css
+++ b/site.css
@@ -40,7 +40,7 @@
4040 *
4141 */
4242
43-/* General page layout and formatting
43+/* General Page Layout and Formatting
4444 * ==================================
4545 */
4646 body
@@ -96,18 +96,42 @@ hr+p, p+hr
9696 { /* Also maintain a deeper space between paragraph text and any
9797 * intervening horizontal rule.
9898 */
99- margin-top: 1.3em;
99+ margin-top: 1.2em;
100100 }
101-p+ul
102-{ /* Keep any unordered list closer to preceding paragraph text
103- * than normal inter-paragraph spacing, but separated slightly
101+p+ul, p+ol, p+dl
102+{ /* Keep any unordered list, ordered list, or defining list
103+ * closer to any immediately preceding paragraph text than
104+ * normal inter-paragraph spacing, but separated slightly
104105 * more than single-line text spacing.
105106 */
106107 margin-top: 0.3em; margin-bottom: 0;
107108 }
109+ul li, ol li
110+{ margin-top: 0.12em;
111+}
112+ul li:first-child, ol li:first-child
113+{ margin-top: 0;
114+}
115+dl dt
116+{ /* Similarly, set explicit layout rules for definition lists.
117+ */
118+ margin-top: 0.8em; font-weight: bold;
119+}
120+dl dt:first-child, dl dd+dd
121+{ margin-top: 0.4em;
122+}
123+dl dt+dd
124+{ margin-top: 0.2em;
125+}
126+dl.no-indent dd
127+{ /* Suppress indentation of definition blocks, within any
128+ * definition list of the "no-indent" class.
129+ */
130+ margin-left: 0;
131+}
108132
109133
110-/* Fixed position page header block formatting
134+/* Fixed Position Page Header Block Formatting
111135 * ===========================================
112136 */
113137 #header
@@ -160,8 +184,8 @@ p+ul
160184 * becomes (99 - 15) / 5 = 16.8%.
161185 */
162186 display: inline-block;
163- min-width: 16.8%; margin-left: 1px; margin-right: 1px;
164- border-top: 1px solid; border-left: 1px solid; border-right: 2px solid;
187+ min-width: 16.8%; margin: 0 1px; border-bottom: 3px solid;
188+ border-top: 1px solid; border-left: 1px solid; border-right: 3px solid;
165189 border-top-left-radius: 7px; border-top-right-radius: 7px;
166190 border-bottom-style: none; border-color: #336699;
167191 color: #003366; background-color: #d9d9ff;
@@ -180,7 +204,7 @@ p+ul
180204 }
181205
182206
183-/* General page content formatting
207+/* General Page Content Formatting
184208 * ===============================
185209 */
186210 .page-view
@@ -230,7 +254,8 @@ dl.masthead+p
230254 margin-top: 1.3em;
231255 }
232256
233-/* Supplementary formatting for sections with numbered headings
257+
258+/* Supplementary Formatting for Sections with Numbered Headings
234259 * ============================================================
235260 */
236261 .h3-numbered
@@ -250,4 +275,47 @@ dl.masthead+p
250275 content: counter(h3-number) ". ";
251276 }
252277
278+
279+/* Styling for In-Line Web-Search Form Fields
280+ * ==========================================
281+ * Derived from Juri Wornowitski's DuckDuckGo search widget implementation,
282+ * version 3.0, as described at https://www.plainlight.com/ddg
283+ */
284+form.search
285+{ /* Let the search box fill the entire width of its containing
286+ * element, with 0.3em spacing above and below; (thus, when two
287+ * search boxes are placed together, they will be separated by
288+ * 0.6em vertical space).
289+ */
290+ width: 100%; margin: 0.3em auto;
291+}
292+form.search input
293+{ /* Establish styling attributes for the keywords input field,
294+ * which fills the search box from its left-hand side, most of
295+ * the way across to the right...
296+ */
297+ display: block; outline: none; box-sizing: border-box;
298+ border: 1px solid #003366; border-right: none; border-radius: 7px 0 0 7px;
299+ height: 30px; width: calc( 100% - 60px ); padding: 0.6em;
300+ font-size: 0.8em; background-color: #f3f3ff;
301+}
302+form.search button
303+{ /* ...with a search button occupying the rightmost 60px.
304+ */
305+ float: right; height: 30px; width: 60px; font-size: 1em;
306+ border: 1px solid #003366; border-left: none; border-radius: 0 7px 7px 0;
307+ cursor: pointer; color: #336699; background-color: #ccccff;
308+}
309+form.search button:active, form.search button:hover
310+{ /* Invert search button colours, when the mouse is placed
311+ * over it, or while a search is in progress.
312+ */
313+ color: #ccccff; background-color: #6699cc;
314+}
315+form.search button:focus
316+{ /* Do not outline the button, even when it has the focus.
317+ */
318+ outline:none;
319+}
320+
253321 /* $RCSfile$: end of file */
Show on old repository browser