Skip to content

docs: update links and improve wording in contributing.md and python_style.md#248

Open
Kunal241207 wants to merge 3 commits intosugarlabs:masterfrom
Kunal241207:docs-update-contributing-python-style
Open

docs: update links and improve wording in contributing.md and python_style.md#248
Kunal241207 wants to merge 3 commits intosugarlabs:masterfrom
Kunal241207:docs-update-contributing-python-style

Conversation

@Kunal241207
Copy link
Contributor

Changes include:

  • Fix a broken Markdown link in contributing.md
  • Update deprecated Github help links to current docs.github.com links
  • Fix minor grammar and formatting issues
  • Minor wording improvements in python-style.md

Copy link
Contributor

@quozl quozl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't like what you've suggested. I suspect you don't speak from experience, you joined GitHub in August.

# Contributing

This is our guide to contributing code. In brief, you will:
This is our guide to contributing code. In brief, you will:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unnecessary.

Blocks, or one of the hundreds of learning activities,
* use the software, so that you know from direct experience what to
change,
* fork the source repository and set it up on your system;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unnecessary duplication of a step in workflow section.

Make your own decision on what to do.

Do not ask permission to work.
You do not need to ask permission to work.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Disagree with your change; we so frequently receive questions about permission to work that we need to be very clear that we do not welcome this.

* [ ] if there is a `po/*.pot` file, regenerate using `python setup.py genpot`, review the changes, and commit,

* [ ] If the activity is on [weblate](weblate.sugarlabs.org), check to make sure that the changes on weblate are also on the repo
* [ ] If the activity is on [weblate](https://weblate.sugarlabs.org), check to make sure that the changes on weblate are also on the repo
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree, but trivial.

a rebuild of the static site using `rebuild-aslo` command, verify if your bundle is
visible on https://v4.activities.sugarlabs.org . For more information, it is
recommended to take a look at the [Activities4 wiki page](https://wiki.sugarlabs.org/go/Service/activities4)
recommended to take a look at the [Activities4 wiki page](https://wiki.sugarlabs.org/go/Service/activities4)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unnecessary change.

This step is needed only once for each repository.
See [complete help in GitHub](https://help.github.com/articles/fork-a-repo).
You should first fork a repository on GitHub.
This step is needed only once.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Disagree; the fork is needed only one for each repository, we have hundreds.

See [complete help in GitHub](https://help.github.com/articles/fork-a-repo).
You should first fork a repository on GitHub.
This step is needed only once.
See [complete help in GitHub](https://docs.github.com/en/get-started/quickstart/fork-a-repo).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unnecessary; we already linked above to documentation at GitHub.

and [D. Joe's
reply](http://lists.sugarlabs.org/archive/sugar-devel/2017-March/053929.html).
changes, then push.
See related discussions in the sugar-devel mailing list archive for more details.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Disagree; this discussion is out of date.

---------

* New code should be written in Python 3, using GTK+ 3, GStreamer 1.0, etc
* New code should be written in Python 3 and use GTK 3, GStreamer 1.0, etc
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Disagree; we should be targeting GTK 4 by now.

-----------

* Methods documentation should be "attached" to the methods (See http://www.python.org/dev/peps/pep-0257)
* Methods documentation should be attached directly to the methods (See http://www.python.org/dev/peps/pep-0257)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unnecessary change.

@Kunal241207
Copy link
Contributor Author

@quozl Thanks for the review. I understand the concerns. I don’t yet have enough project experience as I’m still gaining familiarity with the project. I’ll revert the unnecessary wording changes and keep only the objective fixes (broken links and corrections).

@Kunal241207
Copy link
Contributor Author

Kunal241207 commented Feb 14, 2026

Hi @quozl, gentle follow-up in case this slipped through notifications.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants