22 Nov
2016
22 Nov
'16
3:25 p.m.
On 22 Nov 2016, at 15:03, Guillaume Delhumeau
<guillaume.delhumeau(a)xwiki.com> wrote:
2016-11-22 14:39 GMT+01:00 Vincent Massol <vincent(a)massol.net>et>:
don't
I completely agree and there is no discord on this.
But I still believe that if we promote our tool as a better alternative for
emails and we keep sending brainstorm, votes, news, we're not giving a
consistent signal.
I’m not sure I agree that a wiki (xwiki or any wiki) should replace email.
I see a wiki as a way to extract pure knowledge from their temporary places (irc, mailing
lists, etc) into a place where it can be aggregated and augmented, representing the sum of
knowledge on a topic.
So, a wiki is a good alternative for replacing knowledge stored in emails but emails and
mailing lists are better for asynchronous interactions. If you use comments if a wiki to
achieve this then you’re just using emails too (since you’re going to notify that a
comment has been posted and you’ll send an email and then users can respond to email and
then you get the same problems you have with email, ie you don’t have a single summary of
the knowledge ;)).
BTW I put forums in the same category as emails for organizing information.
On 22 Nov 2016, at 14:18, Guillaume Delhumeau
<
guillaume.delhumeau(a)xwiki.com> wrote:
2016-11-22 13:16 GMT+01:00 Vincent Massol <vincent(a)massol.net>et>:
>
>> On 22 Nov 2016, at 12:13, Guillaume Delhumeau <
> guillaume.delhumeau(a)xwiki.com> wrote:
>>
>> Hi everybody.
>>
>> Today I would like to speak about an issue that annoys me for years.
>>
>> We are working on a tool whose one of the objectives is to stop
> scattering
>> information in multiple places. It's even the main argument explained
in
>> the video integrated on the home page of
XWiki:
>> https://www.youtube.com/watch?v=9QTWrZ7OfzI.
>>
>> But on the other hand, we, developers of XWiki, do the opposite in
>> practice. We discuss on mailing lists that are archived on Markmail, we
>> report issues on Jira and we do investigations on design.xwiki.org,
and
> I
>> don't even count Github.
>
> Honestly I don’t see the relationship between the tool we develop and
how
it’s
developed. These are completely separate things!
We develop a tool that centralize information and we don't use it to
centralize our own informations, except documentation.
Using a car is pretty easy but creating one is hard. That’s normal and
expected :)
Yes but if you also create a tool to help you creating a car and you use it yourself,
XWiki is not a tool to help develop software. It can be used for some
parts of the software development process (the documentation part, the
requirements part, etc). But for example it won’t help you store your
sources files and it won’t help you develop your Java Code (your IDE will
though).
Just look at the video:
Where did I say that? :)
Wikis are the best for knowledge aggregation and collective intelligence for sure.
But development is not just about that. It’s also about discussing and reaching
conclusions and agreements.
Thanks
-Vincent
* Share your ideas & knowledge, promote
collective intelligence
Your answer is ML is the best breed for that… you're giving a bad image to your product.
>
> I’d never promote XWiki as a tool to replace any of the tools I’ve
> mentioned in my previous reply. If you do, you’re doing a disservice to
> your users.
>
> XWiki is not:
> - a forum
> - a CI
> - a SCM
> - a chat tool
> - a mailing list
> - etc.
>
> Each of these tools have a purpose and it’s certainly not that of XWiki.
>
> For example a forum is a place to discuss. A wiki is not a place to
> discuss (it can be as an edge case but it’s certainly not a best of breed
> tool for that). A wiki is first and foremost a place where you can
> aggregate knowledge.
>
> So yes we should use XWiki to aggregate knowledge And this is exactly what
> we do on xwiki.org and design.xwiki.org.
>
> [snip]
>
> Thanks
> -Vincent
>