Hi, I will tackle this from the other direction. When it is clear, what the purpose of each task package is, it is easier to define, which package should e included in it. I have done this for some already, but I won't have much time in the next days, so I ask you to help on this, post corrections, fix spelling and grammar errors etc. Following is a list of current tasks, with description. I still need the description/purpose of some of them. I am sure, Adam will gladly do this for task-sgml and task-tex :-) As these will be usual packages, I hope to give them away to people closer to the respective field of usage after release. If they are kept current and updated, the task thing won't need work next release. But there has to be a guideline how to maintain the task packages (e.g. not to put every possible package into them). But that is future point, they have to exist first. After it is known what purpose a task package has, it is easier to find the packages it should contain. Which still leaves the task to choose between equaly suited packages... I guess, a coin will be my most used tool in the next time :-) Ciao, Martin
Attachment:
tasks
Description: Binary data