GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Status review for unfinished articles · Issue #416 · javascript-tutorial/pt.javascript.info

Status review for unfinished articles #416

New issue
Copy link
New issue
Copy link
Closed as not planned
Closed as not planned
Status review for unfinished articles#416
Copy link

Description

@peruibeloko
peruibeloko
opened on Jan 7, 2024
Issue body actions

I went over the translation checklist and classified each item in one of three categories:

  • Unchecked: Item is present in the master branch but not marked as done
  • Abandoned: Item has work present on a fork but the PR is either closed or absent
  • Untouched: Item is assigned to someone but it wasn't worked on at all

And this is the current status:

Item Status
Basic operators, math Unchecked (#217, #412)
Loops: while and for Abandoned (#50)
Functions Untouched
Object references and copying Unchecked
Symbol type Unchecked
Numbers Untouched (under @rnrnshn)
WeakMap and WeakSet Untouched (under @wnleao)
Object.keys, values, entries Abandoned
Destructuring assignment Untouched
Date and time Untouched
JSON methods, toJSON Abandoned (#185)
Recursion and stack Abandoned
Rest parameters and spread syntax Untouched
Variable scope, closure Untouched
The old "var" Untouched
Scheduling: setTimeout and setInterval Untouched
Function binding Untouched
Property getters and setters Abandoned
Class inheritance Untouched
Static properties and methods Untouched
Extending built-in classes Abandoned (#411)
Error handling, "try...catch" Untouched
Custom errors, extending Error Abandoned
Introduction: callbacks Abandoned
Promise Untouched
Error handling with promises Untouched (under @wnleao)
Promise API Untouched
Promisification Untouched (under @wnleao)
Microtasks Untouched (under @wnleao)
Async/await Untouched
Modules, introduction Untouched
Currying Untouched
Browser environment, specs Abandoned
DOM tree Abandoned
Walking the DOM Abandoned
Attributes Review pending (broken mention @denis-rossati)
Introduction to browser events Untouched (broken mention to @cesarkohl)
Form properties and methods Untouched (broken mention to @recalderon)
Fetch Abandoned (broken mention to @vitorinoaraujo)
Bezier curve Abandoned (broken mention to @lucastrvsn)
JavaScript animations Abandoned (broken mention to @karlasamantha)
Template element Untouched (broken mention to @HakaCode)

We can solve some of these problems as such:

  • Abandoned articles can be resumed through a new PR
  • Untouched articles assigned over a certain period (6 months, 1 year) can be safely unassigned and reopened for translation
  • Unchecked articles can be safely checked for updated tracking

What does everyone think?

Activity

  1. odsantos commented on Jan 7, 2024

    @odsantos
    odsantos
    on Jan 7, 2024
    Contributor
    More actions

    @peruibeloko I agree but we probably need to be sure that Untouched topics have no PR, so three months might also be a good waiting period. Thanks.

  2. peruibeloko commented on Jan 7, 2024

    @peruibeloko
    peruibeloko
    on Jan 7, 2024
    ContributorAuthor
    More actions

    @odsantos most of the Untouched topics are months or years out of date with master. I can go over them and append the age of the assignment if you'd like

  3. odsantos commented on Jan 7, 2024

    @odsantos
    odsantos
    on Jan 7, 2024
    Contributor
    More actions

    @peruibeloko no, there is no need, as long as no work is present this seems good. Thanks.

    Reacted by Carlinhos
  4. peruibeloko commented on Jan 7, 2024

    @peruibeloko
    peruibeloko
    on Jan 7, 2024
    ContributorAuthor
    More actions

    Glad to help, let me know if you need anything!

  5. HakaCode commented on Jan 7, 2024

    @HakaCode
    HakaCode
    on Jan 7, 2024
    Contributor
    More actions

    @peruibeloko @odsantos

    I will arrange it as soon as possible, I had forgotten to translate, thank you for reminding me.

    Reacted by Carlinhos
  6. peruibeloko commented on Jan 7, 2024

    @peruibeloko
    peruibeloko
    on Jan 7, 2024
    ContributorAuthor
    More actions

    @HakaCode thanks! Just a quick reminder to keep the PR contained to the specific as article you're translating!

    Reacted by William Constantinov
  7. HakaCode commented on Jan 7, 2024

    @HakaCode
    HakaCode
    on Jan 7, 2024
    Contributor
    More actions

    @peruibeloko @odsantos I think now I just wait for it to be reviewed and accepted.

  8. danilolmc commented on Jan 8, 2024

    @danilolmc
    danilolmc
    on Jan 8, 2024
    Contributor
    More actions

    Hey guys!

    About the Extending built-in classes article, I'm now just waiting a review in the #413 PR

    I also translated these two articles below, but they are unchecked even thought I created their pull request with their article titles:

    • Object references and copying Object references and copying #408
    • Symbol type Symbol type #409

    How can I mark them as checked?

  9. peruibeloko commented on Jan 8, 2024

    @peruibeloko
    peruibeloko
    on Jan 8, 2024
    ContributorAuthor
    More actions

    @danilolmc I didn't include your class extension article since I remember seeing you picking it one of these days.

    Marking them as done is probably restricted to either the bot or @iliakan

  10. danilolmc commented on Jan 8, 2024

    @danilolmc
    danilolmc
    on Jan 8, 2024
    Contributor
    More actions

    Great, thank you! @peruibeloko

    Reacted by Carlinhos
  11. jonnathan-ls commented on Jan 13, 2024

    @jonnathan-ls
    jonnathan-ls
    on Jan 13, 2024
    Contributor
    More actions

    Abandoned articles can be resumed through a new PR

    Instead of reopening the PR, we could contribute directly to it (PR number), and if the user's branch or repository is protected, then the task goes on to be reopened in a new PR, what do you think?

    In reviews, I'm looking to contribute by adding commits directly to the user's forked repository that is associated with the PR, instead of just registering my comments for simple things, trying to speed up the merge process, instead of waiting for the user's response that may have abandoned the PR

  12. jonnathan-ls commented on Jan 13, 2024

    @jonnathan-ls
    jonnathan-ls
    on Jan 13, 2024
    Contributor
    More actions

    Hey guys!
    ...
    How can I mark them as checked?

    @danilolmc

    My deduction, the bot apparently did not act on the PRs because the merger was apparently carried out without following the necessary review steps (review and approval process) and perhaps because it failed to mark the PR's hash on the list due to absences in the approval and registration procedures of the task on behalf of the person.

    Marking them as done is probably restricted to either the bot or iliakan

    Maintainers have the permission to update PR #1.

    I have updated the list considering the PRs have been completed.

  13. jonnathan-ls commented on Jan 13, 2024

    @jonnathan-ls
    jonnathan-ls
    on Jan 13, 2024
    Contributor
    More actions

    I agree but we probably need to be sure that Untouched topics have no PR, so three months might also be a good waiting period. Thanks.

    I agree with 03 months instead of 06, we need agility and evolution of this repository instead of waiting for PRs that haven't even been touched yet.

  14. savionascimentodev commented on Jan 14, 2024

    @savionascimentodev
    savionascimentodev
    on Jan 14, 2024
    More actions

    Hello everyone, I would really like to contribute to this repository, but I'm kind of new to open source projects, I saw that there are a lot of PRs open and after this list that @peruibeloko sent, it gave me a little idea, but if I want to contribute , is there anyone active I can talk to?

    Note: Or I just raise a Pr and who knows, one day it will be approved.

  15. danilolmc commented on Jan 14, 2024

    @danilolmc
    danilolmc
    on Jan 14, 2024
    Contributor
    More actions

    Hey @savionascimentodev !

    You can take a look at #1 issue.

    Hope it can help you...

    Reacted by Savio Nascimento
  16. peruibeloko commented on Jan 14, 2024

    @peruibeloko
    peruibeloko
    on Jan 14, 2024
    ContributorAuthor
    More actions

    @savionascimentodev Seja bem-vindo mano!

    O processo é bem simples:

    • Escolha um capítulo para traduzir na lista da issue Portuguese Translation Progress #1
    • Comente o nome exato do capitulo
    • Crie um fork do repositório
    • Contribua!

    Esse é o resumo executivo, posso te auxiliar lá no #1 diretamente, já que aqui é mais voltado para outro assunto :D

    Reacted by Savio Nascimento and Jonnathan Lacerda Santos
  17. peruibeloko commented on Jan 25, 2024

    @peruibeloko
    peruibeloko
    on Jan 25, 2024
    ContributorAuthor
    More actions

    Vou fechar essa issue, já que conseguimos trazer atenção ao problema e movimentamos o #1

    Reacted by Jonnathan Lacerda Santos
  18. peruibeloko
    closed this as not plannedon Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.