The NOTES file already says that code contributions should come to mailing list by email. And it is already linked to under "Release Notes" from the website.
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. The only step we might want to make is to rename NOTES to README. On Tue, Feb 19, 2013 at 01:11:28PM -0500, Richard Woodbury wrote: > On Tue, Feb 19, 2013 at 2:13 AM, Thomas Adam <[1]tho...@xteddy.org> wrote: > > I did have a few notes on this once regarding the correct "policy" for > contributors; perhaps I will add a sentence about this to the NOTES > file. > > I might also suggest creating a "Development" link on > [2]http://tmux.sourceforge.net, perhaps just to point to the NOTES file. > I'd also suggest adding more details about the structure of the project > (e.g., the bit about why there are two repos and how they relate). It > would also be nice to clarify if you have a preference for attached or > inline patches. > > References > > Visible links > 1. mailto:tho...@xteddy.org > 2. http://tmux.sourceforge.net/ > ------------------------------------------------------------------------------ > 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 ------------------------------------------------------------------------------ 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
