On 6/22/2023 9:10 AM, Vladimir Panteleev via Digitalmars-d wrote:
> On Thursday, 22 June 2023 at 07:03:00 UTC, Mike Parker wrote:
>> All of that's going to require coordinating with Brad, so I can't really put it on a timeline.
> 
> I have been waiting for over a year now to get the missing files from Brad for the new Bugzilla, so we probably probably shouldn't hold our breath on this.

What files are you seeking?  More or less everything about the configuration, aside from things like the database host name, uid, and password for the db are managed inside the instance itself, all of which is visible through the ui, and those aren't particularly useful to have.

On Thursday, 22 June 2023 at 20:22:46 UTC, Brad Roberts wrote:
> What files are you seeking?  More or less everything about the configuration, aside from things like the database host name, uid, and password for the db are managed inside the instance itself, all of which is visible through the ui, and those aren't particularly useful to have.

Hi Brad!

Looking at my records, I am missing the files localconfig and data/params.

Yes, the files contain parameters which can be configured from the user interface, however they also contain things which are not available from the user interface. One of these, for example, is a key which is used when calculating users' credentials. Without it, we would need to force everyone to reset their passwords (which may be a problem for people who no longer have access to the email address they use to log in to Bugzilla).

Thanks!

On Thursday, June 22, 2023 2:12:34 PM MDT Vladimir Panteleev via Digitalmars-d wrote:
> 2. Ideologically, it's an uphill battle as almost everyone just wants to use GitHub, and would not prefer to use Bugzilla no matter how good it is.

I've never understood why some folks have kept pushing for us to use github issues. They're nice if you're setting up a github repo and don't want to go to the trouble of setting up and hosting a bugzilla instance elsewhere, but they're not as sophisticated as bugzilla.

- Jonathan M Davis

On 6/22/2023 1:35 PM, Vladimir Panteleev via Digitalmars-d wrote:
> On Thursday, 22 June 2023 at 20:22:46 UTC, Brad Roberts wrote:
>> What files are you seeking?  More or less everything about the configuration, aside from things like the database host name, uid, and password for the db are managed inside the instance itself, all of which is visible through the ui, and those aren't particularly useful to have.
> 
> Hi Brad!
> 
> Looking at my records, I am missing the files localconfig and data/params.
> 
> Yes, the files contain parameters which can be configured from the user interface, however they also contain things which are not available from the user interface. One of these, for example, is a key which is used when calculating users' credentials. Without it, we would need to force everyone to reset their passwords (which may be a problem for people who no longer have access to the email address they use to log in to Bugzilla).
> 
> Thanks!

I don't understand why you need that key or to mess with users accounts or passwords at all.  That sounds like a pretty major security and trust violation to me.  Everything else in localconfig is just site specific params (like paths to various executables).  data/params is all available in the ui, but here:

%param = (
           'LDAPBaseDN' => '',
           'LDAPbinddn' => '',
           'LDAPfilter' => '',
           'LDAPmailattribute' => 'mail',
           'LDAPserver' => '',
           'LDAPstarttls' => 0,
           'LDAPuidattribute' => 'uid',
           'RADIUS_NAS_IP' => '',
           'RADIUS_email_suffix' => '',
           'RADIUS_secret' => '',
           'RADIUS_server' => '',
           'ajax_user_autocompletion' => '1',
           'allow_attachment_deletion' => 0,
           'allow_attachment_display' => 0,
           'allowbugdeletion' => '0',
           'allowemailchange' => 1,
           'allowuserdeletion' => 0,
           'announcehtml' => '',
           'attachment_base' => '',
           'auth_env_email' => '',
           'auth_env_id' => '',
           'auth_env_realname' => '',
           'bonsai_url' => '',
           'chartgroup' => 'editbugs',
           'commentonchange_resolution' => 0,
           'commentonduplicate' => 0,
           'confirmuniqueusermatch' => 1,
           'cookiedomain' => '',
           'cookiepath' => '/',
           'createemailregexp' => '.*',
           'cvsroot' => '',
           'cvsroot_get' => '',
           'debug_group' => 'admin',
           'default_search_limit' => '500',
           'defaultopsys' => '',
           'defaultplatform' => '',
           'defaultpriority' => '---',
           'defaultquery' => 'resolution=---&emailassigned_to1=1&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailqa_contact2=1&emaillongdesc3=1&order=Importance&long_desc_type=substring',
           'defaultseverity' => 'enhancement',
           'docs_urlbase' => 'docs/%lang%/html/',
           'duplicate_or_move_bug_status' => 'RESOLVED',
           'emailregexp' => '^[\\w\\.\\+\\-=]+@[\\w\\.\\-]+\\.[\\w\\-]+$',
           'emailregexpdesc' => 'A legal address must contain exactly one \'@\', and at least one \'.\' after the @.',
           'emailsuffix' => '',
           'globalwatchers' => '',
           'inbound_proxies' => '',
           'insidergroup' => '',
           'letsubmitterchoosemilestone' => 1,
           'letsubmitterchoosepriority' => 1,
           'lxr_root' => '',
           'lxr_url' => '',
           'mail_delivery_method' => 'SMTP',
           'mailfrom' => 'd-bugmail@puremagic.com',
           'maintainer' => 'braddr@puremagic.com',
           'makeproductgroups' => 0,
           'max_search_results' => '10000',
           'maxattachmentsize' => '1000',
           'maxlocalattachment' => '0',
           'maxusermatches' => '1000',
           'mostfreqthreshold' => '2',
           'musthavemilestoneonaccept' => 0,
           'mybugstemplate' => 'buglist.cgi?resolution=---&emailassigned_to1=1&emailreporter1=1&emailtype1=exact&email1=%userid%',
           'noresolveonopenblockers' => 0,
           'password_complexity' => 'no_constraints',
           'proxy_url' => '',
           'querysharegroup' => 'editbugs',
           'quip_list_entry_control' => 'moderated',
           'rememberlogin' => 'on',
           'requirelogin' => '0',
           'search_allow_no_criteria' => 1,
           'shadowdb' => '',
           'shadowdbhost' => '',
           'shadowdbport' => '3306',
           'shadowdbsock' => '',
           'shutdownhtml' => '',
           'smtp_debug' => '0',
           'smtp_password' => '',
           'smtp_ssl' => '0',
           'smtp_username' => '',
           'smtpserver' => 'mail.puremagic.com',
           'ssl_redirect' => '1',
           'sslbase' => 'https://issues.dlang.org/',
           'strict_isolation' => 0,
           'strict_transport_security' => 'off',
           'timetrackinggroup' => '',
           'upgrade_notification' => 'latest_stable_release',
           'urlbase' => 'https://issues.dlang.org/',
           'use_mailer_queue' => '1',
           'use_see_also' => 1,
           'useclassification' => 0,
           'usemenuforusers' => '0',
           'useqacontact' => 0,
           'user_info_class' => 'CGI',
           'user_verify_class' => 'DB',
           'usestatuswhiteboard' => 0,
           'usetargetmilestone' => 0,
           'usevisibilitygroups' => 0,
           'utf8' => 1,
           'webdotbase' => '/usr/bin/dot',
           'whinedays' => 7
         );

