Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Badging System: UNIX.COM Bug Hunter Badge (New)
The Lounge What is on Your Mind? Badging System: UNIX.COM Bug Hunter Badge (New) Post 303028878 by Neo on Thursday 17th of January 2019 07:29:24 AM
Old 01-17-2019
Badging System: UNIX.COM Bug Hunter Badge (New)
I have moved the bug badge out of reserve and into the main stream. Basically, I will assign a color level like the others, based on who has made a good actionable bug report for UNIX.COM. "Good" means screenshots, links, and even details from web dev tools our the HTML source code. So far, here is the logic and current awards for this badge (with fanfare).

If your userid is not in these arrays and you think it should be, please let me know via PM (and why, including any links to any forum bugs you have reported and your bug report).

Thanks.

Code:
<?php
$debugger_L4 = array('1'); 
$debugger_L3 = array('Reserved'); 
$debugger_L2 = array('Reserved'); 
$debugger_L1 = array('37127', '302034745', '302122727'); 

if (in_array($uid, $debugger_L4)) { 
    $color['fabug'] = 'black'; 
} elseif (in_array($uid, $debugger_L3)) { 
    $color['fabug'] = 'indigo'; 
} elseif (in_array($uid, $debugger_L2)) { 
    $color['fabug'] = 'blue'; 
} elseif (in_array($uid, $debugger_L1)) { 
    $color['fabug'] = 'limegreen'; 
} else { 
    $color['fabug'] = 'lightgray'; 
}

Please do not be shy. Everyone knows I am very busy coding and developing and so if I forgot your past bug report, that does not mean you are not important, I just don't have time to go back and search all prior posts at this time. Just send me a PM or email with your GOOD well written bug report info and the forum links to it and I'm happy to add you to the "Bug Hunter" Team!
These 4 Users Gave Thanks to Neo For This Post:
Don Cragun nezabudka RavinderSingh13 rbatte1
 

3 More Discussions You Might Find Interesting

1. What is on Your Mind?

New Badging System - Badges Prototype Beta 1 (Badges Only)

Today I mapped out the new badging system using FA icons, Beta 1 in no particular order except a 6 x 8 grid: https://www.unix.com/members/1-albums215-picture991.png The prototype HTML code for this layout: <style> .fa-badge-grid { font-size: 1.5em; } .row { ... (38 Replies)
Discussion started by: Neo
38 Replies

2. Web Development

Notes with Ravinder on Badging System Development Part II

Part II: Current PHP file Beta 73 Not Optimized: <?php $version = 73; $query = "SELECT * FROM " . TABLE_PREFIX . "user WHERE userid='" . $uid . "'"; $usertable = $db->query_read_slave($query); $modaluser = $db->fetch_array($usertable); $modaluser = gmdate("d F Y", $modaluser); $modaluser... (48 Replies)
Discussion started by: Neo
48 Replies

3. What is on Your Mind?

Status of Badging System - Beta 1

Dear All, Here is the current status of the badging system: The Beta 1 phase of the new badging system is close to completion. 42 prototype badges have been "allocated" 6 prototype badge slots are held in reserve The "alert you have new badges" prototype is running and is currently... (4 Replies)
Discussion started by: Neo
4 Replies

LEARN ABOUT SUSE

fvwm-bug

fvwm-bug(1)							   Fvwm Modules 						       fvwm-bug(1)

NAME

       fvwm-bug - report a bug in fvwm

SYNOPSIS

       fvwm-bug [--help] [--version] [address]

DESCRIPTION

       fvwm-bug is a shell script to help the user compose and mail bug reports concerning fvwm in a standard format.  fvwm-bug invokes the editor
       specified by the environment variable EDITOR on a temporary copy of the bug report format outline. The user must fill  in  the  appropriate
       fields  and  exit  the  editor.	 fvwm-bug  then  mails the completed report to the local fvwm maintainer, the fvwm workers list fvwm-work-
       ers@fvwm.org, or address.  If the report cannot be mailed, it is saved in the file dead.fvwm-bug in the invoking user's home directory.

       The bug report format outline consists of several sections.  The first section provides information about the  machine,	operating  system,
       the  fvwm  version, and the compilation environment.  The second section should be filled in with a description of the bug.  The third sec-
       tion should be a description of how to reproduce the bug.  The optional fourth section is for a proposed fix.  Fixes are encouraged.

ENVIRONMENT

       fvwm-bug will utilize the following environment variables if they exist:

       EDITOR Specifies the preferred editor. If EDITOR is not set, fvwm-bug defaults to emacs.

       HOME   Directory in which the failed bug report is saved if the mail fails.

Fvwm								7 May 208 (2.5.26)						       fvwm-bug(1)
All times are GMT -4. The time now is 05:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy