You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: bring bs5 branch up to date with changes on main (ietf-tools#3644)
* chore: bring docker dev init script up to date with bs5 branch (ietf-tools#3611)
* ci: only run codeql on schedule
* feat: shorten long agenda filter button labels (ietf-tools#3602)
Sessions with long names lead to poor rendering of the agenda filter buttons
on the 'customize the agenda view' page. This truncates those labels at 3 words.
* docs: Remove stale and incomplete information from the README (ietf-tools#3612)
* docs: Suggest cloning a fork rather than ietf-tools repo (ietf-tools#3614)
* docs: update README
* chore: add issue templates
* chore: update issue templates config
* chore: remove duplicate security issue link
* docs: point feature requests to discussions
* chore: add bug report form
* chore: remove bug report issue template
* chore: fix bug report form
* fix: point the api index page into Github instead of trac/svn
* chore: remove os + version + log fields from bug report form
* fix: point to GitHub for bug reports (ietf-tools#3625)
* fix: point to GitHub for bug reports
* fix: point report bug link to template chooser
* fix: point report bug link to template chooser (2)
Co-authored-by: Nicolas Giard <github@ngpixel.com>
* fix: remove stale explanation of status reports (ietf-tools#3628)
* fix: adjust about page to reflect move to GitHub. Normalize information level on page. (ietf-tools#3629)
* fix: remove anchor tag with empty href (ietf-tools#3630)
* fix: use same github issue URL on 500 error page as elsewhere (ietf-tools#3631)
* chore: update report-a-bug.yml form
* ci: fix __init__.py version quotes
* chore: bring docker-compose to root level (ietf-tools#3642) (ietf-tools#3643)
Authored-by: Nicolas Giard <github@ngpixel.com>
Co-authored-by: Nicolas Giard <github@ngpixel.com>
Co-authored-by: Robert Sparks <rjsparks@nostrum.com>
Co-authored-by: Jim Fenton <fenton@bluepopcorn.net>
@@ -39,123 +34,38 @@ This project is following the standard **Git Feature Workflow** development mode
39
34
40
35
You can submit bug reports, enhancement and new feature requests in the [discussions](https://github.com/ietf-tools/datatracker/discussions) area. Accepted tickets will be converted to issues.
41
36
42
-
#### Prerequisites
43
-
44
-
- Python 3.6
45
-
- Django 2.x
46
-
- Node.js 16.x
47
-
- MariaDB 10
48
-
49
-
> See the [Docker Dev Environment](docker/README.md) section for a preconfigured docker environment.
50
-
51
37
#### Git Cloning Tips
52
38
53
-
Because of the extensive history of this project, cloning the datatracker project locally can take a long time / disk space. You can speed up the cloning process by limiting the history depth, for example:
39
+
As outlined in the [Contributing](https://github.com/ietf-tools/.github/blob/main/CONTRIBUTING.md) guide, you will first want to create a fork of the datatracker project in your personal GitHub account before cloning it.
40
+
41
+
Because of the extensive history of this project, cloning the datatracker project locally can take a long time / disk space. You can speed up the cloning process by limiting the history depth, for example *(replace `USERNAME` with your GitHub username)*:
The `ietf/templates/` directory contains Django templates used to generate web pagesfor the datatracker, mailing list, wgcharter and other things.
54
+
A beginning of a [walkthrough of the datatracker models](https://notes.ietf.org/iab-aid-datatracker-database-overview) was preparedfor the IAB AID workshop.
67
55
68
-
Most of the other `ietf` sub-directories, such as `meeting`, contain the python/Django model and view information that go with the related templates. In these directories, the key files are:
69
-
70
-
| File | Description |
71
-
|--|--|
72
-
| urls.py | binds a URL to a view, possibly selecting some data from the model. |
73
-
| models.py | has the data models for the tool area. |
74
-
| views.py | has the views for this tool area, and is where views are bound to the template. |
75
-
76
-
#### Adding a New Web Page
77
-
78
-
To add a new page to the tools, first explore the `models.py` to see if the model you need already exists. Within `models.py` are classes such as:
In this example, the `IETFWG` class can be used to reference various fields of the database including `group_type`. Of note here is that `group_acronym` is the `Acronym` model so fields in that model can be accessed (e.g., `group_acronym.name`).
92
-
93
-
Next, add a template forthe new pagein the proper sub-directory of the `ietf/templates` directory. For a simple page that iterates over one type of object, the key part of the template will look something like this:
94
-
95
-
```html
96
-
{% forwgin object_list %}
97
-
<tr>
98
-
<td><a href="{{ wg.email_archive }}">{{ wg }}</a></td>
99
-
<td>{{ wg.group_acronym.name }}</td>
100
-
</tr>
101
-
{% endfor %}
102
-
```
103
-
In this case, we're expecting `object_list` to be passed to the template from the view and expecting it to contain objects with the `IETFWG` model.
104
-
105
-
Then add a view for the template to `views.py`. A simple view might look like:
The selects the IETFWG objects from the database and renders the template with them in object_list. The model you're using has to be explicitly imported at the top of views.py in the imports statement.
113
-
114
-
Finally, add a URL to display the view to `urls.py`. For this example, the reference to `list_wgwebmail` view is called:
115
-
116
-
```python
117
-
urlpatterns += patterns('',
118
-
...
119
-
(r'^wg/$', views.list_wgwebmail),
120
-
)
121
-
```
122
-
123
-
#### Testing your work
124
-
125
-
Assuming you have the database settings configured already, you can run the server locally with:
126
-
127
-
```sh
128
-
$ ietf/manage.py runserver localhost:<port>
129
-
```
130
-
where `<port>` is arbitrary. Then connect your web browser to `localhost:<port>` and provide the URL to see your work.
131
-
132
-
When you believe you are ready to commit your work, you should run the test suite to make sure that no tests break. You do this by running
133
-
134
-
```sh
135
-
$ ietf/manage.py test --settings=settings_sqlitetest
136
-
```
137
-
138
-
### Docker Dev Environment
56
+
#### Docker Dev Environment
139
57
140
58
In order to simplify and reduce the time required for setup, a preconfigured docker environment is available.
141
59
142
60
Read the [Docker Dev Environment](docker/README.md) guide to get started.
143
61
144
-
### Continuous Integration
145
-
146
-
*TODO*
147
-
148
62
### Database & Assets
149
63
150
64
Nightly database dumps of the datatracker are available at
> Note that this link is provided as reference only. To update the database in your dev environment to the latest version, you should instead run the `docker/cleandb` script!
154
68
155
-
Additional data files used by the datatracker (e.g. instance drafts, charters, rfcs, agendas, minutes, etc.) are available at
0 commit comments