Talk:Android Debug Bridge/GA1

Latest comment: 2 years ago by PhotographyEdits in topic GA Review

GA Review

edit

Article (edit | visual edit | history) · Article talk (edit | history) · Watch

Reviewer: Rusalkii (talk · contribs) 18:24, 30 November 2021 (UTC)Reply


I'm a first time reviewer, so I intend to ask for a more experienced review to look this over once the review is complete.

Initial thoughts: the article seems sparse for a GA. No illustrations but the one in the infobox, at this size I would want one or two more; perhaps an image of ADB in use? Architecture section is two sentences and should be significantly expanded or merged elsewhere, preferably expanded. Rusalkii (talk) 18:24, 30 November 2021 (UTC)Reply

GA review (see here for what the criteria are, and here for what they are not)
  1. It is reasonably well written.
    a (prose, spelling, and grammar):   b (MoS for lead, layout, word choice, fiction, and lists):  
    A: Okay. I made a couple minor grammar/phrasing edits myself, and left comments below on what is confusing or otherwise should be rewritten.
    B: Generally good. A couple weasel words mentioned below should be fixed with more specific phrasings.
  2. It is factually accurate and verifiable.
    a (reference section):   b (citations to reliable sources):   c (OR):   d (copyvio and plagiarism):  
    Copyvio: Earwig gives 6.5% similarity, with a couple sentences in the security section resembling this source. Could be rewritten but seems okay.
  3. It is broad in its coverage.
    a (major aspects):   b (focused):  
    A: See below. The purpose of ADB could be addressed more directly, as well as the creator/origin of the tool.
    B: Well focused, avoids going into excess detail or trivia.
  4. It follows the neutral point of view policy.
    Fair representation without bias:  
    No bias or promotional tone.
  5. It is stable.
    No edit wars, etc.:  
    Recent history since August split from Android software development#Android Debug Bridge (ADB) has been almost entirely steady improvements by nominator PhotographyEdits, with a single incident of minor vandalism.
  6. It is illustrated by images and other media, where possible and appropriate.
    a (images are tagged and non-free content have fair use rationales):   b (appropriate use with suitable captions):  
    Own work screenshot and public domain logo. Could do with more images, but I couldn't find any in commons or appropriately licences after a quick search.
  7. Overall:
    Pass/Fail:  


Comments

edit

Lead

edit

Features

edit

History

edit

Enablement

edit

Architecture

edit

Security

edit
  • I added a paragraph to divide RageAgainstTheCage and the unnamed next vulnerability. It's unclear if the new second paragraph describes one vulnerability or several. Clarify and/or split into paragraphs. Rusalkii (talk) 23:44, 30 November 2021 (UTC)Reply


General

edit

Sources

edit
  • All nontrivial statements are cited, no sources in lead. Rusalkii (talk) 23:44, 30 November 2021 (UTC)Reply
  • Sources look generally okay. I'm not thrilled about the number of how to articles but none of them seem individually objectionable. Rusalkii (talk) 00:31, 1 December 2021 (UTC)Reply
  • Spotcheck that claims match sources:
    • 7 (Macworld) does not say that the 2007 release was a beta version.
    • 8 (Android Police) looks good.
    • 9 (Softpedia) looks good.
    • 18 (packages.debian.org) looks good.
    • 20 (Tech Republic) looks good.
    • 24 (Ars Technica) looks good.
    • 25 (ZDNet) is perhaps too closely paraphrased but otherwise good.

2nd opinion

edit

Rusalkii expressed a request for a second opinion on this GAN. I'm willing to provide one, so please ping me once the nominator, PhotographyEdits, has responded to Rusalkii's comments. Thanks for helping out at GAN! (t · c) buidhe 04:10, 1 December 2021 (UTC)Reply

Comment from nominator

edit
@Rusalkii Thanks for all the feedback! I will try to fix it all ASAP in the coming week. PhotographyEdits (talk) 16:31, 5 December 2021 (UTC)Reply
PhotographyEdits do you know when you might be able to finish the review? (t · c) buidhe 22:47, 27 December 2021 (UTC)Reply
@Buidhe Sorry, I have been somewhat distracted with other work. I will try to finish working through all the remaining comments in the next few days. PhotographyEdits (talk) 18:08, 1 January 2022 (UTC)Reply
I'm currently rather busy, I'll try to take a closer look as soon as possible. Rusalkii (talk) 17:16, 22 January 2022 (UTC)Reply
Totally fine, we're all volunteers with limited time here. PhotographyEdits (talk) 15:51, 24 January 2022 (UTC)Reply
Review of the updated version: The Architecture section expansion is good! Generally reads more smoothly, though there are still some rough spots in the prose. Some comments haven't been addressed, but none of them individually are make-or-break. My big concern is still criteria 3a - it feels like there are significant aspects of the program that are barely touched on. My current inclination is to say that it still needs some work before GA status.
@Buidhe: ping for that second opinion whenever you have some time. Rusalkii (talk) 15:25, 28 January 2022 (UTC)Reply
Rusalkii, I definitely think you did a great job of doing a thorough GA review, including taking the time to verify the content against the sources! Although GA does require broadness, this is a looser criterion than "comprehensiveness" required at FAC. Also, if an aspect is not covered in reliable sources, it is not expected to be included in the article, so I would be inclined to be flexible on that point. Another issue I noticed is the lifehacker source, which is marked unreliable by Headbomb's script. What makes this a reliable source? (t · c) buidhe 01:48, 29 January 2022 (UTC)Reply
So you're saying that as long as all the important aspects are touched on, it's okay for a GA to not go particularly in depth on them? I know it needs to be less thorough than a FA but obviously "less thorough" is subjective.
The first couple results here seem to lean towards unreliability but not decisively, and "how to install something" seems in Lifehacker's core competency and not particularly controversial. Also, anecdotally, I've used it for instructions like that before and found it annoyingly wordy but otherwise accurate. Rusalkii (talk) 02:50, 29 January 2022 (UTC)Reply
So you're saying that as long as all the important aspects are touched on, it's okay for a GA to not go particularly in depth on them That's my understanding as well. (t · c) buidhe 03:21, 29 January 2022 (UTC)Reply
@Buidhe @Rusalkii I have replace the Lifehacker source with a book published by CRC Press, but had to remove the aspect that it is bundled with Fastboot since that is not covered in the book paragraph. Is there any other work that needs to be done on the prose? In the meantime, I have added some more links to the lede. PhotographyEdits (talk) 14:29, 29 January 2022 (UTC)Reply
I have some minor quibbles with the prose but overall that criteria is a pass for me. If Buidhe thinks it's good to go on 3a then this is a   pass from me. Rusalkii (talk) 17:22, 29 January 2022 (UTC)Reply
Yep, I'd say it's fine to pass but of course the final decision is yours. (t · c) buidhe 18:53, 29 January 2022 (UTC)Reply
Great. Finishing the review now, congrats PhotographyEdits! Rusalkii (talk) 20:25, 29 January 2022 (UTC)Reply
@Rusalkii Thank you for reviewing and your patience. And congrats to you as well on finishing your first review! PhotographyEdits (talk) 10:24, 31 January 2022 (UTC)Reply