I'm prepared to write the WWN releases in Brian Vincent seeming absence if it pleases the powers that be.
If this is alright I'd like some one to give an overview of what topics should be covered and then for some one to review the first one or two created. I've read the last hundred or so WWN issues over the years so I have a good idea of whats required though clarification would be nice.
I already got wine-devel/wine-users - are there any more that need to be monitored.
Finally I would need to know how to submit the newsletter and the proper syntax.
Edward
On 12/4/06, Edward Savage epssyis@gmail.com wrote:
I'm prepared to write the WWN releases in Brian Vincent seeming absence if it pleases the powers that be.
It pleases the powers that be.
Things have been a little out of control here for the past few months. I've had intentions of it.. I swear.. I shouldn't delude myself into thinking it'll get done any time in the next few months. Especially since my priority at this point has been on another writing project.
Here's some random thoughts:
1. Write about topics you find interesting. 2. Having 4 topics weekly is better than 8 topics every two weeks. 3. Look at the XML file to see the syntax. It's the same syntax shared with Kernel Traffic and I'd recommend submitting those to Zack Brown for inclusion there. (I'll email you offline with his address.) 4. Use an XML checker to check the XML before sending it in. I'd recommend tidy first followed by xmllint. 5. The best day of the week to publish an issue is a Friday. Most threads on Wine-devel start and end between Monday - Thursday. 6. At some point I'll probably want to get back into it, but the structure of WWN lends itself to be easily decentralized. 7. If you want to email me the first few issues you write, I can put them up. Or send them to wine-patches, but that might take longer to get put up. Eventually we should make a CVS log in for you.
-Brian
Alright that sounds reasonably easy.
I'm on uni break for the next three months so apart from learning cpp I don't have much else to do. :P
I will attempt to have an issue by this friday - probably a recap on what has happened since the last release. I'll send it through once done for you to review/submit.
On 12/6/06, Brian Vincent brian.vincent@gmail.com wrote:
On 12/4/06, Edward Savage epssyis@gmail.com wrote:
I'm prepared to write the WWN releases in Brian Vincent seeming absence
if
it pleases the powers that be.
It pleases the powers that be.
Things have been a little out of control here for the past few months. I've had intentions of it.. I swear.. I shouldn't delude myself into thinking it'll get done any time in the next few months. Especially since my priority at this point has been on another writing project.
Here's some random thoughts:
- Write about topics you find interesting.
- Having 4 topics weekly is better than 8 topics every two weeks.
- Look at the XML file to see the syntax. It's the same syntax
shared with Kernel Traffic and I'd recommend submitting those to Zack Brown for inclusion there. (I'll email you offline with his address.) 4. Use an XML checker to check the XML before sending it in. I'd recommend tidy first followed by xmllint. 5. The best day of the week to publish an issue is a Friday. Most threads on Wine-devel start and end between Monday - Thursday. 6. At some point I'll probably want to get back into it, but the structure of WWN lends itself to be easily decentralized. 7. If you want to email me the first few issues you write, I can put them up. Or send them to wine-patches, but that might take longer to get put up. Eventually we should make a CVS log in for you.
-Brian
-
Brian Vincent -
Edward Savage