Community Changelogs-Contribution

From ReactOS Wiki
Revision as of 10:58, 20 February 2018 by Ctasan (talk | contribs) (Created page with "Community Changelogs is free to contribute and use. You just need a Trusted Wiki account, use it wisely. To get it, please contact with Wiki administrators. == Structure of C...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Community Changelogs is free to contribute and use. You just need a Trusted Wiki account, use it wisely. To get it, please contact with Wiki administrators.

Structure of Community Changelogs

Community Changelogs are divided into categories indicating which layer of the system is changed in that release.

  • Kernel: It consists of ntoskrnl.exe and modules, FreeLoader (the bootloader) and UEFI loader, lastly usetup (ReactOS Setup).
  • Win32 subsystem: It includes WIN32K, NTUSER, GDI, USER32, NTVDM, CSRSS etc. If you see them or similar components, then it goes into Win32 subsystem category.
  • Drivers: All drivers go here. Device, class or filesystem drivers; no matter.
  • Shell: ReactOS Explorer and Command Prompt. WARNING: No shell DLLs here.
  • System DLLs: Critical DLLs like hal, ntdll, kernel32, user32, advapi32 and DirectX/WineD3D/OpenGL components.
  • User-mode DLLs: Every DLL that is not critical.
  • Commands and utilities: System accessories, Control Panel, external commands, utilities, tools, services...
  • Tasks: Syncs with external components (Please add version), build improvements and other trivial stuff.

How to contribute

  • These entries are not strict rules, you are free. However, we have a style, we're targeting day-to-day users here. Using your common sense is enough.
  • Think a release is done and sometime, two weeks to a month has passed. Firstly, have a look into commit stream and analyze what's important. Some build fixes and a spree of new functions? Choose. On the other hand, a bunch of technical terms? I think you don't want to copy all of the commit message entirely. Instead, try to find a way to convert them user-readable.
  • We should go progressively as usual.
  • Most of the commits include JIRA issues. Have a look at them. You'll better see what is done. Sometimes, devs will include what's fixed. Try to avoid way too technical stuff, and add what's done. Also following JIRA regularly is helpful.
  • Try to avoid using function names, instead collect them into a category that special enough. (example: iphlpapi: Implemented interface name resolving functions.)
  • Build fixes, translations, glitch/pixel fixes etc. are not so important. Instead, we should focus on fixes and developments.
  • Write everything entry by entry. Especially, in DLLs, commands/utilities and drivers, write which component changed, like Wine commit stream. (example: shell32: Fixed showing disk capacity.)
  • After each entry, add committer name and if exists, author of the patch/pull request.
  • Previous Community Changelogs will give you idea about how to contribute. Don't hesitate to ask for help! And if your English is bad, please request help.
  • A topic in the forum for every changelog will be opened. You can use it for discussions and your ideas.

Ctasan (talk) 10:58, 20 February 2018 (UTC)

Versions / Official Changelogs / Community Changelogs
0.4.x Series 0.4.1 | 0.4.2 | 0.4.3 | 0.4.4 | 0.4.5 | 0.4.6 | 0.4.7 | 0.4.8 | 0.4.9 | 0.4.10 | 0.4.11 | 0.4.12 | 0.4.13 | 0.4.14 | 0.4.15