Hey Gang; Ya guys know that when Judd was handling these kinds of changes (..Ya know the ones that cause problems), he *DID* send emails about upcoming changes that users should know about before doing upgrades. He usually did this very well.
Emails are nice because they do not require much effort for anyone including the devs that have to answer reports from those that could not find the blog OR have trouble finding specific info in them. (Clutter is often a problem with wikis and blogs.) In any event pushing specific announcements to users through a announcement email list is a GREAT idea. Very best regards; Bob Finch > It's incumbant upon users of the testing repositories to be informed. > You can only feed so much. > > It's good to have the front page provide some information, but not, in > my opinion, details of the work in testing. > > I think it would work to give a more obvious link to the dev blog. It's > just sitting over on the side. An Arch user that is unfamiliar with the > process might miss it. > > I'd suggest some extra text about "Testing Info" and keep the link to > the blog. This doesn't require devs to change their behavior, just > continue to use the blog. > > My 2c. > ============================================================ > From: "S. Barret Dolph" <[EMAIL PROTECTED]> > Date: 2005/12/06 Tue AM 10:50:22 EST > To: General Discusson about Arch Linux <[email protected]> > Subject: Re: [arch] patchs > > On Tuesday 06 December 2005 16:33, Jason Chu wrote: >> On Tue, Dec 06, 2005 at 03:30:05PM -0000, Rosenstrauch, David wrote: >> > > -----Original Message----- >> > > From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] Behalf Of Jason Chu >> > > Sent: Tuesday, December 06, 2005 11:11 AM >> > > To: [EMAIL PROTECTED]; General Discusson about Arch Linux >> Subject: Re: [arch] patchs >> > >> > On Tue, Dec 06, 2005 at 11:22:08AM +0100, Essien Ita Essien wrote: >> > >> > How exactly should we notify all Archlinux users? Not everyone uses >> the mailing list or forum. These days there's a dev blog. For the >> most part, things that go into testing are talked about in the dev >> blog first. >> > Maybe people should start reading that... >> > >> > http://archlinux.org/blog/ >> > >> > --- >> > >> > Just my $0.02, but perhaps the devs should designate an "official" >> channel for notifying people. >> > >> > Personally, I'd think that a new, non-discussion "arch announce" >> mailing list might work nicely. Use that to publish dev >> announcements (and ONLY dev announcements). And that takes away the >> "not everyone uses the mailing list" excuse. Anyone who's >> interested can get the all the updates sent to them in a timely way >> - without having all the discussion emails that come along with it >> on this list. >> > >> > Thoughts, anyone? >> > >> > HTH, >> > >> > DR >> >> What about the front page? That's what it's supposed to be used for. >> All you need is an rss reader and you can get all the announcements >> there (assuming we devs actually use it, which is something we'd have >> to get more practice with). >> >> Jason > > As a user I prefer the front page idea. > > Just my opinion but I think it the easiest place. > > Cordially, > Barret > > _______________________________________________ > arch mailing list > [email protected] > http://www.archlinux.org/mailman/listinfo/arch > ============================================================ > > > > _______________________________________________ > arch mailing list > [email protected] > http://www.archlinux.org/mailman/listinfo/arch _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
