16 May
2013
16 May
'13
5:10 p.m.
On 05/16/2013 10:25 AM, Vincent Massol wrote:
I'm rather -0 ATM and very close to -1 because:
1) I haven't heard from a windows dev for a long time, I don't think that happens
that often
Maybe they weren't motivated enough to search for a solution, and just
gave up?
2) It's a *huge* change and it should definitely
not be done lightly. We would need to plan a period like 2 full days, all devs would need
to stop working on what they do and help out. For example all pages on xwiki.org having
some github links are going to be broken and will need to be updated (that's probably
around hunded of pages overall)
So postponing it will solve what?
3) Windows devs have a simple solution which is to use
cygwin so it's not a blocker
Enforcing a special environment is something we try to avoid as much as
possible.
If the checkout doesn't work out of the box with the user's favorite
tool, will they have the motivation to search for an explanation, read
our documentation, set up the "right" tool, and learn to use a new
environment that's not (perceived to be) as good as what they already
know and are efficient with?
This is not a "simple" solution, IMHO. XWiki Development should be
environment-independent.
Thanks
-Vincent
On May 16, 2013, at 4:14 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com> wrote:
> Reviving http://markmail.org/message/hlnqke3igkbec332 for as an official vote.
>
> We have waited way too long and I think we really need to find a
> solution even if none of the committers use Windows since a long time.
> Every time a Windows dev even think of contributing he is very quickly
> discouraged...
>
> As a reminder the issue is that working on XWiki source code is a pain
> for MS Windows developers because of the (impossible to understand I
> agree) limitation on path size.
>
> So the idea is to find a new logical rule to drastically shorten our
> paths and Sergiu proposed the following: remove duplicated information
> from our paths to maven modules.
>
> Here is an example:
>
>
xwiki-platform-core/xwiki-platform-rendering/xwiki-platform-rendering-transformations/xwiki-platform-rendering-transformation-macro
> (131 chars)
>
> would become
>
> core/rendering/transformations/macro (36 chars)
>
> So WDYT ?
>
> Here is my +1
Big +1 from me.
> I also find it nicer when navigating using cd and
tab in a unix shell anyway.
>
> Planning to do it in 5.1 if everyone agree.
--
Sergiu Dumitriu
http://purl.org/net/sergiu