Mail Archives: geda-user/2012/10/25/08:17:47
2 cents: What if there was a subset/separate wiki and git repository
which was wide open at least for a time until it gains momentum with
the purpose to catch scripts/patches and how to use them. A big fat
warning label could be posted before directing anyone to this
repository and wiki. Then if/when valuable content appears it can be
Incorporated in to the protected repository and wiki. I myself wrote a
tool awhile back which does a refdes renum with slots info
refdes_renum_slots and I have never been able to document it properly
anywhere except on this form.
If not anything it might be exciting just to see what happens to it if
people get excited and put stuff in it, or if it doesn't do anything or
if perhaps spammers find it. If it immediately molds well, it was an
interesting experiment.
~Joshua
On Thu 25 Oct 2012 06:21:06 AM EDT, Gareth Edwards wrote:
> Hi DJ, all,
>
> (I realise this thread is about gEDA/PCB but I'm going to hijack it to
> discuss something that's been on my mind for a while...)
>
> On 25 October 2012 02:50, DJ Delorie <dj AT delorie DOT com> wrote:
>> I've been pretty lenient with accepting new committers. It can't be
>> worse than what we had before (few/no committers).
>
> I think that's true for gEDA/PCB, but gEDA/gaf appears to be close to
> abandonware right now. Stable 1.8 was kicked around almost a year ago
> then silence. Of the current committers, only Edward and Krzysztof
> have been in any way active since February.
>
> 4 out of the 6 commits since February have been for the new print
> tool, not in the core of the code. Meanwhile, myself and others have
> been posting patches and pull requests to git repos to Launchpad for
> some months now [for example,:
>
> https://bugs.launchpad.net/geda/+bug/926456 from Kai-Martin
> https://bugs.launchpad.net/geda/+bug/934934 from Juergen Harms
> https://bugs.launchpad.net/geda/+bug/1004757 from Jim Mallatt
> A bunch of fixes from issues flagged by coverity at
> https://github.com/gareth8118/geda-gaf/tree/coverity-fixes
>
> ]
>
> I'm guessing that Peters B and C have other priorities right now,
> which is fair enough considering what they've put into the project,
> but we don't have any ability to fill the huge gap they have left
> behind - we have a chicken and egg problem where those with the talent
> may not be motivated to put the effort in to improve the code or even
> triage bugs and patches if they think there is no way to get the
> contributions and fixes into the code base.
>
> This is too good a toolkit to be left to rot.
>
> Gareth
>
- Raw text -