[Mono-dev] Fork of certmgr - any ideas?

[Arthur Peka]

>The changes that are in your fork seem to be all stylistic changes,
refactoring variable names, changing whitespace, etc.

>It's not clear right now, what the improvements are, or should be.

Valid point, at the moment I haven't done very much (apart from fixing the
bug I mentioned, stylistic changes and minor changes like listing available
stores). I want to improve usability, e.g.
* Listing certificates from all the stores (except Untrusted) when called
with --list -c without specifying the store. Now it fails when no store
specified. Can be useful to get all trusted certs.
* When importing some well-known certificates (e.g. some Nuget-related),
certificate is claimed to be invalid. Needs investigation.
* Unit/integration tests
* Colouring output for readability?
* Other?

I went to this list to collect some input from people who are using
certmgr, do they have any ideas of improvements.

Arthur.

On Thu, Jan 22, 2015 at 1:56 PM, Edward Ned Harvey (mono) <
edward.harvey.mono at clevertrove.com> wrote:

> > From: mono-devel-list-bounces at lists.ximian.com [mailto:mono-devel-list-
> > bounces at lists.ximian.com] On Behalf Of Arthur Peka
> >
> > don't understand about what of kind of 'ethics' we can talk here.
>
> Etiquette.  Not ethics.
>
>
> > http://tirania.org/blog/archive/2010/Dec-31.html
>
> Arthur, how about this:
>
> Sometimes it may be true that it might be difficult to get changes pulled
> into mono source, but you haven't made a compelling case for certmgr to be
> separated out from mono source.  What exactly are the improvements you want
> to make, and why shouldn't they be part of mono source?  The changes that
> are in your fork seem to be all stylistic changes, refactoring variable
> names, changing whitespace, etc.
>
> It's not clear right now, what the improvements are, or should be.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20150122/2ff8e4d8/attachment-0001.html>