add a news section

.gitignore

@@ -0,0 +1 @@
+_site

_layouts/default.html

@@ -18,9 +18,10 @@ <h2> <a href='/index.html'><span>Vim</span>-Scripts.org</a>
       </div>
       <div id='sidebar'>
         <ol class='toc'>
-          <li><a href='index.html'>Home</a></li>
-          <li><a href='faq.html'>FAQ</a></li>
-          <li><a href='scripts.html'>Scripts</a></li>
+          <li><a href='/index.html'>Home</a></li>
+          <li><a href='/news.html'>News</a></li>
+          <li><a href='/faq.html'>FAQ</a></li>
+          <li><a href='/scripts.html'>Scripts</a></li>
           <li><a href='http://github.com/vim-scripts'>GitHub</a></li>
         </ol>
       </div>

_layouts/news.html

@@ -0,0 +1,6 @@
+---
+layout: default
+---
+<div id='news'>
+{{ content }}
+</div>

config.ru

@@ -0,0 +1,10 @@
+# In theory, you should be able to run this like so:
+#      shotgun ./config.ru -p 4000
+# and there's no need to restart the server anymore.
+# In practice, it appears to be corrupting binary files.
+# Use 'jekyll --server' for now and restart every time you make a change.
+
+require 'rack/jekyll'    # rack-jekyll gem
+require 'yaml'
+
+run Rack::Jekyll.new

css/default.css

@@ -145,3 +145,4 @@ blockquote {
   text-align:center;
 }
 
+.newstitle { margin-top: 0.5em; }

index.markdown

@@ -3,20 +3,38 @@ layout: default
 title: About
 ---
 
