1[< Previous (FAQ)](faq.md) 2 3*** 4 5Development 6=========== 7 8Interested in pekwm? Want to keep up with the development? Good, we 9can tell you how. 10 11**Table of Contents** 12 131. [IRC](#irc) 141. [Issue Tracker](#issue-tracker) 151. [The developers](#the-developer) 16 17IRC 18--- 19 20Our IRC channel #pekwm is located on irc.freenode.net. A lot of 21development discussion goes on there, however you can also get simple 22help there pretty easily. 23 24The following is a "do not" list. If some idiotic behaviour like, 25public away messages, or nick changing as a way of telling what you 26are doing, are not mentioned it doesn't mean you can do them. 27 28As it seems to be a problem for some, do not ask questions in IRC 29unless you are willing to listen to the answer. If listening is your 30problem, you need other help than what we at IRC can provide. 31 32If you have a question, ask it. It doesn't help to go around shouting 33"can anyone help me". Help you with what? This will help the right 34people to take initial contact with you, saving your time and adding 35less clutter to the channel. 36 37For same reasons, don't ask if we are alive or other meaningless 38questions leading to the real question. Don't ask if someone specific 39is around either. This is not the pager channel for you and your 40friends. 41 42Do not ask from one person. The fact is, even how much you think he or 43she must be the only one who knows the answer, you are wrong. There's 44at least a handful of people lurking on the channel who could help 45you. 46 47Read the documentation and FAQ before you ask anything. Doing this is 48common courtesy towards the people who answer your questions. Not 49reading at least the FAQ will be considered rude. 50 51When asking a question, the answer more than often depends on the 52version of pekwm you use. Showing us the information the command 53**pekwm --info** gives will help us help you. 54 55Do not expect people to answer your questions during the two minutes 56you stay in the channel. We can't sit there all the time waiting for 57your questions. If you can't wait longer, think about how stressful 58your life is, take a break, go on a vacation, take it easy for a 59while. 60 61For similar reasons, don't repeat yourself. We saw it the first 62time. Repeating easily gets you ignored completely so it eats its own 63purpose. It's also considered rude, much like cutting in line. 64 65If people tell you to read the documentation, they have a good reason 66to do so. If they include an URL that helps you find the info quicker, 67offer them your firstborn as a payback. 68 69Don't offend anyone. They will offend you back two times. 70 71Nicks with excessive capital letters will be hunted down and shot on 72sight. You might as well use a proper nick to start with to avoid 73this. 74 75You can check the [developers](#devel-who) section to see the list of 76developers mapped to their IRC nicks. 77 78As with all IRC channels, it's best to not do anything too drastic 79before keeping an eye for a while on how the channel works. We won't 80mind even if you just idle there, there are long standing traditions 81on that. 82 83Welcome aboard! 84 85Issue Tracker 86------------- 87 88pekwm bugs, feature requests and what-not are filed on Github issue 89tracker available at https://github.com/pekdon/pekwm/issues 90 91When reporting a bug or other misbehavior please provide as much 92information as possible, including but not limited to: 93 941. How is the issue reproduced? 952. What did you expect to happen, what did actually happen? 963. Version of pekwm and other applications used. 974. Output of pekwm --info 98 99### Gathering pekwm log files 100 101To provide more details it is possible to run pekwm with the log level 102set to trace and log to file. If the issue appears during start of 103pekwm, start pekwm like this: 104 105``` 106pekwm --log-file issue.log --log-level trace 107``` 108 109If the issue is reproducible while pekwm is running, it is recommended 110to set the log level and log file while reproducing the issue to avoid 111including potential misleading information. 112 113 114Run the following commands using the CmdDialog or pekwm_ctrl before 115reproducing the issue. 116 117``` 118Debug level trace 119Debug enable logfile 120Debug logfile issue.log 121``` 122 123And directly after the issue has been reproduced: 124 125``` 126Debug disable logfile 127``` 128 129Include the issue.log in the error report if it includes any 130information. 131 132 133### Gathering information about a pekwm crash 134 135If pekwm crash please provide a stack trace from the core dump, if no 136core (or pekwm.core). To ensure a core file is generated enable core 137dumps before starting pekwm: 138 139``` 140ulimit -c unlimited 141exec pekwm 142``` 143 144If a core file has been created, generate a backtrace by running: 145 146``` 147$ gdb /path/to/pekwm core 148(gdb) bt 149#0 ... 150(gdb) 151``` 152 153The output between the two _(gdb)_ lines should be included in the 154report. 155 156The developers 157-------------- 158 159Below is a list of pekwm developers and what they do. The email 160address is more of an informational thing than anything else; the 161developers all subscribe to the + [pekwm mailing 162list](http://pekwm.org/projects/pekwm/mailing_lists/15), so you should 163email that instead. 164 165### Developers 166 167Claes Nästén (aka pekdon) <pekdon@gmail.com> 168 169Main developer- Writes code. Has a serious screenshot fetish. 170 171### Past devekopers 172 173Andreas Schlick (aka ioerror) 174 175Maintainer. 176 177Jyri Jokinen (aka shared) <shared@adresh.com> 178 179Writes documentation. Acts ill-tempered. You have been warned. 180 181*** 182 183[< Previous (FAQ)](faq.md) 184