Skip to content

Commit e1d204e

Browse files
committed
Update of the About information
1 parent c0c6986 commit e1d204e

1 file changed

Lines changed: 45 additions & 17 deletions

File tree

docs/about.md

Lines changed: 45 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -20,30 +20,40 @@ utPLSQL is developed 100% voluntarily and embraces a [Code of Conduct](https://g
2020

2121
Additional information can be found in the [documentation](/documentation) pages.
2222

23+
[![issues](http://img.shields.io/badge/GitHub_Project-Active-blue.svg)](https://github.com/utPLSQL/utPLSQL/issues)
24+
[![license](http://img.shields.io/badge/license-apache%202.0-blue.svg)](https://www.apache.org/licenses/LICENSE-2.0)
25+
[![GitHub Discussions](https://img.shields.io/github/discussions/utPLSQL/utPLSQL)](https://github.com/utPLSQL/utPLSQL/discussions)
26+
[![twitter](https://img.shields.io/twitter/follow/utPLSQL.svg?style=social&label=Follow)](https://twitter.com/utPLSQL)
27+
[![linkedIn](https://img.shields.io/badge/LinkedIn-Follow-blue?logo=linkedin)](https://www.linkedin.com/company/utplsql/)
2328

24-
### Version 3
29+
utPLSQL and its companion tools are open source, [hosted on GitHub](https://github.com/utPLSQL). Contributions, help
30+
and constructive feedback are always appreciated — read the [contributing guide](https://github.com/utPLSQL/utPLSQL/blob/develop/CONTRIBUTING.md)
31+
if you'd like to get involved.
2532

26-
While the framework exists since 1999, the current version 3 got completely rewritten in 2016 by passionate members of
27-
the community, using the object-oriented capabilities of the Oracle database to make it more consistent with other
28-
*Unit frameworks (e.g. JUnit for Java).
29-
30-
This had significant impact on the syntax and the way the framework can be used.
33+
34+
### Framework history
35+
36+
While the framework exists since 1999,
37+
the current version is a consequence of a complete rewrite done in 2016 by passionate developers,
38+
using the object-oriented capabilities of the Oracle database to make it more aligned with other testing frameworks (e.g. JUnit for Java, RSpec for Ruby).
39+
40+
This had significant impact on the test code syntax and how the framework is used.
3141

3242

3343
### Major Contributors
3444

3545

36-
| Name | Comments |
37-
|------------------------------------------------------------------|----------------------------------------------------------------------------------------------------
38-
| [Jacek Gebal](https://twitter.com/GebalJacek/) | Project lead, admin, core PL/SQL framework, pipelines, expectations, reporters, annotations, cache |
39-
| [Pavel Kaplya](https://twitter.com/Pazus) | Core PL/SQL framework, design, annotations |
40-
| [Lukasz Wasylow](https://twitter.com/Baalowy) | Core PL/SQL framework, demo project |
41-
| [Samuel Nitsche](https://twitter.com/Der_Pesse) | utPLSQL-java-api, utPLSQL-cli |
42-
| [Philipp Salvisberg](https://twitter.com/phsalvisberg) | utPLSQL-SQLDeveloper-extension |
43-
| [Simon Martinelli](https://www.linkedin.com/in/simonmartinelli/) | utPLSQL-PLSQL-Developer plugin, utPLSQL-cli |
44-
| [Vinicius Avellar](https://twitter.com/mrvmoreira) | utPLSQL-java-api, maven-plugin, utPLSQL-cli |
45-
| Robert Love | |
46-
| David Pyke | |
46+
| Name | GitHub | Comments |
47+
|-------------------------------------------------------------------|-----------------------------------------------|-----------------------------------------------------------------------------------------------------|
48+
| [Jacek Gebal](https://twitter.com/GebalJacek/) | [jgebal](https://github.com/jgebal) | Project lead, admin, core PL/SQL framework, pipelines, expectations, reporters, annotations, cache |
49+
| [Pavel Kaplya](https://twitter.com/Pazus) | [Pazus](https://github.com/Pazus) | Core PL/SQL framework, design, annotations |
50+
| [Lukasz Wasylow](https://twitter.com/Baalowy) | [lwasylow](https://github.com/lwasylow/) | Core PL/SQL framework, demo project |
51+
| [Samuel Nitsche](https://twitter.com/Der_Pesse) | [pesse](https://github.com/pesse/) | utPLSQL-java-api, utPLSQL-cli |
52+
| [Philipp Salvisberg](https://twitter.com/phsalvisberg) | | utPLSQL-SQLDeveloper-extension |
53+
| [Simon Martinelli](https://www.linkedin.com/in/simonmartinelli/) | | utPLSQL-PLSQL-Developer plugin, utPLSQL-cli |
54+
| [Vinicius Avellar](https://twitter.com/mrvmoreira) | [viniciusam](https://github.com/viniciusam/) | utPLSQL-java-api, maven-plugin, utPLSQL-cli |
55+
| Robert Love | [rlove](https://github.com/rlove) | |
56+
| David Pyke | [Shoelace](https://github.com/Shoelace) | |
4757

4858

4959
Many thanks to [all contributors](https://github.com/utPLSQL/utPLSQL/graphs/contributors) across utPLSQL projects.
@@ -59,6 +69,24 @@ Many thanks to [all contributors](https://github.com/utPLSQL/utPLSQL/graphs/cont
5969
| Paul Walker |
6070

6171

72+
## Getting Support
73+
74+
* Search or start a topic on [GitHub Discussions](https://github.com/utPLSQL/utPLSQL/discussions) to ask questions, find support and share ideas
75+
* Open a new [issue on GitHub](https://github.com/utPLSQL/utPLSQL/issues) for bugs or feature requests
76+
77+
78+
## Licensing
79+
80+
**utPLSQL** and its companion tools are licensed under the [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) license.
81+
82+
This website and the project documentation are built with:
83+
84+
| Tool | License | Purpose |
85+
|-----------------------------------------------------------------------|----------------------------------------------------------|------------------------------------|
86+
| [mkDocs](http://www.mkdocs.org/) | [BSD](http://www.mkdocs.org/about/license/) | Project website and documentation |
87+
| [material-for-mkdocs](https://squidfunk.github.io/mkdocs-material/) | [MIT](https://squidfunk.github.io/mkdocs-material/license/) | Project website and documentation |
88+
89+
6290
## Supporters
6391

6492
The utPLSQL project is community-driven and is not commercially motivated. Nonetheless, donations and other contributions are always welcome, and are detailed below.

0 commit comments

Comments
 (0)