1 |
It has been fairly obvious that for a number of years one of the |
2 |
biggest problem the Foundation struggles with is remembering to take |
3 |
care of things that need to be taken care of on some kind of periodic |
4 |
interval. We forget to file and let our foundation become inactive. |
5 |
We forget to renew trademarks until the last minute, and so on. |
6 |
|
7 |
To help improve this I'm going to try to lead efforts to create a |
8 |
simple and effective periodic activity tracking checklist. The heart |
9 |
of the checklist is just going to be a table of activities that need |
10 |
to happen periodically. Attributes I plan to track include: |
11 |
|
12 |
Name of Activity |
13 |
Who is responsible (by role) - nothing to stop people from teaming up, |
14 |
but one role should be the lead for anything |
15 |
Frequency of Activity (ie annually, quarterly, etc) |
16 |
Whether activity is legally required (vs nice-to-have) |
17 |
Last time activity was completed |
18 |
Next time activity is due |
19 |
Link to details page |
20 |
|
21 |
Then for each activity we can have a details page (or anchors in a |
22 |
single page) that goes into the gory details. I'd expect this to |
23 |
include: |
24 |
Links to appropriate laws/etc. |
25 |
Recommended process to follow. |
26 |
Links to helpful tools/forms/etc. |
27 |
Where to find the information necessary to complete the step. |
28 |
Where we store the official copy of the resulting deliverable. |
29 |
Where interested users can find the deliverable (perhaps redacted), if |
30 |
applicable. I'd encourage as much transparency as possible (many |
31 |
eyeballs/etc). |
32 |
Links to bugs tracking past/current activity completions. |
33 |
|
34 |
I'd just put all of this stuff on the Gentoo website in GuideXML/etc. |
35 |
That is, unless somebody is aware of a tool we could leverage which |
36 |
would better accomplish this while keeping things simple and being |
37 |
aligned with our values. |
38 |
|
39 |
Feel free to chime in here with suggestions for design |
40 |
improvements/etc, but my intent is to get started creating and not |
41 |
wait until things are perfect. Any system of organization is going to |
42 |
be better than what we already have. Once the structure is in place |
43 |
anybody can feel free to suggest additions to the list, and this |
44 |
should be pretty easy to distribute among volunteers (even those |
45 |
without commit access if you can modify a template xml file and submit |
46 |
a bug). |
47 |
|
48 |
Rich |