Community
Participate
Working Groups
Having a standalone example connector (that has no dependencies on web URLs or specific knowledge of a bug provider) would be a great way of learning how to write a new connector. This could just store bugs in a hashtable or other equally trivial implementation, but would show what extension points and such are necessary, as well as what abstract classes need to be subclassed to make the connector work. An existing connector (trac/bugzilla) might be suitable as a seed if cut down and replaced all trac/bugzilla specific code. However, it would need to be written to 'work' without persistence or connection to a real bug tracking system.
Did you look at the LocalRepositoryConnector ? There is also an ancient bug 170395 nobody volunteered to contribute to.
Hadn't seen that (I've not read any documentation pointing it out :-) The problem is that it doesn't have the full set of required features, like the ConnectorUi. Agree, the pde template would be a good way to deliver this.
Local repo does have connector UI
An example connector would be a *great* contribution. A cool standalone (i.e. not coupled to a particular server) driver could be the CSV file format (bug 193439). *** This bug has been marked as a duplicate of bug 170894 ***