You need proper permissions to the Apache organization on GitHub, which I don't seem to have.
We can use the existing repository https://github.com/apache/log4j Is probably a good idea to have a README.md in that repository anyway, it is good practice on GitHub. On Mon, Apr 18, 2016 at 4:55 PM, Remko Popma <[email protected]> wrote: > Mikael, > > Looks like this needs at least a README and a release. Should we do this > when we release 2.6 then? Someone needs to prepare the README. > > Also, what kind of GitHub permissions would be required? > > Remko > > > On Mon, Apr 18, 2016 at 11:49 PM, Mikael Ståldal < > [email protected]> wrote: > >> Perhaps someone from PMC should register Log4j 2 here: >> http://docs.graylog.org/en/latest/pages/marketplace.html >> >> now when we have a GelfLayout. >> >> Currently you will only find a couple of obsolete third-party >> GELF-plugins for Log4j. >> >> I tried to do it myself, but I don't have the proper permissions on >> GitHub. >> >> -- >> [image: MagineTV] >> >> *Mikael Ståldal* >> Senior software developer >> >> *Magine TV* >> [email protected] >> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com >> >> Privileged and/or Confidential Information may be contained in this >> message. If you are not the addressee indicated in this message >> (or responsible for delivery of the message to such a person), you may >> not copy or deliver this message to anyone. In such case, >> you should destroy this message and kindly notify the sender by reply >> email. >> > > -- [image: MagineTV] *Mikael Ståldal* Senior software developer *Magine TV* [email protected] Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email.
