comparison doc/developers.txt @ 6343:bea4a6956c89

Moved roundup-tracker.org infrastructure docs to website/README.txt This change makes developers.txt as the place for people contributing to the code base and README.txt to those maintaining the infrastructure. The old state was website/README.txt had reference to doc/developers.txt for updating issues.roundup-tracker.org. Removed reference and move docs to website/README.txt. doc/developers.txt had a section on updating website and wiki that referenced website/README.txt. Removed section, replaced with sentence that references website/README.txt for all infrastructure.
author John Rouillard <rouilj@ieee.org>
date Sun, 14 Mar 2021 20:52:11 -0400
parents b2eb59ada444
children cbc18a8bc61f
comparison
equal deleted inserted replaced
6342:31bac6f2dd8b 6343:bea4a6956c89
10 Contents 10 Contents
11 11
12 .. contents:: 12 .. contents::
13 :local: 13 :local:
14 14
15 If you are looking for info on managing the roundup-tracker.org
16 infrastructure, that information has migrated to website/README.txt
17 in the roundup repo.
18
15 Getting Started 19 Getting Started
16 --------------- 20 ---------------
17 21
18 Anyone wishing to help in the development of Roundup must read `Roundup's 22 Anyone wishing to help in the development of Roundup must read `Roundup's
19 Design Document`_ and the `implementation notes`_. 23 Design Document`_ and the `implementation notes`_.
22 26
23 - roundup-devel mailing list at 27 - roundup-devel mailing list at
24 https://sourceforge.net/projects/roundup/lists/roundup-devel 28 https://sourceforge.net/projects/roundup/lists/roundup-devel
25 - The issue tracker running at 29 - The issue tracker running at
26 https://issues.roundup-tracker.org/ 30 https://issues.roundup-tracker.org/
27
28 Website, wiki
29 -------------
30
31 The website is in our repository, so is the configuration of the wiki.
32 Please check the README.txt in the "website" subdirectory
33 of a current checkout.
34
35 Issue Tracker
36 -------------
37
38 The tracker resides on bugs.ams1.psf.io (188.166.48.69). You can also
39 ssh to issues.roundup-tracker.org. They have the same fingerprint:
40
41 ED25519 key fingerprint is f1:f7:3d:bf:3b:01:8d:e1:4e:30:b3:0f:6e:98:b8:9b.
42
43 The roundup installation belongs to the user roundup.
44 The setup uses virtualenv. Use the python version:
45
46 /srv/roundup/env/bin/python2.7
47
48 to get a python with roundup on the PYTHONPATH.
49
50 The Roundup tracker https://issues.roundup-tracker.org/ is in
51 /srv/roundup/trackers/roundup/ with the database set to
52 /srv/roundup/data/roundup/. Note that postgres is used for the
53 backend, so the database directory above is used for msgs and files.
54
55 Source is in: /srv/roundup/src/
56
57 Roundup is run using gunicorn and wsgi.
58
59 You have 'sudo -u roundup' access if you need to run things as the
60 roundup user.
61
62 The configuration is in the "website/issues" section of Roundup's
63 Mercurical SCM repository and copied manually to the live tracker.
64
65 * get a working copy of roundup/website/issues from the SCM, either via
66 hg clone https://hg.code.sf.net/p/roundup/code
67 or download a snapshot:
68 https://sourceforge.net/p/roundup/code/ci/default/tarball
69
70 * check the differences
71 diff -ur /srv/roundup/trackers/roundup/ roundup/website/issues/
72
73 Copy differences using 'sudo -u roundup ...'.
74
75 Getting a user account
76 ~~~~~~~~~~~~~~~~~~~~~~
77
78 To get access to the host, submit a pull request for:
79
80 https://github.com/python/psf-salt
81
82 by forking the repo, make a change similar to:
83
84 https://github.com/rouilj/psf-salt/commit/2aa55d0fc5a343f45f5507437d3fba077cbaf852
85
86 and submit it as a pull request. Contact ewdurbin via #roundup IRC or by
87 adding an issue to the master psf-salt repo.
88 31
89 32
90 Small Changes 33 Small Changes
91 ------------- 34 -------------
92 35

Roundup Issue Tracker: http://roundup-tracker.org/