I would think a simple vote would be a good idea. I think Florian has summarised things very well. In particular, the earlier comments about the 'fundamentalist' approach that appears in places (deciding to use tool x because it was written in Python) to be a very odd constraint to impose.

I'm not sure if I've mentioned it previously, but I really like the ZeroMQ team's C4 model (http://rfc.zeromq.org/spec:22), which forms a set of guidelines for how ZeroMQ and related projects can operate.

Andrew

On 03/10/15 11:52, Dirk Baechle wrote:
Hi Florian,

your mail sums it up pretty well. Thanks for taking the time to skim through those old messages. We definitely are interested in making progress wherever that's possible. But with a large project like SCons and major decisions to be made, "bikeshedding" is always around...and can bring things to a halt quickly. Further, we did have a tracker and most of the latest development was done by direct pull requests...which might have let this problem appear as one of lower priority. I agree that it's time for a clear decision...from my angle the two candidates are Roundup and Jira. Both seem to be able to do the job on the technical level. So we can't choose "wrong" and just have to pick. Leaves the question how to do that. Would any of the devs be opposed to a simple poll, where everybody supports his favourite tool?

Independent of how the decision is made, what will happen later is that-just like in the git vs hg battle-voices speak up from time to time, claiming that a switch to the other alternative is what the project needs right now. That's just how open-source works these days I guess. :)

Best regards,

Dirk

P.S.: I wrote all of the above under the assumption that the technical migration from Tigris to Jira is possible and preserves the full history, including the creation dates of issues and messages /comments. I'm stressing this point so much, because even in Roundup it's only possible with a work-around. ;)
--
Sent from my Android with K-9 Mail.


_______________________________________________
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

_______________________________________________
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Reply via email to