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#…
** 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
Hi devs,
I just extracted the old google plugin from oldcore (mostly to move a
few dependencies from oldcore with it).
Thinking more about it it seems to me we should retire it mostly for
the following reasons:
* it simply does not work (since probably a very long time): looks
like there is a missing dependency, see
http://tuska.myxwiki.org/xwiki/bin/view/Test/Google
* it depends on a very old (probably more than 4 years old) and
totally unknown google API which probably don't (fully) work anymore.
I tried to look at recent google api jars (mostly to replace the one
we have) but there is so much differences that it could be about
something totally different
Even if it was working there is not reason for it to be packaged by
default in XE.
--
Thomas Mortagne
Hi,
We introduced the Activity Stream macro in XE 2.6
http://extensions.xwiki.org/xwiki/bin/view/Extension/Activity+Macro
We are investigating ways to improve our Activity Stream, but in order to
do that we would want to know your feedback about it (both from a
technology and an user experience pov):
- Is Activity Stream a macro you use?
- What features you most miss about it? Maybe filtering? Maybe pagination?
- Would you like to see more event types, like events generated by
applications?
- Are you using the "Send Message" functionality?
- Other opinions about it.
Your feedback will help us improve the macro by adding needed functionality
and not breaking used one.
I'll gather ideas on
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ActivityStreamFeed…
Thanks,
Caty
Hi devs,
While working on XWIKI-9200 (which is done expect for that little
question ;)) I found that there is no API to check if a document exist
in specific language. You have to do a custom query.
Since I would like to make my code as readable as possible and
considering that we will have to do it eventually anyway here it is:
two choices:
1) add support for reference locale in XWiki#exist and
XWiki#getDocument as well as XWikiHibernateStore#exists. Both
XWikiHibernateStore#loadXWikiDoc and XWikiCacheStore are already
taking into account the locale since they are based on the id (so this
would also be about consistency)
2) introduce new methods like XWiki#existsWithLocale,
XWiki#getDocumentWithLocale and XWikiStoreInterface#existsWithLocale
(and the corresponding implementations)
WDYT ?
2) is obviously the safest but I can't find method names I like. I
would be OK with 1) if everyone is strongly for it but it's probably a
bit dangerous so my vote goes to 2) for now.
--
Thomas Mortagne