...making Linux just a little more fun!
Martin J Hooper [martinjh at blueyonder.co.uk]
Hey congrats on the 150th issue!!
clarjon1 [clarjon1 at gmail.com]
On Thu, May 1, 2008 at 11:40 PM, Martin J Hooper <martinjh@blueyonder.co.uk> wrote:
> Hey congrats on the 150th issue!!>
I second that!
Happy 150th, LG
Ben Okopnik [ben at linuxgazette.net]
On Fri, May 02, 2008 at 08:59:03AM -0400, clarjon1 wrote:
> On Thu, May 1, 2008 at 11:40 PM, Martin J Hooper > <martinjh@blueyonder.co.uk> wrote: > > Hey congrats on the 150th issue!!
Indeed; happy 150th, LG. It's taken a lot of effort and involved a lot of people, including everyone here. Thanks, everybody, for helping make it a great community resource!
This is also a good point to review the process by which LG happens, and ask for input from you folks. As it stands right now, the process is fragile, top-heavy, and has a couple of bad choke-points; perhaps someone here will have a suggestion or two for improving it.
1) Starting from the source end, we have articles and press releases come into LG, via articles@ and bytes@ addresses (or, occasionally, less orthodox means.) For articles, I review them and either a) add them to the upcoming issue repository (SVN) or b) put them on hold (my personal directory in SVN, p/ben/tmp) for publication in a later issue.
2) PR gets routed to my 'bytes' mailbox. Ever since we lost Sam Bisbee as NewsBytes editor, that load has gone floating... which means that either I do it (very rarely), Kat does it (usually), or it doesn't get done (all too common.)
3) The articles, meanwhile, have been vetted and generally pounded into shape by yours truly. The sit in articles/<issue_number>/, where they are available to our proofreaders and tech editors until the end of the month.
4) At that point, Kat produces the various in-house mail stuff (lg_mailbag, lg_launderette, lg_tips, etc.) and adds them to the repository, while I proof, edit, and review anything that hasn't been handled. In parallel with this, I repeatedly build the issue and check the layout as I work on a given article.
5) Next, I add external content (comics, other news, etc.) and process it to fit the LG format.
6) I build the issue and check it, with Kat providing backup, and fix any flaws. After several rounds of this, the issue is ready to be published. I run the final processing scripts, depending on how much time and energy I have (adding Digg links, 'tidy', etc.), do a final check on the issue, and a final build.
7) Last, I upload the newly-created issue to the LG server, relink https://linuxgazette.net/current to point to it, update 'archives.html' to contain the new issue link, build the FTP tarball, and send out the "LG has been pubbed!" notice to the world.
As you can probably guess by now, all of this is getting to be quite the sore point; this is all besides the usual monthly stuff I do for LG (i.e., dealing with conference promoters, review book submissions and requests, handling author and volunteer questions, updating/maintaining the FAQs, handling site questions and issues, creating and updating the LG scripts, etc.) There are times, especially during that final stretch, that I get so frustrated that I feel like dropping the whole thing and walking away. As it stands, Kat and I usually spend the last three days of the month doing nothing but LG stuff - and this is way, way too much.
This is not to slight the services of our steady reviewers, by the way; in particular, René Pfeiffer has quietly but steadily done a bunch of editing every month, and a number of other people have participated at various times - but to keep LG going, we need more than that. Say, three or four steady reviewers every single month, with help from others on occasion would take care of it.
Folks, I really do need help here. Changes need to happen if LG is to keep running - there's no reasonable way that I and Kat can keep carrying that load. I would really appreciate suggestions, offers of help, ideas on making the process better, etc. It can't keep going like this... and I would really prefer to have this separated into reasonable chunks, each handled by a responsible, reliable person than have it all come suddenly crashing down one month because I just couldn't handle the stress and the effort.
-- * Ben Okopnik * Editor-in-Chief, Linux Gazette * https://LinuxGazette.NET *
Ramanathan Muthaiah [rus.cahimb at gmail.com]
On 5/3/08, Ben Okopnik <ben@linuxgazette.net> wrote:
> On Fri, May 02, 2008 at 08:59:03AM -0400, clarjon1 wrote: > > On Thu, May 1, 2008 at 11:40 PM, Martin J Hooper > > <martinjh@blueyonder.co.uk> wrote: > > > Hey congrats on the 150th issue!!
Ben & Co,
LG rocks.
After my first brief article on Subversion was posted in one of LG's issue. the response and feedback encouraged me to attempt writing articles for print magazines also.
> . . . . . . > . . . . . . > . . . . . . > > > Folks, I really do need help here. Changes need to happen if LG is to > keep running - there's no reasonable way that I and Kat can keep > carrying that load. I would really appreciate suggestions, offers of > help, ideas on making the process better, etc. It can't keep going like > this... and I would really prefer to have this separated into reasonable > chunks, each handled by a responsible, reliable person than have it all > come suddenly crashing down one month because I just couldn't handle the > stress and the effort.
While am reading through LG's open jobs (https://linuxgazette.net/jobs.html) to understand the details, am available immediately for any kind of assistance.
You can count on me.
-- regards Ramanathan
Ben Okopnik [ben at linuxgazette.net]
On Sat, May 03, 2008 at 11:16:05PM +0530, Ramanathan Muthaiah wrote:
> On 5/3/08, Ben Okopnik <ben@linuxgazette.net> wrote: > > On Fri, May 02, 2008 at 08:59:03AM -0400, clarjon1 wrote: > > > On Thu, May 1, 2008 at 11:40 PM, Martin J Hooper > > > <martinjh@blueyonder.co.uk> wrote: > > > > Hey congrats on the 150th issue!!
That's excellent, Ram. I like to see LG functioning as a springboard for people's talents and abilities; I see that as one of the hugely positive effects that Linux has on the world, and I'm always chuffed to hear of another success story of that sort.
> > Folks, I really do need help here. Changes need to happen if LG is to > > keep running - there's no reasonable way that I and Kat can keep > > carrying that load. I would really appreciate suggestions, offers of > > help, ideas on making the process better, etc. It can't keep going like > > this... and I would really prefer to have this separated into reasonable > > chunks, each handled by a responsible, reliable person than have it all > > come suddenly crashing down one month because I just couldn't handle the > > stress and the effort. > > While am reading through LG's open jobs > (https://linuxgazette.net/jobs.html) to understand the details, am > available immediately for any kind of assistance. > > You can count on me.
Thanks, Ram - I appreciate that. What I mostly see as necessary right now is a steady crew of proofreaders and tech editors. We really need a NewsBytes editor - someone who will take in the stream of PR, separate out the hype, and presents our readers with useful, relevant content. We need one or more editors for our mail stream: someone to produce the Mailbag, 2-Cent Tips, Talkbacks, etc. - this is just a matter of tweaking the input to produce a reasonable layout rather than any sort of proofing or editing. Most of all, though, we need people who will be there reliably, every month - or who will let us know, as early as possible, that they won't make it that month. That's a serious commitment - and that's what we really need.
-- * Ben Okopnik * Editor-in-Chief, Linux Gazette * https://LinuxGazette.NET *
René Pfeiffer [lynx at luchs.at]
--===============0708925247== Content-Disposition: inline Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="o7gdRJTuwFmWapyH"
--o7gdRJTuwFmWapyH Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable
On May 03, 2008 at 0849 -0400, Ben Okopnik appeared and said:
> On Fri, May 02, 2008 at 08:59:03AM -0400, clarjon1 wrote: > > On Thu, May 1, 2008 at 11:40 PM, Martin J Hooper > > <martinjh@blueyonder.co.uk> wrote: > > > Hey congrats on the 150th issue!!
And a big thank you for Kat's and your effort! I saw the pile of articles, did what I could, but ran out of time due to a cold and having to pose as a official wedding photographer over the weekend.
> This is also a good point to review the process by which LG happens, and > ask for input from you folks. As it stands right now, the process is > fragile, top-heavy, and has a couple of bad choke-points; perhaps > someone here will have a suggestion or two for improving it.
The first thing that springs to my mind is some sort of coordination between the (technical) proof-readers. Quite often I don't know if someone is working (or is going to work) on an article and if someone needs help when proof-reading an article. Maybe checking the subversion log is sufficient, but I think there should be some words describing what to do and what to look for. There is a workflow description in the "Proofreading LG" FAQ section, but I seldom see the "Editing XYZ" messages in the log.
> [...] > 3) The articles, meanwhile, have been vetted and generally pounded into > shape by yours truly. The sit in articles/<issue_number>/, where they > are available to our proofreaders and tech editors until the end of the > month.=20
So we should mention in said "Proofreading LG" FAQ that perhaps a day after the submission deadline there's lots of text food available, waiting to be checked out. ;)
> [...] > As you can probably guess by now, all of this is getting to be quite the > sore point; this is all besides the usual monthly stuff I do for LG > [...]
This sounds like a call for volunteers, similar to the one you sent in 2006 (if I remember correctly); so we definitely should adress this before it gets out of hand.
> [...] > Folks, I really do need help here. Changes need to happen if LG is to > keep running - there's no reasonable way that I and Kat can keep > carrying that load. I would really appreciate suggestions, offers of > help, ideas on making the process better, etc. It can't keep going like > this... and I would really prefer to have this separated into reasonable > chunks, each handled by a responsible, reliable person than have it all > come suddenly crashing down one month because I just couldn't handle the > stress and the effort.
Right now I don't have more ideas other than looking for more volunteers. Since we always look for more volunteers this isn't breaking news either; I'll try to come up with more ideas.
Best, René.
--o7gdRJTuwFmWapyH Content-Type: application/pgp-signature Content-Disposition: inline
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIHgf2cjShfQp7h4YRAuPrAJ0UmymYXjsZLJbpMMCgN1dKfQpwAwCfZBb9 u7laAcDM8+ov/sa6WcOrJ0I= =35P4 -----END PGP SIGNATURE-----
--o7gdRJTuwFmWapyH--
--===============0708925247== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline
--===============0708925247==--
Ben Okopnik [ben at linuxgazette.net]
On Sun, May 04, 2008 at 09:01:10PM +0200, René Pfeiffer wrote:
> On May 03, 2008 at 0849 -0400, Ben Okopnik appeared and said: > > > This is also a good point to review the process by which LG happens, and > > ask for input from you folks. As it stands right now, the process is > > fragile, top-heavy, and has a couple of bad choke-points; perhaps > > someone here will have a suggestion or two for improving it. > > The first thing that springs to my mind is some sort of coordination > between the (technical) proof-readers. Quite often I don't know if > someone is working (or is going to work) on an article and if someone > needs help when proof-reading an article. Maybe checking the subversion > log is sufficient, but I think there should be some words describing > what to do and what to look for. There is a workflow description in the > "Proofreading LG" FAQ section, but I seldom see the "Editing XYZ" > messages in the log.
In theory, everybody should be using those - as well as setting and clearing the bits they're working on/are done with. Unfortunately, given the usual minimal level of activity in the repository (except my rushing about at the end of the month), that can be hard to track.
> > [...] > > 3) The articles, meanwhile, have been vetted and generally pounded into > > shape by yours truly. The sit in articles/<issue_number>/, where they > > are available to our proofreaders and tech editors until the end of the > > month. > > So we should mention in said "Proofreading LG" FAQ that perhaps a day > after the submission deadline there's lots of text food available, > waiting to be checked out. ;)
It's a good idea to check for updates at any time, and definitely around the deadline. If I have several articles early in the month, I'll just create the new issue and add them in right then, and people should feel free to jump on them.
> > [...] > > As you can probably guess by now, all of this is getting to be quite the > > sore point; this is all besides the usual monthly stuff I do for LG > > [...] > > This sounds like a call for volunteers, similar to the one you sent in > 2006 (if I remember correctly); so we definitely should adress this > before it gets out of hand.
Yeah. I've always managed to hold it together through thick and thin - but sometimes, with a heavy travel schedule, and clients wanting work done *right now*, and a baby to take care of, and various bits of Real Life that tend to intrude... it can be really, really hard. I really do need help and backup.
> Right now I don't have more ideas other than looking for more > volunteers. Since we always look for more volunteers this isn't breaking > news either; I'll try to come up with more ideas.
Thanks, René. You're one of the folks that keep LG running, and I always appreciate your help and your input.
-- * Ben Okopnik * Editor-in-Chief, Linux Gazette * https://LinuxGazette.NET *
René Pfeiffer [lynx at luchs.at]
--===============1432181227== Content-Disposition: inline Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5UGlQXeG3ziZS81+"
--5UGlQXeG3ziZS81+ Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable
On May 06, 2008 at 1153 -0400, Ben Okopnik appeared and said:
> On Sun, May 04, 2008 at 09:01:10PM +0200, René Pfeiffer wrote: > > [...] > > The first thing that springs to my mind is some sort of coordination > > between the (technical) proof-readers. Quite often I don't know if > > someone is working (or is going to work) on an article and if someone > > needs help when proof-reading an article. Maybe checking the subversion > > log is sufficient, but I think there should be some words describing > > what to do and what to look for. There is a workflow description in the > > "Proofreading LG" FAQ section, but I seldom see the "Editing XYZ" > > messages in the log. >=20 > In theory, everybody should be using those - as well as setting and > clearing the bits they're working on/are done with. Unfortunately, given > the usual minimal level of activity in the repository (except my rushing > about at the end of the month), that can be hard to track.
I confess, I don't use the subversion very often. This is mainly because it's a pull log instead of a push log. Exporting the logs to a kind of editors mailing list would be a way to push the information. It's just a thought since in times of stress I cling to my email inbox and sort everything there.
Best, René.
--5UGlQXeG3ziZS81+ Content-Type: application/pgp-signature Content-Disposition: inline
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIIg5zcjShfQp7h4YRAkRMAJ4lZXL4jQHPGKWjVXnzB4fFgP/6EgCghvQu 1ReWnkeCgFT10yUnu3m4sYg= =rnaC -----END PGP SIGNATURE-----
--5UGlQXeG3ziZS81+--
--===============1432181227== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline
--===============1432181227==--
Ben Okopnik [ben at linuxgazette.net]
On Wed, May 07, 2008 at 10:17:55PM +0200, René Pfeiffer wrote:
> On May 06, 2008 at 1153 -0400, Ben Okopnik appeared and said: > > On Sun, May 04, 2008 at 09:01:10PM +0200, René Pfeiffer wrote: > > > [...] > > > The first thing that springs to my mind is some sort of coordination > > > between the (technical) proof-readers. Quite often I don't know if > > > someone is working (or is going to work) on an article and if someone > > > needs help when proof-reading an article. Maybe checking the subversion > > > log is sufficient, but I think there should be some words describing > > > what to do and what to look for. There is a workflow description in the > > > "Proofreading LG" FAQ section, but I seldom see the "Editing XYZ" > > > messages in the log. > > > > In theory, everybody should be using those - as well as setting and > > clearing the bits they're working on/are done with. Unfortunately, given > > the usual minimal level of activity in the repository (except my rushing > > about at the end of the month), that can be hard to track. > > I confess, I don't use the subversion very often. This is mainly because > it's a pull log instead of a push log. Exporting the logs to a kind of > editors mailing list would be a way to push the information. It's just a > thought since in times of stress I cling to my email inbox and sort > everything there.
I have the same general approach at those times. I could set up a cron job to run once a day and email the logs to the 'lg-volunteers' list (hosted on Rick's server, same signup procedure as TAG, etc.) - I suppose that would serve as a reminder to anyone who's signed up that other people are working at it. I could also post reminder messages there ("New article added", "Article submission closed for this month", etc.)
Hmm, this is sounding like a reasonable idea. Any reasons against?
-- * Ben Okopnik * Editor-in-Chief, Linux Gazette * https://LinuxGazette.NET *
Ben Okopnik [ben at linuxgazette.net]
> Ben Okopnik appeared and said:
>
> > On Wed, May 07, 2008 at 10:17:55PM +0200, René Pfeiffer wrote:
> >
> > > I confess, I don't use the subversion very often. This is mainly because
> > > it's a pull log instead of a push log. Exporting the logs to a kind of
> > > editors mailing list would be a way to push the information. It's just a
> > > thought since in times of stress I cling to my email inbox and sort
> > > everything there.
>
> [...] I could set up a cron
> job to run once a day and email the logs to the 'lg-volunteers' list
> (hosted on Rick's server, same signup procedure as TAG, etc.) - I
> suppose that would serve as a reminder to anyone who's signed up that
> other people are working at it. I could also post reminder messages
> there ("New article added", "Article submission closed for this month",
> etc.)
I set this up earlier today; as long as my laptop is on around 5pm, the notice will go out daily. Anyone doing proofing or editing for LG should sign on at https://lists.linuxgazette.net/mailman/listinfo/lg-volunteers/ - this way, you'll get to keep up on what's going on.
-- * Ben Okopnik * Editor-in-Chief, Linux Gazette * https://LinuxGazette.NET *
Deividson Okopnik [deivid.okop at gmail.com]
--===============1365584054== Content-Type: multipart/alternative; boundary="----=_Part_1317_13685732.1209997666380"
------=_Part_1317_13685732.1209997666380 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
> > 2) PR gets routed to my 'bytes' mailbox. Ever since we lost Sam Bisbee > as NewsBytes editor, that load has gone floating... which means that > either I do it (very rarely), Kat does it (usually), or it doesn't get > done (all too common.) >
I do can check the newsbytes material, maybe do some reviewing, but proof-reading is a bit too much for my english i think.
------=_Part_1317_13685732.1209997666380 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">2) PR gets routed to my 'bytes' mailbox. Ever since we lost Sam Bisbee<br>
as NewsBytes editor, that load has gone floating... which means that<br> either I do it (very rarely), Kat does it (usually), or it doesn't get<br> done (all too common.)<br></blockquote></div><br>I do can check the newsbytes material, maybe do some reviewing, but proof-reading is a bit too much for my english i think.<br><br>
------=_Part_1317_13685732.1209997666380--
--===============1365584054== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline
--===============1365584054==--
Ben Okopnik [ben at linuxgazette.net]
On Mon, May 05, 2008 at 11:27:46AM -0300, Deividson Okopnik wrote:
> > > 2) PR gets routed to my 'bytes' mailbox. Ever since we lost Sam Bisbee > as NewsBytes editor, that load has gone floating... which means that > either I do it (very rarely), Kat does it (usually), or it doesn't get > done (all too common.) > > I do can check the newsbytes material, maybe do some reviewing, but > proof-reading is a bit too much for my english i think.
That's not a problem at all, Deividson; if you can condense it down to
interesting material instead of PR-speak, it would go into the
repository and be proofed just like every other article. I'd be very
happy if you'd take that on - although LG is going to look like it's
the Okopnik family magazine, given how many of us are participating.
I've said this several times before, but I find an article from a non-native English speaker who works hard at his grammar and spelling far preferable to sloppy and careless work from someone who is supposed to be at home with the language. Editing the former is relatively easy - the errors are consistent and are far more likely to be handled as soon as they're pointed out. The latter can be an absolute nightmare.
-- * Ben Okopnik * Editor-in-Chief, Linux Gazette * https://LinuxGazette.NET *
Deividson Okopnik [deivid.okop at gmail.com]
--===============1264660138== Content-Type: multipart/alternative; boundary="----=_Part_407_9501782.1210253744225"
------=_Part_407_9501782.1210253744225 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Ok, you can count on me for that then - I'm finishing my the 3/3 of my databases article then I will email you for details (should be ready today) - and yeah :P Okopnik's Magazine :P What can we do tho - its in our veins :P
That's not a problem at all, Deividson; if you can condense it down to
> interesting material instead of PR-speak, it would go into the > repository and be proofed just like every other article. I'd be very > happy if you'd take that on - although LG is going to look like it's > the Okopnik family magazine, given how many of us are participating.
------=_Part_407_9501782.1210253744225 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Ok, you can count on me for that then - I'm finishing my the 3/3 of my databases article then I will email you for details (should be ready today) - and yeah :P Okopnik's Magazine :P What can we do tho - its in our veins :P<br> <br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">That's not a problem at all, Deividson; if you can condense it down to<br>
interesting material instead of PR-speak, it would go into the<br>
repository and be proofed just like every other article. I'd be very<br>
happy if you'd take that on - although LG is going to look like it's<br>
the Okopnik family magazine, given how many of us are participating. <br>
<br>
I've said this several times before, but I find an article from a<br>
non-native English speaker who works hard at his grammar and spelling<br>
far preferable to sloppy and careless work from someone who is supposed<br>
to be at home with the language. Editing the former is relatively easy -<br>
the errors are consistent and are far more likely to be handled as soon<br>
as they're pointed out. The latter can be an absolute nightmare.<br>
<div><div></div><div class="Wj3C7c"><br>
<br>
--<br>
* Ben Okopnik * Editor-in-Chief, Linux Gazette * <a href="https://LinuxGazette.NET" target="_blank">https://LinuxGazette.NET</a> *<br>
</div></div></blockquote></div><br>
------=_Part_407_9501782.1210253744225--
--===============1264660138== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline
--===============1264660138==--
Ben Okopnik [ben at linuxgazette.net]
On Thu, May 08, 2008 at 10:35:44AM -0300, Deividson Okopnik wrote:
> Ok, you can count on me for that then - I'm finishing my the 3/3 of my > databases article then I will email you for details (should be ready > today) - and yeah :P Okopnik's Magazine :P What can we do tho - its in our > veins :P
OK - I've got you listed as being in charge of NewsBytes in
'https://linuxgazette.net/jobs.html'. And even if it's not in our veins,
the next generation (a random sample of which is even now climbing up
the companionway steps like a little monkey...) can certainly lay that
claim.
-- * Ben Okopnik * Editor-in-Chief, Linux Gazette * https://LinuxGazette.NET *