This is an automated email from the git hooks/post-receive script.
git pushed a commit to branch master
in repository www-content.
View the commit online.
commit 1536a327fc0322d222048f07bd6b3747640a6123
Author: Carsten Haitzler (Rasterman) <[email protected]>
AuthorDate: Sun May 8 12:30:44 2022 +0100
remove more phab refs
---
pages/contrib/devs/git-guide.md.txt | 225 ++++++------------------------------
pages/contrib/devs/start.md.txt | 10 +-
pages/contrib/report-bug.md.txt | 10 +-
pages/contrib/start.txt | 51 ++++++--
4 files changed, 83 insertions(+), 213 deletions(-)
diff --git a/pages/contrib/devs/git-guide.md.txt b/pages/contrib/devs/git-guide.md.txt
index e5a174ea6..9b7443fe2 100644
--- a/pages/contrib/devs/git-guide.md.txt
+++ b/pages/contrib/devs/git-guide.md.txt
@@ -5,33 +5,47 @@
# Git Best Practices #
-This document provides advice and guidance on using and contributing to the Enlightenment Project git repositories. Please read through this document before providing pull requests, patches, or working on a repository for the first time.
+This document provides advice and guidance on using and contributing to the
+Enlightenment Project git repositories. Please read through this document
+before providing pull requests, patches, or working on a repository for the
+first time.
-A web interface to the Enlightenment Foundation repositories is available at [git.enlightenment.org](https://git.enlightenment.org/).
+A web interface to the Enlightenment Foundation repositories is available at
+[git.enlightenment.org](https://git.enlightenment.org/).
## Prerequisites ##
-You will require ``git`` to be installed. Linux distributions using the ``apt`` package manager can install this prerequisite with the following command:
+You will require ``git`` to be installed. Linux distributions using the
+``apt`` package manager can install this prerequisite with the following
+command:
```
sudo apt install git
```
-You are also expected to already possess a working knowledge of git; for more information see the [Git User Manual](https://git-scm.com/docs/user-manual.html). You should also have read the [Coding Conventions guide](https://www.enlightenment.org/contrib/devs/coding-conventions.md) before writing any code destined for submission.
+You are also expected to already possess a working knowledge of git;
+for more information see the
+[Git User Manual](https://git-scm.com/docs/user-manual.html). You should
+also have read the
+[Coding Conventions guide](https://www.enlightenment.org/contrib/devs/coding-conventions.md)
+before writing any code destined for submission.
## Submitting and Reviewing Patches ##
-For information about the patch review process see the [Patch Submission and Review with Arcanist guide](arcanist-guide.md)
+Use [https://git.enlightenment.org](Gitea) to fork a repository and create
+pull requests for changes on the original.
## Rebase Instead of Merge ##
-Ensure that you have git set to rebase, rather than merge, by running the following command against your copy of the Enlightenment repository.
+Ensure that you have git set to rebase, rather than merge, by running the
+following command against your copy of the Enlightenment repository.
```
$ git config branch.master.rebase true
```
-You can also make this configuration globally, but be aware this applies to all git repositories you access:
+You can also make this configuration globally, but be aware this applies to
+all git repositories you access:
```
$ git config --global branch.master.rebase true
@@ -39,7 +53,10 @@ $ git config --global branch.master.rebase true
## Commit Messages ##
-Commit messages should be detailed rather than terse and include as much information about the commit as is reasonable. Please use the imperative form in the commit message in order to be consistent with the commit messages generated by git merge and revert. Write "Fix text bug", rather than "Fixed text bug".
+Commit messages should be detailed rather than terse and include as much
+information about the commit as is reasonable. Please use the imperative
+form in the commit message in order to be consistent with the commit
+messages generated by git merge and revert. Write "Fix text bug", rather than "Fixed text bug".
### Message Layout ###
@@ -51,14 +68,17 @@ The general layout of a commit message should be as follows:
### Message Tags ###
-Depending on the nature of your commit some of the following tags might apply:
+Depending on the nature of your commit some of the following tags might
+apply:
* **@fix** - To be used when you fixed a bug which also applies to a released version (i.e. is not exclusively code from this development cycle). This tag is used as a marker for backports, although commits can be tagged as @fix but not backported if the backport is too "dangerous" to be in the stable branch - for example a fix that required some core rewrites.
* **@feature** - To be used when your commit introduces a new feature. Make sure your summary line is in really good shape and descriptive as this will be used in the NEWS file for the release. If this change consists of more than one commit only put it once - or, better yet, put it in the merge commit.
* **CID: XXXXX** - To be used if you fixed a issue discovered by a Coverity scan. It gives credit to them and helps us to see which commit relates to which issue.
-* **Fixes TXXX** - Add a Phab ticket number if you fix a bug being tracked in [Phab](https://phab.enlightenment.org/).
-All these tags should live in the commit body with the detailed description, and not in the summary line. It is preferred if the tags are added as a separate line at the end of the commit message, though they will function from anywhere in the commit body.
+All these tags should live in the commit body with the detailed description,
+and not in the summary line. It is preferred if the tags are added as a
+separate line at the end of the commit message, though they will function
+from anywhere in the commit body.
### Simple Message Example ###
@@ -88,14 +108,15 @@ evas textblock: Fix buffer overflow in anchor code
If we set the anchor on a long text block the buffer might overflow.
Take string len into account. Long-standing bug.
-Fixes T2222
@fix
CID: 123456
```
## Merging Changes Back into Master ##
-Use cherry-pick for small changes if you don't want to push everything into master. If you did work into your own branch and worked on some big feature then you should push to master using the following workflow:
+Use cherry-pick for small changes if you don't want to push everything
+into master. If you did work into your own branch and worked on some big
+feature then you should push to master using the following workflow:
1. Create a branch, either local or remote, for your change.
2. Work on that branch.
@@ -106,189 +127,13 @@ Use cherry-pick for small changes if you don't want to push everything into mast
8. Describe your feature in the commit message.
9. Push to master using ``git push`` or ``git push origin master``.
-## Repository layout ##
-
-The Enlightenment git repository is laid out in the following manner.
-
-### Main Branches ###
-
-The official branches are:
-
-* master - This is where all new work goes.
-* {name}-{version} (e.g. "efl-1.8") - The stabilization branch for a specific version.
-
-### Developer Branches ###
-
-Every developer can create their own branches inside a repository. The naming must be ``devs/{devname}/*`` where ``{devname}`` is your user name (the directory name in the devs repository).
-
-These branches can be used if you're implementing a larger feature and want to share your progress with other developers.
-
-#### Creating a Developer Branch ####
-
-Create a developer branch by pushing it to the remote repository:
-
-```
-$ git push --set-upstream origin devs/{devname}/{branch}
-```
-
-#### Deleting a Developer Branch ####
-
-Pass the ``--delete`` option to ``git-push`` to delete a developer branch:
-
-```
-$ git push origin --delete devs/{devname}/{branch}
-```
-
-### Feature Branches ###
-
-Anyone with full commit access can create, manage, or delete a feature branch for a repository. The naming must be ``feature/{name}`` where ``{name}`` is the name of the feature. Feature branches can be pushed to by anyone with any form of commit access (including probies), but they cannot be rewritten (ie. no ``rebase -i``).
-
-The purpose of a feature branch is to continue the collaborative development of a feature which has already reached the state of being functional during initial development in a developer branch; feature branches should be considered the "alpha release" state for any significant feature prior to merging it to master.
-
-Feature branches will be automatically built by jenkins, and any build failures will be emailed to everyone who has any commits in the branch.
-
-Creating and managing feature branches is identical to the management of developer branches with only the name of the branch being changed.
-
-## Developer Repositories ##
-
-If you are starting a new project, or just trying something out that doesn't belong to any of the existing repositories, you can create your own developer repository.
-
-### Creating a Developer Repository ###
-
-Create a new develop repository by using ``git clone``:
-
-```
-$ git clone ssh://[email protected]/devs/{devname}/foo.git
-```
-
-### Setting the Description ###
-
-In order for the [Repository Web Interface](https://git.enlightenment.org) to show a meaningful description set it with ``gitolite``'s ``desc`` command:
-
-```
-$ ssh [email protected] desc devs/{devname}/foo "Foo repository does bar"
-```
-
-### Deleting a Developer Repository ###
-
-Delete a developer repository using ``gitolite``'s ``trash`` command:
-
-```
-$ ssh [email protected] D trash devs/{devname}/foo
-devs/{devname}/foo moved to trashcan. Please run the 'help' adc for more info.
-```
-
-Please note you need to use the repository name without .git at the end when running the ``trash`` command.
-
-### Listing Deleted Developer Repositories ###
-
-To list the currently deleted repositories type:
-
-```
-$ ssh [email protected] D list-trash
-devs/{devname}/foo/2017-02-18_09:48:08
-```
-
-### Restoring Deleted Developer Repositories ###
-
-To restore a previously deleted repository:
-
-```
-$ ssh [email protected] D restore
-devs/{devname}/foo/2017-02-18_09:48:08
-```
-
-### Gitolite Help ###
-
-Access ``gitolite``'s general help by typing:
-
-```
-$ ssh [email protected] help
-```
-
-Drill down to command-specific help with -h:
-
-```
-$ ssh [email protected] desc -h
-```
-
-## Useful Aliases ##
-
-The following git aliases can be used on any project and are designed to help with working on a central git repository. These aliases can be set in your global configuration by running the command ``git config``.
-
-### up ###
-
-Update the current branch.
-
-```
-$ git config --global alias.up "pull --rebase"
-```
-
-This alias makes git work like svn: it will fetch and rebase your code on the current branch.
-
-### up-master ###
-
-Update master without checking it out.
-
-```
-$ git config --global alias.up-master "fetch origin master:master"
-```
-
-This alias updates the master branch from upstream even if the currently checked out branch is not master. This is useful when you work on a branch and want to rebase on top of upstream's master.
-
-### wu ###
-
-"What's up" report.
-
-```
-$ git config --global alias.wu "log --reverse --stat @{upstream}..HEAD"
-```
-
-This alias shows the commits you're about to push upstream.
-
-### wup ###
-
-"What's up" report with patch information.
-
-
-```
-$ git config --global alias.wup "log --reverse --stat -p @{upstream}..HEAD"
-```
-
-This alias shows the commits you're about to push upstream and their contents.
-
-### wus ###
-Shortened "what's up" report.
-
-```
-$ git config --global alias.wus "log --reverse --oneline @{upstream}..HEAD"
-```
-
-A terse version of the "what's up" alias which shows the commits to push using single-line formatting.
-
-### safepush ###
-
-Push after reviewing which commits will be sent.
-
-```
-$ git config --global alias.safepush '![[ `git wus |wc -l` > 0 ]] && ( git wus && echo -n "Push to `git rev-parse --symbolic-full-name @{upstream}` [y/N]\\ " && read y && ( [[ $y =~ [yY] ]] && git push ) || true ) || echo "Nothing to push."'
-```
-
-This alias tells you what commits you're about to push and asks for confirmation before pushing. This can help you avoid mistakes when pushing stuff out in the wild.
-
## Further Reading ##
[git.enlightenment.org](https://git.enlightenment.org/)
: A web interface to the Enlightenment git repositories.
-[Patch Submission and Review with Arcanist ](arcanist.md)
-: Information on the patch submission and review process.
-
[[email protected]](mailto:[email protected])
: The mailing list for git assistance requests.
-[phab.enlightenment.org](https://phab.enlightenment.org/)
-: The Enlightenment Phab ticket tracking system.
-
[wiki.openstack.org/wiki/GitCommitMessages#Summary_of_Git_commit_message_structure](https://wiki.openstack.org/wiki/GitCommitMessages#Summary_of_Git_commit_message_structure)
: The Openstack Project's guide to what information should be in a commit message.
@@ -299,4 +144,4 @@ This alias tells you what commits you're about to push and asks for confirmation
: The VideoLAN Project uses the same workflow as the Enlightenment Project.
[Coding Conventions](https://www.enlightenment.org/contrib/devs/coding-conventions.md)
-: Rules to which code submitted to the Enlightenment Project must adhere.
\ No newline at end of file
+: Rules to which code submitted to the Enlightenment Project must adhere.
diff --git a/pages/contrib/devs/start.md.txt b/pages/contrib/devs/start.md.txt
index e0a7eeff9..617c05d23 100644
--- a/pages/contrib/devs/start.md.txt
+++ b/pages/contrib/devs/start.md.txt
@@ -32,23 +32,21 @@ The Enlightenment Project uses the *git* version control system to manage its co
A web interface to the git repositories is also available at [git.enlightenment.org](https://git.enlightenment.org/) allowing for easy browsing and search.
-## Phabricator Ticket System ##
+## Bugs ##
-If you're looking for an issue to solve, the [Phabricator Ticketing System](https://phab.enlightenment.org/) tracks all the outstanding tasks relating to the Enlightenment, Enlightenment Foundation Libraries (EFL), Elementary, and Terminology code bases.
+If you're looking for an issue to solve, the [Gitea](https://git.enlightenment.org/) tracks all the outstanding tasks relating to the Enlightenment, Enlightenment Foundation Libraries (EFL), Elementary, and Terminology code bases.
## Patch Submission and Review ##
-New contributors to the project are required to submit their patches through the Arcanist system, which automatically brings them through to the Phabricator Ticket System for tracking and review. The [Patch Submission and Review with Arcanist guide](https://www.enlightenment.org/contrib/devs/arcanist-guide.md) explains how to install, configure, and use Arcanist to submit patches for review.
+New contributors to the project should try use [Gitea](https://git.enlightenment.org), and create a pull request for review.
## Testing and Debugging ##
Before submitting code to the Enlightenment git repositories, mailing list, or through the [patch submission process](#Patch_Submission_and_Review), always test it for errors using both positive (expected values/behavior) and negative (unexpected values/behavior) tests. Run your code inside ``valgrind`` to ensure its memory access is correct and it does not leak.
-More information on debugging is avaialble on the [Phabricator wiki](https://phab.enlightenment.org/w/debugging/).
-
## Editors ##
-Advice on tailoring particular editors for ease of use during Enlightenment development can be found on the Phabricator wiki, presented here in alphabetical order:
+Advice on tailoring particular editors for ease of use during Enlightenment development can be found below.
* [Eclipse](https://phab.enlightenment.org/w/ecoding/eclipse/)
* [Emacs](https://phab.enlightenment.org/w/ecoding/emacs/)
diff --git a/pages/contrib/report-bug.md.txt b/pages/contrib/report-bug.md.txt
index eb6c7b142..86a684bd2 100644
--- a/pages/contrib/report-bug.md.txt
+++ b/pages/contrib/report-bug.md.txt
@@ -11,7 +11,7 @@ Please remember these key guidelines for a good bug report:
* Be precise.
* Be clear.
* Only detail one bug per report.
-* Only report a bug [on the Phabricator ticketing system](https://phab.enlightenment.org/maniphest/task/edit/form/2/).
+* Only report a bug [Gitea](https://git.enlightenment.org/issues).
* Re-read the report prior to submission.
## Before Reporting a Bug ##
@@ -24,7 +24,7 @@ Try to reproduce the bug with the latest version of the software. If you are run
### Checking for Existing Reports ###
-Check the [Phabricator ticketing system](https://phab.enlightenment.org/maniphest/query/all) to see if your bug has already been reported. If you find no existing report, please create one.
+Check the [Gitea](https://git.enlightenment.org/issues) to see if your bug has already been reported. If you find no existing report, please create one.
### Notes on Visual Bugs ###
@@ -34,11 +34,11 @@ If reporting a visual bug please make absolutely sure you test under the default
If you have gathered a large quantity of output traces during debugging, please attach them to your ticket as file uploads rather than by pasting them into the comment itself. For more information on debugging, please consult [Debugging EFL Applications](/develop/debug/start.md), [EFL Debugging](/contrib/efl-debug) and [Enlightenment Debugging](/contrib/enlightenment-debug.md).
-## Reporting a Bug via Phabricator ##
+## Reporting a Bug ##
-Only report bugs in the [Phabricator ticketing system](https://phab.enlightenment.org/maniphest/task/edit/form/2/). Please don't send bug reports and patches to the Enlightenment mailing list, as there is a good chance your report will be lost. If there is more discussion needed around the issue, add a bug report to Phabricator before or after carrying out a discussion on the mailing list.
+Only report bugs in the [Gitea](https://git.enlightenment.org/issues). Please don't send bug reports and patches to the Enlightenment mailing list, as there is a good chance your report will be lost. If there is more discussion needed around the issue, add a bug report before or after carrying out a discussion on the mailing list.
-The workflow for reporting a bug is as follows: go to the [Phabricator ticketing system](https://phab.enlightenment.org/maniphest/task/edit/form/2/), and fill out at least the following fields:
+The workflow for reporting a bug is as follows: go to the [Gitea](https://git.enlightenment.org/issues), and fill out at least the following fields:
* Title - A short one-sentence summary that explains the problem clearly and precisely.
* Assigned To - Leave blank, as the developers will set an assignee.
diff --git a/pages/contrib/start.txt b/pages/contrib/start.txt
index ab0e7ba26..52720dd67 100644
--- a/pages/contrib/start.txt
+++ b/pages/contrib/start.txt
@@ -2,23 +2,50 @@
====== How to Contribute to EFL and Enlightenment ======
-Whether you're an end-user or a developer there are ways to get involved in the Enlightenment Project. Below you'll find various ways you can help out, from offering your time to improve the project's documentation or provide patches to offering to maintain the servers or supply hardware for development and testing.
+Whether you're an end-user or a developer there are ways to get involved in
+the Enlightenment Project. Below you'll find various ways you can help out,
+from offering your time to improve the project's documentation or provide
+patches to offering to maintain the servers or supply hardware for
+development and testing.
-However you want to contribute, know that your contribution will always be warmly received and go towards making the Enlightenment Project the best it can possibly be.
+However you want to contribute, know that your contribution will always
+be warmly received and go towards making the Enlightenment Project the
+best it can possibly be.
-Information on the current status of Enlightenment Project development, along with a list of open issues requiring attention, can be found on the [[https://phab.enlightenment.org/|Phabricator Ticket System]]. Assistance with any and all of the listed tickets is always welcome.
+Information on the current status of Enlightenment Project
+development, along with a list of open issues requiring attention, can
+be found on [[https://git.enlightenment.org/|Gitea]]. Assistance with
+any and all of the listed tickets is always welcome.
===== Contributing Time =====
-If you have free time help is always welcome, with a variety of areas suited to different skill sets.
-
-If you have development skills you'll find ways to contribute in the [[https://www.enlightenment.org/contrib/devs/start.md|Developer Contributions section]], from resolving issues raised in the [[https://phab.enlightenment.org/|Phabricator Ticket System]] to [[https://www.enlightenment.org/contrib/devs/arcanist-guide.md|submitting and reviewing patches]]. You'll also find information for joining the official IRC channels and mailing lists, where you can ask for assistance in getting star [...]
-
-If you have good written skills you'll find guidelines for contributing to project documentation in the [[https://www.enlightenment.org/contrib/docs/start.md|Documentation Contributions section]]. Whether you want to write lengthy tutorials or simply fix a spelling mistake, your assistance will always be gratefully received.
-
-Other skill sets, including translators to assist with bringing the Enlightenment ecosystem to as many users in their native languages as possible and designers to work on new Enlightenment and application themes, are welcome to contribute too. Join the [[/contact|official IRC channel]] and ask how you can help.
-
-Terminology has been translated into several languages already. If your language is missing or incomplete, please use [[https://hosted.weblate.org/engage/terminology/|Weblate]] to help translate Terminology.
+If you have free time help is always welcome, with a variety of areas
+suited to different skill sets.
+
+If you have development skills you'll find ways to contribute in the
+[[https://www.enlightenment.org/contrib/devs/start.md|Developer
+Contributions section]], from resolving issues raised in
+[[https://git.enlightenment.org|Gitea]] and submitting changes. You'll also
+find information for joining the official IRC channels and mailing lists,
+where you can ask for assistance in getting started with the Enlightenment
+code base and receive feedback on your proposals.
+
+If you have good written skills you'll find guidelines for contributing
+to project documentation in the
+[[https://www.enlightenment.org/contrib/docs/start.md|Documentation Contributions section]].
+Whether you want to write lengthy tutorials or simply fix a spelling
+mistake, your assistance will always be gratefully received.
+
+Other skill sets, including translators to assist with bringing the
+Enlightenment ecosystem to as many users in their native languages as
+possible and designers to work on new Enlightenment and application themes,
+are welcome to contribute too. Join the [[/contact|official IRC channel]]
+and ask how you can help.
+
+Terminology has been translated into several languages already. If your
+language is missing or incomplete, please use
+[[https://hosted.weblate.org/engage/terminology/|Weblate]] to help
+translate Terminology.
===== Contributing Financially =====
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
