2
0
mirror of https://github.com/boostorg/website.git synced 2026-01-19 04:42:17 +00:00
Files
website/community/requests.html
Daniel James 40688e1552 Update links for https
Mostly in comments. Might be better to use relative links from html.
2018-04-13 09:14:48 +01:00

86 lines
3.0 KiB
HTML

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<title>Requesting New Features</title>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
<link rel="icon" href="/favicon.ico" type="image/ico" />
<link rel="stylesheet" type="text/css" href=
"/style-v2/section-community.css" />
<!--[if IE 7]> <style type="text/css"> body { behavior: url(/style-v2/csshover3.htc); } </style> <![endif]-->
</head><!--
Note: Editing website content is documented at:
https://www.boost.org/development/website_updating.html
-->
<body>
<div id="heading">
<!--#include virtual="/common/heading.html" -->
</div>
<div id="body">
<div id="body-inner">
<div id="content">
<div class="section" id="intro">
<div class="section-0">
<div class="section-title">
<h1>Requesting new features for Boost libraries</h1>
</div>
<div class="section-body">
<p>If you have an idea for a feature or improvement to an
existing Boost library - go ahead and post it to either
<a href="/community/groups.html#users">boost-users list</a> or
<a href="/community/groups.html#main">boost mailing list</a>
(if you are posting for the first time, please read our
<a href="https://www.boost.org/more/discussion_policy.htm">discussion
policy</a> before you actually post).</p>
<p>You can also try submitting a feature request to our
<a href="http://svn.boost.org/trac/boost/newticket">ticket
system</a>, but experience has shown that posting to either of
the mailing lists is usually a more effective way to get
attention of boost developers.</p>
<p>If your proposal has its merits, it's very likely that it
will generate a constructive discussion that might actually
result in (sometimes substantial) improvement of the library -
and your name being put on the library's <a href=
"/development/requirements.html#Acknowledgements">Acknowledgements</a>
section!</p>
</div>
</div>
</div>
</div>
<div id="sidebar">
<!--#include virtual="/common/sidebar-common.html" -->
<!--#include virtual="/common/sidebar-community.html" -->
</div>
<div class="clear"></div>
</div>
</div>
<div id="footer">
<div id="footer-left">
<div id="revised">
<p>Revised $Date$</p>
</div>
<div id="copyright">
<p>&copy; Copyright <a href=
"/users/people/aleksey_gurtovoy.html">Aleksey Gurtovoy</a> 2002</p>
</div><!--#include virtual="/common/footer-license.html" -->
</div>
<div id="footer-right">
<!--#include virtual="/common/footer-banners.html" -->
</div>
<div class="clear"></div>
</div>
</body>
</html>