Hi!
On 2/1/18 7:39 AM, Andrew Otto wrote:
> This is the first I’ve heard of it! So, we don’t have a plan to change it,
> but I suppose we should if RevisionInsertComplete is deprecated. I haven’t
> looked at RevisionRecordInserted yet so I can’t answer questions about
> schema changes, but I
This is the first I’ve heard of it! So, we don’t have a plan to change it,
but I suppose we should if RevisionInsertComplete is deprecated. I haven’t
looked at RevisionRecordInserted yet so I can’t answer questions about
schema changes, but I doubt it would change anything.
Just created
Hi
For anyone having the same problem: I was added as maintainer to a project
already in the mediawiki vendor namespace. After that I was able to add my new
project. Thanks for the help!
Cheers,
Tobias
--
If this email is rather brief, it is not meant to be impolite but to respect
your time.
[0] is for what it says - developing libraries based on parts of MW code.
It has nothing to do with extension development. I'd advice you to use your
own vendor and mind that we don't officially support extension installation
via Composer at all.
1 февр. 2018 г. 7:08 пользователь "Tobias
Hey
I have released a mediawiki extension and would like to make it available
via composer. Obviously, I need the help of someone with access to the
mediawiki vendor. I dug through the documentation on [0], especially the
Packagist guidelines and tried to reach one of the listed people,
