On 11/18/2012 05:11 AM, Vincent Massol 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 .
This could work but would not be easy, developers have pretty specific requirements.
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.
Indeed.
* 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)
Just converting a mailing list into something web readable that's not aweful to read
is a big bonus.
***Buildbot integration.
** 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
+1
** Some predefined templates for creating well known
project pages: source repository, build, hall in fame, project documentation home page,
etc
** The IRC Bot application
This has to work or developers won't use it. At the moment the irc bot is a bit of a
rough edge in XWiki.
** 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?
I think the idea has merit, I would consider a solution like this for my project but it
needs to be light on resources.
I think the "light on resources" requirement is going to be a general trend
within the developer community, there are offerings which use around 100MB of system ram
total and it's hard to argue that using 400M to 1G is worth it for the benefits.
Thanks,
Caleb
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(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs