I'm back on this topic, because I have news.
On 11/21/2017 09:18 AM, Bartłomiej Piotrowski wrote:
>
> This is example of wishful thinking and misunderstanding what our
> requirements are. Reporting anything on Bugzilla isn't different from
> using Flyspray, and we're far from "the most friendly d
> From: Jelle van der Waa
> Sent: Tue Nov 21 10:36:08 CET 2017
> To: General Discussion about Arch Linux
> Subject: Re: [arch-general] [arch-dev-public] Switching the bugtracker to
> Bugzilla
>
>
> I'm quiet happy that we are still running everything
On 11/21/17 at 09:23am, Óscar García Amor wrote:
> 2017-11-19 18:54 GMT+01:00 Bartłomiej Piotrowski :
> > On 2017-11-19 17:58, William Gathoye wrote:
> >> I'll be using Gitlab professionally on Arch Linux. So as soon I become a
> >> TU (if it happen the Arch Linux community accepts me ;)) I think I
2017-11-19 18:54 GMT+01:00 Bartłomiej Piotrowski :
> On 2017-11-19 17:58, William Gathoye wrote:
>> I'll be using Gitlab professionally on Arch Linux. So as soon I become a
>> TU (if it happen the Arch Linux community accepts me ;)) I think I'll
>> help Sven-Hendrik Haase in this process. Packaging
On 2017-11-19 20:11, Jerome Leclanche wrote:
> I've refrained from commenting on this topic because I don't want to
> sound ungrateful people are taking the time to work on a fairly
> extensive migration off flyspray, but I'm not looking forward to
> Bugzilla (and I've contributed to a lot of Bugzi
On Sun, Nov 19, 2017 at 7:54 PM, Bartłomiej Piotrowski
wrote:
> On 2017-11-19 17:58, William Gathoye wrote:
>> I'll be using Gitlab professionally on Arch Linux. So as soon I become a
>> TU (if it happen the Arch Linux community accepts me ;)) I think I'll
>> help Sven-Hendrik Haase in this proces
On 2017-11-19 17:58, William Gathoye wrote:
> I'll be using Gitlab professionally on Arch Linux. So as soon I become a
> TU (if it happen the Arch Linux community accepts me ;)) I think I'll
> help Sven-Hendrik Haase in this process. Packaging Gitlab as a single
> person is indeed a hard task.
The
On Sun, 19 Nov 2017 17:58:55 +0100
William Gathoye wrote:
> This is why at The Document Foundation and Mattermost, we have a QA team
> (or at least one or two persons) which checks if the bugs are valid and
> put in cc the people that have the abilities to work on it. I know all
> of us have a li
On 11/19/2017 04:24 PM, Eli Schwartz wrote:
>
> OTOH, gitlab is complicated to package and occasionally breaks, which
> would be embarrassing if we could not report bugs against the package
> because the package is broken and we don't have a bugtracker...
I'll be using Gitlab professionally on
On 11/19/2017 11:04 AM, Florian Pritz via arch-general wrote:
> On 19.11.2017 16:24, Eli Schwartz wrote:
>> We cannot migrate to git because no one has put in the work necessary to
>> properly rewrite dbscripts.
>
> Just to clarify: Gabriel Souza Franco (gbsf) has put quite a lot of work
> into t
On 19.11.2017 16:24, Eli Schwartz wrote:
> We cannot migrate to git because no one has put in the work necessary to
> properly rewrite dbscripts.
Just to clarify: Gabriel Souza Franco (gbsf) has put quite a lot of work
into this and some others have also worked on parts, but we haven't yet
assemb
On 11/19/2017 09:08 AM, William Gathoye wrote:
> Bugzilla is old both in terms of look and feel and usability. It doesn't
> even support Markdown formatting[1], which could have been nice in order
> to be on part with the Markdown feature brought with the forthcoming aur
> web version. Contributing
Hello everyone,
On 11/14/2017 10:34 PM, Bartłomiej Piotrowski wrote:
> On 2017-11-14 20:30, Jelle van der Waa wrote:
>> Used by several big projects such as Gnome, LLVM and Mozilla
>
> GNOME will probably end up switching to Gitlab. (Not dismissing the fact
> that bugzilla is rather popular choic
On 11/14/2017 09:06 PM, Giancarlo Razzolini wrote:
> Em novembro 14, 2017 20:27 Bartłomiej Piotrowski escreveu:
>>
>> Just to be clear, it's completely fine thing to do.
>>
>> Feel free to ignore community input if you feel better this way, but
>> don't tell people to cover their eyes when we discu
Em novembro 14, 2017 20:27 Bartłomiej Piotrowski escreveu:
Just to be clear, it's completely fine thing to do.
Feel free to ignore community input if you feel better this way, but
don't tell people to cover their eyes when we discuss something on
publicly readable mailing list.
Just to be (m
On 2017-11-14 23:16, Giancarlo Razzolini wrote:
> Em novembro 14, 2017 19:26 Leonidas Spyropoulos via arch-general escreveu:
>> - Replying on arch-general as don't have access on dev-public -
>>
>
> Please, don't do this. Even though we always welcome input from our
> users, there's
> a reason why
Em novembro 14, 2017 19:26 Leonidas Spyropoulos via arch-general escreveu:
- Replying on arch-general as don't have access on dev-public -
Please, don't do this. Even though we always welcome input from our users,
there's
a reason why this discussion was started on adp, instead of arch-genera
- Replying on arch-general as don't have access on dev-public -
I might have missed something or proposed something which is not
feasible due to the fact I'm not vary familiar with Archlinux
infrastructure.
On 14/11/17, Jelle van der Waa wrote:
> [..]
> # Migration
>
> There are several options f
18 matches
Mail list logo
