Difference between revisions of "Get involved"
m (16 revisions: initial import from SamrtEiffel Wiki - The Grand SmartEiffel Book) |
Hzwakenberg (talk | contribs) m |
||
| (10 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[ |
+ | [[Category: Community]] |
| + | =Interested in the Eiffel language and the Liberty compiler?= |
||
| − | <h2> Who can help? </h2> |
||
| + | First of all you are invited to use Liberty for developing your own applications. If you encounter any problem, just raise your voice and [[Get in touch|get in touch]] with us. We are here to fix your issues and support you in using the Liberty Eiffel compiler and its libraries. Our primary goal is to provide a working Eiffel compiler and a bunch of libraries for real life applications. Now you face the opportunity to come up with a nice little program (or a new office suite), written with Liberty. |
||
| − | Every one can help. |
||
| + | Liberty is an open project, where anyone can clone the public repository from git://git.savannah.gnu.org/liberty-eiffel.git and dig into the code, improve it and get the changes into the master branch. You are welcome to provide patches, issue pull requests and to become a project member on Savannah. |
||
| − | You can help the SmartEiffel project in several ways. (developers, test, documentation -this wiki-) |
||
| + | We are open to any bug fix or new feature in the libraries or tools. And if you don't want to get your hands dirty we are happy for you to create feature requests or bug reports in the [https://savannah.gnu.org/bugs/?func=additem&group=liberty-eiffel issue tracker on GNU Savannah]. |
||
| − | <h2> How to help to documentation? </h2> |
||
| − | Please feel free to improve |
+ | Please also feel free to improve the pages in this Wiki. - Although we disabled the anonymous account creation due to spamming it is simple to get an account by asking via [[Get in touch|email]]. |
| + | =Technical Details of our repository setup= |
||
| − | <h2> How to help to test? </h2> |
||
| + | The main development repository is on Savannah: http://git.savannah.gnu.org/r/liberty-eiffel.git |
||
| + | Pushes to this repo are replicated (every two minutes) to [https://github.com/LibertyEiffel/Liberty Github/LibertyEiffel/Liberty] by ET. Many of us have an account and a private clone of the GitHub repo to be able to publish something, that is not yet pushable to the master repository, but others might want to take a look, comment and/or try. The main trick now is, that the local clones we work with on our development machines have the savannah repo also as remote and we do not directly commit to the Liberty repo master on github, but only to our personal github clones or to savannah. |
||
| + | One easy way to handle patches from not-yet-savannah-project members is probably a pull-request on github. We then just have to remember that we have to manually pull those into our repositories first before pushing them to savannah (using the "manual merging tipps" on github). |
||
| − | If you are a developer interrested in contributing to SmartEiffel, please read the following instructions: |
||
| − | |||
| − | <ol> |
||
| − | <li> Browse the list below of the identified needed feature. Some of these feature requests are documented (follow the link) and some are not. |
||
| − | <li> Choose the one you want to do. |
||
| − | <li> Contact SmartEiffel team to discuss with them about if some one is already involved and about how SE team feels it. |
||
| − | <li> Write the code and the tests that are coming with (here we think that test based development is the must). |
||
| − | <li> Submit your work frequently using the cogito system to have quick feedback on it. |
||
| − | <li> Please consider that submission can be rejected for reasons that will be explained. |
||
| − | <li> Unsolicited submissions are also very welcome. |
||
| − | </ol> |
||
| − | |||
| − | |||
| − | <h2>List of the requested features (june 6, 2005)</h2> |
||
| − | |||
| − | <ul> |
||
| − | <li> block file reading and writing |
||
| − | <li> bidirectional iterators |
||
| − | <li> unicode characters |
||
| − | <li> support of the localisation |
||
| − | <li> support of non blocking I/O |
||
| − | <li> support of time granted jobs |
||
| − | <li> improvement of HTTP_SERVER |
||
| − | <li> binary repository |
||
| − | <li> improvement of the binaries I/O |
||
| − | <li> usage of CSS |
||
| − | <li> ... |
||
| − | </ul> |
||
Latest revision as of 17:23, 2 February 2022
Interested in the Eiffel language and the Liberty compiler?
First of all you are invited to use Liberty for developing your own applications. If you encounter any problem, just raise your voice and get in touch with us. We are here to fix your issues and support you in using the Liberty Eiffel compiler and its libraries. Our primary goal is to provide a working Eiffel compiler and a bunch of libraries for real life applications. Now you face the opportunity to come up with a nice little program (or a new office suite), written with Liberty.
Liberty is an open project, where anyone can clone the public repository from git://git.savannah.gnu.org/liberty-eiffel.git and dig into the code, improve it and get the changes into the master branch. You are welcome to provide patches, issue pull requests and to become a project member on Savannah.
We are open to any bug fix or new feature in the libraries or tools. And if you don't want to get your hands dirty we are happy for you to create feature requests or bug reports in the issue tracker on GNU Savannah.
Please also feel free to improve the pages in this Wiki. - Although we disabled the anonymous account creation due to spamming it is simple to get an account by asking via email.
Technical Details of our repository setup
The main development repository is on Savannah: http://git.savannah.gnu.org/r/liberty-eiffel.git Pushes to this repo are replicated (every two minutes) to Github/LibertyEiffel/Liberty by ET. Many of us have an account and a private clone of the GitHub repo to be able to publish something, that is not yet pushable to the master repository, but others might want to take a look, comment and/or try. The main trick now is, that the local clones we work with on our development machines have the savannah repo also as remote and we do not directly commit to the Liberty repo master on github, but only to our personal github clones or to savannah.
One easy way to handle patches from not-yet-savannah-project members is probably a pull-request on github. We then just have to remember that we have to manually pull those into our repositories first before pushing them to savannah (using the "manual merging tipps" on github).