#x27;m
a tree hugger ;). I also have done some jewelery work with chain mail links.
Basically I'm a jack of all trades."
Welcome to the team Joshua :)
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
ay
> Dec. 26, 2005 this will be pushed into the tree.
>
Don't push new eclasses this fast please and especially not during
christmas when many people are taking a few days off.
Why is it so important that it can't wait a few days so other devs/users
gets a chance to look at it
.
Please welcome Jörg to the team.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
On Thu, Feb 09, 2006 at 07:08:45AM -0600, Harry Putnam wrote:
> From: Harry Putnam <[EMAIL PROTECTED]>
> Subject: rsnapshot and cp bug
> Newsgroups: gmane.linux.gentoo.devel
> Date: Mon, 06 Feb 2006 08:54:02 -0600
> Message-ID: <[EMAIL PROTECTED]>
>
> [This message was posted some time a
On Thu, Feb 09, 2006 at 07:23:27AM -0600, Harry Putnam wrote:
> > Please file a bug on https://bugs.gentoo.org so I can fix this. No, I
> > don't accept bug reports on gentoo-dev ML :)
>
> Will do but I wanted this to be posted because anyone running
> rsnapshot might lose some backups. What hap
On Thu, Feb 09, 2006 at 07:44:06AM -0600, Harry Putnam wrote:
> Bryan "=?utf8?Q?=C3=98stergaard?=" <[EMAIL PROTECTED]> writes:
>
> > Please file a bug on https://bugs.gentoo.org so I can fix this. No, I
> > don't accept bug reports on gentoo-dev ML :)
>
> I'd do this for sure but the bugzilla set
default configuration to protect against bugs in poorly written
applications.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
home in the developer lounge bar with those
qualifications :)
Please give Josh a hearty welcome to the team.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
would probably come naturally from irc
discussions but we're no longer a small, tightly nit group of
developers. As part of "growing up" we (naturally) need more
communication between developers before running off with the newest,
crazy idea.
Gentoo is no longer a playground - we have some 10k+ packages in the
tree and 100k+ users at least afaik. We *need* to take our
responsibility seriously and not play hazard with all those
users/system.
So.. What can we do to improve things? There's lots of things that can
be improved in my opinion. Developer relations is currently pushing out
a new proposed conflict resolution policy for public discussion on the
gentoo-devrel ML. It's been out for a couple days already and I have yet
to see a single comment on it.
Likewise, we're trying to come up with a proposal for improving
recruitment / quizzes.
I'd love to see people (both users and developers) get involved in these
discussions instead of posting general rants on the current state of
gentoo. Working on small corners of gentoo can make a big difference (in
a short amount of time) and I'm sure I'm not the only one who'd love to
see that :)
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
he tree that handles
> branches and merging sanely, which should be doable with Subversion if
> the issues it had last time this was tested have been or can be
> resolved.
> --
This solution also needs experienced developers with lots of free time
on their hands.. And try as I might, I can't think of many people that
fits that description.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
On Fri, Apr 28, 2006 at 05:01:20PM -0500, Daniel Goller wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Thomas Cort wrote:
> > On Fri, 28 Apr 2006 21:42:57 +0200
> > Bryan Østergaard <[EMAIL PROTECTED]> wrote:
> >> So.. What can we do to impr
solution shouldn't exist at all?
> > If the former, that's unrealistic. If the latter, why not?
> >
>
> we shouldn't have an underappreciated overworked entity (not intending
> to upset the members of said entity, i know there are people behind the
> alias) that makes the decisions we ask them to make to hear that they
> did it wrong again (i am sure it gets tiring to hear us say that over
> and over), instead the developers bring up the issue, if someone seconds
> that, people vote and the issue gets resolved, one way or another
> now if the technical issue is brought up by a project lead and does not
> affect gentoo as a whole, then that project should vote, not all of us
> who are not affected, if we like it or not
I strongly disagree with voting, be it by all developers or just the
affected project(s). In the first case the only thing we'll gain is
(relatively) quick, random decisions with no strong base in the
complaint(s). In the second case, we'll have quick decisions made by
obviously biased people - in effect a popularity contest set up to be
unfair in advance.
Now, as developer relations lead I'm obviously biased but I were of the
same opinion even before joining devrel. After devrel have handled a
few conflicts I think the current conflict resolution policy leaves a
lot to be desired. But moving conflict resolution from devrel to more
general voting is the wrong direction.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
art in
the discussion).
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
;> someone to my project overlay, or grant them voice or ops in my
> >> project's IRC channel. I don't need a GLEP to get them subscribed to my
> >> mailing list and I don't need a GLEP to add them to (most) project
> >> aliases. Why does this require one?
> > Because this is about the entire Gentoo project and affects us all in a
> > very direct way as opposed to random projects.
>
> I tried to make it clear above that it doesn't. I hope I succeeded.
I still very much believe this affects all of gentoo, especially seen in
light of the problems micromanaging bugzie privs would imply.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
roprosed glep. Adding a bit of structure to it seemed like a good
thing and I'd argue that the small bit of structure have helped keep
the discussion on track.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
e *always* have an option to deny people those privs - since
> those are privs, not rights. They are not entitled to them, granting
> them those privs is solely up to the discretion of Gentoo devs
> responsible for this.
>
Well, if people don't want to discuss issues such as this I
articipated in the recent Linux
World Conference in San Francisco.
Welcome to the team William and good luck with all that evil java stuff
:)
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
dy besides
Stefan and Recruiters / Developer Relations I'm going to deny the
contributor access idea. Recruiters and Developer Relations feels that
this is a bad idea, especially seeing how hard it has been to reach any
kind of resolution regarding who should get access and how we should
so
this mail.
Regards,
Bryan Østergaard
20:07 <@kloeri> k, everybody seen the agenda? otherwise I've linked to it in
/topic
20:08 <@fmccor> got it
20:08 <@kloeri> I've called the meeting mostly because of avenj stepping down
as devrel lead and the reasons behind
t; I am giving my own spin on things, and I do NOT speak here for devrel as
> a whole.
>
I'm speaking on behalf of devrel because I can :)
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
vejournal.com for the glory details or
wait for it to show up on http://planet.gentoo.org.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
nk proxy maintaining in those
cases are a much better idea.
>
> That leaves me with the conclution that its best to just continue to run
> my own local portage tree and submit bugreports once in a while and hope
> for the best, just like I have always been doing.
See above.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
he notice, I hope to see you around from time to time. And
good luck with graduation and post-graduation.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
"~amd64 ~ia64"
> or none) on every package that don't use 3dnow/sse instructions?
>
> I only ask this because I think the arch teams' could be better spent
> than double-checking the packages.
>
No, they are wildly different architectures.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
of playing
> a dead horse? Really, stop this nonsense.
Yes please stop your friggin nonsense when you have absolutely no idea
wtf you're talking about. Arch teams are doing everything they can to
keep up with bugs but have to take care of things according to how
important they are to the te
ll..). Adding to his
dubious background is the facts that he's a teenager and works for User
Relations and the Alpha and Mips teams :)
Please give Alex a warm welcome.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
were no need to change mailinglist behaviour
regarding reply-to-list. Bryan Østergaard (kloeri) mentioned that a
replytolist plugin for thunderbird-2 had just been committed the day
before. Bryan will update the handbook to include information on
procmail recipes to change reply-to behaviour
On Thu, Nov 09, 2006 at 10:32:43PM +0100, Bryan Østergaard wrote:
> Hi all, here's the complete log from the Council Meeting + a short
> summary.
>
Of course I had to screw up the subject.. It's of course the nov. 9
meeting.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
tional ways.
Anyway, I appreciate you spending time on cleaning up the metadata.xml
files even if it might not have been the best idea in hindsight.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
On Thu, Nov 23, 2006 at 02:56:49AM -0800, David Shakaryan wrote:
> Bryan Østergaard wrote:
> >On Wed, Nov 22, 2006 at 02:08:12PM -0700, Steve Dibb wrote:
> >>Hi guys,
> >>
> >>There are more than a few packages with missing metadata.xml in the
> >>
On Thu, Nov 23, 2006 at 11:20:16AM +0100, Jakub Moc wrote:
> Bryan Østergaard napsal(a):
> > I think the most important thing about adding "empty" metadata.xml files
> > with maintainer-needed as maintainer is that it _changes_ the package to
> > be unmainta
onfig?
>
>
> For help, please send mail to the webmaster ([EMAIL PROTECTED]),
> giving this error message and the time and date of the error.
>
We're waiting for people with admin privs to fix it. It should be back
up soon'ish.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
omplete log attached.
Regards,
Bryan Østergaard
20:59 <@robbat2> kloeri, Kugelfang, SpanKY, you here?
20:59 < vapier> moo
20:59 <@FlameBook> kingtaco?
20:59 < vapier> how do you rebind a channel in bx to a window ?
20:59 <@kloeri> yup
21:00 < vapier> ah here we go
21:00
orking with several
proxy maintainers the last couple of years.
Finally, I hope this can lead to a good discussion about future policies
and not concentrate on past package removals and possible mistakes in
that regard. We want to look forward and improve the processes.
Thanks for the summary and good lu
Hi all.
Just a quick reminder to be careful not to remove the last stable
version of packages on any archs when cleaning out old ebuild.
I'm getting rather tired of having to fix dependency issues on both
Alpha and IA64 because developers don't pay (enough) attention when
cleaning out ebuilds. Sp
to
back this statement up with facts if you want to change any developers
mind about this I'm afraid.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
new location.
Hopefully there'll be no more confusion about which copy to update now.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
ev and have access to that) or contact me on irc or by email
so I can possibly add you. I'm not only looking for current devs but a
strong knowledge of ebuilds, eclasses etc. is required.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
listen. Oh
> well, I give up; go fix the slot, never mind that it's utterly useless.
>
Jakub, please stop making a fool of yourself with your endless rants.
Quite a few experienced ebuild developers have already told you why it's
not being removed. As such your rants are only wasting time.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
w ideas from time to time.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
which would basically force us to stop adding new packages to
the tree until resolved).
Besides that splitting keywords out from ebuilds doesn't solve
*anything* at all related to this as the ebuilds *still* have to stay
around as long as they have keywords. Just like current policy says.
Moving metadata to another place doesn't change that at all.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
that I read now I cannot clearly
> define an outcome.
>
The (very clear imho) outcome was that it wasn't going to save any
bandwidth at all and would increase used diskspace quite a bit.
Bandwidth reduction was jokeys primary goal iirc.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
On Mon, Feb 19, 2007 at 03:13:00PM +0100, Stefan Schweizer wrote:
> Bryan Østergaard wrote:
> >A. ~arch keywords are supposed to be carried over to new versions unless
> >we're talking about big rewrites or similar (so old versions doesn't
> >have to linger around i
man.
Please stop the personal attacks. They serve absolutely no purpose other
than poisoning the developer community further.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
On Tue, Feb 20, 2007 at 01:00:12PM +0100, Francesco Riosa wrote:
> Bryan Østergaard ha scritto:
> >On Tue, Feb 20, 2007 at 11:46:32AM +0100, Francesco Riosa wrote:
> >
> >>Ciaran McCreesh ha scritto:
> >>>It is widely perceived that Gentoo has a huge problem w
On Tue, Feb 20, 2007 at 02:29:32PM +0100, Francesco Riosa wrote:
> Bryan Østergaard ha scritto:
> >On Tue, Feb 20, 2007 at 01:00:12PM +0100, Francesco Riosa wrote:
> >>Bryan Østergaard ha scritto:
> >>>On Tue, Feb 20, 2007 at 11:46:32AM +0100, Francesco Riosa wrote:
On Wed, Feb 21, 2007 at 05:10:49AM +, George Prowse wrote:
> Bryan Østergaard wrote:
> >On Tue, Feb 20, 2007 at 11:46:32AM +0100, Francesco Riosa wrote:
> >
> >
> >>Ciaran McCreesh ha scritto:
> >>
> >>>It is widely perceived tha
t; as it would benefit everyone. If people are truly concerned about
> productivity, then I would expect them to support it.
>
Banning Ciaran *is* going to hurt PMS as he's been asking many questions
related to PMS lately on -dev ML and the discussions have generally been
very good im
That said, could you both (Daniel + Ciaran) please stop this fight? It's
not getting us anywhere at all and just adds to the frustrations many
people currently feel.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
d to spot poisonous people in advance so
recruiters would probably be the least likely devrel group to gain from
this imo.
Besides, you don't need to be an official developer at all to cause
problems as the gentoo community (on purpose) is much wider than just
the people with commit access.
Re
iscussed ?
>
Please don't base your entire opinion on those very few retirement
announcements you've seen. Most devs that retire simply run out of time
for gentoo due to real life commitments etc. or move on to other open
source projects.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
On Mon, Mar 05, 2007 at 02:22:08AM +, Alex Tarkovsky wrote:
> Bryan Østergaard gentoo.org> writes:
>
> Bryan, instead of always addressing the symptoms by asking people to kindly be
> quiet or move things elsewhere, why don't you do something more substantive
>
On Mon, Mar 05, 2007 at 03:46:47AM +0100, Jakub Moc wrote:
> Bryan Østergaard napsal(a):
> > On Sun, Mar 04, 2007 at 11:31:56PM +, Hubert Mercier wrote:
> >> What is more, even if Gentoo is always growing, why are people leaving ?
> >> Personal reasons ? No, in fa
panded policy in a few
weeks.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
tte on
> http://www.gentoo.org/main/en/lists.xml might also be helpfull?
I'll try to remember that when updating etiquette policy.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
On Thu, Mar 08, 2007 at 03:32:38PM -0600, Dale wrote:
> Bryan Østergaard wrote:
> >
> > Gentoo has an etiquette policy as well at
> > http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=3&chap=2
> > for interested people.
> >
> > One thing w
be a warning if anybody bothered to
complain about it.
I agree we have to respect each other but that includes not pushing your
culture as a global culture. We most certainly come from vastly
different cultures and need to keep that in mind.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
lse. What's exactly the benefit from trying to kill support
> for upstream ALSA code and forcing people to use in-kernel drivers
> (beyond what you see as 'duplicated' maintenance effort)? Users honestly
> don't care much about 'duplicated' effort, they want a working sound on
> their boxes.
I'll just repeat myself here as you've basically just repeated your
claim about forcing people to use in-kernel drivers..
Nobody is forcing anybody to use in-kernel drivers.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
On Wed, Mar 28, 2007 at 05:36:57PM +0200, Jakub Moc wrote:
> Bryan Østergaard napsal(a):
> > Nobody is forcing anybody to use in-kernel drivers.
>
> Uhm... http://bugs.gentoo.org/show_bug.cgi?id=172490
>
Which isn't exactly the same as removing alsa-driver and forcing
oving it to Gentoo svn
> - schedule for getting remaining issues settled
> - splitting gentoo-dev mailing lists ?
> -mike
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
On Tue, Apr 10, 2007 at 11:34:25PM +0300, Petteri R??ty wrote:
> As the recent thread showed there is a lot going on in Gentoo land
> although it doesn't always seem so. I propose we extend project xml to
> describe current stuff going on in the project in question and their
> estimated completion
r account and watch the
[EMAIL PROTECTED] as documented in
http://www.gentoo.org/proj/en/infrastructure/retire-process.xml (See
'Retire Bugzilla account' part).
Regards,
Bryan Østergaard
--
[EMAIL PROTECTED] mailing list
t; I'm therefore resigning from this project.
>
> I would be grateful if somebody could refer me to the archive URL of the
> message which triggered this episode so I can make a personal judgment
> about it?
>
There's no such thing as it's based on general bad b
d complaints being filed we finally
take to firmer action which is exactly what have happened in this case.
> >
> So who watches the watchmen? IOW who does one take a complaint about devrel
> to, and will there be any action?
Complaints about devrel actions should be sent to the Gentoo Coun
ral times there's been
no improvement in his behaviour. That's why we're calling for a timeout
with this suspension and hoping that jakub will reconsider his
behaviour.
Regards,
Bryan Østergaard
--
[EMAIL PROTECTED] mailing list
Graphicsmagick is a fork of imagemagick but have been mostly inactive
the past 18 months. It's being removed due to inactive upstream and
several outstanding security issues (all the imagemagick security bugs
also apply to graphicsmagick).
The obvious replacement is imagemagick.
Regards,
en they're done you can
usually just state so in the keywording bug and the arch team will
follow the request.
Regards,
Bryan Østergaard
--
[EMAIL PROTECTED] mailing list
would be much better if he worked
together with other devs in a friendly way and stopped getting in the
way of maintainers as he has done on many occasions.
>
> It's not just me that thinks there haven't been any major b0rkages for
> nearly a year. Could it be that maybe, just may
about real Gentoo users that use Portage.
>
> I think we are setting a VERY dangerous precedent by allowing a subset
> of council members to make decisions as a whole if they decide to make a
> decision outside of a normal session.
>
> Who were the 3?
Already stated in another reply on this thread but the three council
members were robbat2, kugelfang and myself.
Regards,
Bryan Østergaard
--
[EMAIL PROTECTED] mailing list
On Tue, Apr 24, 2007 at 04:00:42PM -0400, Doug Goldstein wrote:
> Bryan Østergaard wrote:
> > On Tue, Apr 24, 2007 at 03:49:44PM -0400, Doug Goldstein wrote:
> >
> Bryan,
>
> You and Danny have clearly shown your bias towards paludis take over and
> support of Gentoo
can't be distributed as binaries, but are not blocked
> by some bindist feature flag or so.
>
License follows the same syntax as DEPEND. See
http://devmanual.gentoo.org/ebuild-writing/variables/index.html#license.
Regards,
Bryan Østergaard
--
[EMAIL PROTECTED] mailing list
ximum
of 6 months which should be enough time to get a new email account set
up and announce it to all your friends etc.
Updated policy is available at
http://www.gentoo.org/proj/en/devrel/policy.xml#doc_chap3 and should hit
our webservers in the next 30-60 minutes.
Regards,
Bryan Østergaard
--
[EMAIL
at work as Ombudsman and welcome Michael as an
official member of Developer Relations conflict resolution team.
Regards,
Bryan Østergaard
--
[EMAIL PROTECTED] mailing list
all of you and may Gentoo development be as much fun for you as
it used to be for me.
Best regards,
Bryan Østergaard
--
[EMAIL PROTECTED] mailing list
On 7/4/07, Blackace <[EMAIL PROTECTED]> wrote:
I'd like to nominate:
avenj
See https://bugs.gentoo.org/show_bug.cgi?id=169826.
Regards,
Bryan Østergaard
--
[EMAIL PROTECTED] mailing list
f you have input, now would be
the time.
Consider this my last post ever to gentoo-dev ML if this really goes
through. Degrading non-dev contributers like myself to second-class
citizens is definitely not going to make me want to contribute
anything more.
Regards,
Bryan Østergaard
--
[EMAIL PROTECTED] mailing list
76 matches
Mail list logo
