Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

OpenNTF.Org Third Generation


Published on

OpenNTF.Org Third Generation

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

OpenNTF.Org Third Generation

  1. 1. 02/20/12 Declan Lynch Bruce Elgort Niklas Heidloff OpenNTF.Org - The Third Generation
  2. 2. Disclaimer This deck is only a starting point outlining some of the ideas how we'd like to extend the OpenNTF.Org web site We are seeking for feedback and volunteers None of this has been committed or approved
  3. 3. OpenNTF.Org Web Site Designs First Generation Second Generation Third Generation To be done
  4. 4. Goals <ul><li>Change the site design to use a modern look and feel, specifically the black OneUI
  5. 5. Provide version control systems on OpenNTF </li><ul><li>First prio: Git, Mercurial
  6. 6. Second prio: SVN </li></ul><li>Extend the reach by being present in established communities </li><ul><li>First prio: GitHub
  7. 7. Second prio: Bitbucket </li></ul><li>Provide the next generation of project/lifecycle management </li></ul>
  8. 8. Objectives <ul><li>Deploy the open source project management application Redmine on OpenNTF and use it as the user interface for contributors
  9. 9. Change the current XPages based project management app to be consumer focussed and link to Redmine for contributors
  10. 10. Deploy Git and Mercurial servers on OpenNTF and integrate them in Redmine
  11. 11. Deploy Redmine plugin to integrate GitHub in Redmine
  12. 12. Change the style of the home page, blog, documents, project finder page and project homes pages to the black OneUI
  13. 13. Change the Redmine default UI to something close to the black OneUI </li></ul>
  14. 14. New Project Home Pages for Consumers <ul><li>Redmine doesn't provide all functionality needed so that some parts need to be done via XPages, esp. releases and screenshots
  15. 15. The new project home pages will be consumer focussed with easy mechanisms to download releases and rate projects
  16. 16. Functionality for contributors (e.g. assignment of members, defect triaging, code reviews) will be done in Redmine
  17. 17. The following functionality remains on the XPages based UI </li><ul><li>Core home page with rich text project description and rating (reachable via or
  18. 18. Releases (existing download tracking can be used)
  19. 19. Screenshots
  20. 20. Reviews </li></ul><li>There will be actions/links to create defects and feature requests which launch into the Redmine UI
  21. 21. Additionally there will be a new widget to display project activity read from Redmine
  22. 22. Help wanted and email owner will be removed
  23. 23. There will be two feeds: Consumers and contributors </li></ul>
  24. 24. New Project Management for Contributors <ul><li>The main functionality for contributors will be handled in Redmine </li><ul><li>Integrated SCM
  25. 25. Defects and feature requests
  26. 26. Wiki, documents, files and forums </li></ul><li>SCM repositories are created when projects are created </li><ul><li>Git ( or Mercurial ( on OpenNTF </li></ul><li>GitHub repositories can be linked to Redmine projects
  27. 27. The contributors project home pages can be reached from the consumer home pages and URL
  28. 28. Documentation can be written in a Wiki
  29. 29. Project specific forums can be used </li></ul>
  30. 30. Contributors Home Page
  31. 31. SCM is created automatically
  32. 32. Git and Mercurial Repositories
  33. 33. GitHub can be used as ext. Repository
  34. 34. Code Reviews
  35. 35. Issues
  36. 36. New Issue
  37. 37. News
  38. 38. Wiki
  39. 39. Forums
  40. 40. Activity
  41. 41. More Modules available
  42. 42. Staging <ul><li>All new projects will use the new reduced consumer home page and Redmine </li><ul><li>When OpenNTF users create a project the XPages project and Redmine project are created </li></ul><li>All projects that haven't been changed for two years will be marked as archived </li><ul><li>They will continue to use the current project management UI (but read only)
  43. 43. They will be less visible on the projects finder page
  44. 44. They can be reactivated by owners, e.g. to be able to create new releases </li></ul><li>For all projects that have been changed in the last two years Redmine projects will be created </li><ul><li>No data will be migrated programmatically
  45. 45. The projects will continue to use the current XPages UI (but read only) and in parallel the new Redmine UI
  46. 46. After one year we'll remove the information that should be stored in Redmine from the consumer project home pages </li></ul></ul>
  47. 47. Open Questions <ul><li>How can we a SSO between Domino and Redmine on Apache be done?
  48. 48. How can the banner and sidebar ads be added to Redmine?
  49. 49. How much can the Redmine theme be changed to look more like the black OneUI?
  50. 50. Using GitHub currently requires manual config. When can this be automated?
  51. 51. How to do search between NSFs and Redmine? </li></ul>
  52. 52. High Level Tasks <ul><li>Set up Ubuntu server with SSH
  53. 53. Set up Git and Mercurial servers
  54. 54. Figure out out to do SSO
  55. 55. Use black OneUI on Redmine
  56. 56. Add ads to Redmine via Ruby
  57. 57. Use black OneUI for XPages
  58. 58. Change project creation to create Redmine projects and read data like owners, activities from Redmine
  59. 59. Implement staging (archived projects, read only information, reactivate)
  60. 60. Set up SSL </li></ul>
  61. 61. Please let us know what you think We'd appreciate help with the implementation