Kexi/Contact: Difference between revisions
< Kexi
No edit summary |
|||
| Line 19: | Line 19: | ||
*The bounty system is hooked into Issues tracking system of GitHub, we're sorry for inconvenience because bugs.kde.org is our official bug tracking. Anyway, report an issue on GitHub add a and we'll handle the rest for you. Or send us the request by email or via bugs.kde.org. Whatever suits you. | *The bounty system is hooked into Issues tracking system of GitHub, we're sorry for inconvenience because bugs.kde.org is our official bug tracking. Anyway, report an issue on GitHub add a and we'll handle the rest for you. Or send us the request by email or via bugs.kde.org. Whatever suits you. | ||
*More information on how Bounties work: [https://github.com/bountysource/frontend/wiki/Frequently-Asked-Questions#how-does-bountysource-work github.com/bountysource]. | *More information on how Bounties work: [https://github.com/bountysource/frontend/wiki/Frequently-Asked-Questions#how-does-bountysource-work github.com/bountysource]. | ||
*We use pages of this wiki for design blueprints. Each such design page related to a bounty is listed on https://community.kde.org/Category:Kexi_Bounties. | |||
===Social Media=== | ===Social Media=== | ||
Revision as of 09:41, 26 August 2015
The Kexi Team values your input and questions!
Recommended forms of contact
All forms of contact are open for everybody.
- Kexi Forums at forum.kde.org/kexi, in particular:
- Kexi News & Discussion forum for publishing news and discussions about Kexi (a good for to contribute to Kexi!)
- Kexi Help forum for asking for help and assistance
- Mailing lists[1]:
- [email protected] mailing list for Kexi users, where they can ask for help and assistance, and find some news
- [email protected] mailing list dedicated for Kexi contributors, useful to be discuss Kexi matters with others, manage the development process, and to efficient contact with other people involved in the project
- Development IRC channel: #kexi on irc.freenode.net for inexpensive realtime contact with contributors. Web-based Kexi IRC chat is also available.
Requesting a feature, enhancement or a fix
- Who, codes decides. Who pays, decides too. Decide on feature, enhancement or fix that will be developed next for you in Kexi!
- Add an Issue at https://github.com/staniek/kexi/issues and click a Post a bounty on it! link on the bottom of your reported issue. Or visit https://www.bountysource.com/teams/kexi/issues and click on your reported issue.
- The bounty system is hooked into Issues tracking system of GitHub, we're sorry for inconvenience because bugs.kde.org is our official bug tracking. Anyway, report an issue on GitHub add a and we'll handle the rest for you. Or send us the request by email or via bugs.kde.org. Whatever suits you.
- More information on how Bounties work: github.com/bountysource.
- We use pages of this wiki for design blueprints. Each such design page related to a bounty is listed on https://community.kde.org/Category:Kexi_Bounties.
Social Media
- http://twitter.com/kexi_project
- https://www.facebook.com/kexi.project
- https://identi.ca/kexi
- Google+: TODO
Contact active contributors directly
- Jarosław Staniek, Project Maintainer and core developer: [email protected]
- Adam Pigg, core developer, [email protected]
- Wojciech Kosowicz, [email protected]
See also
- Former contributors
- Kexi is member of the Calligra suite. [email protected] mailing list is a general Calligra development list, also available as a newsgroup. #calligra IRC channel is also available as well as Web-based IRC chat.
- General Calligra Contact