On Thursday, 22 June 2023 at 20:48:25 UTC, Brad Roberts wrote:
> I don't understand why you need that key or to mess with users accounts or passwords at all.  That sounds like a pretty major security and trust violation to me.

Well, because the ultimate goal is moving the entire installation, and making it seamless. The DFL needs access to the key for the same reason that you have access to the key right now.

If you don't want *me* to have access to the key, that's fine, I can work with someone else from the DFL on a IaC setup where I don't have access to production data, but let's clear up where the problem is first?

If it helps, I run the D forum and wiki, so not much would change in the trust model.

> data/params is all available in the ui, but here:

Thanks! It's good to have it in text form anyway.

On Thu, Jun 22, 2023 at 02:48:09PM -0600, Jonathan M Davis via Digitalmars-d wrote:
> On Thursday, June 22, 2023 2:12:34 PM MDT Vladimir Panteleev via Digitalmars-d wrote:
> > 2. Ideologically, it's an uphill battle as almost everyone just wants to use GitHub, and would not prefer to use Bugzilla no matter how good it is.
> 
> I've never understood why some folks have kept pushing for us to use github issues. They're nice if you're setting up a github repo and don't want to go to the trouble of setting up and hosting a bugzilla instance elsewhere, but they're not as sophisticated as bugzilla.
[...]

Personally I also prefer to use Bugzilla.  I find GH's UI rather klunky to use, esp. when it comes to searching for specific things.

But since the move to GH seems inevitable, I guess I'll just cope with it. It's not a big deal.


T

-- 
I've been around long enough to have seen an endless parade of magic new techniques du jour, most of which purport to remove the necessity of thought about your programming problem.  In the end they wind up contributing one or two pieces to the collective wisdom, and fade away in the rearview mirror. -- Walter Bright

On Thursday, 22 June 2023 at 20:48:09 UTC, Jonathan M Davis wrote:
> but they're not as sophisticated as bugzilla.

Though GitHub seems to have a more sophisticated spam “protection” strategy than straight out blocking all Gmail addresses.

Feel free to choose whether
- those in charge didn’t bother to fix it resp. where unavailable
- or were unable/incapable to fix.
That makes no difference. There’ve been complaints about this policy for years. And effectively, they fell on deaf ears – in terms of outcome.

Getting people to create yet another account (for the Bugzilla instance) is one thing, forcing them to create an additional email account is another. From that perspective I’d say, GitHub issues is a huge win for us all.

On Thursday, 22 June 2023 at 21:40:34 UTC, Elias wrote:
> On Thursday, 22 June 2023 at 20:48:09 UTC, Jonathan M Davis wrote:
>> but they're not as sophisticated as bugzilla.
>
> Though GitHub seems to have a more sophisticated spam “protection” strategy than straight out blocking all Gmail addresses.
>
> Feel free to choose whether
> - those in charge didn’t bother to fix it resp. where unavailable
> - or were unable/incapable to fix.
> That makes no difference. There’ve been complaints about this policy for years. And effectively, they fell on deaf ears – in terms of outcome.

I'm sorry about banning Gmail addresses. It was the best way to stop the flood of spam that I could find at the time. I only have limited access to the Bugzilla server, and Brad was too busy with other things to do something more sophisticated.

> From that perspective I’d say, GitHub issues is a huge win for us all.

On newer Bugzilla versions, you can log in with your GitHub account. You can try it on https://bugzilla.mozilla.org/.

The crude spam measures like the Gmail ban would also hopefully not be needed once the DLF runs the Bugzilla instance.