Hacking:Developer FAQ: Difference between revisions

← Older edit

Hacking:Developer FAQ (edit)

Revision as of 18:22, 12 October 2018

154 bytes removed , 5 years ago

→‎Where should I go for help when I need it?

VisualWikitext

Kmf

541

edits

Revision as of 17:30, 12 October 2018 (edit) Kmf (talk \| contribs) (→‎How can I support Seamly2D development?) ← Older edit		Latest revision as of 18:22, 12 October 2018 (edit) (undo) Kmf (talk \| contribs) (→‎Where should I go for help when I need it?)
(7 intermediate revisions by the same user not shown)
Line 6: Seamly2D has an [[User Manual\|user manual]] that you can help us improve and translate. Also we need your help with localization. You can also have a look at bug reports filed for Seamly2D and pick something. You can use the issue tracker to find bug reports you could take care of, but we encourage you contacting us beforehand to find out if the task you picked is still valid. It's best to discuss working on something in ~~either~~ [https://~~groups~~forum.~~google~~seamly.~~com~~net/~~forum/#!forum~~c/~~valentina-project-list~~issues ~~mailing~~the ~~list~~forum] ~~or IRC channel~~ before beginning to fix things and implement features. This is because requests have to be checked against bigger design decisions. We'd hate if you wasted your time on something that shouldn't have been done. Major planned changes are listed at the feature [https://~~bitbucket~~wiki.valentinaproject.org~~/dismine/valentina~~/wiki/~~Road%20map~~Roadmap roadmap page]. Contacting the team is essential when starting to solve bugs or realizing enhancements/features. Line 16: === Who is planning Seamly2D's development? === Seamly2D team does not have time-based schedules, instead we rely on a [https://~~bitbucket~~wiki.valentinaproject.org~~/dismine/valentina~~/wiki/~~Road%20map~~Roadmap feature roadmap]. We use [https://en.wikipedia.org/wiki/~~Mercurial~~Git ~~Mercurial~~Git] [https://~~www~~leanpub.~~mercurial~~com/git-~~scm.org/wiki~~flow/~~NamedBranches~~read named branches] for developing major new features. Each new feature lives in own ''feature'' branch. If a feature is ready for inclusion into the main develop branch, it is merged. The decision, whether it's ready, is made by the core team ~~(currently: Roman)~~. === How can I become a Seamly2D developer? === If you are a developer who wants to start contributing code to the Seamly2D, the best way to get to know its structure is by fixing bugs reported in [https://~~bitbucket~~github.~~org~~com/~~dismine~~FashionFreedom/~~valentina~~Seamly2D/issues~~?status=new&status=open~~ Issue tracker]. Pick a bug, perhaps ask the advice of another developer as to whether he/she thinks it will be an easy bug or not, and then fix it. Sounds easy, doesn't it? After helping with a couple of bugs, people will start to recognize your immense talent, and you will be on your way to becoming a Seamly2D developer. Any time you feel able, you can pick a smaller enhancement request and have a go at implementing it. It's that easy. Line 27: === Where should I go for help when I need it? === There are several channels of communication: * Main [https://~~groups~~forum.~~google~~seamly.~~com~~net/~~forum~~c/~~#!forum/valentina-project-list~~developer ~~mail~~developer ~~list~~category on forum] (recommended way). * IRC channel [https://webchat.freenode.net/?channels=#seamly2d #seamly2d]. Abandoned right now. * You can ask question on [https://www.facebook.com/~~Valentina.Project~~Seamly2D/ Facebook]. === Where can I find documentation for the Seamly2D API? ===