Becoming an org contributor liaison (thanks for that opportunity!) has
really motivated me to try to learn enough Elisp so that I can
contribute actual code as well. And I'm really excited about that
notion, but I need to learn more before I can do anything concrete about
it.

But, incidentally, I wrote the following in one of my Org files earlier
today:

* TODO Work towards contributing code

** TODO Make preparations

*** TODO Come up with idea for code change

**** Potential ideas

***** Better display of long appointments in agenda time grid

- Sometimes you have appointments which span several "slots" in
  'org-agenda-time-grid', and currently the lines in the grid after the
  first one look empty, even though they are "occupied" by an
  appointment that's only listed on its first time-matching line on the
  grid. For example:

  - 08:00...... ----------------
    09:00-11:00 Sync meeting
    10:00...... ----------------
    11:00...... ----------------
    12:00...... ----------------
    
  - Even though the meeting is listed as being from 09:00 to 11:00 on
    its line, the 10:00 slot still looks empty even though the meeting
    is still ongoing then.
    
- This could be displayed in several better ways:

  - Skipping the deceptively empty-looking slot at 10:00:

    - 08:00...... ----------------
      09:00-11:00 Sync meeting
      11:00...... ----------------
      12:00...... ----------------
      
  - Displaying the meeting on all relevant lines:

    - 08:00...... ----------------
      09:00-11:00 Sync meeting
      10:00...... | Sync meeting (cont)
      11:00...... ----------------
      12:00...... ----------------

  - Displaying only a pipe on subsequent lines to "occupy" the space:

    - 08:00...... ----------------
      09:00-11:00 Sync meeting
      10:00...... |
      11:00...... ----------------
      12:00...... ----------------

*** TODO Get approval for the idea

*** TODO Get the org git repo

** TODO Make a code change

*** TODO Implement the idea

**** TODO Figure out which branch to make it on

**** TODO Make sure the repo is up to date

**** TODO Write the code

*** TODO Test it manually

*** TODO Make automated tests for it

**** TODO Learn and document how to make Elisp tests

**** TODO Implement the tests

** TODO Make a patch

*** TODO Learn and document how to make a patch

*** TODO Make sure git repo is updated

*** TODO Re-test after update

**** TODO Manual test

**** TODO Automated test

*** TODO Generate the patch file

** TODO Submit the patch

*** TODO Learn and document how to submit a patch

[[https://orgmode.org/worg/org-contribute.html#first-patch][Submit a patch]]

*** TODO Send the patch to the mailing list

-- 
Christer Enfors
Org contributor liaison
GPG Fingerprint: 9CF7 3292 83BC D643 DF01  992C 1C3B 434F 2AC2 B1E6
Public Key available at: keys.openpgp.org

Reply via email to