Richard,
On Mon, 2 Nov 2020 at 10:47, Christian Heinrich
wrote:
> Maybe we should define the problems that new end users experience
> during onboarding instead and address those first?
On Tue, 3 Nov 2020 at 02:52, Dick Franks wrote:
> Better documentation would help enormously.
I would
On Nov 2, 2020, at 2:16 PM, Michael Richardson wrote:
> Angus Robertson - Magenta Systems Ltd wrote:
> > OpenSSL is really aimed at two markets, developers using the API and
> > admins using the applications, it would be easier for both groups if
> > the help was separate.
> I think that the
Angus Robertson - Magenta Systems Ltd wrote:
> OpenSSL is really aimed at two markets, developers using the API and
> admins using the applications, it would be easier for both groups if
> the help was separate.
I think that the "admins using the application" has never been a
--- Begin Message ---
Angus Robertson - Magenta Systems Ltd wrote:
> Also, there is an assumption OpenSSL is only used by other C developers,
> by the use of public macros that are not usable in any other language.
> BoringSSL replaced macros with exports and OpenSSL should consider
> My claim is that much of the "applications" should be removed
> from the core system, and should be re-implemented in a cleaner
> way using the APIs.
> I.e. into a separate git repo with it's own release schedule.
>
> They should serve as exemplars for using the APIs, which they are
> often
: Re: Project direction
Date: Mon, 2 Nov 2020 16:51 + (GMT Standard Time)
From: Angus Robertson - Magenta Systems Ltd
Reply-To: an...@magsys.co.uk
To: openssl-us...@openssl.org
> The idea being that supporting existing users means not changing
> the existing API, whereas catering to new
Benjamin Kaduk wrote:
>> On Mon, 2 Nov 2020 at 10:47, Christian Heinrich <
>>
>>
>> > Maybe we should define the problems that new end users experience
>> > during onboarding instead and address those first?
>> >
>>
>> Better documentation would help enormously.
On Mon, Nov 02, 2020 at 03:51:58PM +, Dick Franks wrote:
> On Mon, 2 Nov 2020 at 10:47, Christian Heinrich <
>
>
> > Maybe we should define the problems that new end users experience
> > during onboarding instead and address those first?
> >
>
> Better documentation would help enormously.
On Mon, 2 Nov 2020 at 10:47, Christian Heinrich <
christian.heinr...@cmlh.id.au> wrote:
>
> On Fri, 30 Oct 2020 at 10:45, Dr Paul Dale wrote:
> > The question was should we design our APIs to ease the pain existing
> > users of OpenSSL or should we be trying to attract new users.
> > The idea
Dr Dale,
On Fri, 30 Oct 2020 at 10:45, Dr Paul Dale wrote:
> The question was should we design our APIs to ease the pain existing
> users of OpenSSL or should we be trying to attract new users.
> The idea being that supporting existing users means not changing the
> existing API, whereas
This came in privately from Michael Richardson and is forwarded with permission:
> If you don't grow the user base, you decline.
> As long as the old APIs do not go away too quickly, or the new APIs are
> obvious refactors, then it won't be such a problem.
>
> In general, I think that there are
At the OTC call on Tuesday Tim raise a point about the future direction of the
project. I was tasked with bringing this to the OMC for consideration.
The question was should we design our APIs to ease the pain existing users of
OpenSSL or should we be trying to attract new users.
The idea
12 matches
Mail list logo
