On Tue, Oct 11, 2022 at 7:13 AM Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:
> On Tue, Oct 11, 2022 at 11:48:14AM +0200, Fabio Valentini wrote:
> > On Mon, Oct 10, 2022 at 9:15 AM Jaroslav Mracek
> wrote:
> > >
> > > Please can you be more specific which kind of functionality is
>
Hi, I've orphaned the following packages for lack of time:
nautilus-search-tool
pinpoint
They are available for someone to pick up if desired.
I'm asking co-maintainers about some other packages I own, and if I get no
response, there may be some more to follow (a few minor drupal7 and PHP
On Thu, Apr 2, 2020 at 1:12 PM Robbie Harwood wrote:
> Paul Frields writes:
> > Neal Gompa wrote:
[...snip...]
> >> It's also important to note that at the core of GitLab's incentive
> >> model is that they want to remove incentives to use FOSS solutions in
On Wed, Apr 1, 2020, 7:53 PM Michael Catanzaro wrote:
> On Wed, Apr 1, 2020 at 3:39 pm, Chris Murphy
> wrote:
> > Is the FOSS position adequately represented on the Council?
>
> From my reading of [1], the Council decision is that we use FOSS in
> our infrastructure except where it is "not
On Wed, Apr 1, 2020 at 7:03 AM Neal Gompa wrote:
>
> On Wed, Apr 1, 2020 at 6:52 AM Nicolas Mailhot via devel
> wrote:
> >
> > Le mercredi 01 avril 2020 à 11:30 +0100, Leigh Griffin a écrit :
> > >
> > > To distill it down:
> > >
> > > - Gitlab has more features that are needed right now for our
On Tue, Mar 31, 2020 at 5:23 PM Adam Williamson
wrote:
>
> On Tue, 2020-03-31 at 17:06 -0400, Paul Frields wrote:
> >
> > > Sure. I tend to think of these as 'upstream projects' that we (Fedora)
> > > consume as a downstream. Project hosting has always been a kinda
&
On Tue, Mar 31, 2020 at 3:25 PM Adam Williamson
wrote:
>
> On Tue, 2020-03-31 at 21:18 +0200, Clement Verna wrote:
> > On Tue, 31 Mar 2020 at 20:04, Adam Williamson
> > wrote:
> >
> > > On Tue, 2020-03-31 at 13:55 -0400, Matthew Miller wrote:
> > > > On Tue, Mar 31, 2020 at 10:44:35AM -0700,
This package has been orphaned as discussed here:
https://bugzilla.redhat.com/show_bug.cgi?id=1738068
--
Paul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of
On Tue, Apr 9, 2019 at 12:07 PM Lennart Poettering wrote:
[...]
> Can we maybe reduce the default set of packages a bit? In particular
> the following ones I really don't think should be in our default
> install:
Although somewhat orthogonal to your notes below, overall there's a
lot of
Update: We'll be having discussions over the next few weeks to figure
out how we can accommodate Lifecycle work without interrupting the
Fedora release cadence. That includes in Brno, where we can meet up
f2f with people working on parallel projects in automation, CI, and so
on. We may also be
On Wed, Nov 28, 2018 at 7:43 AM Fabio Valentini wrote:
> I think the kernel is a bad example here. It's exceedly stable across
> releases, so it's probably the one component that's least problematic
> to upgrade during a fedora release. The fedora kernel team is already
> doing that, and they are
On Thu, Nov 29, 2018 at 4:47 AM Miroslav Suchý wrote:
>
> Dne 27. 11. 18 v 17:04 Josh Boyer napsal(a):
> >> In other words, the "technical debt" we are trying to solve here is
> >> not project wide and doesn't justify slowing down the whole project
> >> permanently.
> > I completely disagree.
On Tue, Nov 27, 2018 at 9:59 AM Owen Taylor wrote:
> A lot of discussion about improving the compose process seem to end up
> with a "reality check" - that ideas have already been tried but don't
> work because of requirements a) b) c) d). You can't have the pony, but
> maybe if a lot of effort
On Tue, Nov 27, 2018 at 1:40 PM Owen Taylor wrote:
>
> We can definitely talk about whether moving to a slower cadence for
> certain parts of the base platform. But people don't judge Fedora on
> how beautifully we maintain glibc and gcc - they mostly judge it by
> installing it on a laptop and
On Tue, Nov 27, 2018 at 12:19 PM Josh Boyer wrote:
> On Tue, Nov 27, 2018 at 11:21 AM Owen Taylor wrote:
> > On Tue, Nov 27, 2018 at 11:05 AM Josh Boyer
> > wrote:
[...snip...]
> > > I completely disagree. Our release process and tooling is built on
> > > heroism and tech debt. At some
On Tue, Nov 27, 2018 at 9:50 AM Dennis Gilmore wrote:
[...snip...]
> > The customers RH serves have specific expectations, and in part that
> > dictates how delivery tooling is done. Binding the community to that
> > may be counterproductive. This is especially true now that RHEL 8 Beta
> > is
On Tue, Nov 27, 2018 at 4:41 AM Miroslav Suchý wrote:
>
> Dne 26. 11. 18 v 17:03 Matthew Miller napsal(a):
> > * embrace Taiga (an open source kanban tool) for project planning
> > * fix the compose speed (target: one hour!)
> > * really actually for real gated Rawhide
> > * better CI pipeline
On Mon, Nov 26, 2018 at 5:47 PM Dennis Gilmore wrote:
> El lun, 26-11-2018 a las 17:14 -0500, Josh Boyer escribió:
> > Because the people that would be tasked with doing the development are
> > also tasked with cranking out the release. It's a "need more people
> > problem".
>
> This is no
On Mon, Nov 26, 2018 at 2:42 PM Adam Williamson
wrote:
> On Mon, 2018-11-26 at 11:30 -0800, Kevin Fenzi wrote:
> > Yeah, I think our goal should be 1 minute... just as realistic as one
> > hour. ;)
> >
> > I have not looked into things recently. However:
> >
> > * The mock fsync change
t; > On Fri, Nov 16, 2018 at 09:50:33AM -0500, Paul Frields wrote:
> > > > > Here's the summary from the page, which proposes we pause the release
> > > > > after F30 for these efforts:
> > > >
> > > > I know it was a big time-off holiday week
I worked with FPL Matthew Miller and our engineering manager Jim
Perrin, among others, to define the various problems we want to solve
in diversifying the Fedora lifecycle. We're seeking review and
feedback from community members. The most salient feedback will be
from those involved in the
On Thu, Oct 11, 2018 at 12:54 PM Josh Boyer wrote:
> I believe it's time for me to move on from my current role as the
> Council Engineering representative. When I resigned from FESCo a bit
> ago, I thought I could still fulfill this role. Unfortunately, that
> turns out to not be the case. I
On Wed, Aug 29, 2018 at 4:35 AM Adam Samalik wrote:
> On Tue, Aug 28, 2018 at 6:44 PM Paul Frields wrote:
>>
>> On Wed, Aug 22, 2018 at 7:26 AM Adam Samalik wrote:
>> > == Approaches
>> >
>> > Option 1: The current, yet unfinished approach
>> >
On Wed, Aug 22, 2018 at 7:26 AM Adam Samalik wrote:
> == Approaches
>
> Option 1: The current, yet unfinished approach
>
> We specify an EOL (end of life) date for each stream branch of individual
> packages. This is done when requesting a new stream branch for a package [2]
> by passing "--sl
On Tue, Aug 2, 2011 at 12:32 PM, Ryan Rix r...@n.rix.si wrote:
On Tue 2 August 2011 11:36:20 Hans de Goede wrote:
Hi,
On 08/01/2011 09:44 PM, Ryan Rix wrote:
On Mon 1 August 2011 19:43:37 Tomas Mraz wrote:
On Mon, 2011-08-01 at 10:29 -0700, Ryan Rix wrote:
On Mon 1 August 2011 11:46:00
With a Fedora release coming soon, it's also time for Fedora
Elections. Both the Fedora Project Board and the Fedora Engineering
Steering Committee (FESCo) will have open seats during this election
cycle.
Nominations for these seats open tomorrow, Saturday, April 24, 2010.
You can nominate
With a Fedora release coming soon, it's also time for Fedora
Elections. Both the Fedora Project Board and the Fedora Engineering
Steering Committee (FESCo) will have open seats during this election
cycle.
Nominations for these seats open tomorrow, Saturday, April 24, 2010.
You can nominate
On Sat, Feb 27, 2010 at 3:45 AM, Camilo Mesias cam...@mesias.co.uk wrote:
On Sat, Feb 27, 2010 at 6:12 AM, Adam Williamson awill...@redhat.com wrote:
this is a *terrible* idea. We may see users as a 'resource', but they
don't see themselves this way. We should not interrupt their usage of
28 matches
Mail list logo
