You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@community.apache.org by "Dave Brondsema (JIRA)" <ji...@apache.org> on 2017/02/09 22:28:41 UTC

[jira] [Updated] (COMDEV-211) Allura - discussion thread improvements

     [ https://issues.apache.org/jira/browse/COMDEV-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dave Brondsema updated COMDEV-211:
----------------------------------
    Issue Type: Improvement  (was: New Feature)

> Allura - discussion thread improvements
> ---------------------------------------
>
>                 Key: COMDEV-211
>                 URL: https://issues.apache.org/jira/browse/COMDEV-211
>             Project: Community Development
>          Issue Type: Improvement
>          Components: GSoC/Mentoring ideas
>            Reporter: Dave Brondsema
>              Labels: css, gsoc2017, javascript, mongodb, python
>
> In Allura, threaded discussions are used everywhere.  They are the core part of forums, and are used on each ticket, wiki page, blog post, etc.  Several improvements can be made in this specific area.  This code is in python, with a mongodb backend.  Frontend JS & CSS would be necessary for some of these items: 
> * better pagination through long discussions (ajax fetching, nicer display of each item, etc) https://forge-allura.apache.org/p/allura/tickets/5709/
> * add toggle to show/hide "meta" comments (e.g. status or field changes) https://forge-allura.apache.org/p/allura/tickets/7883/
> * when emails are converted into comments, parse the reply so only the new text is included.  https://forge-allura.apache.org/p/allura/tickets/1782/
> * performance improvements https://forge-allura.apache.org/p/allura/tickets/4359/
> * separate list of attachments from all the comments https://forge-allura.apache.org/p/allura/tickets/6096/
> * etc...



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)