<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 10/5/12 11:42 AM, Marc Beneteau
wrote:<br>
</div>
<blockquote
cite="mid:CADZaJgPD202CrV6TcYjMvsYu9Wafc7hgRX7_BrYuABy5BW3KdA@mail.gmail.com"
type="cite">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Sorry
Jane I am now confused.<span style="">
</span>"that is what the support group is working on </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><a
moz-do-not-send="true" href="http://svnbook.red-bean.com/">http://svnbook.red-bean.com/</a></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">"…
you
mean the Codex people (this list)?<span style=""> </span>Or
is this a separate group?<span style=""> </span>I want to be
invited to that.</span></p>
</blockquote>
There's no special invitation, you just start contributing. The
group is at <a class="moz-txt-link-freetext" href="http://make.wordpress.org/support">http://make.wordpress.org/support</a>. That includes both
support forums and documentation. The Codex is the existing
documentation. The handbooks are the new documentation project they
are working on there. Review the history on the blog there for more
information. This list (along with the forums list) is
semi-deprecated in favor of the blog, which is more accessible to
potential contributors. <br>
<br>
<blockquote
cite="mid:CADZaJgPD202CrV6TcYjMvsYu9Wafc7hgRX7_BrYuABy5BW3KdA@mail.gmail.com"
type="cite">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> I
have stuff to contribute but I am not very interested in
working on a
legacy platform, I hope that's clear now, </span></p>
</blockquote>
It's been clear from your first email, as has been our disinterest
in pursuing the windows-style platform you prefer.<br>
<br>
<blockquote
cite="mid:CADZaJgPD202CrV6TcYjMvsYu9Wafc7hgRX7_BrYuABy5BW3KdA@mail.gmail.com"
type="cite">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">and
also I disagree with you "</span><span style=""> the SVN book
is just HTML</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
", the
organization of the topics is crucial, </span></p>
</blockquote>
Yes, but the organization of topics is CONTENT, not PLATFORM.<br>
<br>
<blockquote
cite="mid:CADZaJgPD202CrV6TcYjMvsYu9Wafc7hgRX7_BrYuABy5BW3KdA@mail.gmail.com"
type="cite">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">and
also the decision of whether this is
going to context-sensitive help inside the dashboard</span></p>
</blockquote>
Documentation and core ux are two different things. Changing the way
help is treated in the dashboard would go through the core team.
Nacin is the release lead, and 3.5 is already in beta, so
suggestions for new features will probably be taken in January at
the beginning of the 3.6 cycle. But again, there is nothing stopping
you from making a plugin that does things exactly the way you want
them, and releasing that. If someone who hasn't contributed to core
before wants to make suggestions to change the core ux/ui, having a
publicly released plugin that does what is being suggested will get
more attention than someone just coming in cold and saying "I think
you should do x". <br>
<br>
</body>
</html>