[horde] Request to the community

[Simon B]

Hi Ralf,

thanks for the great and comprehensive answer.

The project is in good hands. And I hope you find something sooner rather
than later that doesn't involve Microslop, github, and Copilot.

Regards

Simon



On Fri, 3 Jul 2026, 08:32 Ralf Lang, <ralf.lang at gmail.com> wrote:

> Hi Simon,
>
> I share your concern about a lock-in.
> We want to keep our own data in our own hands, including our history of
> changes and bug reports.
>
> This is why our github actions pipelines are largely a thin wrapper around
> a tool chain you can run on your own desktop or in jenkins, circle ci or
> whatever.
> This is why we do not give up whups (bug tracker) but make it receive
> hooks when you do something on github and send out updates to github if you
> interact via whups (and don't even own a github account).
>
> Horde has migrated CI systems at least three times through it history. We
> changed our code versioning system from cvs to monolithic git, from
> monolithic git to separate components.
> We changed delivery from tarball to pear to composer.
>
> We frankly do not know if we will be hosting on github five years into the
> future.
> Give us some time to get the infra and tools into shape to support our
> traditional, sovereign approach.
>
> At the moment it just doesn't work for most users across multiple hours
> per day and we must accomodate the way a lot of casual contributors work.
> You might have noticed we are tooling up to support mastodon API
> (preferred) and modernizing our X API (it's still a big place with all its
> problems).
>
> Regards
>
> Ralf
>
>
> On Fri, Jul 3, 2026 at 8:13 AM Simon B <simon.buongiorno at gmail.com> wrote:
>
>> There must surely be a better option than lock-in with a big US Tech Corp
>> precisely at a time the Rest of the world seeks to reduce reliance and
>> contrary to the ENTIRE raison d'être of Horde....
>>
>>
>> Think that through again please.   And look for a federated alternative..
>>
>> Cheers
>>
>> Simon B
>>
>>
>>
>> On Fri, 3 Jul 2026, 07:40 Torben Dannhauer, <torben at dannhauer.info>
>> wrote:
>>
>> > Dear Horde users,
>> >
>> >
>> >
>> > we are glad to have progressed so far with you in the last months and
>> make
>> > H6 possible.
>> >
>> > with growing community activity and participation, the mailing list will
>> > get more and more confusing to keep track which discussion is still open
>> > and what is solved already.
>> >
>> > my ask and proposal is, to migrate bug reports and discussions to github
>> > actions. This eases the tracking, discussion and relation to PRs,
>> commits
>> > etc.
>> >
>> > if you are not used to github: No issue, that’s very easy:
>> >
>> >
>> >
>> > *       go to github.com
>> > *       setup an account ( its free)
>> > *       log in
>> > *       go to github.com/horde/<your package) (e.g.
>> > https://github.com/horde/ActiveSync)
>> > *       click on “issues” in the top menu
>> > *       click on the green button “New issue”  on the right side
>> > *       write your text
>> > *       assign it to either  <mailto:ralf.lang at ralf-lang.de> @'Ralf
>> Lang'
>> > or me to avoid we miss it
>> > *       save
>> >
>> >
>> >
>> > Done 😊
>> >
>> >
>> >
>> > Many thanks!
>> >
>> >
>> >
>> > Torben
>> >
>> > --
>> > Horde mailing list
>> > Frequently Asked Questions: http://horde.org/faq/
>> > To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>> >
>> --
>> Horde mailing list
>> Frequently Asked Questions: http://horde.org/faq/
>> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>>
>