There are countless ways to organize the Someday/Maybe population:
- Categories. Books to Read, Movies to See, Features to Code, etc. Categories can often be treated in a one done/one out way--for example, only after you finish the last book do you scan and maybe re-order and clean up the Books to Read list.
- Review frequency. Review Soon, Review Monthly, Review Quarterly, Review Annually.
- Tickler items. If you have a reliable tickler system, there are probably some items that you can just ignore until the tickler comes up. Sure, you probably want to look at it once in a while, but not weekly.
- Projects versus project support material. Maybe you have a great idea for a new piece of software to write. Maybe you have thoughts about it all the time. You don't need to review those notes until you're ready to do the project. So the project can be one item in your lists, not dozens of items--you can store the project support material somewhere else.
For me, someday/maybe items are rarely populated with actions or contexts--they would only be populated if I expect to do them very soon, or if they were recently active and I temporarily demoted them.