Module: website
Branch: master
Commit: 5d77e2fd6ee96ab250d128326a9790336306acc5
URL: http://source.winehq.org/git/website.git/?a=commit;h=5d77e2fd6ee96ab250d128…
Author: Zachary Goldberg <zgs(a)seas.upenn.edu>
Date: Mon Dec 3 00:22:08 2007 -0500
Fwd: Wine Weekly Newsletter
Jeremy,
Attached is the output of the command "git diff origin". Please let
me know if this will work for you.
Thanks very much!
--Zach
On Nov 30, 2007 2:08 PM, Zachary Goldberg <zgs(a)seas.upenn.edu> wrote:
> Sounds good to me :)
>
>
> On Nov 30, 2007 1:45 PM, Jeremy Newman <jnewman(a)codeweavers.com> wrote:
> > OK, I may not get to apply it until Monday morning. I usually only apply
> > patches when I'm in the office. 9-5 CST M-F
> >
> >
> > Zachary Goldberg wrote:
> > > Aha! Found the other git tree, website.git. Will send you a patch
> > > sunday night?
> > >
> > > On Nov 30, 2007 12:11 PM, Zachary Goldberg <zgs(a)seas.upenn.edu> wrote:
> > >> Jeremy,
> > >>
> > >> So I'm cloning the git tree to my local pc as we speak. I'm guessing
> > >> that WineHQ itself is in the git somewhere, i'll commit my new files
> > >> and then email you a patch?
> > >>
> > >> --Zach
> > >>
> > >>
> > >>
> > >> On Nov 27, 2007 10:25 AM, Jeremy Newman <jnewman(a)codeweavers.com> wrote:
> > >>> Hello Zack, good to have someone taking on this task.
> > >>>
> > >>> Brian did most of the grunt work on this. I simply applied his patches
> > >>> to my working tree, and did a simple check to make sure the XML was
> > >>> valid. If it looked OK, I committed it.
> > >>>
> > >>> These days we have switched the Website over to Git. I usually will only
> > >>> accept patches in git format. You may want to read up on the Wiki on how
> > >>> to use Git. Since you are new to this gig, I will accept new issues just
> > >>> as they are.
> > >>>
> > >>> Feel free to ask questions, I will help in any way that I can.
> > >>>
> > >>> -newman
> > >>>
> > >>>
> > >>> Zachary Goldberg wrote:
> > >>>> Mr. Newman,
> > >>>>
> > >>>> Hi, I'm Zach. I've been in contact with Brian Vincent a bit these
> > >>>> past few days and I've begun working on the WWN again. Just wanted to
> > >>>> give you a heads up that the project has been picked up again. I
> > >>>> expect to have a finished XML file for publishing for next Monday
> > >>>> covering the past 2 weeks of devel (ish). In the future it was
> > >>>> proposed to have a 'big wwn' to cover the lapsed months. The purpose
> > >>>> of this email is just to touch base with you; let you know that stuff
> > >>>> is going on and to request any information you may have that might be
> > >>>> helpful in the writing or publishing process.
> > >>>>
> > >>>> Thanks,
> > >>>> Zach
> > >>>>
> > >>>>
> > >>>> ---------- Forwarded message ----------
> > >>>> From: Brian Vincent <brian.vincent(a)gmail.com>
> > >>>> Date: Nov 22, 2007 8:42 PM
> > >>>> Subject: Re: Wine Weekly Newsletter
> > >>>> To: Zachary Goldberg <zgs(a)seas.upenn.edu>
> > >>>> Cc: Alex Waite <awaite2(a)uiuc.edu>
> > >>>>
> > >>>>
> > >>>> I finally got around to writing this and its a lot of random thoughts:
> > >>>>
> > >>>> 1. The writing is simple. It's the markup that takes time. I used
> > >>>> to use some vi macros for it (I lost them, so they won't be of any
> > >>>> help.)
> > >>>>
> > >>>> 2. Legal stuff.. this one is kind of tricky, but it's rather
> > >>>> important. Wine walks a tightrope of legality and the sharks swimming
> > >>>> underneath are a bunch of lawyers in Redmond. Make no mistake about
> > >>>> it, there's a lot of Wine developers who worry about Microsoft. Now,
> > >>>> Alexandre and Jeremy have done a fine, fine job of making sure the
> > >>>> project doesn't infringe on any copyrights or violate the DMCA, etc.
> > >>>> However, there's been developers in the past and there will be more in
> > >>>> the future who are going to break the law. Maybe they'll copy
> > >>>> Microsoft source code, maybe they'll disassemble code, or something
> > >>>> else. These issues get brought up on the mailing list from time to
> > >>>> time and sometimes even result in heated debate. Don't write about
> > >>>> them. Please. Yes they're on a public mailing list, but the dirty
> > >>>> laundry doesn't need to be aired in WWN. There was something in the
> > >>>> draft thing Zach did similar to this.
> > >>>>
> > >>>> 3. CodeWeavers really is a godsend for Wine. If it wasn't for them
> > >>>> the project would have gone nowhere a long time ago. Plus, Jeremy and
> > >>>> company are just a genuinely nice group of people. I always tried to
> > >>>> give them as much credit as they deserve.
> > >>>>
> > >>>> 4. Write every day. I can't stress this enough. Don't try to sit
> > >>>> down and do a whole WWN at once. This is hard at first because you
> > >>>> don't know which threads to pick. Later it gets easier because you
> > >>>> can tell right from the first post which threads will go in WWN for
> > >>>> the week and you can add to them slowly over a series of days.
> > >>>>
> > >>>> 5. Picking threads - it takes a while to figure out which threads to
> > >>>> write about. Don't worry so much about it. Covering any thread is
> > >>>> better than covering no threads.
> > >>>>
> > >>>> 6. Be wary of any thread on the mailing list by someone new who says
> > >>>> something like, "I'm going to start working on Wine and I'm going to
> > >>>> implement .Net". Big boasts often don't come true. This used to be
> > >>>> much more of problem than it is now.
> > >>>>
> > >>>> 7. Zach Brown used to run Kernel Traffic (kerneltraffic.org) and I'd
> > >>>> mail him each WWN for posting on that site as well. I don't think too
> > >>>> many people read that site any more so I'm not sure how important that
> > >>>> is. For that reason, you might want to consider dropping the <topic>
> > >>>> tag.
> > >>>>
> > >>>> 8. You don't need to include every sentence of every post. There's
> > >>>> more than a few times where I'd whittle a multi-paragraph email down
> > >>>> to one sentence.
> > >>>>
> > >>>> 9. Alexandre writes extremely dense sentences. If he responds to a
> > >>>> post, read it carefully because there's a good chance they're the two
> > >>>> most important sentences in a thread.
> > >>>>
> > >>>> 10. I almost never rewrote anyone's posts. Keep in mind the English
> > >>>> isn't the first language for most of Wine's developers. Some
> > >>>> developers have excellent English while others don't. Only in a few
> > >>>> extreme cases did I rewrite a sentence because I knew the developer
> > >>>> didn't say what he meant to say. Early on I didn't correct spelling
> > >>>> mistakes, later I started correcting the glaring errors. Francois
> > >>>> Gouget will fix all the spelling problems for you anyway.
> > >>>>
> > >>>> 11. Jeremy Newman is the webmaster for WineHQ. He can answer lots of
> > >>>> questions you might run into. jnewman(a)codeweavers.com
> > >>>>
> > >>>> 12. Fridays are a great day to finish to finish an issue but a lousy
> > >>>> day to publish one. The mailing list is very much a Monday - Friday
> > >>>> thing. Many threads start on a Monday and wrap up by the end of the
> > >>>> week. It's really weird how regular that is. Friday sucks as a day
> > >>>> to publish because less people will read that issue of WWN. You get a
> > >>>> lot more readership if you publish on a Monday or a Thursday. I
> > >>>> always found those days work best.
> > >>>>
> > >>>> 13. Keep in mind what you're doing really has the potential to bring
> > >>>> in $$$ and new developers to the project. I used to always highlight
> > >>>> threads that talked about projects that needed to be done. More than
> > >>>> once someone would read WWN and think, "I know how to work on
> > >>>> something like that, maybe I can contribute to the project."
> > >>>>
> > >>>> 14. WWN seems really thankless and it's easy to get disillusioned
> > >>>> that no one reads it. It took me quite a few years to realize a lot
> > >>>> of people really appreciate it. Most of the developers read it every
> > >>>> week even though they're on the mailing list.
> > >>>>
> > >>>> 15. It would be easy to collaborate on a WWN issue by simply letting
> > >>>> different people write different <section>'s each week. However, I
> > >>>> had an idea - is there a way to use Google Docs to collaborate on such
> > >>>> a thing?
> > >>>>
> > >>>> Now for the nitty gritty on how I'd actually write an issue:
> > >>>>
> > >>>> 1. I'd write each <section> separately and store them in separate
> > >>>> files. Look at the XML source and that'll make sense. Remember when
> > >>>> I said all the work was in the markup?
> > >>>>
> > >>>> 2. Then at the end of the week I'd run a script that downloaded the
> > >>>> mailing list, created the stats, and built the header for the XML
> > >>>> file. It also tried to find some of the duplicate names in the stats
> > >>>> and alert me to them as well as convert the Unicode names to ANSI.
> > >>>>
> > >>>> 3. I'd usually write the first <section>, the News section, toward
> > >>>> the end of the week. It used to be fairly time consuming combing
> > >>>> sites for news about Wine. It's a lot easier now - just go to Google
> > >>>> News and search for "Wine Linux". It'll turn up everything you want
> > >>>> to cover.
> > >>>>
> > >>>> 4. Then I'd cat header file with all the <section> files. I'd run
> > >>>> the whole thing first through a program called 'tidy' to check if the
> > >>>> XML was malformed. Then I'd run it all through xmllint after those
> > >>>> mistakes were fixed. tidy gives easier to read output compared to
> > >>>> xmllint. However, xmllint is extremely strict and follows the same
> > >>>> standards required by the backend on WineHQ.
> > >>>>
> > >>>> 5. All of WineHQ used to reside in CVS. Now it's in git. So I
> > >>>> really can't help you with how to commit to that because I never have.
> > >>>> Ask jnewman(a)codeweavers.com for details. I used to directly commit
> > >>>> to CVS, I'm sure the same can be done with git.
> > >>>>
> > >>>> 6. A lot of times I'd start the next issue before the current one was
> > >>>> even out. It's useful to wait for threads to wrap up.
> > >>>>
> > >>>> 7. I'll send another email from my shell account with all the scripts
> > >>>> I used to generate stats and build the XML header.
> > >>>>
> > >>>> -Brian
> > >>>>
> > >>>>
> > >>>> On 10/26/07, Zachary Goldberg <zgs(a)seas.upenn.edu> wrote:
> > >>>>
> > >>>>> Alex,
> > >>>>>
> > >>>>> Attached is ~20 minutes of working crawling this month's devel list
> > >>>>> serv. Let me know your thoughts.
> > >>>>>
> > >>>>> --Zach
> > >>>>>
> > >>>>> On 10/26/07, Alex Waite <awaite2(a)uiuc.edu> wrote:
> > >>>>>
> > >>>>>> Sounds good to me. And don't worry, I understand what life is like in
> > >>>>>> college; I'm a current student. We'll cover October and then proceed
> > >>>>>> from there.
> > >>>>>>
> > >>>>>> ---Alex
> > >>>>>>
> > >>>>>> Zachary Goldberg wrote:
> > >>>>>>
> > >>>>>>> I completely agree and was contemplating this as I wrote my last e-mail.
> > >>>>>>>
> > >>>>>>> While I do see the value in covering all important things, I think
> > >>>>>>> given that none of us has infinite time (even though you may think
> > >>>>>>> college kids do =P) a comprehensive WWN since may might be hard.
> > >>>>>>> However I propose the following:
> > >>>>>>>
> > >>>>>>> We begin WWN with the month of october, then continue weekly from there.
> > >>>>>>>
> > >>>>>>> Somewhere down the road, within the next couple weeks, we release a
> > >>>>>>> 'special edition' WWN which covers late May June July August and
> > >>>>>>> September.
> > >>>>>>>
> > >>>>>>> --Zach
> > >>>>>>>
> > >>>>> --
> > >>>>> Zachary Goldberg
> > >>>>> Computer Science Major
> > >>>>> School of Engineering at the University of Pennsylvania
> > >>>>> Philadelphia PA
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>
> > >>
> > >>
> > >> --
> > >> Zachary Goldberg
> > >> Computer Science & Engineering
> > >> Electrical Captain of Penn Electric Race Team
> > >>
> > >> School of Engineering at the University of Pennsylvania
> > >>
> > >
> > >
> > >
> >
>
>
>
> --
>
> Zachary Goldberg
> Computer Science & Engineering
> Electrical Captain of Penn Electric Race Team
> School of Engineering at the University of Pennsylvania
>
--
Zachary Goldberg
Computer Science & Engineering
Electrical Captain of Penn Electric Race Team
School of Engineering at the University of Pennsylvania
---
news/200712301.xml | 7 +
wwn/wn20071203_333.xml | 495 ++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 502 insertions(+), 0 deletions(-)
Diff: http://source.winehq.org/git/website.git/?a=commitdiff;h=5d77e2fd6ee96ab250…