The document outlines plans for a third generation of the OpenNTF.org website, including: 1. Deploying the Redmine project management application and integrating version control systems like Git and GitHub to provide improved functionality for contributors. 2. Changing consumer-facing project pages to be simpler and link to Redmine, while retaining functionality like downloads and reviews. 3. Creating Redmine projects for all existing OpenNTF projects over two years while retaining the current system in parallel, then transitioning fully to Redmine.

1. 02/20/12 Declan Lynch Bruce Elgort Niklas Heidloff OpenNTF.Org - The Third Generation

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. OpenNTF.Org Web Site Designs First Generation Second Generation Third Generation To be done

4. Goals Change the site design to use a modern look and feel, specifically the black OneUI

5. Provide version control systems on OpenNTF First prio: Git, Mercurial

6. Second prio: SVN Extend the reach by being present in established communities First prio: GitHub

7. Second prio: Bitbucket Provide the next generation of project/lifecycle management

8. Objectives Deploy the open source project management application Redmine on OpenNTF and use it as the user interface for contributors

9. Change the current XPages based project management app to be consumer focussed and link to Redmine for contributors

10. Deploy Git and Mercurial servers on OpenNTF and integrate them in Redmine

11. Deploy Redmine plugin to integrate GitHub in Redmine

12. Change the style of the home page, blog, documents, project finder page and project homes pages to the black OneUI

13. Change the Redmine default UI to something close to the black OneUI

14. New Project Home Pages for Consumers Redmine doesn't provide all functionality needed so that some parts need to be done via XPages, esp. releases and screenshots

15. The new project home pages will be consumer focussed with easy mechanisms to download releases and rate projects

16. Functionality for contributors (e.g. assignment of members, defect triaging, code reviews) will be done in Redmine

17. The following functionality remains on the XPages based UI Core home page with rich text project description and rating (reachable via openntf.org/p/projectName or myproject.openntf.org)

18. Releases (existing download tracking can be used)

19. Screenshots

20. Reviews There will be actions/links to create defects and feature requests which launch into the Redmine UI

21. Additionally there will be a new widget to display project activity read from Redmine

22. Help wanted and email owner will be removed

23. There will be two feeds: Consumers and contributors

24. New Project Management for Contributors The main functionality for contributors will be handled in Redmine Integrated SCM

25. Defects and feature requests

26. Wiki, documents, files and forums SCM repositories are created when projects are created Git (git.openntf.org) or Mercurial (hg.openntf.org) on OpenNTF GitHub repositories can be linked to Redmine projects

27. The contributors project home pages can be reached from the consumer home pages and URL projects.openntf.org/projectName

28. Documentation can be written in a Wiki

29. Project specific forums can be used

30. Contributors Home Page

31. SCM is created automatically

32. Git and Mercurial Repositories

33. GitHub can be used as ext. Repository

34. Code Reviews

35. Issues

36. New Issue

37. News

38. Wiki

39. Forums

40. Activity

41. More Modules available

42. Staging All new projects will use the new reduced consumer home page and Redmine When OpenNTF users create a project the XPages project and Redmine project are created All projects that haven't been changed for two years will be marked as archived They will continue to use the current project management UI (but read only)

43. They will be less visible on the projects finder page

44. They can be reactivated by owners, e.g. to be able to create new releases For all projects that have been changed in the last two years Redmine projects will be created No data will be migrated programmatically

45. The projects will continue to use the current XPages UI (but read only) and in parallel the new Redmine UI

46. After one year we'll remove the information that should be stored in Redmine from the consumer project home pages

47. Open Questions How can we a SSO between Domino and Redmine on Apache be done?

48. How can the banner and sidebar ads be added to Redmine?

49. How much can the Redmine theme be changed to look more like the black OneUI?

50. Using GitHub currently requires manual config. When can this be automated?

51. How to do search between NSFs and Redmine?

52. High Level Tasks Set up Ubuntu server with SSH

53. Set up Git and Mercurial servers

54. Figure out out to do SSO

55. Use black OneUI on Redmine

56. Add ads to Redmine via Ruby

57. Use black OneUI for XPages

58. Change project creation to create Redmine projects and read data like owners, activities from Redmine

59. Implement staging (archived projects, read only information, reactivate)

60. Set up SSL

61. Please let us know what you think We'd appreciate help with the implementation