-This is a mirror of all the [Vim scripts](http://www.vim.org/scripts/).
+This is a mirror of all [scripts on vim.org](http://www.vim.org/scripts/).
+It provides unified access to all
+[available Vim scripts](http://github.com/vim-scripts/repositories)
+using [Git].
 
 **WARNING: we are not live yet!  Do not expect stability.**
 There is still a good chance that you will have to delete and
 re-clone your repos without warning.  We are close though!
 
-## Motivation
+# Recent News
 
-This mirror is an attempt to improve [Vim] ecosystem by simplifying plugin management.
+No news is good news!  The news archives are <a href='/news.html'>here</a>.
 
-While [Pathogen] simplifies approach to [Vim] plugins, this mirror provides unified access to all [available Vim scripts](http://github.com/vim-scripts/repositories) using [Git].
-Check out [vim-update-bundles](http://github.com/bronson/vim-update-bundles) for an easy way to maintain your plugins with [Pathogen], see [Faq] for more information. 
+{% for post in site.categories.news offset: 0 limit: 3 %}
+  <div id='news'>
+    <div class='newstitle'><a href="{{ post.url }}">{{ post.title }}</a></div>
+    <p>{{ post.date | date_to_string }} &mdash; {{ post.content | strip_html | truncatewords: 25 }} (<a href="{{ post.url }}/">Read more</a>)</p>
+  </div>
+{% endfor %}
 
-## Updates
+# Tools
+
+[Pathogen]'s simple approach to [Vim] plugins inspired this mirror.
+Since then, others have written tools to make things even easier.
+
+ * [vim-update-bundles](http://github.com/bronson/vim-update-bundles)
+   is a small ruby script that makes it easy to set up and manage [Pathogen].
+ * [vundle](http://github.com/gmarik/vundle) is similar and 100% vimscript.
+
+See the [Faq] for more.
+
+# Updates
 
 Visit [GitHub page](http://github.com/vim-scripts/) or grab the [feed](http://github.com/vim-scripts.atom)![feed](http://github.com/images/icons/feed.png) to stay updated on recent activity.
 
@@ -25,3 +43,4 @@ Visit [GitHub page](http://github.com/vim-scripts/) or grab the [feed](http://gi
 [Git]:http://git-scm.com
 [Ruby]:http://ruby-lang.org
 [Faq]:/faq.html
+

news.markdown

@@ -0,0 +1,13 @@
+---
+layout: default
+title: News
+---
+
+{% for post in site.categories.news %}
+  <div class="post">
+    <h2><a href="http://blog.favrik.com{{ post.id }}/">{{ post.title }}</a></h2>
+    <p><strong>{{ post.date | date_to_string }}</strong></p>
+    {{ post.content }}
+  </div>
+{% endfor %}
+

news/_posts/2010-10-15-big-improvements.md

@@ -0,0 +1,49 @@
+---
+layout: news
+title: Major Changes
+category: news
+---
+
+Major changes are afoot: we've deleted and re-created every repository
+on vim-scripts.  The biggest reason we did this was to conver the
+email addresses in the commits messages into something that GitHub
+can link automatically.  This was
+also a good opportunity to fix long and multi-line commit messages and
+suppress a bunch of .swp files that authors uploaded accidentally.
+
+As a side-effect of the ground-up rebuild, various problems in the
+following scripts have been repaired.
+If they gave you trouble before, it's worth trying again.
+
+ - 0065 - CD.vim
+ - 0356 - dbext.vim
+ - 0492 - SQLUtilities
+ - 0848 - SrchRplcHiGrp.vim
+ - 1234 - YankRing.vim
+ - 1839 - IndentAnything
+ - 3025 - Command-T
+ - 3051 - vimform
+ - 3087 - OutlookVim
+ - 3154 - vorax
+ - 3169 - luainspect
+
+It's minor, but it's nice that the dates on these scripts were fixed:
+
+ - 1052 - The-Mail-Suite-tms
+ - 1082 - MS-Word-from-VIM
+
+Finally, in the past two months the authors of the following scripts
+deleted some or all of their histories.  We restored missing revisions
+were restored from the previous vim-scripts mirror.  This explains why
+a few commits here and there still have the old (broken) email addresses
+and commit messages.
+
+ - 2791 - popup\_it--su
+ - 1259 - sienna
+ - 2653 - cuteErrorMarker
+ - 1651 - freya
+ - 2109 - BBCode--Dahn
+ - 2188 - earendel
+ - 3118 - skk.vim-B
+
+Upload starting soon!

news/_posts/2010-10-17-github-organizations.md

@@ -0,0 +1,59 @@
+---
+layout: news
+title: GitHub Organization Conversion Mistake
+category: news
+---
+
+A quick note on why I converted vim-scripts to a GitHub organization,
+and then converted it back.
+
+Let's start at the beginning...
+
+I'm fairly unhappy with the way GitHub handles messaging.
+Mostly it's because GitHub makes it impossible to reply directly
+to a GitHub message via email.
+
+When somebody sends vim-scripts a
+message, I need to log out of my account, log into vim-scripts, write
+the reply from scratch using the lame webform editor,
+log out, log back into my personal account, and then do it all
+over again in a few hours.  The outgoing message
+isn't saved so I can't easily copy from previous converations.
+It's private.  It's tedious.  It's horrible.  I'll never do it.
+
+Therefore, I'd like to disable messaging completely on the vim-scripts account.
+Alas, GitHub doesn't allow that.  If you turn off message notifications,
+people will still send you messages, you'll just never hear about it.
+
+That's why I was rejoicing when I saw that all of this business
+appears to be fixed with
+[GitHub organizations](http://github.com/blog/674-introducing-organizations).
+I converted vim-scripts last week.
+
+Result: catastrophe.
+
+The first problem was that GitHub
+[doesn't allow you to follow](http://groups.google.com/group/github/browse_thread/thread/16d6bb44db891568)
+an organization
+[(support issue)](http://support.github.com/discussions/feature-requests/950-feature-request-follow-this-organization).
+Without warning, everyone following vim-scripts was bumped out.  Sorry!
+I tried creating a [vim-scraper](http://github.com/vim-scraper)
+user for interested people to follow but that had problems of its own.
+
+Besides, who would think to follow vim-scraper when you want to watch
+what's happening on vim-scripts?  This organization
+was barely 10 minutes old and already it was starting to smell putrid.
+
+After a few more hours I managed to work around all of the problems except
+[one showstopper](http://github.com/develop/develop.github.com/commit/4ec1902ca7573aeacdf29866556fcf0ac827b290#comments).
+Oh well!  There's no way to convert an organization back into a user
+so I had to delete vim-scripts and start from scratch.
+
+Even if GitHub fixes all the problems we ran into, I don't think I'll
+convert back any time soon.  Feel free to follow vim-scripts without
+having to worry about what GitHub's confusion about what it means to
+follow an organization.
+
+So, we're back to where we started.
+The best way to watch what's happening on vim-scripts?  Follow it!
+

news/_posts/2010-10-18-upload-continuing.md

@@ -0,0 +1,9 @@
+---
+layout: news
+title: Upload Continuing
+category: news
+---
+
+The first 1000 scripts have been uploaded.  Things are moving at about
+one script every 15 seconds so all 3229 scripts should be up before tomorrow.
+When the counter hits 3231, we're done!