+1000
42 is one of the most quoted pop culture refs in tech that I know of. We
nerds don't reference pop culture a lot so we should celebrate it when we
can!
Langdon
On Mon, Nov 4, 2024, 10:52 Stephen Gallagher wrote:
> I posted this discussion on Fedora Discussion[1] last week,
g.cgi?id=1853261
> [7] https://bugzilla.redhat.com/show_bug.cgi?id=1853293
> [8] https://bugzilla.redhat.com/show_bug.cgi?id=1853409
> [9] https://bugzilla.redhat.com/show_bug.cgi?id=1851608
> [10] https://bugzilla.redhat.com/show_bug.cgi?id=1829792
> [11] https://src.f
As a result of PTO, fosdem, etc, availability for the meeting today is
pretty light. We should resume next week.
Langdon
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora
As many of the people who would be at the meeting are tied up today, we are
canceling.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedora
==
#fedora-meeting-3: Modularity Team Meeting
==
Meeting started by langdon at 15:00:37 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting-3/2020-01-14/modularity.2020-01-14-15.00.log.html
g rpm from
a default stream module
* Request dnf provide an indication of what module is providing a
particular rpm (e.g. `dnf provides protobuf` not just indicate repo origin
but also module name and stream)
Langdon
[1]: if you are unfamiliar, this is the functionality that allows a modu
et/#fedora-meeting-3.
Please join us if you are interested.
langdon
[1]:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/3EP3LXGGZABBCAHF5EPZCVEL4FQ23GS3/#VIX7R6QA6EH4DHHEPGMFEQ5MQ5FF7TBE
___
devel mailing lis
-12-03-15.02.log.html
==
#fedora-meeting-3: Modularity Team Meeting
==
Meeting started by langdon at 15:02:49 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-3/2019-12-03/modularity
Most of the primary team members are unavailable today so we are canceling
the meeting.
Join us next week instead!
langdon
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
-11-12-15.01.log.html
#fedora-meeting-3: Weekly'ish Meeting of the Modularity Team
Meeting started by langdon at 15:01:21 UTC. The full logs are available
at
On 10/25/19 10:15 AM, Randy Barlow wrote:
On Fri, 2019-10-25 at 09:43 +0200, Pierre-Yves Chibon wrote:
That is true, but the wording used also implied that this design has
not been
considered.
The question of whether other designs have been considered has been
raised many times over the years,
-10-15-15.01.log.html
#fedora-meeting-3: Weekly'ish Meeting of the Modularity Team
Meeting started by langdon at 15:01:02 UTC. The full logs are available
at
-10-08-15.08.log.html
==
#fedora-meeting-3: Modularity Team Meeting
==
Meeting started by langdon at 15:08:18 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-3/2019-10-08/modularity
-09-17-15.02.log.html
#fedora-meeting-3: Weekly'ish Meeting of the Modularity Team
Meeting started by langdon at 15:02:03 UTC. The full logs are available
at
On Tue, Sep 11, 2018 at 3:09 PM Stephen Gallagher
wrote:
> Go ahead
>
>
+1
On Tue, Sep 11, 2018 at 3:04 PM Adam Samalik wrote:
>
>> We have some obsolete github repositories [1] from the f26 and f27 period
>> we are no longer using. I feel like it might be confusing to people. So I'd
>> like to
Meeting started by langdon at 14:05:28 UTC.
Minutes:
https://meetbot.fedoraproject.org/teams/modularity_wg/modularity_wg.2018-06-26-14.05.html
Minutes (text):
https://meetbot-raw.fedoraproject.org/teams/modularity_wg/modularity_wg.2018-06-26-14.05.txt
Log:
https://meetbot.fedoraproject.org/teams
an
assign which would be a simpler way to solve the "email back to
chairperson" problem. Not actually sure if there is an RFE for this. Have
the same problem with the modularity-wg meeting-tag.
Langdon
--
> Matthew Miller
>
> Fedora Project Leader
> ___
Meeting started by langdon at 14:01:52 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting-3/2018-05-01/modularity_wg.2018-05-01-14.01.html
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting-3/2018-05-01/modularity_wg.2018-05-01-14.01.txt
Log:
https
as) the elements of an rpm "name".
We chose a colon & slash (for profile names) somewhat based on the
practice(s) of docker. However, the dnf team made the ultimate choice,
so their opinion on the subject matters.
Langdon
[1]: what is referred to in the naming guidelines as the &qu
gt; PS: I'm figuring out https://pulpproject.org support for modular content
>
> Cool. I'm not fully sure how this will look for f28, but likely you
> could ask the releng list or modulariy workgroup.
>
>
If you would like to track progress, we have a ticket open here:
https:/
ng at SCALE 16x[7].
Please let us know if you have questions or comments here or in
#fedora-modularity.
Langdon White
Modularity Objective Lead^3
[0]: https://pagure.io/Fedora-Council/tickets/issue/170
[1]:
https://fedoraproject.org/wiki/Objectives/Fedora_Modularization_%E2%80%94_The_Release
[2]:
;.
Meeting summary
---
* Roll Call (langdon, 14:07:40)
* Agenda (langdon, 14:11:07)
* langdon: Review "What goes into a module?" in
https://fedoraproject.org/wiki/Module:Guidelines (langdon,
14:11:07)
* [langdon]: propose we adopt the workstation wg model for
Quick Minutes:
* Topic: when build-requireing bootstrap, nothing else can cascade to
build-require anything that conflicts (langdon, 14:09:45) * LINK:
http://pkgs.fedoraproject.org/cgit/modules/python3.git/tree/python3.yaml
(langdon, 14:28:22) * ACTION: langdon to get bootstrap guidance added to
Blocking (F26 page)
https://fedoraproject.org/wiki/Releases/27/ReleaseBlocking (Doesn't
exist)
^^ I am not sure how this is related to modular server at all as it is a
normal part of the traditional distribution process and not provided by
the modularity wg.
Langdon
of application
and os distribution. I would say, as the modularity work becomes completely
mainstream, I think you could propose adding "fancy install profiles" and
the other things you need to make your concept real.
I have a lot of ideas of what we *could* do next with the flexib
On Tue, Aug 22, 2017 at 9:53 AM Owen Taylor wrote:
> Hi Langdon,
>
> Thanks for all the work that went into the process and guidelines!
>
> My particular interest is in what I consider the simplest use case -
> taking an existing leaf-node application (desktop or otherwise), c
On Tue, Aug 22, 2017 at 5:23 AM Petr Pisar wrote:
> On 2017-08-21, Langdon White wrote:
> > [2]: https://fedoraproject.org/wiki/Module:Review_Process
>
> I don't understand purpose of this paragraph:
>
> > As a Contributor, you should only be creating modules out of
file issues/PRs on pagure[4] if you have other comments/edits/etc.
thanks
Langdon
[1]:
https://fedoraproject.org/wiki/Module:Guidelines?rd=Fedora_Packaging_Guidelines_for_Modules
[2]: https://fedoraproject.org/wiki/Module:Review_Process
[3]: https://docs.pagure.org/modularity/
[4]: https://pagure.io
cle for f27, not to mention
$DAYJOB, I just didn't get to it. I am really sorry to have lost the seat
and not campaigned hard enough.
Congrats to Justin!
Langdon
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
or find other methods around this problem (private
namespacing, containers, rpathing, etc), we could have the openssl-1.1
sources in dist-git be included in multiple modules. When the openssl
maintainer elects to add the openssl-1.2 stream, wordpress-4 could decide
if it is appropriately backwards compatible for their use case and consume
it (by changing their modulemd to point to the new stream).
Langdon
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
e we don't have to make release == "collection of
> specific module versions". If that's one of the outcomes, then
> Changes simply become "this module version is available".
>
>
Exactly. See my "httpd for simple html" exampl
On Tue, Jul 25, 2017, 19:34 Zbigniew Jędrzejewski-Szmek
wrote:
> On Tue, Jul 25, 2017 at 10:49:41AM -0400, langdon wrote:
> > As you may have seen on Fedora Magazine[1], the Modularity and
> > Server Working Groups are very excited to announce the availability
> > of the Bo
you could try the walkthrough[5].
On behalf of all the people involved,
Langdon White
Modularity Objective
PS: and a massive thanks to all the people involved.. zodbot ++ all the
people!
[1]: Blog Post: https://fedoramagazine.org/announcing-boltron/
[2]: Docs: https://docs.pagure.org
On 07/06/2017 02:58 PM, Owen Taylor wrote:
On Thu, 2017-07-06 at 13:39 -0400, langdon wrote:
On 06/29/2017 11:30 AM, Matthew Miller wrote:
On Thu, Jun 29, 2017 at 10:49:20AM -0400, Owen Taylor wrote:
So my expectation is that the number of "collections modules"
that have no strong
wiki
discussion" page? Should we move the guidelines to a pagure repo and do
it with PRs, issues, etc?
Langdon
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
nable to say that they all
are versioned at the same tempo and even keep the F stream naming.
Langdon? Rebuttal? :)
I think containers are just a packaging type. In other words, whether
the "thing" is delivered as a docker container, flatpak, rpm,
something-not-though-of-yet, it is
it"
has come up multiple times because it is HARD. I am also not sure EOL is
something we can just plop in somewhere and then fix it later. So, your
concerns are very valid and well understood, we just haven't figured out
exactly how to solve it. Current plan is PDC along with SLA but
k
lifecycles in the end, that point isn't achieved at all.
This is partly why I described EOL as "EOL no earlier than" (thanks to
Langdon). I think the best thing to do in the case of a long extension
would be to create a new branch/stream with the new EOL. That's part of
why I
On 06/27/2017 06:10 PM, Adam Williamson wrote:
On Mon, 2017-06-26 at 14:30 -0400, Matthew Miller wrote:
On Mon, Jun 26, 2017 at 01:55:58PM -0400, langdon wrote:
Apologies, but I was talking about "available in the Fedora Server
repo". Specifically, we have a lofty goal that everythi
On Tue, Jun 27, 2017, 10:54 Josh Boyer wrote:
> On Tue, Jun 27, 2017 at 10:44 AM, langdon wrote:
> > On 06/27/2017 08:30 AM, Josh Boyer wrote:
> >>
> >> On Sun, Jun 25, 2017 at 1:44 PM, langdon
> >> wrote:
> >>>
> >>> OVERVIEW
>
On 06/27/2017 08:30 AM, Josh Boyer wrote:
On Sun, Jun 25, 2017 at 1:44 PM, langdon wrote:
OVERVIEW
As the modularity work starts to enter Fedora with the Fedora 27
release, a typical Change Proposal did not seem to do justice on
capturing the moving parts and dependencies for the
On 06/26/2017 01:44 PM, Petr Šabata wrote:
On Mon, Jun 26, 2017 at 11:29:08AM -0600, Kevin Fenzi wrote:
On 06/26/2017 11:04 AM, Langdon White wrote:
We talked about this with the server wg and decided for F27 server we would
try to avoid an "everything else" module and figure out ho
On 06/26/2017 01:29 PM, Kevin Fenzi wrote:
On 06/26/2017 11:04 AM, Langdon White wrote:
We talked about this with the server wg and decided for F27 server we would
try to avoid an "everything else" module and figure out how to solve this
problem more nicely between now and releas
s here
including : generating modules for everything, making an extra repo of
stuff available, leaving non-modules out, and, finally, the everything else
module.
Definitely a recognized issue, but not sure we are decided on the answer
(or answers). We would like the module guidelines to addr
project.org/wiki/Infrastructure/Factory2/Focus/ODCS)
- Branching Focus doc
[*https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/ArbitraryBranching*](https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/ArbitraryBranching)
Langdon White
Fedora Modularit
ttps://apps.fedoraproject.org/calendar/meeting/5246/
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Canceled tomorrow. Missed killing it from fedocal
Langdon
&g
oraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
Exactly, yes, a huge *potential* problem. However, it is fixable with
policy and changeable by exception. Just because we can have 40 versions of
one thing doesn't mean Fedora will allow that. Ho
*applications* that it runs. The
distribution concept might, in some ways, be lost but the goals of the
distribution would be retained just leveraging different mechanisms to
implement it.
Langdon
I don't think it's "alarmist" to note that things change, and that we
need
On 12/09/2016 03:26 PM, Matthew Miller wrote:
On Fri, Dec 09, 2016 at 03:19:58PM -0500, langdon wrote:
Langdon is sitting right next to me right now and I'm going to tag him
in for more on Modularity.
[...]
them. We can also decide when a "release" makes sense based on
mar
since I thought those were the primary
drivers of planned major change to how we deliver Fedora.
Somewhere back in the early part of one of these threads, that *was* in
there — Generational Core on _three month_ cycles following new kernel
releases, userspace modules updated on their own natural cy
hout the newline.
Wouldn't it make more sense to be checking for status 200? Checking for
content on the page seems fragile in general.
Also, and perhaps related, I filed a bug[1] about captive portals that
seems to have some attention.
Langdon
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1
Does this still need testing? I have a MacBook pro I could try it on.
Langdon
On Thu, Nov 10, 2016, 13:33 Mauricio Tavares wrote:
> How old can the OSX box be? I have in a box an old Mac mini (Dual core
> and can only officially supported to 10.7) I have no issues to put to
> servic
o the comment on which your preference is attached.
Would like to resolve this in the Modularity WG meeting tomorrow so voting
closes at 15h UTC Sept 13, 2016.
thanks! And, thanks especially to the design/badges team for their
work/proposals!
langdon
--
devel mailing list
devel@lists.fedoraprojec
**
*Uhh that was weird. *
*
Modularity WG Meeting
===
Reminder! Meeting[1] tomorrow (Jun 21) 15h UTC in #fedora-meeting-3.
Agenda[2]. Please add any ideas/questions you may have.
[1]: https://apps.fedoraproject.org/calendar/modularity/
[2]: http://piratepa
Modularity WG Meeting
===
Reminder! Meeting[1] tomorrow (Jun 21) 15h UTC in #fedora-meeting-3. Agenda[2]. Please add any ideas/questions you may have.
[1]: https://apps.fedoraproject.org/calendar/modularity/
[2]:
**
*Modularity Working Group Meeting*
*
===
The Modularity Working Group meeting has moved time and locations. You
can now find us on Tuesdays at 15h UTC in #fedora-meeting-3[1].
[1]: https://apps.fedoraproject.org/calendar/modularity/
Life of a Module
==
Apologies on these being a bit intermittent lately. Will try and do
better going forward.
Agenda for today:
* New meeting time
* Discuss Ralph & Lubos' diagram of "future life of a package/module" (
We may switch to a jitsi meeting for higher bandwidth conversation)
Langd
Hi,
Unfortunately, I heard from some of the new voting members that the
current Modularity WG meeting time is not doable for them. Please use
the link below to help us figure out a new time.
http://whenisgood.net/hzd7x2b
Langdon
PS: haven't actually used whenisgood to schedule a me
sct
* discuss open bzs (dnf, anaconda)
* discuss future outreach
Langdon
Modularization Home: https://fedoraproject.org/wiki/Modularization
Modularity WG: https://fedoraproject.org/wiki/Modularity_Working_Group
Calendar:https://apps.fedoraproject.org/calendar/modularity/
--
devel mailing list
d
Apologies for the late notice, but I, and a number of others, can't make
the meeting slot today. As a result, I feel it is of better value to
cancel the meeting rather than waste people's time.
See you next week,
Langdon
Modularity Objective Lead
--
devel mailing
-04-14/modularity_wg.2016-04-14-15.01.log.html
As always, please let us know here or in #fedora-modularization if you
have any questions/thoughts/etc.
Langdon
Fedora Modularity Objective Lead
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel
Please join us for the modularity wg meeting.
Agenda:
* Finalize charter
* Review progress
Langdon
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
We had another Modularity Working group meeting last Thursday (Apr. 7)
where I managed to screw up the meetbot commands. You can find the
meeting minutes in the usual place[1][2][3], but they may not be very
useful. As a result, I decided to do a more expansive recap, hence the
delay.
[1]: La
Please join us in #fedora-meeting in about 2 hours (15h UTC). Please
feel free to propose any agenda items here or during the roll call of
the meeting.
Agenda:
* Governance
* What & when
Langdon
PS: the proposed governance wiki page should be updated by then[1]
PPS: you can find
so
that will be on the agenda for next meeting.
Meeting summary
---
* roll call (langdon, 15:03:56)
* context setting (langdon, 15:07:12)
* LINK: https://fedoraproject.org/wiki/Modularization (langdon,
15:08:12)
* modularization wiki page (langdon, 15:08
kely have more than required
* discuss the best time for future, recurring meetings
* discuss "what to deliver" & planned delivery dates
* discuss approach for "doing work"
* assign people to update wiki with decisions
Langdon
Modularity Objective Lead
[1]: https://app
. We can keep the nominations open until April 18th,
but maybe we can start moving forward even before then.
I would like to hold the first meeting with the nominees and any other
interested participants on Mar. 31 15h/3pm UTC in #fedora-meeting.
Please come and join us!
Langdon
Modularity
please feel free to add user stories[7][8].
Langdon
Fedora Modularity Objective Lead
[1]: https://fedoraproject.org/wiki/Modularization
[2]:
https://fedoraproject.org/wiki/Objectives/Fedora_Modularization,_Prototype_Phase
[3]: https://communityblog.fedoraproject.org/
[4]:
https://communi
Looking at fedocal vs the wiki page, I am not sure when the Base Meeting
time & day is (or if there are multiple). Could someone please update
fedocal if it is incorrect?
Langdon
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fe
com/show_bug.cgi?id=1240634
> I was packaging python module with really fascinating functionality.
> Python-afl is an experimental module that enables American fuzzy lop fork
> server and instrumentation for pure-Python code.
>
> Best regards
>
>
Nice to meet you! We look forward to y
out"? Was
considering giving it a whirl, but not sure I could help the testing
information without more scenario-type details.
Langdon
> ___
> test-announce mailing list
> test-annou...@lists.fedoraproject.org
> https://admin.fedoraproje
veral revisions (up2date, pup, gpk-update etc). It might be
change with better software managers now but I suspect that most of our
"regular" users are in fact using the command line for updates at this
point.
>
> Rahul
Now that the gui updater *requires* a reboot, I don't even use
72 matches
Mail list logo
