On 7/23/19 3:37 PM, Ondřej Kuzník wrote: > I've prepared a plan what the project wants to achieve as part of the > 2.5 stream apart from core OpenLDAP development that I intend to send to > -technical for wider discussion and as a call for participation. > > It has been suggested to me that people might want to comment/propose > changes to it so attaching a draft here. Please let me know what you > think or if you agree in broad terms it is fit to be circulated more > widely. Thanks for driving this. Text looks good to me. Eventually there will be lengthy discussions about various tools (now reaching out for the popcorn bag). So you might want to tighten it some more by suggesting all the gitlab stuff (Wiki, CI pipelines) as possible tools. E.g. AFAIK the Wiki in gitlab is just a git repo of markdown files.

Regarding the test suite: Would it be feasible to use Python for the job? If yes, you can directly use the unittest module from its standard lib which gives you much better control, error handling and reporting.

And I already enjoy using gitlab's CI runner stuff for this (but using static slapd.conf generated): https://gitlab.com/ae-dir/python-aedir/blob/master/.gitlab-ci.yml

--On Tuesday, July 23, 2019 4:37 PM +0200 Ondřej Kuzník <ondra(a)mistotebe.net&gt; wrote: >Hi, >I've prepared a plan what the project wants to achieve as part of the >2.5 stream apart from core OpenLDAP development that I intend to send to >-technical for wider discussion and as a call for participation. > >It has been suggested to me that people might want to comment/propose >changes to it so attaching a draft here. Please let me know what you >think or if you agree in broad terms it is fit to be circulated more >widely. Hi Ondrej, Thanks for writing this up! In the section about the bug tracker, I would note that the plan is to use Bugzilla for the tracker (as opposed to gitlab issues) via Gitlab's built in bugzilla integration feature. For contributions, I'd like to see something like <https://about.gitlab.com/2017/11/01/gitlab-switches-to-dco-license/> implemented, so it's simply a part of the contribution process rather than us having to constantly bug people about it. I agree with Michael that the FAQ should probably just be migrated to using the Gitlab wiki, since we'll already have that available. On CI/CD, hopefully we can make use of some of the freely available resources, such as <https://build.opensuse.org/>;. What we're particularly missing is Windows as a platform for CI/CD, which would have helped us catch the additional bits necessary for ITS#7585 for example.

--On Tuesday, July 23, 2019 8:57 PM +0300 Alexander Bokovoy <abokovoy(a)redhat.com&gt; wrote: > Azure Pipelines give free 10 concurrent runners for open source projects > and can connect with GitLab instances for CI/CD. We use it in FreeIPA > in our GitHub pull request review process. The runners are fairly easy to > configure; they run Ubuntu 16.04 but include Docker so it is possible to > do a lot more. FreeIPA runs tests on containerized Fedora 30, for example. > > And Azure Pipelines also have Windows and macOS runners: > https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?vie > w=azure-devops > > If you are interested, I can share my experience on setting it up. I > haven't tried Windows images as I didn't need them but the rest is quite > well working. Hi Alexander, That would be great, thanks for the offer. :) I currently build on Windows using gcc under MSYS2, which doesn't seem to be an offering from MS (no surprise there).  But I do see a project maintaining VC bits for OpenLDAP that perhaps we could leverage (<https://github.com/winlibs/openldap>).