Thanks everybody for suggestions. I'll come up with some temporary
solution and will see what's happening.
Kind regards,
-- Jan Pacner
Hello,
I've come in touch with this
https://bugzilla.redhat.com/show_bug.cgi?id=1096756 request which
suggests compiling with DEBUG and shipping such package to end users.
I'm not sure if it's a good idea as I don't know mutt that thoroughly to
be able to think of all cases where it could cause h
> mutt-1.5.23 signed
Thank you Brendan!
Kind regards
-- Jan Pacner
Hi,
> 2004 actually.
Awesome!
> All the patches I posted yesterday I use for approx 10 years with one
> exception: The umask patch. However getting patches in mutt is hard
> work. I remember getting the header cache into mutt took me one year full
> time. The problem was that Thomas Roessler did
Hello again,
I'd like to thank you everybody who read and participated in this
discussion. I really appreciate the changes which emerged in the
meantime and therefore I'm closing this discussion.
I'm certain the project will stay alive and vital even if the interest
for such "low-level" MUAs has
Hi there,
> no, actually, i was referring to the first part of my first sentence in
> that paragraph. of course there is a time perspective to it, but that's
> not the point.
Oh, I see now. The survey is not essential - the proposals themselves
are needed (e.g. with proper arguments based on some
Hi Oswald,
> and who makes *that* call? where do you draw the line? it doesn't appear
> magically, somebody with the competence and guts (=> authority) has to
> do it.
If you're bold enough (devs/committers are :)), you'll do it.
> ... but the simple fact is that there is nobody here
> who wants
Hi Oswald,
> from my experience, people without maintainership ambitions simply adapt
> to lower standards.
Such people are fast to discover => you can ban them (it may/should have
also a social face, not only sudden change of commit rights or alike) at
the very beginning => solved :).
> they co
Hi Gary,
you must be right. The only concern is about the very final slow-down of
patch adoption. In case of mutt, this slow-down was/is (?) really
counterproductive.
Kind regards
-- Jan Pacner
Hi Holger,
> try more context. hint: it's a response to what *you* wrote.
Well, it seems we both have no idea if some of mutt devs are paid or
not, so let's move to the next point :).
> obviously.
> i'll point out that we were talking about the motivation to polish
> patches.
> so how exactly ca
Hi Holger,
you're entirely right with my misuse of 'high-quality'. I should have
quoted it. The submitter himself would be responsible for the quality.
The point of this suggestion is that patches would be incorporated
faster, but on the other hand they could be much faster abandoned
(because the
Hi Holger,
> But the solution is not to give everyone
> commit access.
Don't get me wrong, but a high-quality patch in conjunction with
constructive track ticket seems enough for accepting the person as a
commiter into (and only into) the quick-moving partly stable branch.
It's imho quite far fro
Hi Holger,
> You suggest the project could be moved forward without
> maintainership, while I believe that strong maintainership is the only
> realistic option.
More accurately, I suggest the project could be moved forward by
_adding_ another tier, which would fill in the hole called "missing
pos
Hi Holger,
> This sounds so awesome! No need for maintainers. The community will
> just magically take over all their work.
>
> Of course, in practice, it doesn't work this way. Occasional
> contributors add their favourite feature or fix a bug they stumbled
> over. That's it. They provide p
Hi Fredrik,
> If you need an automated tool to enforce formatting rules, doesn't that
> apply that your code review process is broken and you risc to slip in
> serious bugs? Shouldn't formatting rules be part of the ordinary code
> review process?
It depends. IMHO it should be, but if the project
Amazing! Thank you guys.
-- Jan Pacner
> While I'd like to see a more inclusive patch process (I have created
> several over the years that I'd like to see included in mutt) I think,
> as others have mentioned before, that a comprehensive regression test
> needs to be created and included in the mutt source tree with a make
> target to
> Mutt might not *any longer* be able to garner that kind of support.
> The number of people I know who use Mutt today has become A LOT
> smaller than the number of people I know who previously used Mutt.
> It's a small project which fills a particular niche that is becoming
> less and less interes
Hi Oswald,
>> In one of your emails you mentioned, there are most probably some paid
>> developers. Now you're writing "would need" as if there were none of
>> them right now. I'm not sure what is actually your point.
>>
> i made no such claim regarding mutt. you should re-read the relevant
> mail
Hi Oswald,
> yes, there is a huge difference for the *users*, because as it stands,
> they are in fact faced with a whole forrest of branches which they need
> to merge by themselves. from the perspective of the developers it is the
> same - an external source of random patches.
Exactly.
> chasi
Hi Oswald,
On 10/07/2013 10:29 AM, Oswald Buddenhagen wrote:
> the difference is that these branches are maintained by the same people,
> or at least that those maintaining the stable branch are *paid* to
> actively cherry-pick from the unstable branch.
> you proposed an open-for-all branch with v
Hi,
>> Let me propose a fairly minor change in the development process.
>>
> you are proposing a fork on mutt's own infrastructure.
Not at all. Look at many other projects. Even huge projects like Fedora
("not guaranteed to work in a production environment") and RHEL
("everything bundled is guara
Well,
if you don't mind, I would try to make a small intermediate aggregation
of the current topics discussed regarding the purpose of this discussion
(which is solving the declining vitality of the mutt project).
Except for many examples of technical stuff, patches and situations
where the proje
Hello everybody,
by this email I'd like to open discussion about the future of the mutt
project. From year to year we can witness a small, but certain decline
in the overall mutt project vitality. This is in direct contrast with
the user-base which is (according to tickets and mailing lists) both
24 matches
Mail list logo
