It seems clear to me that at least some distribution of development is required. But I think you've got the cart before the horse. Even if resynchronizing with E2 is practical, I would imagine that it would require enough work that I'd be quite surprised if vroom alone could manage to finish such a task even in the next couple of years (since he is busy and can't do this type of work full time). We need distribution of development effort long before we'll get synchronization between E2 and PM.
I'd much rather go forward with the original plan for several people to be added to the developers group such that they have read-only access to the full, live source code of PM so that they can help vroom develop. This was even requested by an E2 developer who wanted to do some merging. So I think it is the clear first step towards being able to take more steps as directed by vroom.
-
tye
(but my friends call me "Tye")
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
