Calligra/First Contact: Difference between revisions

From KDE Community Wiki
No edit summary
mNo edit summary
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
'''Developers interested to join, please read.'''
'''Are you potential contributor interested to join? Please read.'''


'''Hello and Welcome.'''
'''Hello and Welcome!'''


*Recommended skills for Calligra software developers are:
__TOC__
**C++ advanced knowledge
===Software Engineering Skills===
**Qt development skills
It helps if a new Calligra software engineer has:
**Practice of development for KDE are welcome
*good C++ knowledge
*Qt development skills


Specific knowledge like graphics processing for Krita or database-related knowledge for Kexi is not required but may be a plus for some tasks.
Moreover:
Linux/Unix/Mac OS X and MS Windows developers are welcome but please note that x86 Linux is the development environment of most (if not all) Calligra Developers.
*Practice of KDE applications development is optional.
*Some experience of using version control systems (git or svn) is welcome


Please write to the [https://mail.kde.org/mailman/listinfo/calligra-devel [email protected] mailing list] and answer these generic questions that would help to proceed:
# what projects have you contributed to (type of projects, provide links if possible)?
# what are your skills regarding to: C++, Qt Framework, KDE Development Frameworks
# do you have specific skills like graphics processing or database knowledge?
# how much time for the project have you got? (examples: 4 hours twice a week, or weekends)


Additional information is welcome:
Specific knowledge is not required but may be useful for certain tasks. For example graphics processing for Krita or database technologies for Kexi.
# are you student or full time developer?
 
Linux/Unix/Mac OS X and MS Windows developers are welcome but please note that x86 Linux is the development environment of most Calligra developers.
 
===Present yourself===
It would be nice to [[Calligra/Contact|contact the Calligra team]] (or specifically: [[Kexi/Contact|Kexi]]) and answer general questions listed below. That would help to proceed faster but it's not required if you feel unsafe about it. Also, feel free to write something more.
 
# What projects have you contributed to (type of projects, provide links if possible)?
# What are your skills such as C++ development, Qt Framework, KDE Development Frameworks, Software design, GUI design, testing, project management, marketing, writing
# Do you have specific skills you'd like to utilize while contributing, like graphics processing or database knowledge?
# Is there specific Calligra app or library or feature that you'd be interested (or you have not decided yet)?
# How much time for the project would you have? (examples: 4 hours twice a week, or weekends)
 
 
Additional information is welcome too:
# are you student or full time employee?
# have you got permanent internet connection?
# have you got permanent internet connection?
# do you speak/read/type (at least) "internet" english?
# do you speak/read/type (at least) "internet" English?


You would need to study quite a bit and look around.
===Look around===
Then you would want to study quite a bit and look around.


You can study information on how to develop/contribute on [[Calligra]] wiki pages, especially the [[Calligra#Getting_started|Getting Started]] section and how to build Calligra from the source code or how to report bug.
You can study information on how to develop/contribute on [[Calligra]] wiki pages, especially:
# [[../Building/3|How to build Calligra]] from the source code, that's the first step
# [[../Contributing a Patch/]]
# [[../File_a_bug_or_wish|How to report bug]].
 
 
Depending on your skills you can in particular look at the [[../Junior Jobs/]] page. It's rather incomplete, so ask maintainer of give application for more.
 
Should any question arise don't hesitate to [[../Contact/|ask]]!


And depending on your skills you can in particular look at the [[../Junior Jobs/]] page.




          ''Have fun!''
          ''Have fun!''
Should any question arise please ask on the calligra-devel mailing list.

Latest revision as of 10:22, 4 August 2022

Are you potential contributor interested to join? Please read.

Hello and Welcome!

Software Engineering Skills

It helps if a new Calligra software engineer has:

  • good C++ knowledge
  • Qt development skills

Moreover:

  • Practice of KDE applications development is optional.
  • Some experience of using version control systems (git or svn) is welcome


Specific knowledge is not required but may be useful for certain tasks. For example graphics processing for Krita or database technologies for Kexi.

Linux/Unix/Mac OS X and MS Windows developers are welcome but please note that x86 Linux is the development environment of most Calligra developers.

Present yourself

It would be nice to contact the Calligra team (or specifically: Kexi) and answer general questions listed below. That would help to proceed faster but it's not required if you feel unsafe about it. Also, feel free to write something more.

  1. What projects have you contributed to (type of projects, provide links if possible)?
  2. What are your skills such as C++ development, Qt Framework, KDE Development Frameworks, Software design, GUI design, testing, project management, marketing, writing
  3. Do you have specific skills you'd like to utilize while contributing, like graphics processing or database knowledge?
  4. Is there specific Calligra app or library or feature that you'd be interested (or you have not decided yet)?
  5. How much time for the project would you have? (examples: 4 hours twice a week, or weekends)


Additional information is welcome too:

  1. are you student or full time employee?
  2. have you got permanent internet connection?
  3. do you speak/read/type (at least) "internet" English?

Look around

Then you would want to study quite a bit and look around.

You can study information on how to develop/contribute on Calligra wiki pages, especially:

  1. How to build Calligra from the source code, that's the first step
  2. Contributing a Patch
  3. How to report bug.


Depending on your skills you can in particular look at the Junior Jobs page. It's rather incomplete, so ask maintainer of give application for more.

Should any question arise don't hesitate to ask!


          Have fun!