[drupal-docs] Drupal Newsletter #3 - Draft 1

[Steven Wittens]

I noticed that we don't actually have an unsubscription form at 
/newsletter. I added one.

Some content notes:
- I don't think we should market the Portland Drupalcon as "Mini"... 
remember, when we did the FOSDEM thing, we were unsure of how many 
people would attend. We ended up having about 80 people in the room at 
all times.
- Killes is quite modest about the revisions patch: it does affect 
end-users in that it improves the revisions UI, and also makes it vastly 
easier to make revision-enhancing modules :P.

More specifically: (not sure about some of the corrections)

>  The big news this month is out large scale outage lasting over 3
>days which caused a severe disruption in the Drupal services
><http://drupal.org/node/26545>.
>
out -> our. Also, to my (non-native) ears, "big news" sounds positive. 
Perhaps "important" is a better phrasing.

>  It appears our downtime was a blessing in disguise; raising over
>$10,000 USD, setting up a long term hosting plan with OSL
><http://drupal.org/node/26707> and getting server and service
>donations!
>
This sounds like a good place to add in "Every cloud has a silver lining" ;)

>Server Infrastructure – Get an inside viewpoint on the upcoming Server upgrades.
>  
>
Server -> server

>OSCON Portland August 1-5, 2005
>  
>
Like in the last newsletter, I think we should expand OSCON to "O'Reilly 
Open-Source Conference" at least once in the text.

>GK: Not too bad.  I am known as a anti-JS zealot, but I was actually
>  
>
a anti -> an anti ?

>RM: So, you mentioned a revision system, could you share some more
>about this for our readers?
>  
>
share ... for -> share ... with ?

>RM: Ok, so how will the help administrators and developers?
>  
>
how will the help -> how will this help

>GK: Admins will have the benefit that I also added the "log" field,
>which is currently reserved for book nodes, to the node table, making
>it generally available.  Also, the logs are stored alongside the
>revision they belong to allowing for better workflow.  Etc.
>  
>
Maybe "etc" should be replaced with something more meaningful like "This 
opens up more possibilities for future modules as well."

>RM: So, do you feel that the development is slowing down on Drupal? 
>Or are there still some big features in the works?
>
>GK: No, development cannot possibly slow down Drupal.  
>  
>
You asked "development is slowing down on Drupal" but Gerhard replied 
with "cannot possibly slow down Drupal". Could be a typo?

>round robin DNS.  The third Dell will host CVS (future SVN) and all
>  
>
"future SVN" should be clarified, as there is currently no official 
decision on whether we will move to SVN or simply use SVN to complement 
CVS. "possibly SVN in the future as well" is probably a better phrasing 
that will raise less questions.

>Moving forward, the next step is look into implementing Linux Virtual
>  
>
the next step is look -> the next step is to look ?

>yourself?  That what this Cafepress site wants to happen, so why not
>  
>
that -> that's

Steven Wittens