Many changes that could be made to development process would discourage at least one active contributor from continuing to contribute.
For example, I'm not a fan of Git, but it's easier to develop tools around it, it's easier to integrate patches, etc. There may be other VCSes, but this one has existing tools, would solve the difficulties in integrating patches,, would solve the problem of us not using actively developed, easy to use, responsive tools, etc. I'd be in favor of switching SVN into 'archive mode' and using Git for further development for one big reason: I still have an archive of .patch files which someone contributed to get Android support for gnustep-make and gnustep-base. And working on Opal backend, I always feared that I'll break something (and code review helps here). Aside from needing to have a big goal split into manageable pieces, which are then split into pieces someone can work on during a weekend, we're also not using best tools for the job. On Fri Dec 20 2013 at 12:49:04 PM, Graham Lee <[email protected]> wrote: > On 20 Dec 2013, at 12:34, David Chisnall <[email protected]> wrote: > > it definitely refutes the assertion that patches are not accepted > > > Sure. It’s the presentation that’s at fault. There’s an internal feeling > that GNUstep is doing stuff and welcomes external contribution, and an > external presentation of a stale bug database that isn’t linked to the > source code (and I wonder how many people find the source mirror on github > and think there hasn’t been a commit in over three months, too). > > Graham. >
_______________________________________________ Discuss-gnustep mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnustep
