21 Nov
2012
21 Nov
'12
2:33 p.m.
Hi Vincent,
if I may, this looks like a common fallacy: developers wanting to build
tools for developers. Of course building a "XWiki for Software Development"
flavor will sound sexy to you, since you're a developer yourself as well as
a XWiki committer. You would be your own target audience. In other words,
you want to build something for yourself.
However, please note that the market for such tools is already very, very
crowded. There's Trac / Bloodhound, there's the whole Atlassian suite,
there is what Github is building as well as countless other solutions.
One of XWiki's great strengths and differentiators is in its ability to let
people manage structured and unstructured content easily. I think we should
keep focusing our work on this instead of trying to enter a crowded space
with little perceivable benefits. In your mind, is this the very best thing
we could possibly work on in order to ensure XWiki's long-term success and
sustainability?
My 2 cents,
Guillaume
On Wed, Nov 21, 2012 at 1:20 PM, Vincent Massol <vincent(a)massol.net> wrote:
On Nov 21, 2012, at 12:40 PM, Jeremie BOUSQUET <jeremie.bousquet(a)gmail.com>
wrote:
Yes, it's the same thing I agree.
Hi Vincent,
2012/11/18 Vincent Massol <vincent(a)massol.net>
the
Hi devs,
> *** Latest emails (taken from mailman or other mailing list software,
> possibly by subscribing the project to a mailing list so that it gets emails)
** 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
Couldn't / shouldn't it be the same thing ?
I know the Mail Archive App is not finished at all, but one feature is
possibility to generate code to include in pages in order to display
filtered lists of emails or topics loaded by the app (filtering by
mailing-list, with ordering, max nb, etc…). If I may add some comment, it's a very nice
idea. To me the biggest trap
is
integration with external sources. If it's
not easily pluggable /
configurable and choice is too restricted, it will attract only a little
subset of developers. In my office for example, I would use it if I could
link to Rhodecode or Mercurial (instead of github) and Redmine (instead
of
jira).
Yep, we would need contributions for other issue trackers but once we
start having something it may attract devs to develop other integrations.
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs