Re: [gentoo-dev] Re: Gentoo Hangouts
On 06/24/2013 05:54 AM, Michael Palimaka wrote: On 24/06/2013 07:30, Pavlos Ratis wrote: That's why I'd like to propose Gentoo Hangouts. Gentoo Hangouts will be Google+ video Hangouts(video calls) held by teams or developers independent of a team. The main goal is to have the teams introduce themselves and discuss about different issues in their Gentoo-related projects. Thanks for taking the time and initiative to work on something new, I am sure it will prove interesting. It is the response that confuses me - I don't understand why everyone is rushing to shut it down before it even begins. For those that are not interested in the idea of a video hangout, just don't use it and move on - simple. I'm a user (and would-be dev) and don't like the idea of relying on anything related to Google or another outside entity for devs and/or users to communicate. The software is also non-free and closed source. It's true that people can just move on, but that strikes me as an attempt to ward off criticism and not work at solving the perceived problem: how do we get richer communication between Gentoo devs/users? Mumble exists for voice chat... certainly there's a FOSS video chat option somewhere? Diego's points wrt time management and multitasking are also salient.
Re: [gentoo-dev] Gentoo Hangouts
- Original Message - From: Michael Palimaka kensing...@gentoo.org On 26/06/2013 01:09, Egg Plant wrote: According to Pavlos Ratis proposal, it will be another channel of communication. I am not protesting to setup an unofficial channel there. I am fearing that it will gradually become an avenue for talent show, similar to other binary distros. That is why I am against to make it official channel. What makes it official or not? Does it make any practical difference? Yes. I think it will make our life better if any developer discuss or at least notify in the proper mailing list or IRC channel (as of now more accessible by majority of users developers) before committing any horrible idea. Again I would remind you, I am not against any change that will improve our life. E.g., one can install Gentoo from binary packages, one can run Gentoo with Systemd instead of OpenRC, there are lots of other possibilities with Gentoo. But a newcommer is directed to read a handbook which will guide him/her using source packages OpenRC. This is what I call official recommendation. Video is more attractive than Text or still photo. Several developers, who can afford the resources, will gradually shift their communication to that channel. It's somewhat cyclic dependency or chain reaction. It will just increase our workload (of gentoo development awareness). More fragmentation distraction as well as other technical problems mentioned by others me. Perhaps some will. Does that matter? There is already plenty of fragmentation - we have over 70 IRC channels and 60 mailing lists, not to mention blogs, wikis, overlays and countless other methods of development and communication. Yes. We can not control or change this universe, only we can try to make our life beter. As Rich said, everyone has their favourite medium and every medium is not suitable for every person. I am not against it. Read my mails one more time. I don't want any unnecessary attention from some Computer Science students (unable to get a job at Microsoft or Apple! sorry, I don't like to be that hard) to show their talent and gift me with another unstable, unreliable, expectation only, useless distro. I am not sure what this has to do with hangouts. I am keeping my mouth shut here. More talk will lead to discussion on religion or political or management level (i.e., /dev/null). Change is good, only if it improves our life. For colourfull life there are other things one can play with. The resourcefull developers/users can meet each other at Gentoo Miniconf and similar other gatherings in real world. That will make us more human. Again, Rich was spot on here. A quick search of reveals that it would have taken me approximately 30-40 hours in transit and $4,000-$6,000 in flights alone to have attended the Miniconf. I am not saying these gatherings are good replacement for Video conferencing. [P.S.: request you to read my first mail once again, I am not totally against this type of activity. Everything has it's place time.] Best regards, Michael I am replying only to you doesn't mean I am attacking you personally. Just I am explaining my point of view about the proposal. Thanks for your kind attention. I am not going to indulge on this topic any more. === I'm yet a learner, warn me if I'm doing any wrong... [|:-)
Re: [gentoo-dev] [1/3] Automatic *XML-Wiki wiki.gentoo.org
On 16.06.2013 02:28, Robin H. Johnson wrote:
From the infra perspective, I would like to add that I support this
move, I just have a few concerns on the conversion, one of which is
dealt with here.
I've committed my draft XSL to the gentoo/xml/htdocs/xsl location, named
guidexml2wiki.xsl. It still requires some updates that I'll work on soon
(such as handling internal links) as I'll be using it more and more for the
guides on gentoo.org/doc/en to move to the wiki as well.
ProjectXML generates towards GuideXML, so should be usable chained.
It would be nice to move the foundation/ content to the Wiki as well I
think.
Sure. It doesn't count as a project I guess, so you would move into
Foundation:.* ?
PS An ebuild for a single stylesheet seems like overkill to me, but i've
been proven incorrect in the past...
I think it would help a lot of the devs that are put off by the concept
of XML/XSLT. Just give them a little wrapper script to generate wiki
output.
One of my large concerns was how to handle some of the tag conversion.
We have a lot of custom tags, plus some interesting behavior in some
tags.
Sven's XSL makes a very good start, but somebody needs to put in some
TLC for the following tags in conversion, and/or can we have it emit
something useful so we know when we hit a tag that's missing in the
XSLT.
Here's my list of tags found in proj/ that aren't in the XSLT so far:
(the / is just because I collapsed the tag of any attributes, there
probably
needs to be an audit of how the XSL handles attributes).
179 body/
ignore, needed by guidexml
145 i/
i.*?/i - ''\1''
74 mail/ (optional attribute link)
This functionality is replaced by the {{Mail}} template.
Usage:
* {{Mail|a3li}} - a href=mailto:a...@gentoo.org;Alex Legler/a
* {{Mail|a3li|foo}} - a href=mailto@a...@gentoo.orgfoo/a
* {{Mail|a3li@g.o}} - a href=mailto:a3li@g.o;a3li@g.o/a
* {{Mail|a3li@g.o|foo}} - a href=mailto:a3li@g.o;foo/a
27 dev/
Project members will have to be recreated using the form.
25 br/
keep br /
18 license/
Discard, everything is the same CC license, the old 2.x version allows
upgrade to the 3.0 we use.
15 extrachapter/ (optional attribute position)
Discard, GuideXML specific.
9 resource/ (attribute resource)
These resource things could just become a list:
* foo
* bar
* baz
7 project/
7 name/
7 longname/
7 longdescription/
7 description/
6 subproject/ (attribute ref)
Dump information, contents need to be recreated using the form as well.
Longdescription should 'just' be the first paragraph of the wiki page.
4 goals/
2 summary/
2 requirements/
Does anyone actually use the goals feature? imo, discard.
2 recruitment/
2 keyword/
2 job/
2 details/
2 contact/
Discard. I have moved staffing needs already.
1 var/
1 subtitle/
1 stmt/
1 ident/
1 const/
We have proper syntax hilighting in the wiki. Discard?
1 extraproject/ (attribute name)
Shouldn't these be proper projects?
--
Alex Legler a...@gentoo.org
Gentoo Security/Ruby/Infrastructure
signature.asc
Description: OpenPGP digital signature
[gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in x11-libs/cairo: ChangeLog cairo-9999.ebuild
On 26/06/13 16:57, Luca Barbato (lu_zero) wrote:
lu_zero 13/06/26 13:57:03
Modified: ChangeLog cairo-.ebuild
Log:
Update live ebuild
(Portage version: 2.1.12.9/cvs/Linux x86_64, unsigned Manifest commit)
Revision ChangesPath
1.337x11-libs/cairo/ChangeLog
file :
http://sources.gentoo.org/viewvc.cgi/gentoo-x86/x11-libs/cairo/ChangeLog?rev=1.337view=markup
plain:
http://sources.gentoo.org/viewvc.cgi/gentoo-x86/x11-libs/cairo/ChangeLog?rev=1.337content-type=text/plain
diff :
http://sources.gentoo.org/viewvc.cgi/gentoo-x86/x11-libs/cairo/ChangeLog?r1=1.336r2=1.337
Index: ChangeLog
===
RCS file: /var/cvsroot/gentoo-x86/x11-libs/cairo/ChangeLog,v
retrieving revision 1.336
retrieving revision 1.337
diff -u -r1.336 -r1.337
--- ChangeLog 5 Jun 2013 00:43:49 - 1.336
+++ ChangeLog 26 Jun 2013 13:57:03 - 1.337
@@ -1,6 +1,9 @@
# ChangeLog for x11-libs/cairo
# Copyright 1999-2013 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/x11-libs/cairo/ChangeLog,v 1.336 2013/06/05
00:43:49 vapier Exp $
+# $Header: /var/cvsroot/gentoo-x86/x11-libs/cairo/ChangeLog,v 1.337 2013/06/26
13:57:03 lu_zero Exp $
+
+ 26 Jun 2013; Luca Barbato lu_z...@gentoo.org cairo-.ebuild:
+ Update live ebuild
05 Jun 2013; Mike Frysinger vap...@gentoo.org metadata.xml:
Add upstream CPE tag (security info) from ChromiumOS.
1.31 x11-libs/cairo/cairo-.ebuild
file :
http://sources.gentoo.org/viewvc.cgi/gentoo-x86/x11-libs/cairo/cairo-.ebuild?rev=1.31view=markup
plain:
http://sources.gentoo.org/viewvc.cgi/gentoo-x86/x11-libs/cairo/cairo-.ebuild?rev=1.31content-type=text/plain
diff :
http://sources.gentoo.org/viewvc.cgi/gentoo-x86/x11-libs/cairo/cairo-.ebuild?r1=1.30r2=1.31
Index: cairo-.ebuild
===
RCS file: /var/cvsroot/gentoo-x86/x11-libs/cairo/cairo-.ebuild,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- cairo-.ebuild 9 Apr 2013 22:05:38 - 1.30
+++ cairo-.ebuild 26 Jun 2013 13:57:03 - 1.31
@@ -1,6 +1,6 @@
# Copyright 1999-2013 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/x11-libs/cairo/cairo-.ebuild,v 1.30
2013/04/09 22:05:38 ssuominen Exp $
+# $Header: /var/cvsroot/gentoo-x86/x11-libs/cairo/cairo-.ebuild,v 1.31
2013/06/26 13:57:03 lu_zero Exp $
EAPI=5
@@ -71,9 +71,6 @@
src_prepare() {
- epatch ${FILESDIR}/${PN}-1.8.8-interix.patch
- use legacy-drivers epatch
${FILESDIR}/${PN}-1.10.0-buggy_gradients.patch
You forgot legacy-drivers to IUSE.
$ grep legacy-drivers cairo-.ebuild
IUSE=X aqua debug directfb doc drm gallium +glib legacy-drivers opengl
openvg qt4 static-libs +svg xcb
$
[gentoo-dev] About m68k arch status in perl packages
Hi all. We have very long delay with m68k arch in many stabilization bugs, especially in perl-related. I think this is not ok. The only one mk68k developer is vapier, so i want say: if we'll have no progress in stabilization for m68k for a two weeks, i'll close all bugs, that have m68k as last arch (i have no hardware to test it) and drop related keyword in package to unstable. -- Best reagrds, Mikle Kolyada. Gentoo Linux Developer
Re: [gentoo-dev] About m68k arch status in perl packages
On Wed, Jun 26, 2013 at 8:58 PM, Mikle Kolyada zlog...@gentoo.org wrote: Hi all. We have very long delay with m68k arch in many stabilization bugs, especially in perl-related. I think this is not ok. The only one mk68k developer is vapier, so i want say: if we'll have no progress in stabilization for m68k for a two weeks, i'll close all bugs, that have m68k as last arch (i have no hardware to test it) and drop related keyword in package to unstable. IIRC we've had discussions in the past about making m68k permanently ~arch-only, like mips. Cheers, Dirkjan
