Documentation / Code Migrating

[dieend]

Jadi kita ada lx yang lama di lx-old. Itu kode-kode yang lama.

Migrasi dilakukan di branch migration yang berfungsi sebagai buffer dari lx-old. Setiap mau nge-migrate code dari sebuah part, let's say part user, bikin branch migration-user dari branch migration.

Yang dilakukan untuk melakukan sebuah migrasi:

• dokumentasi. ikuti guidelines
• unit test. example nyusul
• functional testing

Part di sini maksudnya something yang cukup besar, or we can say module.

To Do List (Bakal ada issue-nya sendiri-sendiri)

• User Management
• Problem Management
  • Problem
  • Problem Type
  • Problem Set
• Open Problem Management
• Organization Management
• Content Management

Requirement:

• Install PHPUnit
• Install Selenium

[dieend]

Dokumentasinya ntar make phpDocumentor atau Doxygen? Kalau berdasarkan link ini: http://technosophos.com/node/246 doxygen felt better. Any suggestion?

[petrabarus]

I'm okay with either, actually. Although seumur hidup cuman pernah pake Doxygen sama Javadoc doang. But, we should make a standards about code commenting. Biar semuanya uniform.

[dieend]

Yep. Udah buat page documentation guidelines kok. Tapi masih kosong. Berhubung gw jg pernah make doxygen ama javadoc. Jadinya make doxygen aja kali ya. On Jul 11, 2012 3:39 PM, "Petra Barus" < reply@reply.github.com> wrote:

I'm okay with either, actually. Although seumur hidup cuman pernah pake Doxygen sama Javadoc doang. But, we should make a standards about code commenting. Biar semuanya uniform.

---

Reply to this email directly or view it on GitHub:

https://github.com/tokilearning/tokilearning-web/issues/2#issuecomment-6922039

[dieend]

@petrabarus lengkapin pet issue descriptionnya

[petrabarus]

Just finished applying the administration theme.