Wiki source code of Flavor: Development

Last modified by Vincent Massol on 2024/11/19 16:12

Show last authors
1 {{include document="XWiki.DesignClassSheet"/}}
2
3 * First, from the point of view of the XWiki project I believe it could be a game changer if we did it right since it has the potential of being adopted by projects around the world and thus making them discover xwiki as a result. And since they're developers they would be able to take advantage of XWiki's development features and contribute back to the project through extensions for example.
4
5 * Ideally it would be awesome that this project be started independently of the XWiki project I think and just use XWiki as the platform since it's a full fledged project with a different goal than the XWiki project itself.
6
7 * We need to finish the Flavor idea by allowing the DM to list flavors.
8
9 * Some ideas of content for this Development Project flavor:
10 ** A home page dashboard about metrics of your project. These metrics would be retried from external sources. Examples:
11 *** Statistics about commits using Git/GitHub
12 *** Latest emails (taken from mailman or other mailing list software, possibly by subscribing the project to a mailing list so that it gets the emails)
13 *** Latest issues (taken from JIRA for example)
14 *** Screenshot example: http://incubator.myxwiki.org/xwiki/bin/view/Improvements/XWikiOrgProposal2#HCommunityHome
15 ** A Release application to help perform releases
16 ** A forum application, for example the Mail Archive Application done by Jeremie which would need to be improved to add ability to post from it
17 ** A Release notes application
18 ** The Blog application
19 ** Ability to generate a whole PDF for the project's documentation for a given version
20 ** A modern and nice skin (either Lyrebird or the new Skin proposal: http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Skin4x)
21 ** A layout configured for the flavor
22 ** Future: a simple issue tracker (or integrate one) for those who want an all-in-one solution. However keep the external issue tracker possibility for those already having an issue tracker
23 ** Some predefined templates for creating well known project pages: source repository, build, hall in fame, project documentation home page, etc
24 ** The IRC Bot application
25 ** Bundle the JIRA macro
26 ** Bundle the FAQ application
27 ** A Roadmap application
28
29 * Of course we should use this flavor on xwiki.org itself. And we could move some of the modules we currently have in platform and that would make more sense there (jira macro, IRC Bot application, FAQ application, etc).

Get Connected