On Tue, Feb 19, 2013 at 1:23 PM, Nicholas Marriott <
nicholas.marri...@gmail.com> wrote:
> The NOTES file already says that code contributions should come to
> mailing list by email.
Yes, but it doesn't specify a preference for attached vs. inline. If there
is no preference, may it is fine the way it is.
> And it is already linked to under "Release
> Notes" from the website.
>
Ah... I didn't realize that link took you to that file, as I would have
expected to find release notes there, not "how to build".
> So far we've had one person enquiring about this - and he still managed
> to do it just fine. I don't think we need any extra documentation,
> policies or whatever on this just yet.
>
I chimed in on this thread because I ran into similar problems, but didn't
inquire originally and just took a stab at it. My first patch was sent as a
pull request to the mailing list, which is one interpretation of the NOTES
file. Given that it seems at first blush that the project uses git, it
seemed reasonable. A little bit of clarification could help newbies.
> The only step we might want to make is to rename NOTES to README.
>
Agreed... and then perhaps make that accessible from the website via
something other than "Release Notes" so it is discoverable?
This may seem like yak shaving, but my intuition is that being clearer
about how to contribute helps encourage people to submit patches instead of
just bug reports.
Let me know if I can help in any way.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users
