Hi Fabio, I just want to share some work I did related to this subject. * My vision of what extensions we could use for this "Project Development Flavor" and the current XWiki.org status https://docs.google.com/spreadsheet/ccc?key=0AnlUBgkhiZA8dElwbEVmUjJnbEhFOUF... * Vincent's 'initia'l vision http://dev.xwiki.org/xwiki/bin/view/Design/DevelopmentFlavor * XWiki.org websites proposals http://incubator.myxwiki.org/xwiki/bin/view/Improvements/XWikiOrgProposal2 http://incubator.myxwiki.org/xwiki/bin/view/Improvements/XWikiOrgHomepage * A more generic development flavor 'Application Development Flavor' http://incubator.myxwiki.org/xwiki/bin/view/Improvements/AppDevelopmentFlavo... Hope this helps, Caty On Thu, Jul 4, 2013 at 12:56 PM, Fabio Mancinelli < fabio.mancinelli@xwiki.com> wrote:
Hi devs,
I am reviving this thread because in one of the collaborative R&D project we are carrying on at XWikiSAS we might address some of the points stated into this mail.
The project I am talking about is RISCOSS (http://riscoss.eu/bin/view/Main/) which aims at performing risk and cost analysis of OSS in order to help decision makers to adopt OSS in their environment. There's a lot of things in this project that are marginally relevant for XWiki and XWiki Project Development Flavor, but one thing that imho matches part of the goal stated in this thread is that in order to evaluate the risk and cost of an OSS you must start from the OSS project by gathering and analysing project's data.
So in an ideal RISCOSS-Platform users might create "OSS projects descriptors" and associate to them data sources where interesting data can be harvested and presented to the user (...and also to automatic tools that are in charge of performing advanced mumbo-jumbo :))
This looks very similar to one of the point about "dashboard metrics of your project" where ideally you can have plugins scanning data from different data sources (git, mailing lists, IRC, Sonar, Jenkins, whatever) and organize it in nice dashboards.
In RISCOSS probably we'll need to address more problems (e.g., how much to collect and where to store the data) but I think that the high-level feature is almost the same in the two cases.
I am open to suggestions and discussions and I'll try to keep you posted as the project advances.
Thanks, Fabio
On Sun, Nov 18, 2012 at 11:11 AM, Vincent Massol <vincent@massol.net> wrote:
Hi devs,
I've noticed Apache BloodHound (https://issues.apache.org/bloodhound/) and this reminded of this idea I've had several times in the past: Creating a Project Development Flavor of XE. I mentioned it in some other email already but I wanted to see if this excites you as much as it does for me and maybe we could brainstorm in this thread about what it could be like .
Some scattered thoughts:
* 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.
* 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.
* We need to finish the Flavor idea by allowing the DM to list flavors.
* Some ideas of content for this Development Project flavor: ** A home page dashboard about metrics of your project. These metrics would be retried from external sources. Examples: *** Statistics about commits using Git/GitHub *** 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) *** Latest issues (taken from JIRA for example) *** Screenshot example: http://incubator.myxwiki.org/xwiki/bin/view/Improvements/XWikiOrgProposal2#H... ** A Release application to help perform releases ** 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 ** A Release notes application ** The Blog application ** Ability to generate a whole PDF for the project's documentation for a given version ** A modern and nice skin (either Lyrebird or the new Skin proposal: http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Skin4x) ** A layout configured for the flavor ** 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 ** Some predefined templates for creating well known project pages: source repository, build, hall in fame, project documentation home page, etc ** The IRC Bot application ** Bundle the JIRA macro ** Bundle the FAQ application ** A Roadmap application
* 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).
WDYT?
Add your ideas to this email thread or, better, on http://dev.xwiki.org/xwiki/bin/view/Design/DevelopmentFlavor
Thanks -Vincent
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs