Browse files

Final spit&polish before release

  • Loading branch information...
1 parent f444878 commit 98a172de8b7113a6746a2dcdf2fe7cfacf1c19ed @bsdphk bsdphk committed Sep 15, 2016
Showing with 20 additions and 12 deletions.
  1. +15 −7 CONTRIBUTING
  2. +1 −1 LICENSE
  3. +1 −1 README.Packaging
  4. +3 −3 README.rst
@@ -1,21 +1,29 @@
Contributing to Varnish Cache
-To contribute to Varnish, read
- as a starting
-point and follow relevant parts linked there.
Official development tree is here:
-Patches can be sent to
+These days we prefer patches as pull requests directly to that tree.
+Bugreports go there too.
+Our main project communication is through or developer IRC channel::
+ #varnish-hacking on server
+(That channel is not for user questions, use the #varnish channel for that.)
+Mondays at 13:00 EU time we hold our weekly "bugwash" where we go
+through new (and old) tickets. It speeds things up a lot if you
+can be join the channel and answer questions directly when we go
+over the ticket.
Github pull requests
Pull requests are handled like other tickets.
-Trivial pull requests (fix typos, etc) are welcomed, but they will be commited
+Trivial pull requests (fix typos, etc) are welcomed, but they may be commited
by a core team member and the author credited in the commit message.
@@ -1,5 +1,5 @@
Copyright (c) 2006 Verdens Gang AS
-Copyright (c) 2006-2014 Varnish Software AS
+Copyright (c) 2006-2016 Varnish Software AS
All rights reserved.
Redistribution and use in source and binary forms, with or without
@@ -24,4 +24,4 @@ Third-party packages
Varnish Cache is built and packaged in many different operating systems and
-distributions. Please see the wiki for more information.
+distributions. Please see for more information.
@@ -7,9 +7,9 @@ Documentation and additional information about Varnish is available on
Technical questions about Varnish and this release should be addressed
-to <>. Please see
- for how to
-contribute patches and report bugs.
+to <>.
+Please see CONTRIBUTING for how to contribute patches and report bugs.
Questions about commercial support and services related to Varnish
should be addressed to <>.

0 comments on commit 98a172d

Please sign in to comment.