RE: [gentoo-dev] {Guide,Project,Foo}XML too confusing for many devs?
-Original Message-
From: Alec Warner [mailto:[EMAIL PROTECTED]
Sent: Monday, March 26, 2007 10:06 AM
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] {Guide,Project,Foo}XML too confusing for many devs?
my basic question is do you as a
developer find writing web pages to be confusing or difficult? Is there
not a good tutorial for learning our webpage XML syntax? Do you find that
you bump up against restrictions in the DTD or other problems that prevent
you from expressing yourself properly? Do you have any idea how to
actually go about extending GuideXML (or the other XML's we provide) Have
you ever tried? Could we improve training with regards to any of this?
Thanks,
-Alec
--
gentoo-dev@gentoo.org mailing list
I have never had a problem writing for GuideXML, but I haven't done a lot of
it. I found the online guide to be sufficient for getting things working.
I've never had a problem with the DTD or any other obstacle for expressing
content in XML. As for extending GuideXML, I think we should discuss the
"business driver" behind that idea.
Do we have usage stats on the web sites? I use the Handbook, package.g.o,
and the forums the most. Would extensions to GuideXML help improve those
areas? Should we encourage more content to go into the wiki, expecially
content that is likely to change over a short period of time?
Mike
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.18/733 - Release Date: 3/25/2007
11:07 AM
--
gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: Distrowatch
Christian Faulhammer wrote: "Kevin F. Quinn" <[EMAIL PROTECTED]>: So please, friends, just ignore it, nothing positive will come of it. Unfortunately it made its way onto big news site and lowers the view on Gentoo even more. From many comments I read we are a dying distro. V-Li Gentoo will never die; it will just get forked and carry on. ;-) Mike -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Introducing the Proctors - Draft Code of Conduct for Gentoo
Christel Dahlskjaer wrote: Hiya all, As some of you are already aware, I was at the last Council meeting given a Task. This Task was to draft a proposed Code of Conduct for Gentoo, and a scheme for enforcing it. The current version of this proposal can be found at http://dev.gentoo.org/~christel/coc.xml comments and suggestions both on- and off-list are appreciated. Any input will have to be received by Thursday, 15 March, 1200GMT in order to be useful; the Council will be voting on it later that day at 2100UTC. I would like to thank a few people for their help in getting it to this stage: the council for review, spb for translating Christelsk into English (with the help of the OED), nightmorph for making it look prettier than plain text in vim (without a fancy colourscheme), and marienz for being sane and reading it over. I'd also like to thank our Infrastructure team for working with us and answering questions regarding the mechanics of enforcing such a code. Christelx Does "flaming and trolling" need some kind of definition? Or is it generally understood? Does the role of the "proctor" need explaining? How is it defined? Where does the authority come from? etc? Mike -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: Introducing Daniel Robbins (drobbins)
Michael Sterrett -Mr. Bones.- wrote: On Tue, 27 Feb 2007, Petteri Räty wrote: Please give him the usual warm welcome. WB drobbins. Michael Sterrett -Mr. Bones.- [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 268.18.4/705 - Release Date: 2/27/2007 3:24 PM Oh great! Another newbie! ;-) -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] bugstest.gentoo.org - public beta for the new Gentoo BugZilla - please test!
Robin H. Johnson wrote: On Thu, Nov 16, 2006 at 01:42:40AM -0800, Robin H. Johnson wrote: This testing period will last for 2-4 weeks, depending on how stable the setup of bugstest turns out to be. Then we can hopefully roll out the new Bugzilla for production use in time for Christmas! Hi Everybody, I'd like to ask for one more renewed round of testing. All bugs filed have been dealt with, as well as revisiting the regressions that got filed the previous time Bugzilla got upgraded. A few of them are data-related changes that need revisiting when I re-import later on, but other than that, I believe we are almost set. Could everybody please give it one last push of testing before Christmas? If all goes well, I'm hoping to be able to migrate on Boxing Day, while everybody is off playing with their new toys. If everyone's Login ID is their email address, may I suggest changing 'Login:' to 'E-mail:'? I usually try 2 or 3 wrong ID's before recalling that my ID is my email address. Mike -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: Last rites for XMMS
On Monday 23 October 2006 10:26, Duncan wrote: > "Diego 'Flameeyes' =?utf-8?q?Petten=C3=B2?=" <[EMAIL PROTECTED]> posted > [EMAIL PROTECTED], excerpted below, on > > Mon, 23 Oct 2006 16:16:50 +0200: > > Probably not covered everything, I left Mr_Bones_ and jakub to run a > > check for me afterward, unfortunately identifying every and all the > > packages on the first run was pretty impossible -considering also there > > are packages with unstated dependencies, like two XFCE4 packages- I'll > > mask and notify about anything else that might come up as soona s they > > can give me the data. > > I don't suppose it's possible to let amarok continue to use all those xmms > visualizations, is it? It'd be nice... > > -- > Duncan - List replies preferred. No HTML msgs. > "Every nonfree program has a lord, a master -- > and if you use the program, he is your master." Richard Stallman Removing xmms breaks amarok, at least for me. I had to recompile xine-lib without the xmms use flag to get amarok to play music again. Glide -- Mike Bonar [EMAIL PROTECTED] -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Democracy: No silver bullet
Daniel Ostrow wrote: On Thu, 2006-08-24 at 17:26 -0400, Michael Cummings wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stuart Herbert wrote: > We've had a global vision for where Gentoo is going from before I joined - Gentoo is here to create a source-based distribution where each package is as close to what $UPSTREAM intended it to be as possible. We're not trying to take $UPSTREAM packages and innovate with them - we're here to do a first class job of packaging them up. Um, that's a mission statement, not a vision. A vision is a series of goals for a project, like "my vision is that we will produce knoppix like catalyst+template releases for myth, firewalls-on-a-disk, etc by the 2007.0 release." a mission statement is "we'll make the best from source distro ever." i.e, mission statements never change because they are just an overarching definition of a project, not the vision or goal it might be working towards at the moment. somebody shoot me, my job in middle management is finally getting to me. Exactly... Above and beyond that is the next step...once you have a vision...ok so what do we need to do to further the vision, do we need more devs doing X, do we need hardware Y, do we need an Ice Cream machine... Leadership is way more then just shouting a vision out to the world and expecting people to hop to it...its about helping facilitate that visions completion, keeping yourself involved so those working on it feel involved themselves...leadership is just as much a community building exercise as any of the rest of it. --Dan Vision says who we are and why we are here. It speaks to our shared values and what makes us a community. Once you have a vision, you need Strategy. A Strategy describes the big plays you are going to make to achieve your vision. Examples might be, "We want to be the biggest distro, or We want to be the most user friendly distro, or We want to capture the enterprise market for Linux, etc. Once you have your Strategy, you need a plan and the plan must match the Strategy. Once you have a plan, you execute. That's what leadership does. My 2 cents. Mike -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] KDE and Ruby herd call for help
Caleb Tennis wrote: Hi all, Right now both the KDE and Ruby herds (which, informally, I am the *lead* on both) are hurting for people. I don't have the time to work on general Thanks, Caleb I was looking for an excuse to learn Ruby. I'll help all I can. Mike -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] User support system
Enrico Weigelt wrote: * Jakub Moc <[EMAIL PROTECTED]> schrieb: That somehow looks like the guided file-a-new-bug form we had some time ago. It's still there, just not linked from homepage (and needs a few touches here and there) http://bugs.gentoo.org/enter_bug.cgi?format=guided http://bugs.gentoo.org/enter_bug.cgi?product=Gentoo%20Linux&format=guided hmm, looks like an good start, but for me doesn't go far enough. The user still has to type in too much manually. I'd suggest an tool, where the user *first* gives the package name, and the tool gathers any necessary information (version, useflags, make config, ...). Dependend on the package, this tool may ask specific questions or gather specific information (ie. on web applications, we'd be interested in webserver, browser, certain network configs, ...). The usage should be as simple as possible for normal users, so they have great interest in using it. For example, asking the user to look for similar bug is probably good for devs/maintainers, but uncomfortable for plain users. But we shouldn't forget, that all the plain users are (in their mass) also an important contributor. (they find and report bugs, which probably never would be found by the maintainers). cu I think this is an excellent idea. I wrote an automated trouble ticketing system years ago for the mainframe and it's an excellent way to get quality information into the system. The one drawback was that we ended up having a lot more bugs entered into the system. Once you have the shell it wouldn't be hard to hook it into batch processes and have emerge automatically send bug reports when it fails. When this happens you end up with multiple, identical bug reports because users tend to re-create the error a few times before they head to the forums or bugzilla for help. On the plus side it would be much easier to find duplicate bugs since the titles would be uniform. Glide -- gentoo-dev@gentoo.org mailing list
