code-20e0e5ce217f/website/www/Makefile0000644000000000000000000000120011777631144015656 0ustar 00000000000000TMP := _tmp HTML := html .PHONY: help clean html linkcheck help: @echo "Please use \`make ' where is one of" @echo " html to make standalone HTML files" @echo " linkcheck to check all external links for integrity" clean: -rm -rf $(TMP) docs: ln -s ../../doc ./docs html: docs mkdir -p $(TMP)/doctrees $(HTML) sphinx-build -b html -d $(TMP)/doctrees . $(HTML) linkcheck: mkdir -p $(TMP)/linkcheck $(TMP)/doctrees sphinx-build -b linkcheck -d $(TMP)/doctrees . $(TMP)/linkcheck @echo @echo "Link check complete; look for any errors in the above output " \ "or in .build/linkcheck/output.txt." code-20e0e5ce217f/website/www/README0000644000000000000000000000052611777631144015110 0ustar 00000000000000These are the sources of the Roundup website. To build them, you need Sphinx (http://sphinx.pocoo.org/). pip install sphinx pip install sphinxcontrib-cheeseshop The content of the 'docs' section are mirrored in from the roundup package - typically just a symlink of "docs" from the roundup source. Good luck ! Stefan code-20e0e5ce217f/website/www/_static/style.css0000644000000000000000000000414111777631144017525 0ustar 00000000000000/* layout*/ body { font-family: sans-serif, Arial, Helvetica; background-color: white; color: #333; margin:0; padding: 0 3em 0 13em; } body > .header { margin: 0 0 0 -13em;} body > .footer { margin: 0 0 0 -13em; clear:both;} body > .navigation { margin-left: -13em; width: 13em; float: left; } body > .content { width: 100%; margin: 0; } body > .header > #searchbox { position: absolute; right: 1em; top: 1em;} /* style */ :link { color: #bb0000; text-decoration: none;} :visited { color: #770000; text-decoration: none;} a.toc-backref { color: #000000; } .header h1 { margin-left: 1em; } body { font-family: sans-serif, Arial, Helvetica; background-color: #f5f5f5; color: #333; } .menu { padding: 0; margin-right: 1em;} .menu ul { padding: 0; margin: 0; } .menu li { margin: 5pt 0; } .menu > ul > li > * { display: block; padding: 2pt 2pt 2pt 10pt; border: solid thin #dadada; background-color:#ffffff; } .menu > ul > li.current > * { background-color:#dddddd; } .menu ul li:first-child { margin-top:0;} .menu ul { list-style-type:none;} /* sub-menus are indented */ .menu > ul > li > ul, .menu > ul > li.current > ul { border:none; background-color: inherit; } .menu ul ul { margin-left: 2em; font-size: smaller; } /* sub-menu items draw a separator */ .menu ul ul > li { margin: 0; padding: 0; border: none; border-top: solid thin #dadada; background-color: inherit; } .menu ul ul > li:first-child { border-top: none; } .footer { font-size: small; text-align: center; color: lightgrey; } .content { padding: 1em; border: solid thin #dadada; background-color: #ffffff; } /* This is a little hack to inject a 'news' block into the title page without having to set up a custom directive. */ #roundup-issue-tracker .note { float: right; width: auto; border: solid thin #dadada; background-color:#f5f5f5; padding: 1em; margin: 1em; } #roundup-issue-tracker .note .admonition-title { display: none; } table { border-collapse: collapse; border-spacing: 1px; background-color: #fafafa; } input, textarea { border-width: 1px; } code-20e0e5ce217f/website/www/_templates/layout.html0000644000000000000000000001112311777631144020563 0ustar 00000000000000 {{ metatags }} {%- if builder != 'htmlhelp' %} {%- set titlesuffix = docstitle|e %} {%- set titlesuffix = " - " + titlesuffix %} {%- endif %} {{ title|striptags }}{{ titlesuffix }} {%- if builder == 'web' %} {%- for link, type, title in page_links %} {%- endfor %} {%- else %} {%- endif %} {%- if builder != 'htmlhelp' %} {%- for scriptfile in script_files %} {%- endfor %} {%- if use_opensearch %} {%- endif %} {%- if favicon %} {%- endif %} {%- endif %} {%- block linktags %} {%- if hasdoc('about') %} {%- endif %} {%- if hasdoc('copyright') %} {%- endif %} {%- if parents %} {%- endif %} {%- if next %} {%- endif %} {%- if prev %} {%- endif %} {%- endblock %} {%- block extrahead %} {% endblock %}

Roundup

{%- if pagename != "search" %} {%- endif %}
{{ toctree() }}
{% block body %} {% endblock %}
{%- block footer %}

hosted by SourceForge.net Logo

{%- if hasdoc('copyright') %} {% trans path=pathto('copyright'), copyright=copyright|e %}© Copyright {{ copyright }}.{% endtrans %} {%- else %} {% trans copyright=copyright|e %}© Copyright {{ copyright }}.{% endtrans %} {%- endif %} {%- if last_updated %} {% trans last_updated=last_updated|e %}Last updated on {{ last_updated }}.{% endtrans %} {%- endif %} {%- if show_source and has_source and sourcename %}

{{ _('source') }}

{%- endif %}
{%- endblock %} code-20e0e5ce217f/website/www/code.txt0000644000000000000000000000203011777631144015673 0ustar 00000000000000Code ==== Changelog ---------- The changelog is available as `CHANGES.txt in the SCM repository `_. Browse ------ You may browse the repository via the `Mercurial webinterface `_. Read-only Access ---------------- Read-only repository access is provided through :: hg clone http://roundup.hg.sourceforge.net:8000/hgroot/roundup/roundup The URL for the webinterface works, too, but you will see messages about redirects to the URL shown here. Read-write Access ----------------- The read/write access uses your SourceForge.net ssh password or ssh key to authorize your access. (See `SF's site documentation on Mercurial access `_) :: hg clone ssh://@roundup.hg.sourceforge.net/hgroot/roundup/roundup Of course a roundup developer must have granted you write access first - ask for it on the roundup-devel list. code-20e0e5ce217f/website/www/conf.py0000644000000000000000000001354311777631144015532 0ustar 00000000000000# -*- coding: utf-8 -*- # # Roundup documentation build configuration file, created by # sphinx-quickstart on Tue Jan 20 17:33:20 2009. # # This file is execfile()d with the current directory set to its containing dir. # # The contents of this file are pickled, so don't put values in the namespace # that aren't pickleable (module imports are okay, they're removed automatically). # # All configuration values have a default; values that are commented out # serve to show the default. import sys, os # If your extensions are in another directory, add it here. If the directory # is relative to the documentation root, use os.path.abspath to make it # absolute, like shown here. #sys.path.append(os.path.abspath('.')) # General configuration # --------------------- # Add any Sphinx extension module names here, as strings. They can be extensions # coming with Sphinx (named 'sphinx.ext.*') or your custom ones. #extensions = ['toctree'] # Add any paths that contain templates here, relative to this directory. templates_path = ['_templates'] # The suffix of source filenames. source_suffix = '.txt' # The encoding of source files. #source_encoding = 'utf-8' # The master toctree document. master_doc = 'contents' # General information about the project. project = u'Roundup' copyright = u'2009, Richard Jones' # The version info for the project you're documenting, acts as replacement for # |version| and |release|, also used in various other places throughout the # built documents. # # The short X.Y version. version = '1.4' # The full version, including alpha/beta/rc tags. release = '1.4' # The language for content autogenerated by Sphinx. Refer to documentation # for a list of supported languages. #language = None # There are two options for replacing |today|: either, you set today to some # non-false value, then it is used: #today = '' # Else, today_fmt is used as the format for a strftime call. #today_fmt = '%B %d, %Y' # List of documents that shouldn't be included in the build. #unused_docs = [] # List of directories, relative to source directory, that shouldn't be searched # for source files. exclude_trees = ['.build'] # The reST default role (used for this markup: `text`) to use for all documents. #default_role = None # If true, '()' will be appended to :func: etc. cross-reference text. #add_function_parentheses = True # If true, the current module name will be prepended to all description # unit titles (such as .. function::). #add_module_names = True # If true, sectionauthor and moduleauthor directives will be shown in the # output. They are ignored by default. #show_authors = False # The name of the Pygments (syntax highlighting) style to use. pygments_style = 'sphinx' # Options for HTML output # ----------------------- # The style sheet to use for HTML and HTML Help pages. A file of that name # must exist either in Sphinx' static/ path, or in one of the custom paths # given in html_static_path. html_style = 'default.css' # The name for this set of Sphinx documents. If None, it defaults to # " v documentation". #html_title = None # A shorter title for the navigation bar. Default is the same as html_title. #html_short_title = None # The name of an image file (relative to this directory) to place at the top # of the sidebar. #html_logo = None # The name of an image file (within the static path) to use as favicon of the # docs. This file should be a Windows icon file (.ico) being 16x16 or 32x32 # pixels large. #html_favicon = None # Add any paths that contain custom static files (such as style sheets) here, # relative to this directory. They are copied after the builtin static files, # so a file named "default.css" will overwrite the builtin "default.css". html_static_path = ['_static'] # If not '', a 'Last updated on:' timestamp is inserted at every page bottom, # using the given strftime format. html_last_updated_fmt = '%b %d, %Y' # If true, SmartyPants will be used to convert quotes and dashes to # typographically correct entities. #html_use_smartypants = True # Custom sidebar templates, maps document names to template names. #html_sidebars = {} html_collapse_toctree = True # Additional templates that should be rendered to pages, maps page names to # template names. #html_additional_pages = {} html_add_permalinks = False # If false, no module index is generated. #html_use_modindex = True # If false, no index is generated. #html_use_index = True # If true, the index is split into individual pages for each letter. #html_split_index = False # If true, the reST sources are included in the HTML build as _sources/. #html_copy_source = True # If true, an OpenSearch description file will be output, and all pages will # contain a tag referring to it. The value of this option must be the # base URL from which the finished HTML is served. #html_use_opensearch = '' # If nonempty, this is the file name suffix for HTML files (e.g. ".xhtml"). #html_file_suffix = '' # Output file base name for HTML help builder. htmlhelp_basename = 'Roundupdoc' # Options for LaTeX output # ------------------------ # The paper size ('letter' or 'a4'). #latex_paper_size = 'letter' # The font size ('10pt', '11pt' or '12pt'). #latex_font_size = '10pt' # Grouping the document tree into LaTeX files. List of tuples # (source start file, target name, title, author, document class [howto/manual]). latex_documents = [ ('docs/index', 'Roundup.tex', ur'Roundup Documentation', ur'Richard Jones', 'manual'), ] # The name of an image file (relative to this directory) to place at the top of # the title page. #latex_logo = None # For "manual" documents, if this is true, then toplevel headings are parts, # not chapters. #latex_use_parts = False # Additional stuff for the LaTeX preamble. #latex_preamble = '' # Documents to append as an appendix to all manuals. #latex_appendices = [] # If false, no module index is generated. #latex_use_modindex = True code-20e0e5ce217f/website/www/contact.txt0000644000000000000000000000216611777631144016426 0ustar 00000000000000Contact ======= We maintain the following mailing lists: ================ ========================================================================== ====================================================================================== roundup-user `sign up `_ `archive `_ roundup-devel `sign up `_ `archive `_ roundup-checkins `sign up `_ `archive `_ ================ ========================================================================== ====================================================================================== These lists are moderated to protect them against spam. Please sign up if you intend to mail repeatedly. You may talk to Roundup developers directly via irc at irc://irc.oftc.net/roundup. code-20e0e5ce217f/website/www/contents.txt0000644000000000000000000000104311777631144016621 0ustar 00000000000000.. Roundup documentation master file, created by sphinx-quickstart on Tue Jan 20 17:33:20 2009. You can adapt this file completely to your liking, but it should at least contain the root `toctree` directive. Sitemap ======= Contents: .. toctree:: :maxdepth: 2 Home Download docs Issues contact Wiki code Indices and tables ================== * :ref:`genindex` * :ref:`modindex` * :ref:`search` code-20e0e5ce217f/website/www/docs.txt0000644000000000000000000000046011777631144015716 0ustar 00000000000000Docs ==== .. toctree:: :maxdepth: 2 docs/features docs/installation docs/upgrading docs/FAQ docs/user_guide docs/customizing docs/admin_guide docs/xmlrpc Design (original) docs/developers docs/tracker_templates docs/acknowledgements docs/license code-20e0e5ce217f/website/www/index.txt0000644000000000000000000000337611777631144016106 0ustar 00000000000000Roundup Issue Tracker ===================== .. pypi-release:: roundup :prefix: Download :class: note Roundup is a simple-to-use and -install issue-tracking system with command-line, web and e-mail interfaces. It is based on the winning design from Ka-Ping Yee in the Software Carpentry "Track" design competition. The current stable version of Roundup is 1.4.x which has quite a comprehensive :doc:`feature set `. For more information see the :doc:`design overview `, and all the other :doc:`documentation `. Roundup has been deployed for: * bug tracking and TODO list management (the classic installation) * customer help desk support (with a wizard for the phone answerers, linking to networking, system and development issue trackers) * issue management for IETF working groups * sales lead tracking * conference paper submission and double-blind referee management * weblogging (well, almost :) ...and so on. It's been designed with :doc:`flexibility ` in mind - it's not just another bug tracker. Roundup ships with a *demo tracker* to play with - after you've unpacked the source, just run "python demo.py" and load up the URL it prints out! Roundup was originally released as version 0.1.1 in late August, 2001. The first `change note`_ I wrote says: Needed a bug tracking system. Looked around. Tried to install many Perl-based systems, to no avail. Got tired of waiting for Roundup to be released. Had just finished major product project, so needed something different for a while. Roundup here I come... .. _`download`: http://cheeseshop.python.org/pypi/roundup .. _`change note`: http://svn.roundup-tracker.org/viewvc/roundup/roundup/trunk/CHANGES.txt?view=markup